Google LOOKML-DEVELOPER Online Practice Questions and Exam Preparation

Google LOOKML-DEVELOPER Online Questions & Answers

• Question 11:

  Users have built a popular dashboard and want to have change management built in for any edits made to the dashboard. The developer sets up version control for the model on which the dashboard is based. What should the developer build to meet the business requirement?

  A. A native derived table based on the dashboard.
  B. A dashboard LookML file included in the project.
  C. A link to the dashboard included in the project.
  D. An Explore LookML file based on the dashboard.
  B. A dashboard LookML file included in the project.

• Question 12:

  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. There is a missing join.

• Question 13:

  Users report that the main dashboard has been slow to show results.

  Which two options should the developer evaluate to improve dashboard performance? (Сhoose two.)

  A. Number of databases used by dashboard elements
  B. Number of queries used by the dashboard
  C. Ratio of visualizations to text tiles
  D. Format used to deliver these reports
  E. Amount of data rendered for each query
  B. Number of queries used by the dashboard
  C. Ratio of visualizations to text tiles

• Question 14:

  A developer needs to build a new dimension that offers an age-based cohort representation of users. Which LookML code should the developer use to meet the requirement?

  

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

• Question 15:

  A user reports the following SQL error when selecting the discounted sale price field:

  ERROR: column “order_items.sale_price”; must appear in the GROUP BY clause or be used in an aggregate function.

  The developer checks the field definition and finds it to be:

  measure: discounted_sale_price {

  type: number

  sql: ${sale_price} * 0.8 ;;

  }

  The developer also finds the LookML definition of the sale_price field to be:

  dimension: sale_price {

  type: number

  sql: ${TABLE}.sale_price ;;

  }

  What is the likely cause of the SQL error?

  A. The discounted_sale_price field should have a group_by: yes parameter.
  B. The sale_price field should be defined as a measure of type: number, not as a dimension.
  C. The underlying database table does not have a field called sale_price.
  D. The discounted_sale_price field should be defined as a dimension of type: number, not as a measure.
  B. The sale_price field should be defined as a measure of type: number, not as a dimension.

• Question 16:

  A LookML developer finishes some LookML work and commits changes in their personal development branch. The developer is asked to Pull and Merge Other Changes. What does this indicate?

  A. A change has been deployed to a shared branch.
  B. A change has been committed in another developer's personal branch.
  C. A change has been committed in another shared branch.
  D. A change has been deployed to production.
  B. A change has been committed in another developer's personal branch.

• Question 17:

  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?

  A. Set definition
  B. Join condition
  C. Fields parameter
  D. Hidden parameter
  B. Join condition

• Question 18:

  The code below shows a view order_items with its measures total_revenue and user_count

  

  Which code correctly represents a new measure that calculates average revenue per user?

  

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

• Question 19:

  A retail company wants to limit who can see the financial information in their reports to executives and store managers. The LookML Developer creates a user attribute called leadership with the value “000” for executives and “999” for store managers. The developer creates three access grant objects and one dimension:

  

  How should the developer ensure that only authorized users see the data in the Total Revenue dimension?

  A. required_access_grants: [can_view_financial_data]
  B. required_access_grants: [leadership]
  C. required_access_grants: [“000”,“999”]
  D. required_access_grants: [total_revenue]
  A. required_access_grants: [can_view_financial_data]

• Question 20:

  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 to select 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.
  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.