Databricks-Certified-Data-Analyst-Associate Exam Dumps - Databricks Certified Data Analyst Associate Exam

External tables are tables that are defined in the Databricks metastore using the information stored in a cloud object storage location. External tables do not manage the data, but provide a schema and a table name to query the data. To create an external table, you can use the CREATE EXTERNAL TABLE statement and specify the object storage path to the LOCATION clause. For example, to create an external table named ext_table on a Parquet file stored in S3, you can use the following statement:

SQL

CREATE EXTERNAL TABLE ext_table (

col1 INT,

col2 STRING

)

STORED AS PARQUET

LOCATION ' s3://bucket/path/file.parquet '

AI-generated code. Review and use carefully. More info on FAQ.

 External tables

Option D is correct. Databricks SQL alerts run a query on a schedule, evaluate a condition, and notify destinations when the condition is met. Since the requirement is notification through a messaging webhook, the alert should use a webhook alert destination. Official Databricks extract: alerts “run queries on a schedule and notify you when a condition that you define is met.” Databricks notification documentation also states that admins can configure alternate notification destinations using webhooks.

The correct answer is C because Databricks SQL Editor is used to create and save SQL queries. A saved query can later be opened, reused, shared, visualized, and added to a dashboard. A dashboard is not the saved SQL statement itself; it is a reporting object that can contain query results and visualizations. Query History stores past executions, but it is not the correct object for saving a reusable SQL statement.

Official documentation extract used: Databricks states that the SQL editor can be used to “author queries” and “create visualizations.” It also states that the Save button “saves your query,” and query results can be added to a dashboard.

The correct answer is C because the task requires creating or replacing a managed table with an explicitly defined schema. In Databricks SQL, column definitions are placed directly after the table name inside parentheses. The USING clause is for specifying a data source format, not for defining columns. Option C correctly uses CREATE OR REPLACE TABLE database_name.table_name (...), which recreates the table if it already exists and creates an empty table with the specified schema.

Official documentation extract used: Databricks CREATE TABLE syntax supports [CREATE OR] REPLACE followed by the table name and a table_specification containing column identifiers and column types.

A data analyst can create multiple visualizations from the same query in Databricks SQL by clicking the + button next to the Results tab and selecting Visualization. Each visualization can have a different type, name, and configuration. To add a visualization to a dashboard, the data analyst can click the vertical ellipsis button beneath the visualization, select + Add to Dashboard, and choose an existing or new dashboard. The data analyst can repeat this process for each visualization they want to add to the same dashboard. References: Visualization in Databricks SQL, Visualize queries and create a dashboard in Databricks SQL

The Owner field in the table page shows the current owner of the table and allows the owner to change it to another user or group. To change the ownership of the table, the owner can click on the Owner field and select the new owner from the drop-down list. This will transfer the ownership of the table to the selected user or group and remove the previous owner from the list of table access control entries1. The other options are incorrect because:

A. Removing the owner’s account from the Owner field will not change the ownership of the table, but will make the table ownerless2.

B. Selecting All Users from the Owner field will not change the ownership of the table, but will grant all users access to the table3.

D. Selecting the Admins group from the Owner field will not change the ownership of the table, but will grant the Admins group access to the table3.

E. Removing all access from the Owner field will not change the ownership of the table, but will revoke all access to the table4. References:

1: Change table ownership

2: Ownerless tables

3: Table access control

4: Revoke access to a table

Databricks provides a user-friendly interface that allows data analysts to quickly upload small datasets, such as a 50-row CSV file, and create tables within Databricks SQL. The steps are as follows:​

Access the Data Upload Interface:

In the Databricks workspace, navigate to the sidebar and click on New > Add or upload data.​

Select Create or modify a table.​

Upload the CSV File:

Click on the browse button or drag and drop the CSV file directly onto the designated area.​

The interface supports uploading up to 10 files simultaneously, with a total size limit of 2 GB.​

Configure Table Settings:

After uploading, a preview of the data is displayed.​

Specify the table name, select the appropriate schema, and configure any additional settings as needed.​

Create the Table:

Once all configurations are set, click on the Create Table button to finalize the process.​

This method is efficient for quickly importing small datasets without the need for additional tools or complex configurations. Options B, C, and D involve more complex or manual processes that are unnecessary for this task.​

Option D is correct. Delta Live Tables / Lakeflow Declarative Pipelines supports expectations, which are rules used to validate data as it flows through ETL pipelines. These expectations provide automated visibility into data quality and can be configured to fail updates or drop invalid records. Unity Catalog governs data, Data Explorer/Catalog Explorer helps browse data, Delta Lake provides reliable table storage, and Auto Loader ingests files incrementally, but the pipeline-level automated data quality monitoring tool is Delta Live Tables expectations. Official Databricks extract: expectations “validate data as it flows through ETL pipelines” and provide “data quality metrics.”