LookML-Developer Exam Dumps : Looker LookML Developer Exam

Only users with department attributes of Finance and Executive should be able to access the revenue view. Only users with the value ofExecutive for the department user attribute should be able to view the total_revenue field.

Given the code snippet below:

How should the required access grants be structured to set up this system of access?

A user reports the following SQL error when selecting the discounted sale price field:

ERROR: column “order_items.sale_price”; must appear in the GROUP BY clause or be used in an aggregate function.

The developer checks the field definition and finds it to be:

measure: discounted_sale_price {

type: number

sql: ${sale_price} * 0.8 ;;

}

The developer also finds the LookML definition of the sale_price field to be:

dimension: sale_price {

type: number

sql: ${TABLE}.sale_price ;;

}

What isthe likely cause of the SQL error?

A developer needs to add an Explore built off of the orders view, which surfaces only completed orders. An orders Explore exists that contains all order information. Fields from the orders view arealso referenced in other existing views such as ${orders.fieldname}.

How should developer define a new Explore for completed orders and keep all field references working correctly?

A)

B)

C)

D)