Looker Business Analyst study materials
Looker Business Analyst study resources

Looker Business Analyst study plan

Looker Business Analyst · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Business Intelligence and Looker Fundamentals & Data Modeling and LookML

  • Map the Looker object hierarchy (connection, project, model, Explore, view, field) and write a one-page diagram showing how a query travels from Explore to SQL.

  • Distinguish dimension types (string, number, time, yesno, tier, duration) and pick the correct type for ten sample business fields.

  • Build a minimal LookML project with one view file and one model file, then validate it with the project health tools.

  • Explain to a non-technical stakeholder what an Explore is versus a dashboard, using your own working instance.

Your checkpoint

A working single-view LookML project plus a one-page hierarchy diagram with the ten field-type decisions annotated.

Week 2

Data Modeling and LookML

  • Define primary keys, foreign keys, and join relationships in LookML and justify each join's relationship type.

  • Create dimensions, dimension groups for time fields, and measures with the correct aggregate type for additive and non-additive metrics.

  • Use symmetric aggregates to prevent fan-out and demonstrate the difference in results with a one-to-many join.

  • Configure a derived table or native derived table and explain when each is preferable to a persistent table.

Your checkpoint

A two-view Explore with a validated one-to-many join, a time dimension group, at least four measures, and a written note proving symmetric aggregates changed the totals correctly.

Week 3

Data Modeling and LookML & Business Intelligence and Looker Fundamentals

  • Refactor repeated filter and dimension logic into a refinement or extends pattern and confirm downstream Explores still validate.

  • Apply access filters and field-level access to restrict a sensitive column and verify the restriction as a test user.

  • Implement parameters and templated filters in a derived table and document the resulting SQL.

  • Trace a slow Explore to its generated SQL and identify at least one modeling cause of the slowdown.

Your checkpoint

A refactored project using extends or refinements, a documented access-filter test showing allowed and denied results, and a short SQL performance write-up.

Week 4

Explore and Visualization Design & Data Modeling and LookML

  • Design an Explore with a curated field picker, sensible default filters, and required filters where full scans would be costly.

  • Build pivot and row-total configurations that answer a specific business question without post-processing.

  • Select the correct visualization type for five different question shapes and justify each choice in one sentence.

  • Configure drill fields and drill links so a user can move from a summary tile to row-level detail.

Your checkpoint

A published Explore with curated fields, required filters, two working visualizations, and a drill path that lands on row-level detail.

Week 5

Explore and Visualization Design

  • Create a dashboard with filters that cross-filter multiple tiles and confirm filter behavior on each tile.

  • Apply table calculations for percent-of-total and running totals and verify them against a hand calculation.

  • Write a custom measure or table calculation using a documented function and explain its evaluation order.

  • Tune a dashboard for performance by reducing tile count or query cost and record the before-and-after load behavior.

Your checkpoint

A dashboard with at least four tiles, cross-filtering, two table calculations verified by hand, and a before-and-after performance note.

Week 6

Analysis, Sharing, and Governance

  • Schedule a recurring delivery to a destination and confirm the recipient receives correctly formatted output.

  • Set up an alert with a threshold condition and describe what triggers it and what does not.

  • Compare sharing via schedules, alerts, and embedded or public access, and state the governance risk of each.

  • Apply content validation and fix or retire at least one broken content item.

Your checkpoint

A scheduled delivery and a working alert, plus a one-page comparison of sharing methods with governance risks and a content-validation cleanup log.

Week 7

Analysis, Sharing, and Governance & Business Intelligence and Looker Fundamentals

  • Audit a folder's content access using roles and permission sets and correct one over-permissioned group.

  • Use System Activity Explores to report on query history and identify the most expensive recurring queries.

  • Document a content-organization convention (folders, naming, boards) and apply it to your practice content.

  • Explain how Looker handles data access versus content access and where each is enforced.

Your checkpoint

A System Activity report of your top expensive queries, a corrected permission assignment, and a written naming and folder convention applied to your content.

Week 8

Business Intelligence and Looker Fundamentals & Data Modeling and LookML & Explore and Visualization Design & Analysis, Sharing, and Governance

  • Complete a timed full-length practice set and score each domain separately to find weak areas.

  • Rebuild from scratch the two weakest artifacts from earlier weeks without notes.

  • Review every missed question and write the underlying rule, not just the correct answer.

  • Confirm readiness by re-taking the weakest domain's practice questions and comparing scores.

Your checkpoint

A scored practice-set report by domain, a list of corrected rules for every miss, and a rebuilt artifact for each of your two weakest areas.

Milestones

Week 2: You can explain and demonstrate why a one-to-many join inflates a sum and how symmetric aggregates fix it, using your own project.

Week 4: Your Explore validates cleanly, has curated fields and required filters, and a stakeholder could answer a business question from it without help.

Week 6: You can articulate the governance tradeoffs of schedules, alerts, and public or embedded access, and you have retired at least one broken content item.

Week 8: Your per-domain practice scores show no domain below your target threshold, and you have rebuilt your two weakest artifacts without notes.