Winter Sale Limited Time 60% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: av54zq84

Exact2Pass Menu

Question # 4

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.

Change the sql_trigger_value parameter of user_facts toselect the current date plus one hour, so it triggers an hour after orders_rollup.

B.

Change the orders_rollup view reference to ${orders_rollup.DERVIED_TABLE_NAME}

C.

Change the sql_trigger_value parameter for both persistent derived tables to a datagroup_trigger parameter, and set them to use the same datagroup.

D.

Change the orders_rollup view reference to the literal table name from the database’s scratch schema.

Full Access
Question # 5

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.

The sum measure used is defined correctly.

B.

A unique primary key is defined in each view.

C.

Symmetric_aggregates: no is not present in the Explore definition.

D.

No concatenated primary keys are used.

Full Access
Question # 6

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)

A.

Option A

B.

Option B

C.

Option C

D.

Option D

Full Access
Question # 7

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.

required_access_grants: [grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

B.

required_access_grants: [grant_a] in the revenue view, required_access_grants: [grant_a, grant_b] in the total_revenue field

C.

required_access_grants: [grant_b] in the financial_data Explore, required_access_grants: [grant_a] in the total_revenue field

D.

required_access_grants: [grant_a, grant_b] in the revenue view, required_access_grants: [grant_a] in the total_revenue field

Full Access