SAP C_HAMOD_2404 Practice Test - Questions Answers, Page 4
Question list
List of questions
Related questions
Why would you use the Transparent Filter property in a calculation view?
To prevent filtered columns from producing incorrect aggregation results.
To improve filter performance in join node
To allow filter push-down in stacked calculation views
To ignore a filter applied to a hidden column
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?
Combine the transaction tables using a star join node in a CUBE calculation view. * Use a join node to join the DIMENSIONS to the resulting fact table.
Combine the transaction tables using a join node in a CUBE calculation view. * Combine the DIMENSIONS using another join node. * Use a star join node to combine both resulting fact and dimension tables.
Combine the transaction tables using a join node in a CUBE calculation view. * Use a star join node to join the DIMENSIONS to the resulting fact table.
Combine the transaction tables using an aggregation node in a CUBE calculation view. * Use a star join node to join the DIMENSIONS to the resulting fact table.
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.
To force the calculation at the relevant level of granularity, even if this level is not the grouping level defined by the query
To allow data analysis at different levels of granularity with the same calculation view
To ensure that the aggregation always happens after the join execution
To ensure that the join execution uses only the join columns requested in the query
What is the default top view node for a calculation view of type CUBE?
PROJECTION
UNION
HIERARCHY
AGGREGATION
Why do you create calculation views of data category DIMENSION with type TIME?
To add a temporal condition to a join to find matching records from two tables based on a date
To provide additional time-related navigation possibilities
To store historical versions of attributes
To provide the time intervals required by time-dependent parent-child hierarchies
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.
To avoid exposing sensitive columns when defining calculated columns
To prevent passing columns in stacked calculation views
To ensure specific columns are NOT exposed to the reporting tool
To remove a column that is also used as a Label column
You want to join two tables in a calculation view. Why do you use a non-equi join?
Join columns have different data types.
The number of joined columns is different in each table.
The join condition is not represented by matching values.
Join columns need to be ignored when NOT requested by the query.
You have products that appear in table A and sometimes also in table B. What would you use to find products only appearing in table A?
A right outer join node between table A and table B
A left outer join node between table A and table B
An intersect node between table A and table B
A minus node between table A and table B
Which of the following data sources can you include in a graphical calculation view? Note: There are 2 correct answers to this question.
Table function
Procedure
Row table
Scalar function
You created a calculation view that combines two tables in a join node. To improve the runtime of your calculation view, you use a referential join to prune data sources.
How do you check if pruning occurs? Note: There are 2 correct answers to this question.
Check the SQL query generated by the Data Preview.
Use the SQL Analyzer to identify the tables used.
Enable the Debug Query mode to identify the source columns used.
Observe which columns are mapped using the Performance Analysis mode.
Question