Understanding of Databricks Data Intelligence Platform: Databricks Data Analyst Associate Practice Questions

A solutions architect is designing a new data platform on Databricks. She has three distinct requirements: (1) ingest streaming events from Apache Kafka and declaratively apply multi-hop transformations before writing clean data to Delta tables, (2) enforce fine-grained column-level access controls and capture data lineage across all data assets, and (3) schedule and orchestrate a nightly batch aggregation job that depends on the successful completion of the streaming pipeline. Which combination of Databricks platform components BEST maps to these three requirements, in order?

1. ARequirement 1: Databricks SQL — Databricks SQL supports streaming ingestion from Kafka via streaming SQL queries executed on SQL Warehouses; Requirement 2: Delta Lake — Delta Lake has built-in row-level and column-level access policy enforcement that integrates with LDAP directories; Requirement 3: Mosaic AI — Mosaic AI provides MLOps-style workflow orchestration for scheduling batch aggregation pipelines as recurring ML training jobs.
2. BRequirement 1: Lakeflow Spark Declarative Pipelines (Delta Live Tables) — this framework provides a declarative SQL/Python interface for building multi-hop batch and streaming pipelines, including native Kafka source connectors; Requirement 2: Unity Catalog — Unity Catalog enforces fine-grained access controls through column masks and row filters and automatically captures column-level data lineage; Requirement 3: Lakeflow Jobs — Lakeflow Jobs orchestrates automated workflows, supports task dependencies across pipeline steps, and triggers runs on cron schedules or upon upstream task success.
3. CRequirement 1: Lakeflow Jobs — Lakeflow Jobs is the correct component for consuming Kafka events in real time and applying streaming transformations because it supports long-running background tasks; Requirement 2: Mosaic AI — Mosaic AI manages data access permissions for ML features and tables through its Feature Store governance layer; Requirement 3: Delta Lake — Delta Lake contains a built-in CRON scheduler that triggers OPTIMIZE and ZORDER jobs automatically when new data partitions are detected.
4. DRequirement 1: Unity Catalog — Unity Catalog contains built-in Kafka streaming ingestion connectors that route incoming messages to the correct schema based on Unity Catalog access control policies; Requirement 2: Databricks SQL — Databricks SQL provides a visual column-level masking editor in the SQL Editor UI that also auto-generates lineage diagrams from query patterns; Requirement 3: Lakeflow Spark Declarative Pipelines — Lakeflow SDP is the recommended Databricks scheduler for triggering nightly Delta table compaction and aggregation batches.
5. ERequirement 1: Delta Lake — Delta Lake provides native Apache Kafka consumer clients that ingest streaming events and apply schema enforcement before writing transactions; Requirement 2: Lakeflow Jobs — Lakeflow Jobs manages column-level security by running identity-aware job clusters that restrict column access based on the job owner's permissions; Requirement 3: Unity Catalog — Unity Catalog contains a built-in cron-based pipeline trigger that automatically schedules nightly batch aggregation workflows against registered Delta tables.

A data engineer creates a managed Delta table named analytics.sales.transactions in Unity Catalog by running CREATE TABLE analytics.sales.transactions AS SELECT * FROM raw.events. A second engineer independently creates an external table named finance.reporting.invoices using CREATE EXTERNAL TABLE finance.reporting.invoices LOCATION 's3://company-data/invoices/'. Both engineers later run DROP TABLE on their respective tables. Which statement CORRECTLY describes the outcome of both DROP operations?

1. ABoth the managed and external table DROP operations delete the table's metadata entries from the Unity Catalog metastore AND permanently delete the underlying data files from cloud storage, because registering any table in Unity Catalog — whether managed or external — transfers full data lifecycle ownership to Unity Catalog, which then controls deletion behavior identically for both table types.
2. BDropping the managed table analytics.sales.transactions removes its metadata AND, after a recovery period (7 days by default), deletes its data files. Dropping the external table finance.reporting.invoices removes only the metadata pointer; the files at s3://company-data/invoices/ stay intact.
3. CBoth DROP operations remove only the metadata entry from the Unity Catalog metastore; neither operation ever deletes the underlying data files, because Unity Catalog operates exclusively at the governance layer and delegates all data file lifecycle management to the cloud provider's storage service, which requires a separate storage API call to permanently remove files.
4. DDropping the managed table analytics.sales.transactions removes only the metadata entry and leaves the data files in place until an engineer manually runs VACUUM on the storage path. Dropping the external table finance.reporting.invoices immediately and permanently deletes both the metadata and all underlying data files in S3, because external tables transfer complete storage ownership to Unity Catalog upon initial table registration.
5. EDropping either type of table in Unity Catalog automatically places the table in a 30-day recycle bin from which it can be fully restored, including all historical data versions. The underlying data files for both managed and external tables are preserved during this recycle period in a quarantine storage tier, and administrators must explicitly call PURGE TABLE with a FORCE flag to permanently remove them from storage.

A data analyst at a logistics company is exploring Databricks Marketplace to acquire a public geospatial reference dataset and a Databricks notebook demonstrating geospatial analysis patterns. The analyst has a Unity Catalog-enabled Databricks workspace. Which set of statements about Databricks Marketplace behavior and capabilities is ACCURATE?

1. ATo browse any Marketplace listing, the analyst must first apply to become a registered Marketplace provider, because provider and consumer identities are linked in a single unified registration workflow; read-only consumer browsing access is only unlocked after Databricks approves the provider application and assigns a provider profile to the workspace.
2. BMarketplace operates exclusively with Databricks-proprietary data formats; any external dataset acquired through Marketplace is automatically and irreversibly converted from its original Parquet, CSV, or JSON format into a Databricks-proprietary encrypted binary archive format before delivery. This conversion makes the data incompatible with Apache Spark running outside of Databricks and with any non-Databricks downstream analytics tools.
3. CThe Open Marketplace (marketplace.databricks.com) can be browsed without logging in to any Databricks workspace, allowing the analyst to explore listings and evaluate provider documentation before committing. To request access and install the geospatial dataset or notebook, the analyst uses the Marketplace section within their Unity Catalog-enabled Databricks workspace; once the provider approves the request, the dataset becomes available as a read-only Unity Catalog catalog that the analyst can query directly with SQL, and the notebook is installed to the workspace for immediate use.
4. DAll Marketplace listings — both datasets and notebooks — are delivered instantly and unconditionally to any Databricks user who clicks the 'Get' button, with no provider approval step, no terms-of-use acceptance, and no workspace-level permission requirements under any circumstances. Once acquired, the dataset catalog is made fully writable in the consumer's Unity Catalog so that local transformations can be written back to the provider's original data source.
5. EDatabricks notebooks available in Marketplace are static, read-only PDF exports of notebook code that cannot be imported into a Databricks workspace. To use Marketplace notebook content, analysts must manually copy the code from the PDF document into a new blank notebook. Datasets, by contrast, are delivered as live queryable catalogs. This asymmetry exists because Databricks considers only structured tabular data assets to have sufficient governance controls for live delivery.

A data engineering team is evaluating the Databricks Data Intelligence Platform for the first time. A team member lists several platform components and assigns each one a primary role. Which of the following descriptions CORRECTLY matches a platform component to its primary purpose?

1. ADelta Live Tables (Lakeflow Spark Declarative Pipelines) is responsible for providing unified governance, access control, and lineage tracking across all data and AI assets stored in the Databricks platform; it enforces fine-grained table permissions through ANSI SQL GRANT and REVOKE statements and enables cross-workspace data discovery through a centralized metadata catalog.
2. BMosaic AI is the integrated AI and machine learning platform on Databricks that provides an end-to-end environment for building, deploying, and managing AI applications — including generative AI agents, foundation model APIs, Vector Search for RAG, AutoML for automated model training, scalable model serving endpoints, and MLflow-based experiment tracking and model lifecycle management.
3. CLakeflow Jobs is a declarative pipeline framework used specifically to define, schedule, and execute batch or streaming ETL transformations written in SQL or Python; its primary architectural contribution is the ability to define streaming tables and materialized views that automatically refresh as new source data arrives, without requiring manual trigger logic.
4. DUnity Catalog functions as the performance-optimized query execution engine embedded in the Databricks Runtime that dramatically accelerates SQL and DataFrame workloads by replacing the standard Apache Spark execution engine with a vectorized, LLVM-compiled query engine called Photon, processing data at native CPU speeds without any code changes.
5. EDatabricks SQL is a machine learning model registry and real-time deployment service that stores trained model artifacts, manages model versioning with approval workflows, and exposes trained LLMs and classic ML models as auto-scaling REST endpoints; it is the only Databricks component capable of hosting inference traffic at sub-100ms response latencies.

A data governance team is conducting a quarterly audit of their Unity Catalog setup using the Catalog Explorer in Databricks. The team lead asks which of the following tasks can be accomplished DIRECTLY within the Catalog Explorer UI, without needing to write SQL, open a notebook, or use the CLI.

1. AExecuting long-running SQL transformation queries to repartition large Delta tables, previewing the Directed Acyclic Graph (DAG) execution plan using the Spark UI embedded within Catalog Explorer, and stopping a stalled Lakeflow Jobs pipeline run from a dedicated pipeline operations panel that surfaces within the Catalog Explorer sidebar.
2. BViewing column-level data lineage that traces which upstream tables, views, and notebooks contributed to the data in a specific downstream Delta table; tagging a data asset with custom business metadata labels to improve discoverability; inspecting table ownership and granular GRANT permissions; and marking a table as a certified dataset to signal data quality and trustworthiness to downstream consumers — all directly within the Catalog Explorer interface.
3. CConfiguring Kafka stream ingestion source settings for a specific schema, assigning serverless compute SKU sizes to individual SQL Warehouses from within the table detail panel, writing and testing row filter SQL expressions through a drag-and-drop visual security policy editor, and enabling automatic schema evolution for streaming tables — all accessible from a unified configuration panel in Catalog Explorer.
4. DProvisioning new all-purpose compute clusters and defining auto-scaling policies from within the Catalog Explorer, uploading raw CSV and Parquet files directly to a managed table schema to create new tables without any SQL, and browsing MLflow experiment run metrics and artifacts — all without leaving the Catalog Explorer tab or accessing any other section of the Databricks UI.
5. EAutomatically rewriting all queries registered under a schema to incorporate the latest Liquid Clustering key definitions, generating synthetic test data for tables that are currently empty to validate dashboard visualizations, and scheduling automated data quality threshold alerts that trigger Slack notifications when freshness SLAs are violated — these represent the primary analytical workflow features available natively inside the Catalog Explorer.