Business users report that they are unable to build useful queries because the list of fields in the Explore is too long to find what they need.

Which three LookML options should a developer use to curate the business user's experience? (Choose three.)

A. Add a description parameter to each field with context so that users can search key terms.

B. Create a separate project for each business unit containing only the fields that the unit needs.

C. Add a group_label parameter to relevant fields to organize them into logical categories.

D. Use the hidden parameter to remove irrelevant fields from the Explore.

E. Use a derived table to show only the relevant fields.

Only users with department attributes of Finance and Executive should be able to access the revenue view. Only users with the value of Executive 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

Business users report that an ephemeral derived table tile on the dashboard is slow.

Information about the dashboard includes:

The dashboard filter is linked to the user attributes.

This tile usually takes approximately 5 minutes to complete running.

Which solution should be used to improve the dashboard load time?

A. Use a conditional WHERE clause for Development Mode.

B. Build a user attribute filter into the Explore.

C. Use index distribution_key or sort_key for this derived table.

D. Persist the derived table.

A developer has a persistent derived table view called user_facts that contains aggregated data for each user. The developer needs to query the data from this table in another derived table view called user_region_facts.

Which strategy should the developer use to write the query for user_region_facts that will leverage the existing derived table?

A. Use ${user_facts.SQL_TABLE_NAME} to reference the user_facts derived table.

B. Copy the name of the database table in the scratch schema for the user_facts derived table.

C. Writhe the query form user_facts into a common table expression (WITH user_facts AS...).

D. Write a subquery in the FROM clause and alias with ${user_facts}.

A user reports an error message 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.

A LookML developer has a transactions view with several measures that each perform complex calculations involving multiple fields. The LookML developer creates an Explore based on the transactions view. The product team wants to perform further functions on these measures, such as SUM, AVG, MIN, MAX, and RANK. The team wants these further functions to be performed at different levels of detail: weekly, monthly, and yearly.

How can the LookML developer model these requirements and minimize the amount of code rewriting?

A. Add measures to the transactions view of type: number to apply the required functions.

B. Change the existing measures in the transactions view to dimensions, and add measures of the different required types.

C. Create a constant for each measure so it can be reused across other areas of the LookML project.

D. Create native derived tables using transactions as the explore_source.

After validating LookML code, a developer receives the following error message:

“Unknown or Inaccessible Field users.name”

What is causing this error?

A. There is a missing join.

B. The field is set to “hidden”.

C. The join relationship is incorrect.

D. The field uses incorrect SQL syntax.

A developer creates a derived table and wants to add persistence to it. Because the table is not used on a frequent basis, the developer wants the table to be cached for 12 hours, but only when a user has queried it.

Which persistence parameter should be added to the derived table's definition in order to satisfy this use case?

A. persist_with: “12 hours”

B. datagroup: 12_hours { max_cache_age: “12 hours” }

C. persist_for: “12 hours”

D. sql_trigger_value: SELECT FLOOR{UNIX_TIMESTAMP{} / {6*60*60}} ;;

A developer has the dimensions enrollment_month and graduation_month already defined in the view. Both were created as part of dimension_groups of type: time. The developer need to use these two dimensions in the sql_start and sql_end parameters of a dimension group of type: duration.

Which LookML should be used to calculate the number of month and years between enrollment month and graduation month?

A. Option A

B. Option B

C. Option C

D. Option D

A user reports that, when a date dimension is filtered to “before now” results are returned that consistently include tomorrow. Dimension fill has been ruled out as a cause of the issue.

Which LookML parameter should be used to resolve this issue?

A. Week_start_day

B. Convert_tz

C. Datatype

D. Fiscal_month_offset