You create a table function to remove historic records, sum the current total weekly working hours for each employee, and update the personnel table with the results. The deployment of the table function fails.Which of the following could be a valid reason?

Your table function includes a DELETE statement.

You did not define at least one input parameter.

You did not define a valid table type.

Your table function includes a DELETE statement.

Your table function refers to a scalar function.

In a calculation view, why would you implement an SQL expression? Note: There are 3 correct answers to this question.

To generate a restricted column

To generate a calculated column

To generate a restricted column

To generate a calculated column

Why would you use an anonymous block when writing SQLScript?

To test your code without generating a logic container.

To check the results without applying user privileges.

To test your code without generating a logic container.

To hide the actual tables by using aliases in the code.

To execute a statement without creating entries in the database log.

In a calculation view, your table function node executes a table function that requires input parameters.How can you fill the input parameters of the table function? Note: There are 3 correct answers to this question.

Create and map an input parameter.

Reference the output of a procedure.

Create and map an input parameter.

Two calculation views, A and B, are defined as shown in the diagram. Three analytic privileges have been granted to you. When you preview calculation view A, what data do you see?

US for P1 and P2, and GE for P1 and P2

US for P1 and P2, and GE for P2

You are creating a procedure to be consumed in a DYNAMIC analytic privilege. What must you consider? Note: There are 2 correct answers to this question.

The procedure should have the value DEFINER for the security mode

The procedure should be defined as read-only

The procedure should have the value DEFINER for the security mode

The procedure should include an input parameter to specify the user ID

The procedure should return a table with the list of allowed values

The procedure should be defined as read-only

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?

You did not define masking in calculation view A.

The UNMASKED privilege has NOT been granted at the schema level.

You did not define masking in calculation view A.

You previewed the data with the technical user in the SAP HANA modeling tool.

The type of the Account Number column is VARCHAR.

How can you define a variable that presents its value help hierarchically? Note: There are 2 correct answers to this question.

Create a parent-child hierarchy and assign it to the variable. * Ensure the variable's reference column is the child attribute of the hierarchy.

Create a level hierarchy and assign it to the variable. * Ensure the variable's reference column is the leaf level of the hierarchy.

Create a level hierarchy and assign it to the variable. * Ensure the variable's reference column is the top level of the hierarchy.

Create a parent-child hierarchy and assign it to the variable. * Ensure the variable's reference column is the parent attribute of the hierarchy.

Create a parent-child hierarchy and assign it to the variable. * Ensure the variable's reference column is the child attribute of the hierarchy.

Create a level hierarchy and assign it to the variable. * Ensure the variable's reference column is the leaf level of the hierarchy.

What options do you have to handle orphan nodes in your hierarchy? Note: There are 2 correct answers to this question.

Assign them to an existing node at the root level.

Define them as additional root nodes.

Assign them to a parent determined by an expression.

Assign them to a leaf level node.

Assign them to an existing node at the root level.

Define them as additional root nodes.

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

To push down filters to the lowest level calculation views

To pass variable values to external value help views

To push down filters to the lowest level calculation views

To convert the data types of input parameters

To pass variable values to external value help views

To assign variables to one or more attributes

What can you do with shared hierarchies? Note: There are 2 correct answers to this question.

Provide reusable hierarchies for drilldown in a CUBE with star join

Enable SQL SELECT statements to access hierarchies

Provide reusable hierarchies for drilldown in a CUBE with star join

Access hierarchies created in external schemas

Provide reusable hierarchies for drilldown in a CUBE without star join

Enable SQL SELECT statements to access hierarchies

Why would you set the 'Ignore multiple outputs for filters' property in a calculation view?

To force filters to apply at the lowest node

To avoid duplicate rows in the output

To force filters to apply at the lowest node

To hide columns that are not required

You define a hierarchy in a calculation view. You want to expose the hierarchy to SQL. Which of the following conditions must be met? Note: There are 2 correct answers to this question.

The hierarchy must be a shared hierarchy.

The hierarchy must be exposed by a CUBE calculation view with star join.

The hierarchy must be defined as a local hierarchy.

The hierarchy must be a shared hierarchy.

The hierarchy must be a parent-child hierarchy.

The hierarchy must be exposed by a CUBE calculation view with star join.

In a calculation view, what is the purpose of a variable?

To filter an attribute at run-time based on a user input

To provide a dynamic value in a calculated column

To break up complex SQL into smaller steps

To pass values between procedures and calculation views

To filter an attribute at run-time based on a user input

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?

You already mapped the input parameters in another calculation view.

The names of the input parameters do not match.

You selected the wrong parameter mapping TYPE.

Your source calculation view is of type DIMENSION.

You already mapped the input parameters in another calculation view.

What is a restricted measure?

A measure that is filtered by one or more attribute values

A measure that can only be displayed by those with necessary privileges

A measure that is filtered by one or more attribute values

A measure that can be consumed by a CUBE and not a DIMENSION

A measure that cannot be referenced by a calculated column

Using the table in the diagram, you need to create a cube calculation view. What is the simplest approach to create the output from the screenshot?

Implement a union node and map each year as a separate column.

Create a filter expression that uses an OR operator.

Implement a union node and map each year as a separate column.

Create a restricted column for each year.

What are the key steps to implement currency conversion in a calculation view?

Assign semantic type. * Enable the measure for conversion. * Choose client, source and target currencies. * Choose conversion date and rate type.

Assign semantic type. * Choose client, source and target currencies. . * Choose conversion date and rate type. * Define an expression in a calculated column.

Enable the measure for conversion. * Choose client, source and target currencies. * Choose conversion date and rate type. * Assign the conversion rule to your calculation view.

Assign semantic type. * Enable the measure for conversion. * Choose client, source and target currencies. * Choose conversion date and rate type.

Enable the measure for conversion. * Choose client, source, and target currencies. * Choose conversion date and rate type. * Build the conversion rule.

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

To include columns that are NOT requested by a query but are essential for the correct result

To exclude columns that are NOT requested by a query to avoid incorrect results

To ensure that the aggregation behavior defined in the aggregation node for a measure CANNOT be overridden by a query

To include columns that are NOT requested by a query but are essential for the correct result

To retain the correct aggregation behavior in stacked views

What is generated when you build/deploy a CUBE calculation view design-time file? Note: There are 2 correct answers to this question.

Metadata to enable consumption by external tools

Cached results to improve read performance

What are the limitations of using a full outer join in a star join node? Note: There are 2 correct answers to this question.

It must appear in the last DIMENSION in the star join node.

It is restricted to one DIMENSION in a star join node.

It CANNOT be mixed in the same star join node with other join types.

Only one column can be included in the join condition.

It must appear in the last DIMENSION in the star join node.

It is restricted to one DIMENSION in a star join node.

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?

Include an aggregation node above the union node.

Define a restricted column in a union node.

Add an intersect node above the union node.

Include an aggregation node above the union node.

In the union node, map both source customer name columns to one target column.

Why would you choose to implement a referential join?

To ignore unnecessary data sources

To automate the setting of cardinality rules

To reuse the settings of an existing join

To develop a series of linked joins

To ignore unnecessary data sources

Why would you use the Transparent Filter property in a calculation view?

To allow filter push-down in stacked calculation views

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 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 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 allow data analysis at different levels of granularity with the same calculation view

To ensure that the join execution uses only the join columns requested in the query

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

Why do you create calculation views of data category DIMENSION with type TIME?

To provide additional time-related navigation possibilities

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 ensure specific columns are NOT exposed to the reporting tool

To remove a column that is also used as a Label column

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?

The join condition is not represented by matching values.

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 left outer join node between table A and table B

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

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.

Enable the Debug Query mode to identify the source columns used.

Observe which columns are mapped using the Performance Analysis mode.

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.

SAP C_HAMOD_2404 Practice Test 1 - Free Online Exam Prep & Questions

Question 1 / 40

Referring to the diagram, which privileges would a user require to view United States data when querying the CUBE calculation view?

A SELECT privilege and an Analytic Privilege (Country United States) on the CUBE calculation view

A SELECT privilege on the CUBE calculation view and an Analytic Privilege (Country United States) on the DIMENSION calculation view

SELECT privileges and Analytic Privileges (Country United States) on both views

A SELECT privilege and an Analytic Privilege (Country United States) on the DIMENSION calculation view

Comment (0)

SAP C_HAMOD_2404 Practice Test 1

Question

SAP C_HAMOD_2404 Practice Tests

Practice Tests