A LookML developer has written the following persistent derived table. It references orders_rollup, another persistent derived table that also rebuilds with the same SQL trigger value.

Which change is needed to guarantee that user_facts will always rebuild with the latest data from orders_rollup?

A user reports an errormessage on an Explore: “Non-unique value/primary key (or sql_distinct_key), value overflow or collision when computing sum”.

What should the LookML developer check for in the joined views of the Explore?

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)

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?