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

• A.It is restricted to one DIMENSION in a star join node.
• B.Only one column can be included in the join condition.
• C.It must appear in the last DIMENSION in the star join node.
• D.It CANNOT be mixed in the same star join node with other join types.

Comment: *

Name: *

Email: *

Verification: *

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?

• A.Your source calculation view is of type DIMENSION.
• B.You selected the wrong parameter mapping TYPE.
• C.You already mapped the input parameters in another calculation view.
• D.The names of the input parameters do not match.

Comment: *

Name: *

Email: *

Verification: *

A calculation view includes a rank node that uses the source data and settings shown in the graphic.
Your query requests all columns of the rank node. How many rows are in the output of your query?

• A.9
• B.2
• C.5
• D.6

Comment: *

Name: *

Email: *

Verification: *

Which tool generates and executes the SQL for a specific node of your calculation view?

• A.Debug Query mode
• B.Explain plan
• C.Database explorer
• D.SQL analyzer

Comment: *

Name: *

Email: *

Verification: *

You have imported calculation views from SAP HANA on-premise to SAP HANA Cloud. Why should you switch calculated column expression language from column engine to SQL?

• A.Incorrect aggregations may be generated
• B.To define limits for query unfolding
• C.To benefit from additional SQL optimizations
• D.Column engine language is not supported.

Comment: *

Name: *

Email: *

Verification: *