How do you ensure that each customer name appears only once in the results?

You combine two customer master data tables with a union node in a calculation view. Both master data tables include the same customer name.

How do you ensure that each customer name appears only once in the results?
A . Define a restricted column in a union node.
B. In the union node, map both source customer name columns to one target column.
C. Include an aggregation node above the union node.
D. Add an intersect node above the union node.

Answer: C

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

Why might you use the Keep Flag property in an aggregation node?
A . To ensure that the aggregation behavior defined in the aggregation node for a measure CANNOT be overridden by a query
B. To retain the correct aggregation behavior in stacked views
C. To include columns that are NOT requested by a query but are essential for the correct result
D. To exclude columns that are NOT requested by a query to avoid incorrect results

Answer: C

What might be the reason for this?

You have configured static cache for your calculation view and run a query against it, but the cache results are not being used.

What might be the reason for this?
A . You did not define any columns in the cache setting.
B. The cache data retention period has expired.
C. The query requests only a subset of the cached results.
D. You did not define a filter in the cache setting.

Answer: A

Why do you use parameter mapping in a calculation view? Note: There are 2 correct answers to this question.

Why do you use parameter mapping in a calculation view? Note: There are 2 correct answers to this question.
A . To convert the data types of input parameters
B. To assign variables to one or more attributes
C. To push down filters to the lowest level calculation views
D. To pass variable values to external value help views

Answer: C,D