The Looker Certified Explorer exam covers five domain areas. Knowing which areas exist is not enough — the exam weights some domains more heavily than others, and the concepts within each domain have a specific depth that end-user experience alone does not cover. Here is what each domain actually tests.
What Are the Official Looker Certified Explorer Exam Domains?
| Domain | Core Topics | Common Weak Areas for Candidates |
|---|
| 1. Exploring Data |
Running Explore queries, applying filters, pivoting data, using table calculations, downloading results |
Table calculation timing (client-side vs SQL), pivot behavior with nulls |
| 2. LookML and Data Modeling |
View files, model files, dimensions vs measures, derived tables, explore joins, field parameters |
Model file vs view file responsibilities, PDT triggers, derived table SQL syntax |
| 3. Dashboards and Visualizations |
Tile types, cross-filtering, dashboard filters, scheduling, sharing, user attributes for filtering |
User attributes vs LookML fields, cross-filter scope, schedule vs alert differences |
| 4. Administration and Access Control |
Permission sets, roles, model access, access filters, folder permissions, row-level security |
When to use access_filter vs access_grant, folder vs model-level permissions |
| 5. Looker Platform and Integrations |
Dev mode vs production, Git workflow, Looker vs Looker Studio, BigQuery connection, API overview |
Looker Studio confusion, Git deployment sequence, service account authentication |
Domain 1: Exploring Data
This is the domain most candidates feel comfortable with before studying — running queries in Looker's Explore interface is the daily activity of most Looker users. The exam goes deeper on two concepts: table calculations and merge results. Table calculations run in the browser after data is returned from the warehouse, which means they cannot be used in LookML filters and they only operate on the rows already in the result set. Merge results allow combining data from multiple Explores when LookML joins are not possible — but the primary query controls which shared dimension is used to join the results.
Domain 2: LookML and Data Modeling
This is consistently where exam candidates score lowest if they have only used Looker as end users. The exam expects you to know: what goes in a view file versus a model file, what happens when you change a field's type from dimension to measure, what a derived table is and when a PDT is preferable to a standard derived table, what always_filter does in a model, and how join relationships affect what users can query in an Explore. You do not need to write production-grade LookML, but you do need to read a short LookML snippet and understand what it does.
Domain 3: Dashboards and Visualizations
Dashboards in this domain means Looker dashboards — not Looker Studio dashboards. Key concepts include the difference between dashboard filters and tile-level filters, what cross-filtering does and its limitations, how to schedule a dashboard delivery versus setting a data alert, and how user attributes work at the dashboard level (personalizing default filter values without building separate dashboards per user segment).
Domain 4: Administration and Access Control
The Looker permission model has three layers: model-level access (which Explores a user can see), row-level security (which rows they can query within an Explore), and folder-level access (which saved content they can view). The exam tests when to apply each layer and what happens when multiple permission mechanisms interact. The access_filter parameter in LookML is the row-level security mechanism; access_grant restricts which Explores a user can see based on a LookML field value. These two are commonly confused.
Domain 5: Looker Platform and Integrations
The platform domain covers two concepts candidates underestimate: the dev mode and Git workflow, and the distinction between Looker and Looker Studio. For the Git workflow, the exam tests the correct sequence for deploying a LookML change (make change in dev mode → commit → push to Git remote → merge to production → deploy in Looker). For the Looker vs Looker Studio question — this appears in some form on most exam sittings. Looker Studio is a free product with a different interface, no LookML, and different data connectivity. If you have only used Looker Studio and not Looker, features you associate with "Google's BI product" may not exist in Looker.
The domain-by-domain study guide maps every exam concept to specific study resources. For domain-specific practice questions, the Looker Certified Explorer practice quiz covers all five domains with scenario-based questions and answer explanations.
Prepare Faster With the Right Resources
The Looker Certified Explorer exam tests more than button-clicking — it requires a working understanding of LookML structure, Explore behavior, dimension and measure logic, and how Looker connects to your data warehouse. The Looker Cert Prep PDF Study Guide covers every exam domain in plain language: LookML syntax walkthroughs, Explore and filter mechanics, visualization rules, a domain-by-domain study checklist, and 50 practice questions with answer explanations. Use code LOOKERSTUDY50 for 50% off.
If you want to practice interactively, SimpuTech's Looker AI tutor can walk through LookML scenarios, quiz you on Explore and dashboard concepts, and help you identify gaps before exam day. Available at SimpuTech.com.