Skip to content

Databricks Data Analyst Associate - Fact Sheet

Exam Overview

Exam Name: Databricks Certified Data Analyst Associate Exam Code: None published (no separate code) Duration: 90 minutes Questions: 45 scored multiple-choice questions, plus up to 10 unscored items Passing Score: Not published; set statistically and may change Cost: $200 USD plus applicable taxes (exam page and guide, read 2026-11-07) Delivery: Online proctored or test center; no test aids Languages: English Valid For: 2 years; recertify by passing the current exam Retakes: Allowed 14 days after an attempt; each retake costs the full fee Prerequisites: None; related training highly recommended; 6+ months of hands-on Databricks analysis recommended

Registration: through the exam delivery platform at webassessor.com/databricks (per the exam page). All SQL follows ANSI standards and Python is not required. The guide's update table lists "Exam Published October 19, 2026" and "Exam Guide Updated October 8, 2026". Check the guide two weeks before your exam date.

πŸ“– Official exam page - format, fee, weights, registration πŸ“– Exam guide PDF (August 2026) - every objective and ten sample questions πŸ“– Databricks Free Edition - free workspace for practice (linked from the guide) πŸ“– Databricks documentation - the authoritative reference

Sections and Weights

# Section Weight
1 Understanding of the Databricks Data Intelligence Platform 11%
2 Managing Data 8%
3 Importing Data 5%
4 Executing queries using Databricks SQL and SQL Warehouses 20%
5 Analyzing Queries 15%
6 Working with Dashboards and Visualizations 16%
7 Developing, Sharing, and Maintaining AI/BI Genie Agents (Genie Spaces) 12%
8 Data Modeling with Databricks SQL 5%
9 Securing Data 8%

Target Audience

  • Business and data analysts who query and visualize data on Databricks
  • SQL developers moving into the Databricks Data Intelligence Platform
  • People who build dashboards and Genie agents for business users

Section 1: Platform (11%)

πŸ“– AI/BI overview - dashboards, Genie, Unity Catalog semantics πŸ“– Unity Catalog - securable objects, three-level namespace πŸ“– Marketplace - listings and consumers

Key Facts: - Delta Lake = open table format with a transaction log; Unity Catalog = governance, lineage, access control - Names are catalog.schema.object; tables are managed or external - Lineage is on the table's Lineage tab, down to columns; external lineage via external metadata - Metric views define measures once and query them by any dimension

Section 2: Managing Data (8%)

πŸ“– Tags - governed tags πŸ“– Lineage - Lineage tab

Key Facts: - Governed tags have enforced values and controlled assignment; regular tags need ownership or APPLY TAG - Tags on catalogs, schemas and tables are inherited downward, not by columns - Clean with COALESCE, IS NOT NULL, TRIM; equality with NULL never matches

Section 3: Importing Data (5%)

πŸ“– Ingest with SQL and Spark APIs - layers of ingestion πŸ“– Upload files - UI upload

Key Facts: - UI upload to a volume needs WRITE VOLUME, USE SCHEMA, USE CATALOG; 5 GB limit; Create table gives a managed table - Auto Loader or streaming tables for continuous files; Lakeflow Connect for SaaS and databases; Delta Sharing for shared data; Marketplace for third-party listings - Federation queries external databases in place, read-only

Section 4: Executing Queries (20%)

πŸ“– SQL warehouses - serverless recommended πŸ“– Materialized views - syntax and refresh πŸ“– JOIN syntax - join types πŸ“– Table history - time travel and retention

Key Facts: - Streaming table: continuous append-only; materialized view: stored, refreshed, for BI; view: computed on read - Joins: INNER (default), LEFT, RIGHT, FULL, CROSS, LEFT SEMI, LEFT ANTI; UNION removes duplicates, UNION ALL keeps them - approx_count_distinct: HyperLogLog++, default accuracy within 5% - CREATE OR REPLACE TABLE keeps history and privileges - History 30 days; deleted-file retention 7 days; VACUUM makes older versions unreadable

Section 5: Analyzing Queries (15%)

πŸ“– Query history - filters and profile πŸ“– Query caching - three caches πŸ“– Photon - engine πŸ“– Liquid clustering - CLUSTER BY, AUTO

Key Facts: - Photon: native vectorized C++ engine; default engine for all SQL warehouses; no UDF or stateful streaming support - Result cache entries last 24 hours; UI cache up to 7 days; invalidated when tables change - Predictive optimization runs OPTIMIZE, VACUUM, ANALYZE on managed tables only - CLUSTER BY AUTO needs predictive optimization and managed tables; up to four keys otherwise

Section 6: Dashboards and Visualizations (16%)

πŸ“– AI/BI dashboards - build, share, embed πŸ“– Dashboard parameters - :keyword syntax πŸ“– SQL alerts - states πŸ“– Create an alert - conditions and destinations

Key Facts: - Parameters: :keyword; date ranges use .min and .max; filters outperform parameters on large data - Publish with shared or individual data permissions; embed via iframe; account-level sharing; email and Slack subscriptions - Alert states: OK, TRIGGERED, ERROR; schedule supports Quartz cron

Section 7: Genie Agents (12%)

πŸ“– Genie - overview πŸ“– Set up a Genie Agent - data, warehouse, instructions πŸ“– Benchmarks - monitoring and accuracy

Key Facts: - Up to 50 tables, views or metric views per agent; pro or serverless warehouse; CAN USE on the warehouse for the author - Permissions: CAN MANAGE, CAN EDIT, CAN RUN, CAN VIEW; viewers also need SELECT on the data - Feedback does not change behaviour by itself; edit instructions and example queries; benchmarks up to 500 questions

Section 8: Data Modeling (5%)

πŸ“– Medallion architecture - layers

Key Facts: - Star: fact table plus denormalized dimensions; snowflake: normalized dimensions; data vault: hubs, links, satellites - Gold is modeled with a dimensional model

Section 9: Securing Data (8%)

πŸ“– Manage privileges - GRANT, ownership

Key Facts: - Read needs USE CATALOG, USE SCHEMA, SELECT; grant to groups - Owner has all privileges including granting; MANAGE delegates privilege management - Protect PII with tags, column masks, row filters, lineage

Exam Tips

  1. Executing queries, dashboards and analyzing queries are 51%. Be fluent in SQL and the dashboard workflow.
  2. Learn the object choice: view, materialized view, streaming table.
  3. Read queries for defects: GROUP BY, HAVING, join type, NULL logic.
  4. Know alert versus dashboard versus job.
  5. Time: about 2 minutes per question.

Quick Reference

-- Syntax per docs; not run.
CREATE OR REPLACE MATERIALIZED VIEW main.gold.daily AS SELECT date(ts) d, SUM(x) s FROM main.silver.t GROUP BY date(ts);
SELECT * FROM main.silver.t VERSION AS OF 12;
ALTER TABLE main.silver.t CLUSTER BY (customer_id);
GRANT USE CATALOG ON CATALOG main TO `analysts`;