You want to map an input parameter of calculation view A to an input parameter of calculation view B using the parameter mapping feature in the calculation view editor. However, the input parameters of calculation view B are not proposed as source parameters.What might be the reason for this?

• A.Your source calculation view is of type DIMENSION.
• B.The names of the input parameters do not match.
• C.You selected the wrong parameter mapping TYPE.
• D.You already mapped the input parameters in another calculation view.

Comment: *

Name: *

Email: *

Verification: *

In a calculation view, why would you choose the DEPRECATED setting?Note: There are 2 correct answers to this question.

• A.To indicate that it should not be used as a data source to other calculation views
• B.To lock the calculation view from further modifications
• C.To warn developers that the calculation view is no longer supported
• D.To ensure it is not exposed to reporting tools for consumption

Comment: *

Name: *

Email: *

Verification: *

You are building a new calculation view A that uses calculation view B, as shown in the diagram. When you preview the calculation view A, the Account Number is not masked.

What could be the reason?

• A.You previewed the data with the technical user in SAP Web IDE for SAP HANA.
• B.Analytic privilege _SYS_BI_CP_ALL has been assigned.
• C.You did not define masking in calculation view A.
• D.The UNMASKED privilege for calculation view A has been granted.

Comment: *

Name: *

Email: *

Verification: *

Why do you use the Hidden Columns checkbox in the semantics node of your calculation view?Note: There are 2 correct answers to this question.

• A.To avoid exposing sensitive columns when defining calculated columns
• B.To remove a column that is also used as a Label column
• C.To ensure specific columns are NOT exposed to the reporting tool
• D.To prevent passing columns in stacked calculation views

Comment: *

Name: *

Email: *

Verification: *

Which of the following techniques can you use to improve the performance of calculation views?Note: There are 2 correct answers to this question.

• A.Implement union pruning.
• B.Limit the number of stacked calculation views.
• C.Avoid aggregating data early in the data flow.
• D.Partition large tables.

Comment: *

Name: *

Email: *

Verification: *