Why would you enable Debug Query mode in a calculation view?

• A.To check which database engines are invoked
• B.To identify data sources that are not accessed by a query
• C.To set breakpoints and step through the execution
• D.To understand how tables are partitioned

Comment: *

Name: *

Email: *

Verification: *

What is the SQL keyword used to process input parameters defined in a calculation view?

• A.WHERE
• B.HINT
• C.SET
• D.PLACEHOLDER

Comment: *

Name: *

Email: *

Verification: *

You are deploying a new calculation view, A, that uses calculation view B, as shown in the diagram.

When you preview calculation view A, the account number is not masked.What could be the reason?

• A.You did not define masking in calculation view A.
• B.You previewed the data with the technical user in SAP Business Application Studio.
• C.The UNMASKED privilege has NOT been granted at the schema level.
• D.The type of the Account_Number column is VARCHAR.

Comment: *

Name: *

Email: *

Verification: *

Which project structure object corresponds to a unique HDI container?

• A.src folder
• B.space
• C.database module
• D.project

Comment: *

Name: *

Email: *

Verification: *

You implement a referential join between Table A and Table B, but when you query the calculation view, Table B is not pruned.

What could be the problem?Note: There are 2 correct answers to this question.

• A.Join cardinality is set :1.
• B.The Keep flag is activated for the Customer column.
• C.Integrity constraint is set to RIGHT.
• D.The Country column is requested.

Comment: *

Name: *

Email: *

Verification: *