C_HAMOD_2404 SAP Certified Associate - Data Engineer - SAP HANA Questions and Answers

Synonym

Remote source

SQL view

Authorization

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

Break up large statements by using variables.

Use dynamic SQL.

Control the flow logic using IF-THEN-ELSE conditions.

Choose declarative language instead of imperative language.

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.

To set breakpoints and step through the execution

To identify data sources that are not accessed by a query

To understand how tables are partitioned

To check which database engines are invoked

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.

Projection

Aggregate

Case

Pivot

The metadata of remote tables is cached on the target system

Hidden virtual tables are automatically created on the target system

The source and target system must be SAP HANA

A database name is used in an SQL statement to identify the remote object

Table function

Procedure

Row table

Scalar function

Dependencies between calculation views

Descriptions of all objects defined in a calculation view

All settings defined in a calculation view

Documentation to support the calculation view

SELECT on the source object

CREATE VIRTUAL TABLE on the remote source

CREATE ANY on the target schema

ALTER on the remote source

Enable the linked database feature

Create a remote subscription

Create a target table

Define a flowgraph

Create a virtual table

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

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

To display dependencies in stacked scenarios

To automate the build process

To manage versions of source files

To enable collaboration between developers

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

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

US for P1

US for P1 and GE for P1

US for P1 and P2, and GE for P2

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

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

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

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.

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

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

The consuming application always references the virtual table

The replica table always stores real-time data

You can choose your own replica table name

You can toggle queries routing between remote table data and replica table data

You do not need to create the physical replica table manually