Google LOOKML-DEVELOPER Online Practice Questions and Exam Preparation

Google LOOKML-DEVELOPER Online Questions & Answers

• Question 31:

  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. Option A

• Question 32:

  A LookML Developer is working with denormalized tables and needs to create a measure adding up the Order Shipping column in the table below:

  

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  A. Option A

• Question 33:

  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.
  C. Symmetric_aggregates: no is not present in the Explore definition.

• Question 34:

  A developer commits changes after adding LookML for a new measure. Upon pulling from production, the developer notices the following lines in the LookML:

  

  A. Remove “andlt;> branch ‘master’”
  B. Remove “andlt;
  C. Remove everything between “andlt;> branch ‘master’”
  D. Remove everything between “andlt;> branch ‘master’”
  D. Remove everything between “andlt;> branch ‘master’”

• Question 35:

  A user is seeing an error in the Explore that indicates the primary key defined for a one-million-row table is not unique.

  How can the developer use SQL Runner to troubleshoot quickly?

  A. Create a query that selects all the fields from the table, and sort by primary key.
  B. Create a query that selects the primary key from the base view, and look for duplicates.
  C. Create a query that counts how many occurrences of the primary key value are in the base view, and sort by count.
  D. Create a query that concatenates two columns to create a compound primary key.
  D. Create a query that concatenates two columns to create a compound primary key.

• Question 36:

  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.
  D. Create native derived tables using transactions as the explore_source.

• Question 37:

  The developer is creating an Explore that includes the product users, and orders views that will meet the following guidelines.

  Joins between the orders and users views should not incur high performance costs.

  Users of this Explore will primarily be looking at data from the orders view.

  Users of this Explore should only be able to see orders from the retailer “Fashion.ly”.

  The only field the users need from the products view is product.name.

  Which LookML should the developer use?

  

  A. Option A
  B. Option B
  C. Option C
  D. Option D
  D. Option D

• Question 38:

  A LookML developer has created a model with many Explores in it. Business users are having a difficult time locating the Explore they want in the long list displayed. Which two actions can the LookML developer take to improve the user interface? (Choose two.)

  A. Apply the hidden parameter with a value of yes to Explores that only exist to power specific Looks, dashboards, or suggestion menus.
  B. Modify the business users’ roles so they do not have this model in their model set.
  C. Combine the Explores into just a few Explores that each join to many views.
  D. Apply the group_label parameter to organize the Explores under different headings.
  E. Apply the fields parameter so that each Explore has fewer fields in it.
  B. Modify the business users’ roles so they do not have this model in their model set.
  C. Combine the Explores into just a few Explores that each join to many views.

• Question 39:

  A LookML developer creates an Explore that joins two views. The base view has information about users’ interactions with the support team. The joined view contains data about the users. The support team using this Explore feels overwhelmed by the amount of data this Explore shows them and decides to just look at open tickets.

  What should the developer add to the Explore in the model to achieve these requirements?

  A. A filtered measure
  B. The hidden parameter
  C. The sql_always_where parameter
  D. A relationship definition
  D. A relationship definition

• Question 40:

  A developer is defining the users table within a view file in Looker. The users table will be available as an individual Explore and it will also be joined into other Explores, such as the products Explore. The developer needs to limit the fields visible in the products Explore without affecting the visibility of the fields in the users Explore.

  How should the developer meet this requirement?

  A. Use the fields parameter at the join level for the products Explore to specify which fields should be included and leave the users Explore as is.
  B. Create duplicate dimensions and measures, one for the users Explore and one for the products Explore, and use the hidden parameter to modify the visibility of the fields.
  C. Create two view files for the users table. One view file will have all possible fields for the users Explore, and the other will have only the fields required for the products Explore.
  D. Use the hidden parameter in the users view file for the fields that should not come over to the products Explore and leave the users Explore as is.
  A. Use the fields parameter at the join level for the products Explore to specify which fields should be included and leave the users Explore as is.