Free Databricks Databricks-Certified-Data-Analyst-Associate Practice Exam with Questions & Answers | Set: 2

The correct answer is C because a dashboard is designed to collect multiple visualizations and query outputs in one shared reporting interface. A SQL warehouse provides compute for running SQL queries, but it is not a sharing/reporting interface. Query History only shows past query executions. A visualization tab belongs to one query result, while a dashboard can display multiple results together for stakeholders.

Official documentation extract used: Databricks states that dashboards are used to “build data visualizations and share reports with your team.”

Delta Lake is a storage layer that enhances data lakes with features like ACID transactions, schema enforcement, and time travel. While it stores table data as Parquet files, Delta Lake also keeps a transaction log (stored in the _delta_log directory) that contains detailed table metadata.

This metadata includes:

Table schema

Partitioning information

Data file paths

Transactional operations like inserts, updates, and deletes

Commit history and version control

This metadata is critical for supporting Delta Lake’s advanced capabilities such as time travel and efficient query execution. Delta Lake does not store data summary visualizations or owner account information directly alongside the data files.

Databricks SQL uses ANSI SQL as its standard SQL dialect, which means it follows the SQL specifications defined by the American National Standards Institute (ANSI). This makes it easier to migrate existing SQL queries from other data warehouses or platforms that also use ANSI SQL or a similar dialect, such as PostgreSQL, Oracle, or Teradata. By using ANSI SQL, Databricks SQL avoids surprises in behavior or unfamiliar syntax that may arise from using a non-standard SQL dialect, such as Spark SQL or Hive SQL12. Moreover, Databricks SQL also adds compatibility features to support common SQL constructs that are widely used in other data warehouses, such as QUALIFY, FILTER, and user-defined functions2. References: ANSI compliance in Databricks Runtime, Evolution of the SQL language at Databricks: ANSI standard by default and easier migrations from data warehouses

A Serverless SQL endpoint is a type of SQL endpoint that does not require a dedicated cluster to run queries. Instead, it uses a shared pool of resources that can scale up and down automatically based on the demand. This means that a Serverless SQL endpoint can start up much faster than a SQL endpoint that uses a cluster, and it can also save costs by only paying for the resources that are used. A Serverless SQL endpoint is suitable for ad-hoc queries and exploratory analysis, but it may not offer the same level of performance and isolation as a SQL endpoint that uses a cluster. Therefore, a data analyst should consider the trade-offs between speed, cost, and quality when choosing between a Serverless SQL endpoint and a SQL endpoint that uses a cluster. References: Databricks SQL endpoints, Serverless SQL endpoints, SQL endpoint clusters

The correct answer is C because axis settings are configured in the visualization editor, specifically under the Y-axis settings. The Query Editor is for writing SQL, not configuring chart axes. User Settings do not control individual chart scales. Dashboard editing may contain visualizations, but the specific control is in the visualization editor’s Y Axis configuration.

Official documentation extract used: Databricks chart options state that to configure formatting for the X axis or Y axis, click the corresponding axis tab, and the Y-axis supports scale and range controls.

Data enhancement is the process of adding or enriching data with additional information to improve its quality, accuracy, and usefulness. Data enhancement can be used to augment existing data sources with new data sources, such as external datasets, synthetic data, or machine learning models. Data enhancement can help data analysts to gain deeper insights, discover new patterns, and solve complex problems. Data enhancement is one of the applications of generative AI, which can leverage machine learning to generate synthetic data for better models or safer data sharing1.

In the context of the question, the data analyst is working with gold-layer tables, which are curated business-level tables that are typically organized in consumption-ready project-specific databases234. The gold-layer tables are the final layer of data transformations and data quality rules in the medallion lakehouse architecture, which is a data design pattern used to logically organize data in a lakehouse2. The stakeholder has provided the analyst with an additional dataset that can be used to augment the gold-layer tables already in use. This means that the analyst can use the additional dataset to enhance the existing gold-layer tables with more information, such as new features, attributes, or metrics. This data augmentation can help the analyst to complete the ad-hoc project more effectively and efficiently.

What is the medallion lakehouse architecture? - Databricks

Data Warehousing Modeling Techniques and Their Implementation on the Databricks Lakehouse Platform | Databricks Blog

What is the medallion lakehouse architecture? - Azure Databricks

What is a Medallion Architecture? - Databricks

Synthetic Data for Better Machine Learning | Databricks Blog

Option B is correct. The statement explicitly sets the schema/database location to dbfs:/accounting/data. In Databricks SQL, CREATE SCHEMA supports a LOCATION schema_directory, and the documentation explains that the schema directory is the filesystem path where the schema is created. Because the user supplied LOCATION ' dbfs:/accounting/data ' , Databricks uses that path instead of the default warehouse directory. Option D would apply only when no custom location is supplied. References: Databricks CREATE SCHEMA documentation.

 Option A uses the SELECT DISTINCT statement to remove duplicate rows from the table_bronze and create a new table table_silver with the deduplicated data. This is the correct way to deduplicate data using Spark SQL12. Option B simply inserts all the rows from table_bronze into table_silver, without removing any duplicates. Option C is not a valid syntax for Spark SQL, as there is no MERGE DEDUPLICATE statement. Option D appends all the rows from table_bronze into table_silver, without removing any duplicates. Option E overwrites the existing data in table_silver with the data from table_bronze, without removing any duplicates. References: Delete Duplicate using SPARK SQL, Spark SQL - How to Remove Duplicate Rows

Option C is correct. DESCRIBE DATABASE customer360 returns metadata for the database/schema, including its filesystem location. DESCRIBE LOCATION is for external locations, not databases. DROP DATABASE deletes a database, ALTER DATABASE changes metadata/properties, and USE DATABASE changes the current database context. Official Databricks extract: DESCRIBE DATABASE is an alias for DESCRIBE SCHEMA, and DESCRIBE SCHEMA returns metadata including the schema’s “location on the filesystem.”

Option B is correct. In Databricks, when a managed table is dropped, Databricks removes the table and its associated managed storage location. For an external table, Databricks removes only the table metadata; the underlying external data files are not deleted. Therefore, dropping both tables deletes the managed table’s data but leaves the external table’s data untouched. Official Databricks documentation states that DROP TABLE “deletes the table and removes the directory associated with the table from the file system if the table is not an EXTERNAL table,” and for external tables, Unity Catalog “removes the table metadata but does not delete the underlying data files.”