Question 1

Why would you enable Debug Query mode in a calculation view?

Options :

A : To identify data sources that are not accessed by a query

B : To check which database engines are invoked

C : To set breakpoints and step through the execution

D : To understand how tables are partitioned

Answer: A

Question 2

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

Options :

A : To pass values between procedures and calculation views

B : To provide a dynamic value in a calculated column

C : To break up complex SQL into smaller steps

D : To filter an attribute at runtime based on a user input

Answer: D

Question 3

At which levels of a project structure can you execute a deploy operation?Note: There are 2 correct answers to this question.

Options :

A : Individual source file

B : Entire workspace

C : Sub-folder of a database module

D : Individual container

Answer: B,C

Question 4

Your calculation view consumes one data source, which includes the following columns: SALES_ORDER_ID, PRODUCT_ID, QUANTITY and PRICE.In the output, you want to see summarized data by PRODUCT_ID and a calculated column, PRODUCT_TOTAL, with the formula QUANTITY * PRICE.In which type of node do you define the calculation to display the correct result?

Options :

A : Projection

B : Join

C : Union

D : Aggregation

Answer: C

Question 5

Why would you create SQL in calculation views?

Options :

A : To implement custom logic

B : To provide an alternative to graphical modeling

C : To fine-tune performance

D : To enable write capabilities

Answer: A