Free LookML Developer Exam Braindumps

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 are also 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?

Answer(s): C


A LookML developer is creating a new view with 20 dimensions in Development Mode using the Create View from Table functionality. Now users want the developer to add only four dimensions from this new view to an existing Explore.

What can the developer add to the Explore to limit the number of fields from the view that are accessible to the user in the Explore?

  1. Set definition
  2. Join condition
  3. Fields parameter
  4. Hidden parameter

Answer(s): B


A developer wants to create a new Explore based on the order_items view. The developer creates an Explore in the ecommerce model file with the following definition:

explore: order_items {}

After saving and validations, the developer receives this LookML validator error:

Inaccessible view “inventory_items”, “inventory_items” is not accessible in explore” “order_items”. Check for typos and missing joins in explore “order_items”.

What caused this error to appear?

  1. A field in the order_items view references a field in the inventory_items view.
  2. A field in the inventory_items view references a field in the order_items view.
  3. There is an Explore named inventory_items which references the order_items view.
  4. There is another Explore named order_items which references the inventory_items view.

Answer(s): A

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?

  1. The sum measure used is defined correctly.
  2. A unique primary key is defined in each view.
  3. Symmetric_aggregates: no is not present in the Explore definition.
  4. No concatenated primary keys are used.

Answer(s): C

A developer needs to implement three persistent derived tables (PDTs) as described below.
The PDTs need to be refreshed after the daily ETL pipeline adds incremental loads to the underlying tables.
Each PDT is built off of one underlying table in the database (one PDT per table).
The underlying tables for each PDT are updated one after the other, and a new row is added to an ETL log table each time a table is updated.
Due to the unpredictable nature of the ETL pipeline, each PDT does not refresh at the same time from day to day.
Each PDT takes over an hour to build, and to save on compute costs each PDT should only be refreshed once per day.

How can the developer set up the PDTs according to these requirements?

  1. Create one datagroup tied to all three PDTs that runs when the total row count across all three tables changes.
  2. Create one datagroup tied to all three PDTs that parameterizes the view name for each PDT in the SQL trigger condition.
  3. Create three separate datagroups tied to three PDTs that run when each corresponding table’s row count changes.
  4. Create three separate datagroups tied to three PDTs that run when a new row is added to the ETL log table.

Answer(s): D