Building Gold-layer views and tables for BI and analytics
Gold layer objects expose curated, business-ready data to BI and analytics consumers in Unity Catalog. The main object types are managed tables, views, materialized views, and streaming tables, each differing in refresh behavior, storage, and cost tradeoffs. Choosing the right type depends on freshness requirements, query patterns, and compute cost tolerance.
Must-know
- A view is a virtual object with no stored data; it re-executes its defining query on every access, so it is always fresh but adds compute cost per query.
- A table (managed or external) stores materialized data physically and must be explicitly refreshed via write/merge/overwrite operations or a pipeline; queries against it are fast since no recomputation happens at read time.
- A materialized view precomputes and stores query results, refreshing incrementally where possible, and is created and managed through Lakeflow Declarative Pipelines (formerly Delta Live Tables), reducing query latency for repeated BI dashboard queries.
- A streaming table is designed for incremental, append-only or CDC-style ingestion using Structured Streaming semantics within a pipeline, continuously or incrementally processing new data rather than reprocessing the full dataset.
- Materialized views and streaming tables are pipeline-managed objects and cannot be directly modified with arbitrary DML like a normal managed table; they are updated by re-running or triggering the owning pipeline.
- Gold tables typically apply business logic, aggregations, and joins on top of Silver layer data, and access is governed through Unity Catalog permissions (GRANT SELECT) so BI tools connect only to these curated objects.
An analytics engineer wants a Gold table that ingests append-only Change Data Feed records from a Silver Delta table continuously, applying incremental processing rather than reprocessing all history on each run. Which object should they create?
What you have tried across Databricks DEA's objectives, not a readiness score.
Databricks Intelligence Platform
Data Ingestion and Loading
- Batch, streaming, and incremental loading patterns, and where the data comes from
- Loading files from cloud storage into governed tables with COPY INTO
- Landing data with Auto Loader, and handling schema enforcement and evolution
- Setting up Lakeflow Connect to ingest from enterprise sources reliably
- Pulling data through JDBC, ODBC, or REST clients and scheduling the job
- Choosing the right ingestion method for a given volume, frequency, and governance need
- Bringing semi-structured and unstructured data into governed Delta tables
Data Transformation and Modeling
- Cleaning bronze data into silver tables with PySpark and SQL
- Joining and combining DataFrames with the different join and union types
- Reshaping columns, rows, and arrays in a table
- Deduplicating and aggregating DataFrames
- Tuning Spark's core parameters and measuring what changed
- Building Gold-layer views and tables for BI and analytics
- Validating Silver and Gold datasets for quality
Working with Lakeflow Jobs
Implementing CI/CD
- Branching, committing, and opening pull requests from inside the Databricks workspace
- Promoting one codebase across dev, test, and prod with bundle variables and overrides
- Packaging and deploying jobs and pipelines with Automation Bundles
- Validating and managing bundle deployments from the Databricks CLI
Troubleshooting, Monitoring, and Optimization
- Spotting performance trends in a job's run history
- Reading job status, task graphs, and failure rates to monitor pipeline health
- Diagnosing skew, shuffle, and spill from Spark UI stage metrics
- What Liquid Clustering and predictive optimization actually do
- Diagnosing cluster startup failures, library conflicts, and out-of-memory errors
Governance and Security
Coverage checked against the published exam guide on Jul 27, 2026.
These are independent practice questions, written against this certification's published exam guide. They are not the certification vendor's own questions, and not the real exam.