Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

A company's analytics team wants to enable business users to create their own reports and dashboards from a governed set of BigQuery data, without writing SQL. At the same time, the data engineering team must maintain centralized control over how key metrics (like 'revenue' or 'active users') are defined. Which Google Cloud product architecture best meets both requirements?

⚠ Common exam trap

Candidates often think Looker Studio (formerly Data Studio) is sufficient for self-service reporting, but they overlook the critical requirement for a governed semantic layer (LookML) to enforce centralized metric definitions, which Looker Studio alone does not provide.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Looker with LookML semantic layer: data engineers centrally govern metric definitions in LookML, business users create self-service reports through Looker's interface using those governed definitions — no SQL required

Looker with LookML provides a semantic layer where data engineers centrally define governed metric definitions (e.g., 'revenue' as SUM(price * quantity) with specific filters). Business users can then create self-service reports and dashboards via Looker's drag-and-drop interface without writing SQL, ensuring consistency and control over key metrics.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Looker Studio connected directly to BigQuery, allowing each business user to create their own metric definitions
Why it's wrong here
Connecting Looker Studio directly to BigQuery removes any common definition layer. Each business user creates their own calculated fields, filters, and dimensions, so two reports can compute 'revenue' differently depending on how they handle refunds, taxes, or customer segments. Looker Studio does provide governance features like data source certification or field descriptions, but it does not enforce a single, reusable metric definition hierarchy like LookML does; inconsistent reporting is the inevitable result.
✓
Looker with LookML semantic layer: data engineers centrally govern metric definitions in LookML, business users create self-service reports through Looker's interface using those governed definitions — no SQL required
Why this is correct
Looker's LookML semantic layer is precisely designed for this dual requirement. Engineers write LookML once; it becomes the source of truth for metric definitions. Business users explore and report using a visual interface that always queries through LookML — guaranteed consistency, no SQL needed.
✗
Sharing BigQuery query templates with business users and training them to modify them for their reports
Why it's wrong here
Providing users with BigQuery SQL templates and training them to adapt the queries requires SQL literacy and still permits uncontrolled edits. Because each user saves a personal copy of the query, the logic forks: one person may change the date filter, another may alter a join or exclude offline revenue, and no tracking mechanism knows which version is 'official.' Updating a business rule means re-communicating and re-editing many copies, rather than changing one LookML definition that auto-updates every report.
✗
Building a custom web application that wraps BigQuery APIs and presents data to business users
Why it's wrong here
Building a custom web application on top of BigQuery APIs would let you centralize data access, but it essentially replaces a BI tool with a bespoke analytics portal. Every metric, filter, and drill-down path becomes hardcoded in application code, so changing a definition requires a development cycle—merge request, deployment, testing—while Looker allows non-engineers to modify business logic in a protected, versioned environment. It also lacks a self-service model that lets business users explore on their own without bespoke frontend features.

Go deeper

Cloud Digital Leader Practice Question: Google Cloud products, services, and solutions

Why each option matters

Option-by-option breakdown

Related to this question