Databricks · Free Practice Questions · Last reviewed May 2026
54real exam-style questions organised by domain, each with the correct answer highlighted and a plain-English explanation of why it's right — and why the others are wrong.
A data analyst needs to optimize query performance for a large sales table that is frequently filtered by 'region_id'. Which physical data modeling strategy should be implemented to minimize data scanning?
Implement a primary key constraint on the region_id column.
Execute the ANALYZE TABLE command periodically without any data clustering.
Apply Z-Ordering on the region_id column.
Z-Ordering maps multi-dimensional data to one dimension while preserving locality. By clustering data with similar 'region_id' values into the same files, the engine can utilize min-max statistics to skip entire files that do not contain the requested region, drastically reducing I/O and improving overall query latency.
Change the file format to CSV to allow easier manual partitioning.
Refer to the exhibit. The 'sales_data' table is growing rapidly. You notice queries filtering by 'event_date' are fast, but queries filtering by 'id' are slow. What is the most effective data modeling change to optimize for 'id' lookups?
Re-partition the table by 'id' instead of 'event_date'.
Use Z-Ordering or Liquid Clustering on the 'id' column.
Z-Ordering or Liquid Clustering allows the engine to organize data within the existing partitions to facilitate efficient skipping on the 'id' column. This keeps the physical folder structure manageable based on 'event_date' while providing high-performance access paths for queries filtering by specific 'id' values without creating excess files.
Create a secondary table for 'id' lookups that is partitioned by 'id'.
Change the table type to a standard Parquet table without partitioning.
When designing a star schema in Databricks SQL, why is it recommended to use Delta Lake for both Fact and Dimension tables?
It forces the use of Star Schema optimization, which is only supported for Delta format.
Delta Lake supports ACID transactions, which are necessary for reliable SCD updates.
SCD (Slowly Changing Dimension) patterns require atomic updates to history and status flags. Delta Lake ensures these operations are ACID compliant, meaning they are either fully committed or not committed at all. This prevents partial writes that could invalidate downstream analytical queries or lead to erroneous historical reporting.
Delta Lake automatically reorders dimension tables to improve join performance.
It is required to store dimensions in the same schema as fact tables for performance.
Which THREE of the following are benefits of using Liquid Clustering instead of traditional partitioning in Databricks SQL?
It simplifies data layout management by removing the need for manual partitioning.
Liquid Clustering eliminates the rigid structure of traditional partitioning. It allows users to define clustering keys, and the system automatically reorganizes data to optimize for query performance over time. This removes the administrative overhead of re-partitioning tables when business requirements or filter patterns shift significantly over the project lifecycle.
It prevents the creation of small files caused by high-cardinality partitions.
High-cardinality columns in traditional partitioning lead to thousands of tiny files, which degrade performance. Liquid Clustering manages data distribution more intelligently, aiming for optimal file sizes regardless of the cardinality of the clustering keys. This creates a much more efficient metadata layer and speeds up overall query execution times.
It provides faster write throughput by disabling transaction logs during updates.
It allows for easier clustering key updates without needing to rewrite the entire table.
With traditional partitioning, changing a partition column usually requires a full table rewrite. Liquid Clustering allows users to evolve clustering keys over time with minimal impact. The system handles the transition smoothly, allowing the data to be reorganized incrementally as new data arrives, which is highly efficient for evolving business requirements.
It forces data to be sorted by every column in the table automatically.
You are modeling a table where users need to query based on a 'user_id' but also need to perform historical point-in-time analysis. Which feature is most appropriate?
Implement a materialized view with a static snapshot.
Use Delta Time Travel.
Time Travel in Delta Lake allows querying data as of a specific version or timestamp using the 'VERSION AS OF' or 'TIMESTAMP AS OF' clauses. This provides seamless access to historical states without requiring extra storage for snapshots or complex architectural workarounds for point-in-time analytical requirements.
Create a new table for every daily load.
Store all historical records in a single table with an 'is_current' flag.
An organization requires that certain sensitive columns be removed from a table for specific groups of users. Which Databricks feature should be used to enforce this at the data modeling level?
Create separate physical tables for each security level.
Use Delta Lake dynamic masking.
Dynamic masking allows for the definition of policies that transform or redact column content based on the user's role at query time. This ensures security is enforced consistently across all applications and users, without altering the underlying data on disk, which is vital for maintaining data governance and compliance standards.
Change the file format to JSON to strip sensitive fields.
Hard-code the filtering logic in every user's SQL query.
Want more Data Modeling with Databricks SQL practice?
Practice this domainAn analyst is running queries on a shared Databricks SQL Warehouse. Which TWO actions improve query performance by reducing the impact of high concurrency?
Enable Result Set Caching on the SQL Warehouse.
Result set caching stores the output of repeated queries in the warehouse's local storage. When a subsequent user runs an identical query, the warehouse returns the cached result immediately without re-executing the query logic. This drastically reduces latency and saves compute resources during high-concurrency periods for frequent dashboards.
Use SELECT * exclusively in all production dashboards.
Convert complex frequently-queried tables into Materialized Views.
Materialized views precompute the results of complex queries. When an analyst queries the view, the engine reads the precomputed data rather than calculating joins and aggregations from scratch. This significantly lowers the latency for concurrent users and offloads the intensive computation from the standard SQL warehouse execution time.
Increase the warehouse size to 4XL regardless of query complexity.
Always use ORDER BY in every subquery.
Refer to the exhibit. An analyst receives this error when attempting to select from a table in Databricks SQL. What is the most likely cause?
The table schema is corrupted and requires a REPAIR TABLE command.
The analyst is missing the USE CATALOG or USE SCHEMA statement.
The error occurs because the SQL Warehouse cannot locate the object within the default scope. Setting the session context with USE CATALOG or USE SCHEMA ensures the engine looks in the intended location. Alternatively, using the fully qualified path catalog.schema.table resolves the lookup failure by providing the complete address.
The SQL Warehouse is stopped and needs to be restarted.
The table has too many partitions, causing a timeout.
An analyst is performing a join between a large fact table and a small dimension table. To ensure optimal performance in Databricks SQL, which join type is preferred when the dimension table fits in memory?
Sort-merge join
Broadcast hash join
A broadcast join broadcasts the smaller table to every executor, allowing the join to occur locally at each node without shuffling the large fact table. This significantly reduces data movement across the network, which is the primary bottleneck in distributed join operations within Databricks SQL environments.
Cartesian join
Full outer join
You want to create a temporary view that is only available for the duration of the current SQL session. Which command achieves this?
CREATE VIEW view_name AS SELECT * FROM table
CREATE TEMPORARY VIEW view_name AS SELECT * FROM table
The TEMPORARY keyword limits the visibility of the view to the current SQL session. Once the session ends, the view is automatically dropped. This is perfect for complex queries requiring intermediate steps that do not need to be shared or persisted across the broader organizational data environment.
CREATE LOCAL VIEW view_name AS SELECT * FROM table
CREATE SESSION TABLE view_name AS SELECT * FROM table
An analyst is preparing a report and needs to ensure that sensitive PII columns are not exposed. Which TWO techniques can be used to achieve this in Databricks SQL?
Apply Dynamic Data Masking to the sensitive columns.
Dynamic data masking allows administrators to redact or hash sensitive data based on the user's role. For example, a partial mask can be applied to email addresses or SSNs, ensuring the raw data is hidden while still allowing analytical processing on the masked values by unauthorized users.
Use the GRANT ALL PRIVILEGES command on all tables.
Implement Row-Level Security using a filter clause in the view definition.
Use the GRANT SELECT command only on non-sensitive columns.
By explicitly granting SELECT privileges only on columns that do not contain PII, you effectively prevent users from accessing sensitive data. This is a simple, effective method for column-level security that leverages the underlying Unity Catalog access control model to ensure data protection at the schema and object levels.
Run the query as a superuser to bypass masks.
An analyst wants to view the query profile for a specific query that was run recently. Where should they look in the Databricks SQL UI?
The Catalog Explorer
The SQL Editor
The Query History tab
The Query History tab in the Databricks SQL UI logs all queries executed on the warehouse. By selecting a specific query ID, users can access the Query Profile, which displays the execution graph, metrics, and bottlenecks, allowing for granular analysis of how the engine processed the data during runtime.
The SQL Warehouse settings page
Want more Executing Queries with Databricks SQL practice?
Practice this domainWhich visualization type is most appropriate for displaying the distribution of a single continuous numerical variable, such as transaction amounts, in a Databricks Dashboard?
Pie chart
Line plot
Histogram
Histograms aggregate continuous numerical data into distinct intervals or bins, plotting frequency counts on the vertical axis. This makes them the definitive choice for analyzing the statistical distribution and spread of metrics like transaction amounts.
Scatter plot
An analyst is creating a visualization of daily sales trends over the past year. They notice that the chart is cluttered and difficult to interpret due to the high volume of individual data points. Which action should the analyst take to improve readability?
Change the chart type to a scatter plot.
Filter the dataset to only include the last seven days.
Change the X-axis grouping from 'Day' to 'Month'.
Grouping by month aggregates the daily values into manageable segments, effectively smoothing out the line chart. This reduction in granularity helps the viewer focus on monthly performance patterns and seasonal changes, which provides clearer insights than attempting to interpret 365 individual data points on a single chart view.
Increase the chart size to fill the entire screen width.
Which TWO of the following are valid ways to improve the performance of a slow-loading Databricks SQL dashboard? (Choose two)
Convert all visualizations into a single complex query.
Enable query result caching on the SQL warehouse.
Query result caching stores the results of queries so that subsequent executions of the same query retrieve the data directly from the cache. This bypasses the need for the warehouse to re-read and re-process the underlying data, resulting in near-instant load times for repeated dashboard views.
Add more users to the dashboard to increase processing power.
Optimize the underlying SQL queries using filters and aggregates.
Optimizing queries by pushing down filters and pre-aggregating data ensures that the SQL warehouse processes only the necessary information. This reduces the amount of data scanned and transferred, minimizing compute time and memory usage, which directly leads to faster rendering of dashboard visualizations for the end-users.
Switch the dashboard to manual refresh mode only.
Which visualization type is most appropriate for showing the distribution of a single continuous variable, such as the spread of customer ages?
Pie Chart
Line Chart
Histogram
Histograms are specifically designed to visualize the distribution of continuous numerical data. By binning values and showing counts per bin, they provide a clear view of where data points are concentrated, which is exactly what is needed to understand the spread of variables like customer age.
Scatter Plot
An analyst wants to publish a dashboard for the executive team. The dashboard contains sensitive data that should only be accessible to specific users. What is the correct way to handle access control?
Hard-code the security logic into the SQL queries.
Export the dashboard as a PDF and email it to the team.
Use the 'Share' button to grant 'Can View' access to authorized groups.
The 'Share' functionality in Databricks allows for precise, role-based access control. By sharing the dashboard with specific groups, the analyst ensures that authentication and authorization are handled by the platform's security framework, keeping data access centralized, auditable, and restricted to only those who strictly require it.
Make the dashboard public and add a password to the title.
Which THREE of the following steps are necessary to create an interactive dashboard in Databricks SQL? (Choose three)
Write a SQL query that includes filter parameters.
To make a dashboard interactive, the underlying SQL queries must be parameterized. By using syntax like '{{ parameter_name }}', the analyst creates placeholders that the dashboard interface can dynamically replace with user-selected values, enabling the interactivity required for meaningful data exploration and ad-hoc analysis by the end-users.
Define the visualization type in the SQL query code.
Add the visualization to a dashboard canvas.
Once a visualization is created from a query, it must be added to a dashboard canvas to be shared. The canvas acts as the container where multiple visualizations and widgets are arranged, allowing for a cohesive layout that tells a story and provides context to the business users.
Configure dashboard filters to link to parameters.
After adding visualizations with parameters to a dashboard, the final step is to configure the dashboard filters. This binds the user-facing filter controls to the query parameters, ensuring that when a user selects a value in the UI, the parameter is updated and the underlying query re-runs automatically.
Upload a CSV file containing the final report data.
Want more Creating Dashboards and Visualizations practice?
Practice this domainA data analyst needs to ingest a large volume of CSV files from an external S3 bucket into a Delta table. Which method provides the most efficient, fault-tolerant, and incremental loading approach in Databricks?
Use the COPY INTO command with a static file path.
Manually read files into a DataFrame and use write.mode('append').
Implement Auto Loader using cloudFiles source.
Auto Loader uses cloud-native notifications and directory listing to detect new files efficiently. By managing its own checkpointing, it ensures exactly-once semantics and handles schema evolution automatically. It is the industry standard for production-grade ingestion pipelines in Databricks, providing superior performance and reliability compared to manual file-based ingestion methods.
Use the Databricks SQL 'Import' wizard via the UI.
An analyst is preparing to upload a small local CSV file to a Databricks workspace. Which tool is most appropriate for a quick, one-time upload without requiring infrastructure setup?
Auto Loader
Databricks Add Data UI
The Add Data UI allows users to drag and drop files from a local computer directly into the workspace. It creates a managed table or file path in DBFS, making it the most efficient and straightforward method for a small, one-time upload requirement by a data analyst.
COPY INTO command
Databricks Connect
Refer to the exhibit. An analyst is attempting to read a CSV file using Spark. Why is the code failing?
The cluster is running on a single-node configuration.
The file path provided does not exist in the mounted location.
The AnalysisException clearly states that the path does not exist. This indicates that either the mount point /mnt/data is not correctly established or the specific file sales_2023.csv is missing or misspelled in the underlying storage. The analyst must verify the mount point and the file existence.
Spark does not support reading CSV files directly from DBFS.
The user lacks sufficient memory to read the file.
Which TWO of the following scenarios are valid use cases for using the COPY INTO command? (Choose two)
Ingesting data that arrives in files at unpredictable, irregular intervals.
COPY INTO is idempotent, meaning if you run the same command multiple times on the same files, it will not duplicate the data. This makes it perfect for irregular batch uploads where you just want to load everything that has landed since the last successful execution without building streams.
Implementing a continuous streaming pipeline with sub-second latency.
Loading CSV files into Delta tables while performing basic transformation.
COPY INTO supports loading data directly into Delta tables from CSV, JSON, Parquet, and Avro files. It also allows for basic column filtering and transformation via a select statement during the load, making it a versatile tool for quick, reliable batch loading tasks in a data warehouse environment.
Performing complex, multi-stage ELT pipeline orchestration.
Ingesting historical data from a database using JDBC connectors.
When importing data into Databricks using the 'Add Data' UI, what is the default file format for the created table if the source is a CSV file?
CSV
Parquet
Delta
Delta Lake is the default table format in Databricks. When you use the UI to import a CSV file, Databricks performs an internal transformation to load that data into a Delta table, enabling all the benefits of the Lakehouse architecture, including ACID guarantees and optimized performance for SQL queries.
JSON
An analyst is using the Spark DataFrame API to read a large JSON dataset. The dataset contains nested fields that are causing schema inference to fail. Which approach best resolves this?
Use the option 'mergeSchema' set to true.
Define a schema explicitly using StructType.
Explicitly defining the schema using StructType ensures that Spark knows exactly how to map the nested JSON fields to the DataFrame columns. This eliminates the need for Spark to perform a full file scan for inference, preventing errors on complex datasets and ensuring consistent data types for downstream analytical tasks.
Convert the JSON to CSV before reading it.
Increase the number of partitions during read.
Want more Importing Data practice?
Practice this domainA data analyst is troubleshooting a slow-running SQL query against a massive Delta table in Databricks. The query frequently scans the entire table despite filtering on a high-cardinality timestamp column. Which approach will most effectively reduce the data scanned by eliminating full-table reads?
Run an OPTIMIZE command with a ZORDER BY clause on the timestamp column to co-locate related data and improve data skipping.
Z-Ordering clusters data with similar values into the same file spaces. This enables the Delta Lake file-skipping mechanism to bypass irrelevant files entirely when queries apply range filters on the target timestamp column, directly lowering overall scan volume and query duration.
Increase the cluster size to a driver instance with more memory to hold the entire uncompressed Delta table in cache.
Execute a VACUUM command with a retention threshold of zero hours to purge old data files immediately.
Convert the Delta table format to standard Parquet files to take advantage of native Apache Spark partitioning.
A data analyst needs to inspect the logical and physical execution plans of a slow Spark SQL query to understand how filters and joins are being evaluated. Which command should the analyst execute in a Databricks notebook cell?
DESCRIBE EXTENDED table_name;
EXPLAIN EXTENDED SELECT * FROM table_name WHERE condition;
EXPLAIN EXTENDED generates a comprehensive breakdown of the query lifecycle, showing the logical optimizations and physical operators chosen by the Catalyst optimizer. This insight is vital for diagnosing performance bottlenecks and verifying predicate pushdown.
SHOW QUERY PLAN FOR SELECT * FROM table_name WHERE condition;
ANALYZE TABLE table_name COMPUTE STATISTICS FOR COLUMNS;
A data analyst notices that a query involving a large join between two tables is consistently slow. The analyst suspects that one of the tables is significantly skewed. Which tool in the Databricks SQL query profile is most effective for confirming this skew?
The Query History list view.
The SQL Query Profile 'Metrics' tab.
The Query Profile metrics provide deep visibility into task-level statistics, including the minimum, maximum, and median rows processed per task. If the maximum row count significantly exceeds the median, it confirms data skew, allowing the analyst to implement partitioning strategies like salting to balance the workload across executors.
The Cluster Usage dashboard.
The Table details metadata panel.
An analyst is optimizing a query that performs multiple aggregations on a Delta table. Which TWO actions can the analyst take to improve query performance via the SQL editor?
Use Z-Ordering on columns frequently used in WHERE filters.
Z-Ordering co-locates related data in the same set of files, significantly enhancing data skipping capabilities. By clustering data based on frequently filtered columns, the engine can ignore irrelevant files during query execution, leading to faster data retrieval and lower overall compute resource consumption for the query.
Enable partition pruning by including partition columns in the WHERE clause.
Partition pruning restricts the scan to specific directories on storage. By explicitly filtering on partition columns in the WHERE clause, the engine avoids scanning partitions that do not meet the criteria, drastically reducing the volume of data read from storage and significantly accelerating the query's total execution time.
Increase the cluster size to 'Large' for every query execution.
Force a Broadcast Join for all small tables.
Convert all tables to Parquet format.
Which of the following is the primary purpose of examining the 'Query Profile' in Databricks SQL?
To change the permissions of the underlying table.
To visualize the execution steps and identify bottlenecks.
The Query Profile provides a graphical representation of the physical query plan. It allows analysts to see the duration of individual operators, data volumes, and task metrics, making it easier to pinpoint specific stages that are causing slow execution or high resource utilization within a complex SQL statement.
To automatically rewrite SQL for better performance.
To view the raw logs of the cluster driver.
When analyzing query performance, what does a high 'Spill to Disk' metric indicate?
The query is successfully using the cache.
The cluster has insufficient memory for the operation.
Spilling happens when a transformation, such as a large-scale shuffle or aggregate, consumes more memory than allocated. The system temporarily moves data to disk to prevent an 'OutOfMemory' crash. This slows the query down significantly, suggesting that the memory allocation per executor should be increased or the query optimized.
The data is highly compressed.
The query is finished and writing results to the table.
Want more Analyzing Queries practice?
Practice this domainA data engineer has created a Delta table named `sales_summary` and needs to ensure that downstream analysts can only read rows where the `region` column matches their assigned territory. Which Databricks feature should be implemented to enforce this restriction securely at the row level?
Apply dynamic views using standard Spark SQL case statements that evaluate session user functions.
Implement Unity Catalog row filters using a SQL function that evaluates the current user.
Unity Catalog row filters attach a SQL function to the table that evaluates the invoking user's identity, returning only rows matching their assigned territory. Enforcement occurs at query time in the governance layer, so analysts cannot bypass the restriction through direct table reads.
Grant SELECT privileges on filtered partitions using Unity Catalog folder-level access controls.
Configure cluster-level environment variables to filter data frames automatically upon session start.
You are a data analyst working in Databricks SQL. Your workspace has Unity Catalog enabled. You need to inspect the metadata of a table named `customers` in the `sales` schema of the `retail` catalog, but you do not want to return any rows of data. Which SQL statement should you use?
DESCRIBE TABLE retail.sales.customers;
DESCRIBE TABLE (or DESC TABLE) returns the column names, data types, and comments for the specified table without scanning or returning any data rows. It works with the fully qualified three-part Unity Catalog namespace catalog.schema.table, so it correctly targets retail.sales.customers and satisfies the requirement to inspect metadata only.
SELECT * FROM retail.sales.customers LIMIT 0;
SHOW CREATE TABLE retail.sales.customers;
SHOW TABLES IN retail.sales;
A data analyst has a Delta table `events` in Unity Catalog and needs to see the history of operations performed on it, including which user ran each operation and when, in order to audit recent changes. Which command should the analyst run?
DESCRIBE DETAIL events;
SELECT * FROM events VERSION AS OF 0;
SHOW TABLES IN main.default;
DESCRIBE HISTORY events;
DESCRIBE HISTORY returns the Delta transaction log entries for the table, including version, timestamp, operation, operation parameters, user identity, and other metadata. This directly satisfies the requirement to audit who changed the table and when, and it is the canonical Delta Lake command for table history inspection in Databricks.
You are an analyst in a Unity Catalog-enabled Databricks workspace. A colleague has shared a table `finance.transactions` with you, and you need to confirm what privileges you currently hold on it before running a sensitive query. Which TWO of the following statements about inspecting privileges in Unity Catalog are accurate? (Choose two.)
You can run SHOW GRANTS ON TABLE finance.transactions to see the privileges granted on that specific table.
SHOW GRANTS ON TABLE returns the privileges granted on the specified securable, including which principals hold SELECT, MODIFY, or other rights. It is the direct way to inspect table-level grants in Unity Catalog and works with the three-part catalog.schema.table namespace, so it correctly answers what privileges exist on the transactions table.
Privileges granted at the catalog or schema level are inherited by the table, so SHOW GRANTS ON TABLE may not show every effective privilege you hold.
Unity Catalog privileges are hierarchical: grants at the catalog or schema propagate to objects within them. SHOW GRANTS ON TABLE lists grants applied directly to the table, but your effective ability to query it can also come from inherited catalog or schema grants. This makes the statement accurate about how effective privileges are determined.
You must be the table owner or a metastore admin to run SHOW GRANTS ON TABLE on a table you can query.
SHOW GRANTS ON TABLE finance.transactions will also list the privileges granted on the parent catalog and schema automatically.
SHOW GRANTS ON TABLE returns only the privileges of the current user and hides grants to other principals for privacy.
An analyst needs to create a new table in a Unity Catalog schema to store aggregated results, and the table should be managed by Unity Catalog so that storage lifecycle and access are handled by the platform. Which SQL statement correctly creates a managed Delta table named `summary` in the `analytics` schema of the `reporting` catalog?
CREATE TABLE reporting.analytics.summary (id INT, total DOUBLE);
In Unity Catalog, CREATE TABLE with a three-part name creates a managed table by default when no LOCATION is specified. Unity Catalog manages the storage location and lifecycle, which matches the requirement. The statement is syntactically valid and uses the correct catalog.schema.table namespace for the reporting catalog and analytics schema.
CREATE MANAGED TABLE reporting.analytics.summary (id INT, total DOUBLE);
CREATE EXTERNAL TABLE reporting.analytics.summary (id INT, total DOUBLE) LOCATION '/mnt/data/summary';
CREATE TABLE reporting.analytics.summary USING DELTA LOCATION 'dbfs:/user/hive/warehouse/summary';
A data analyst runs the following command in a Databricks SQL editor connected to a Unity Catalog workspace:
```sql DROP TABLE IF EXISTS analytics.events.raw_clicks; ```
What is the result of this statement if `analytics.events.raw_clicks` is a managed Delta table?
The table metadata, data files, and any associated directories are permanently removed from the metastore and cloud storage.
For a managed table, Databricks owns the lifecycle of both metadata and data. Dropping it removes the catalog entry and deletes the underlying data files from the managed storage location. This is the defining behavior that separates managed from external tables and is why the statement succeeds without any additional file cleanup step from the analyst.
The table is renamed to a recycle-bin schema and can be restored by any workspace user within 30 days.
The command fails because Databricks SQL does not permit dropping tables that other users may be querying.
Only the table metadata is removed; the underlying Parquet data files remain in cloud storage for later recovery.
Want more Managing Data practice?
Practice this domainA data analyst needs to share a sensitive sales table with the marketing team in Databricks. The marketing team should only see rows where the region column matches 'North America' and should not have access to the credit_card column. Which Unity Catalog feature should the data analyst implement?
Create a static clone of the table, drop the restricted column, and grant SELECT permission on the clone to the marketing group.
Apply row filters and column masks using SQL functions within Unity Catalog to restrict data visibility dynamically for the marketing group.
Unity Catalog row filters and column masks dynamically filter rows and redact column values at query time based on user identity or group membership. This approach eliminates data duplication, ensures real-time updates, and provides robust governance security.
Configure an access control list on the parent catalog to deny SELECT access on specific columns for the marketing group.
Export the filtered subset of data into CSV files and upload them to a secured volume inside the marketing team's schema.
A data analyst needs to grant a colleague read access to a specific table named 'quarterly_sales' within Unity Catalog without exposing other tables in the same schema. Which SQL command should the analyst execute?
GRANT SELECT ON TABLE quarterly_sales TO `colleague@company.com`;
Granting the SELECT privilege directly on a specific table provides precise access control. This ensures the recipient can query only the targeted dataset while adhering strictly to the principle of least privilege across the schema.
GRANT ALL PRIVILEGES ON SCHEMA sales_schema TO `colleague@company.com`;
GRANT READ ACCESS ON CATALOG main TO `colleague@company.com`;
GRANT USE TABLE ON quarterly_sales TO `colleague@company.com`;
Which identity management approach is required to utilize Unity Catalog for centralized governance across multiple Databricks workspaces?
Local workspace-level user management.
Account-level identity provisioning using SCIM.
SCIM provisioning at the account level ensures that identities are synchronized from your identity provider directly to the Databricks account. This is the prerequisite for Unity Catalog because it provides a unified identity namespace, allowing for consistent access control policies across all connected workspaces and catalogs within the metastore.
Database-level authentication via JDBC drivers.
Private Link connectivity for all users.
An administrator needs to secure a table containing sensitive customer data. Which TWO options represent valid ways to restrict access using Unity Catalog?
Use GRANT SELECT on the table to specific users or groups.
Standard SQL access controls allow administrators to explicitly define who can read a table. This is the fundamental mechanism for data governance in Unity Catalog, ensuring that only authorized users or service principals can execute queries against the sensitive data, adhering to the principle of least privilege.
Delete the sensitive rows from the table manually.
Implement column masking policies on sensitive columns.
Masking policies provide a way to redact or obfuscate sensitive column values at query time. This allows users to access the table structure while preventing them from seeing the actual sensitive contents, providing a flexible and secure way to manage data access without creating multiple physical versions of the table.
Rotate the workspace passwords weekly.
Disable the table for all users except the owner.
What is the primary function of a Storage Credential in Unity Catalog?
To encrypt files stored in the S3 bucket.
To provide a secure way to access cloud storage locations.
Storage credentials act as a secure bridge, allowing the Databricks platform to assume a managed identity to perform operations on behalf of the user. This architecture prevents the need for embedding raw access keys in notebooks or cluster configurations, significantly reducing the surface area for credential leakage or misuse.
To manage user passwords for the Databricks workspace.
To define table schema definitions for external tables.
When sharing data with external organizations using Delta Sharing, which component manages the secure exchange of data?
Unity Catalog metastore.
The Unity Catalog metastore serves as the governance layer that defines and tracks Delta Shares. It holds the metadata about the share, including which tables are included and which recipients have access. Without the metastore, there is no central mechanism to authorize or audit the external sharing of data assets.
Workspace-local Hive metastore.
Databricks File System (DBFS) Root.
User-managed S3 bucket policies.
Want more Securing Data practice?
Practice this domainAn analytics team is building an AI/BI Genie space to allow business users to query sales data using natural language. After setting up the base tables, the initial user questions return inaccurate filter values because the LLM struggles to map colloquial region names to the exact string codes stored in the database. What is the most effective feature within AI/BI Genie to resolve this mapping issue without modifying the underlying physical tables?
Create a materialized view containing hardcoded string mappings for every possible regional variation queried by business users.
Enable automatic schema inference and let the Genie space rebuild its internal vector embeddings from scratch overnight.
Configure table and column descriptions, add explicit instructions, and provide verified queries demonstrating the correct region mappings.
Detailed table documentation, clear spatial instructions, and few-shot examples via verified queries provide the LLM with exact patterns to follow. This improves translation accuracy for ambiguous colloquialisms and ensures reliable SQL generation for business users.
Modify the source table column constraints to reject any query that does not use the exact database region code.
Which component of an AI/BI Genie space is responsible for defining the scope of data available to a user and ensuring that the natural language model only references authorized tables?
The Unity Catalog Data Explorer integration
The Genie space instructions and metadata definition
Instructions and table definitions act as the grounding layer for the Genie space. By specifying allowed tables and providing business context in the instructions, you restrict the LLM to a specific subset of Unity Catalog assets, effectively managing scope and preventing unauthorized query generation across the broader catalog.
The Databricks SQL Warehouse access policy
The workspace-level workspace AI configuration
What is the primary purpose of adding 'Instructions' to a Genie space in Databricks?
To automate the deployment of SQL Warehouses
To enable automatic updates for underlying tables
To provide context and guidance for query generation
Instructions act as the 'brain' of the Genie space by providing the AI with domain-specific knowledge. This context helps the LLM interpret ambiguous questions correctly, apply standard business metrics, and choose the right columns, which leads to more accurate and relevant responses for end-users.
To store user credentials for data access
A data analyst is setting up a new Genie space. Which TWO of the following are prerequisites for the successful creation and usage of a Genie space?
A Unity Catalog-enabled workspace
Unity Catalog is mandatory because it provides the unified metadata and governance required for the LLM to discover and reason over tables. Without Unity Catalog, the Genie space cannot resolve table schemas, identify relationships, or enforce the data access controls necessary for safe natural language interactions.
A running Serverless SQL Warehouse
A SQL Warehouse is the compute engine that processes the SQL generated by the Genie space. Serverless warehouses are preferred for their fast startup times and performance, ensuring that when an analyst asks a question, the execution happens quickly without manual intervention or long resource cold-start delays.
A pre-trained custom Large Language Model
A local Python environment with Genie SDK
A Delta Live Table pipeline with high availability
An analyst notices that the Genie space is consistently ignoring a specific column during query generation. What is the most effective way to force the model to consider this column?
Rename the column to start with 'Required_'
Add a column comment in Unity Catalog and mention it in instructions
Combining Unity Catalog table comments with explicit Genie instructions provides a two-pronged approach for grounding. The LLM prioritizes information found in metadata, and the instructions provide the necessary behavioral context to ensure the column is utilized effectively during query generation, solving the issue of it being ignored.
Hard-code the column in the SQL Warehouse settings
Delete and recreate the Genie space
Which THREE features are provided by AI/BI Genie spaces to help business users analyze data independently?
Conversational natural language querying
The core of Genie is the ability to interpret natural language questions and translate them into valid SQL. This removes the barrier of entry for non-technical users, allowing them to ask business questions directly without needing to understand the underlying table structures or complex query syntax.
Automatic chart and visualization generation
Genie spaces do not just provide raw data; they intelligently select the best visualization type for the result set. This allows users to grasp trends, distributions, or comparisons instantly, making the data insights accessible and actionable without the need for additional dashboarding tools or manual chart configuration.
Interactive model performance feedback
Users can provide feedback on the answers provided by Genie. This feedback loop is essential for continuous improvement of the model's accuracy. By flagging incorrect or helpful responses, users contribute to refining the space's reasoning capabilities, leading to better outcomes for all stakeholders over time.
One-click deployment of production ETL pipelines
Automatic generation of unit tests for Python code
Want more Developing AI/BI Genie Spaces practice?
Practice this domainA data analyst is working in a Databricks workspace and needs to ensure that their notebook code is version-controlled and collaborative. Which TWO actions should they take?
Use the built-in Databricks Repos feature to connect to a Git provider.
Databricks Repos provides seamless integration with Git providers like GitHub, GitLab, and Azure DevOps. This allows users to perform standard Git operations like pull, push, and commit directly from the notebook interface. This native integration is the recommended path for managing source code versions within the Databricks ecosystem for data projects.
Copy and paste code into a local text file.
Enable 'Collaboration' settings on the notebook to allow multiple users to edit simultaneously.
Enabling real-time collaborative editing allows multiple data analysts to work on the same notebook concurrently. This feature is vital for pair programming and iterative analysis, significantly increasing productivity. By synchronizing edits across users, the platform prevents conflicts and ensures that the team maintains a unified, up-to-date version of the analytical notebook.
Create a new notebook file for every code change.
Download the notebook to their local machine every hour.
Refer to the exhibit. Given the provided JSON configuration for a Databricks cluster, what is the primary use case for this resource?
Running automated production ETL jobs.
Interactive data analysis and notebook development.
The all-purpose cluster type is designed for interactive development in notebooks. It allows users to start, stop, and restart clusters to run ad-hoc queries and perform data exploration. This configuration is standard for analytical tasks where developers need a responsive environment to test code and visualize findings in real-time.
Long-running streaming data ingestion.
Batch processing of large ML models.
Which component of the Databricks Data Intelligence Platform allows users to discover, govern, and share data across the entire organization?
Databricks SQL
Unity Catalog
Unity Catalog is the primary governance and discovery component in Databricks. It enables administrators to manage access control lists, perform auditing, and document data assets across multiple workspaces. It serves as the single source of truth for metadata, facilitating secure collaboration and compliance across the entire organizational data landscape.
Delta Live Tables
Compute Clusters
Which THREE of the following are benefits of using Delta Lake over standard Parquet files in Databricks?
ACID transaction support
Delta Lake provides Atomicity, Consistency, Isolation, and Durability (ACID) guarantees. This ensures that concurrent reads and writes are handled safely, preventing data corruption and partial writes. This is a fundamental requirement for reliable data warehousing on top of cloud object storage, ensuring users always see consistent data states.
Automatic data compression to non-standard formats
Time travel capabilities
Time travel allows users to query previous versions of their data using versioning or timestamps. This feature is invaluable for auditing, reproducing experiments, and recovering from accidental deletions or incorrect updates, providing a robust mechanism for data lifecycle management that is simply not possible with raw Parquet files.
Schema enforcement and evolution
Delta Lake prevents the insertion of malformed data by enforcing schemas on write and supports schema evolution to handle changing requirements. This prevents downstream pipeline failures and ensures that the data quality is maintained throughout the ingestion process, which is critical for trustworthy analytics in a data-driven enterprise.
The ability to run queries without a compute engine
A data analyst is troubleshooting a performance issue in a notebook. The query runs slowly when processing a large table. Which approach should the analyst take to improve performance?
Increase the number of users connected to the workspace.
Run the 'OPTIMIZE' command on the Delta table.
The OPTIMIZE command compacts small files into larger, more efficient files, significantly improving read performance. It is a standard procedure for data analysts to maintain high performance in Delta Lake tables. This simple action can drastically reduce I/O overhead for analytical queries scanning large volumes of data.
Delete the table and re-create it without Delta Lake.
Force the notebook to run on a single-node cluster.
Refer to the exhibit. What is the most appropriate action to resolve this access issue?
Change the cluster configuration to use a different Spark version.
Request the workspace administrator to grant appropriate privileges in Unity Catalog.
Unity Catalog uses a centralized grant-based permission model. The administrator must explicitly grant the 'USE CATALOG' privilege to the user for the 'sales_data' catalog. This is the correct procedure for resolving access errors, ensuring that security remains intact while allowing the analyst to perform their required data operations.
Move the data to a local file in DBFS.
Re-create the table in a different schema.
Want more Understanding the Databricks Platform practice?
Practice this domainThe Databricks-DA-Assoc exam has 60–90 questions and must be completed in 120 minutes. The passing score is 700/1000.
Scenario-based questions covering exam objectives with detailed answer explanations.
The exam covers 9 domains: Data Modeling with Databricks SQL, Executing Queries with Databricks SQL, Creating Dashboards and Visualizations, Importing Data, Analyzing Queries, Managing Data, Securing Data, Developing AI/BI Genie Spaces, Understanding the Databricks Platform. Questions are weighted by domain — higher-weight domains appear more on your actual exam.
No. These are original exam-style practice questions written against the official Databricks Databricks-DA-Assoc exam objectives. They are not copied from the real exam. Courseiva focuses on genuine understanding, not memorisation of braindumps.
Courseiva tracks your accuracy per domain and routes you toward weak areas automatically. Free, no account required.