Looker for visualization in GCP - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

How does Looker handle data refresh for visualizations?

Looker connects to your data warehouse to create visualizations. When you open a dashboard, how does Looker ensure the data is up to date?

A Looker stores a local copy of the data and updates it once a day automatically.

B Looker queries the data warehouse live each time you open or refresh a dashboard to get the latest data.

C Looker only updates data when you manually export and re-import datasets.

D Looker caches data permanently and never refreshes it unless you rebuild the entire dashboard.

💡 Hint

Think about how Looker connects to your data source and how it keeps data fresh for users.

Looker runs live queries against your data warehouse when you open or refresh dashboards, ensuring you see the most current data without storing copies locally.

❓ Architecture

intermediate

Which Looker component defines how data is modeled for visualization?

Looker uses a special layer to describe your data structure and relationships before creating visualizations. What is this layer called?

A Data extracts

B SQL views in the data warehouse

C Looker dashboards

D LookML model files

💡 Hint

This layer uses a language designed by Looker to define data relationships and metrics.

LookML is Looker's modeling language that defines dimensions, measures, and relationships to shape data for analysis and visualization.

❓ security

advanced

How does Looker enforce data access control for different users?

You want to ensure users only see data they are allowed to view in Looker dashboards. Which method does Looker use to enforce this?

A Looker relies on the data warehouse to block unauthorized queries without any configuration.

B Looker exports data to separate files per user to control access.

C Looker applies row-level security filters based on user attributes defined in LookML and user roles.

D Looker disables dashboards for users without permission but does not filter data inside dashboards.

💡 Hint

Think about how Looker uses user roles and attributes to limit data visibility.

Looker uses row-level security by applying filters in LookML that depend on user roles and attributes, ensuring users only see permitted data.

✅ Best Practice

advanced

What is a recommended practice to optimize Looker dashboard performance?

You notice some Looker dashboards load slowly. Which practice helps improve dashboard load times?

A Use persistent derived tables (PDTs) to precompute complex queries and speed up dashboards.

B Add more visualizations with complex calculations directly in dashboards to reduce modeling effort.

C Disable caching so dashboards always query live data for accuracy.

D Use only raw SQL queries in dashboards without LookML models.

💡 Hint

Think about precomputing data to avoid slow live queries.

Persistent derived tables (PDTs) store precomputed results in the warehouse, reducing query time and improving dashboard performance.

🧠 Conceptual

expert

What happens if a Looker user tries to access a dashboard with a missing or invalid LookML model?

Consider a scenario where the LookML model defining a dashboard's data is deleted or corrupted. What will the user experience when opening that dashboard?

A Looker will show an error message indicating the model is missing or invalid, and the dashboard will not load.

B Looker will automatically rebuild the model from the data warehouse schema and display the dashboard.

C Looker will display the last cached version of the dashboard without errors.

D Looker will silently skip the missing model and show an empty dashboard.

💡 Hint

Think about how Looker depends on LookML models to define data structure.

If the LookML model is missing or invalid, Looker cannot generate queries for the dashboard and will show an error instead of loading data.

Practice

1. What is the main purpose of Looker in data analysis?

easy

A. To write complex SQL queries manually

B. To create visual reports from raw data without coding

C. To store large amounts of raw data

D. To replace databases with spreadsheets

Solution

1. Step 1: Understand Looker's role

   Looker is designed to turn raw data into visual reports easily.

2. Step 2: Compare options

   Only To create visual reports from raw data without coding describes Looker's main function correctly; others describe unrelated tasks.

3. Final Answer:

   To create visual reports from raw data without coding -> Option B

4. Quick Check:

   Looker = Visual reports without coding [OK]

Hint: Looker = easy visuals from data, no coding needed [OK]

Common Mistakes:

• Thinking Looker stores data like a database
• Confusing Looker with manual SQL writing
• Assuming Looker replaces spreadsheets

2. Which syntax correctly defines a measure in LookML?

easy

A. measure total_sales { sum: sales }

B. measure total_sales = sum(${TABLE}.sales)

C. measure: total_sales { type: sum; sql: ${TABLE}.sales ;; }

D. measure: total_sales = sum(sales)

Solution

1. Step 1: Recall LookML measure syntax

   Measures use the format: measure: name { type: ...; sql: ... ;; }

2. Step 2: Check each option

   measure: total_sales { type: sum; sql: ${TABLE}.sales ;; } matches correct LookML syntax with colons and braces; others do not.

3. Final Answer:

   measure: total_sales { type: sum; sql: ${TABLE}.sales ;; } -> Option C

4. Quick Check:

   LookML measure syntax uses colons and braces [OK]

Hint: LookML uses colons and braces for measures [OK]

Common Mistakes:

• Using equal signs instead of colons
• Omitting braces {} around measure definition
• Incorrect SQL syntax inside measure

3. Given this LookML snippet, what will the measure average_price calculate?

measure: average_price {
  type: average
  sql: ${TABLE}.price ;; }

medium

A. Sum of all prices

B. Count of price entries

C. Maximum price value

D. Average of the price column

Solution

1. Step 1: Identify measure type

   The measure type is 'average', which calculates the mean value.

2. Step 2: Understand SQL reference

   The SQL references the price column, so it averages all prices.

3. Final Answer:

   Average of the price column -> Option D

4. Quick Check:

   Measure type 'average' = mean value [OK]

Hint: Measure type 'average' means mean value [OK]

Common Mistakes:

• Confusing average with sum or count
• Ignoring the measure type keyword
• Assuming it returns max value

4. You wrote this LookML measure but get an error:

measure: total_revenue {
  type: sum
  sql: ${revenue} ;; }

What is the likely cause?

medium

A. Missing ${TABLE} prefix before revenue

B. Incorrect measure type 'sum'

C. Extra semicolon after sql statement

D. Measure name cannot have underscores

Solution

1. Step 1: Check SQL reference format

   LookML requires ${TABLE}.column to reference table columns properly.

2. Step 2: Identify missing prefix

   The sql references ${revenue} without ${TABLE}., causing error.

3. Final Answer:

   Missing ${TABLE} prefix before revenue -> Option A

4. Quick Check:

   Column refs need ${TABLE}. prefix [OK]

Hint: Always prefix columns with ${TABLE}. in LookML SQL [OK]

Common Mistakes:

• Omitting ${TABLE}. before column names
• Thinking measure type 'sum' is invalid
• Assuming underscores are not allowed in names

5. You want to create a dashboard showing total sales and average order value per region. Which LookML approach is best?

hard

A. Define measures for total sales and average order value, then create an explore with region dimension

B. Write raw SQL queries for each metric and paste results manually into dashboard

C. Create separate dashboards for sales and orders without linking regions

D. Use only dimensions without measures to keep dashboard simple

Solution

1. Step 1: Identify needed metrics and grouping

   You need total sales and average order value as measures, grouped by region dimension.

2. Step 2: Use LookML best practice

   Defining measures and an explore with region dimension allows dynamic, reusable dashboards.

3. Step 3: Evaluate other options

   The other options do not provide integrated, maintainable visualization.

4. Final Answer:

   Define measures for total sales and average order value, then create an explore with region dimension -> Option A

5. Quick Check:

   Measures + dimension + explore = best dashboard [OK]

Hint: Use measures + dimension + explore for dashboards [OK]

Common Mistakes:

• Manually copying SQL results instead of using LookML
• Separating dashboards without common grouping
• Ignoring measures and using only dimensions