Why might you use the Keep Flag property in an aggregation node?

• A.To retain the correct aggregation behavior in stacked views
• B.To exclude columns that are NOT requested by a query to avoid incorrect results
• C.To include columns that are NOT requested by a query but are essential for the correct result
• D.To ensure that the aggregation behavior defined in the aggregation node for a measure CANNOT be overridden by a query

Comment: *

Name: *

Email: *

Verification: *

You want to create a star schema using a calculation view. The measures are based on columns from two transaction tables. DIMENSION calculation views provide the attributes.What is the correct approach?

• A.Combine the transaction tables using a star join node in a calculation view of type CUBE with star join./Use a join node to join the DIMENSIONS to the fact table.
• B.Combine the transaction tables using an aggregation node in a calculation view of type CUBE with star join./Use a star join node to join the DIMENSIONS to the fact table.
• C.Combine the transaction tables using a join node in a calculation view of type CUBE with star join.Use a star join node to join the DIMENSIONS to the fact table.
• D.Combine the transaction tables using a star join node in a calculation view of type CUBE with star join.Use the same star join node to connect the DIMENSIONS to the fact table.

Comment: *

Name: *

Email: *

Verification: *

What are some of the typical tasks performed by the SAP HANA Cloud modeler role? Note: There are 2 correct answers to this question.

• A.Configure data tiering
• B.Create graph workspaces
• C.Develop calculation views
• D.Develop SAP Fiori apps

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

Comment: *

Name: *

Email: *

Verification: *

You combine two tables in a join node using multiple columns in each table.Why do you enable the dynamic join option? Note: There are 2 correct answers to this question.

• A.To force the calculation at the relevant level of granularity, even if this level is not the grouping level defined by the query
• B.To ensure that the aggregation always happens after the join execution
• C.To allow data analysis at different levels of granularity with the same calculation view
• D.To ensure that the join execution only uses the join columns requested in the query

Comment: *

Name: *

Email: *

Verification: *