Who should take this exam?

Data explorers with a suggested minimum of two months of experience using Looker daily to create and curate content, as well as prior experience with data visualization and building reports.

Recommended Looker knowledge:
  • Using visualizations to represent data
  • Scheduling and sharing Looks and dashboards
  • Table calculations
  • Looker expressions
  • Custom and advanced filters
  • Impacts of pivoting
  • Best practices around designing dashboards
  • Fundamentals of caching
Recommended tools:
  • Reporting tools (e.g., Excel, Google Studio, etc.)

Exam Details:

  • Registration fee: $250 ($200 introductory pricing for 2019)
  • Number of questions: 60 multiple choice or multiple response questions*
  • Exam duration: 100 minutes
  • Score needed to pass: 750 (scale of 100-1000)
  • References: no hard-copy or online reference materials are allowed during the exam
  • Prerequisite: none required (course attendance highly recommended. For more details on courses, please see the recommended training and documentation section).

* There will be additional unscored questions included on each Looker exam. These questions gather exam data for future use. These questions will not impact your score, and additional time is factored in to account for this content.

Recommended training and documentation

Looker training
Documentation

What does the Looker Business Analyst Certification exam cover?

1.0 Analyze — 38%
  1. Use Looker Explores to query data and create actionable metrics in a given scenario. For example:
    • Utilize requirements and create queries using fields (e.g., dimensions, measures, filters, pivots).
    • Determine additional metrics needed and construct custom metrics using table calculations.
    • Determine how to utilize filters (e.g., standard filters, matches advanced filters, and custom filters).
    • Determine which fields to use merge results for joining across different Explores and data sources.
  2. Use Looker to validate data accuracy in a given scenario. For example:
    • Investigate data results to determine accuracy (e.g., using SQL, drilling, A/B testing, comparisons).
    • Investigate discrepancies by viewing row-level data using Explores (e.g., review individual dimension values that make up the result of a measure).
  3. Apply procedural concepts to identify error sources. For example:
    • Utilize Looker's features to determine the cause of the error (e.g., read error message to get context).
    • Interpret error message to identify the source (e.g., caused by the database, query, LookML code, permissions, visualizations).
2.0 Build — 46%
  1. Build dashboards to meet business requirements. For example:
    • Construct dashboards to meet requirements (e.g., using dashboard filters, merged results).
    • Apply procedural concepts to design impactful dashboards (e.g., storytelling, tile organization, use of text tiles, amount of data per dashboard).
  2. Deliver reports for data consumers. For example:
    • Determine appropriate report delivery methods (e.g., file format, destination, delivery cadence, recipients, scheduling, sending, downloading, test delivery).
    • Determine appropriate download configurations (e.g., no option for unlimited downloads, table calculations, pivots, lack of permissions, database limitations).
  3. Use visualization types to meet analysis requirements in a given scenario. For example:
    • Select appropriate visualizations to illustrate data results (e.g., bar, line, scatter, column, pie).
    • Determine which visualization settings to use (e.g., conditional formatting, subtotals, double axis, value label format using spreadsheet functions, grouping).
3.0 Curate — 16%
  1. Apply procedural concepts to curate content for intuitive navigation. For example:
    • Determine appropriate setups for folders and boards (e.g., structures, subfolders, hierarchy).
    • Apply naming conventions to identify folders, boards, or other content for users (e.g., clear titles, description fields, naming folders, content, and conventions).
  2. Apply procedural concepts to control content access for security. For example:
    • Utilize appropriate Explores based on audience to prevent data leak (e.g., restricting sensitive data to specific users).
    • Assign folders and boards permissions to organize content based on user groups.