C_HCMOD_05 SAP Certified Application Associate - SAP HANA Cloud Modeling Questions and Answers

You previewed the data with the technical user in SAP Business Application Studio.

You did not define masking in calculation view A.

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

The type of the Account_Number column is VARCHAR.

The Country column is requested.

Join cardinality is set :1.

The Keep flag is activated for the Customer column.

Integrity constraint is set to RIGHT.

When a delta merge is triggered

When the table is created

When partitions are regenerated

When a backup is started

Question

Read performance decreases.

New records are not read.

Memory is not optimized.

Aggregates are not adjusted.

Table function

Procedure

Scalar function

Row table

To benefit from additional SQL optimizations

Incorrect aggregations may be generated

Column engine language is not supported.

To define limits for query unfolding

SAP Analytics Cloud

Data lake

SAP HANA database

SAP Enterprise Architecture Designer

Deploy the folder that contained the deleted design-time file.

Execute a DROP statement in an SQL Console connected to the HDI container.

Deploy the project that contained the deleted design-time file.

Execute the refactor function for the calculation view.

The deployment is successful but the data preview returns an error message.

The deployment fails and the table is not dropped.

The deployment fails and the table is dropped.

The deployment is successful and the data preview returns expected data.

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

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 cannot be referenced by a calculated column.

To pass values between procedures and calculation views

To provide a dynamic value in a calculated column

To break up complex SQL into smaller steps

To filter an attribute at runtime based on a user input

To include columns that are NOT requested by a query

To avoid columns being unnecessarily used in an aggregation

To apply filters that are hidden from the end user

To allow filter push-down in stacked calculation views

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.

To improve response time when multiple users access the same table

To improve query performance when accessing large column tables

To improve data replication performance on large row tables

To overcome the 2 billion record limit

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

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

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

A table function that returns a list of allowed values.

A scalar function that returns a list of the allowed values for each attribute.

A procedure that returns the data access condition as an SQL expression.

An organization hierarchy that provides role-based access to data.

.hdiconfig

.mtar

.yaml

.namespace

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

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/Choose client, source, and target currencies/Choose conversion date and rate type/Define an expression in a calculated column

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

Data architect

Modeler

Kubernetes expert

ABAP developer

Specify the join cardinality

Limit the number of joined columns

Use an inner join

Define join direction in a full outer join

The namespace used within the calculation view to reference the table is different from the actual namespace in the identifier of this table.

The imported calculation view and its data source have different namespaces.

An .hdinamespace file is defined in the SRC folder that specifies a different namespace property than the one in the identifier of the calculation view.

The .hdinamespace specifies "sub-folder":"append", so calculation views can only be created in subfolders.

Higher data compression rates

Improved write performance on frequent updates

Additional indexes are used

Parallel access is improved

Higher performance for query operations

To specify an external schema in which calculation views will get their data

To specify which HDI plug-ins are available

To specify in which space the container should be deployed

To specify the namespace rules applicable to the name of database objects