Databricks Data Engineer Associate Practice Exam Q & A - Part 5

Question 41:

A data engineering manager uses a Databricks SQL query to monitor their team’s progress on fixes related to customer-reported bugs. The manager checks the results of the query every day, but they are manually rerunning the query each day and waiting for the results.

 

Options:

- A. They can schedule the query to run every 1 day from the Jobs UI.

- B. They can schedule the query to refresh every 1 day from the query’s page in Databricks SQL.

- C. They can schedule the query to run every 12 hours from the Jobs UI.

- D. They can schedule the query to refresh every 1 day from the SQL endpoint’s page in Databricks SQL.

- E. They can schedule the query to refresh every 12 hours from the SQL endpoint’s page in Databricks SQL.

Answer: 

B. They can schedule the query to refresh every 1 day from the query’s page in Databricks SQL.

Explanation: 

In Databricks SQL, you can schedule queries directly from the query’s page to refresh at a set interval, such as every day. This allows the manager to have the query automatically updated daily without manually rerunning it. Scheduling from the Jobs UI (Option A) is possible but less straightforward than the query page scheduling.

 

Question 42:

A data engineering team has been using a Databricks SQL query to monitor the performance of an ELT job. The ELT job is triggered by a specific number of input records being ready to process. The Databricks SQL query returns the number of minutes since the job’s most recent runtime.

Options:

- A. They can set up an Alert for the accompanying dashboard to notify them if the returned value is greater than 60.

- B. They can set up an Alert for the query to notify when the ELT job fails.

- C. They can set up an Alert for the accompanying dashboard to notify when it has not refreshed in 60 minutes.

- D. They can set up an Alert for the query to notify them if the returned value is greater than 60.

- E. This type of alerting is not possible in Databricks.

Answer: 

D. They can set up an Alert for the query to notify them if the returned value is greater than 60.

Explanation: 

Databricks SQL allows alerts to be configured based on query results. Since the query returns the minutes since the last job runtime, an alert can notify the team if this value exceeds 60, indicating that the job hasn’t run in over an hour. This is the most direct and effective solution.

 

Question 43:

A data engineering manager has noticed that each of the queries in a Databricks SQL dashboard takes a few minutes to update when they manually click the “Refresh” button. They are curious why this might be occurring, so a team member provides a variety of reasons on why the delay might be occurring.

Options:

- A. The SQL endpoint being used by each of the queries might need a few minutes to start up.

- B. The queries attached to the dashboard might take a few minutes to run under normal circumstances.

- C. The queries attached to the dashboard might first be checking to determine if new data is available.

- D. The Job associated with updating the dashboard might be using a non-pooled endpoint.

- E. The queries attached to the dashboard might all be connected to their own, unstarted Databricks clusters.

 

Answer: 

E. The queries attached to the dashboard might all be connected to their own, unstarted Databricks clusters.

Explanation: 

In Databricks SQL, dashboards typically run on a shared SQL endpoint, not separate clusters for each query. Therefore, the queries don’t connect to individual clusters. This option does not explain the delay, while all other options could potentially contribute to slower refresh times.

 

Question 44:

A new data engineer has started at a company. The data engineer has recently been added to the company’s Databricks workspace as new.engineer@company.com. The data engineer needs to be able to query the table `sales` in the database `retail`. The new data engineer already has been granted `USAGE` on the database `retail`.

Options:

- A. GRANT USAGE ON TABLE sales TO new.engineer@company.com;

- B. GRANT CREATE ON TABLE sales TO new.engineer@company.com;

- C. GRANT SELECT ON TABLE sales TO new.engineer@company.com;

- D. GRANT USAGE ON TABLE new.engineer@company.com TO sales;

- E. GRANT SELECT ON TABLE new.engineer@company.com TO sales;

Answer: 

C. GRANT SELECT ON TABLE sales TO new.engineer@company.com;

 Explanation: 

The data engineer needs permission to read data in the `sales` table, which requires `SELECT` privileges. The `USAGE` permission on the database allows access to the database itself, but not its tables, so adding `SELECT` for the `sales` table is necessary

 

Question 45:

A new data engineer new.engineer@company.com has been assigned to an ELT project. The new data engineer will need full privileges on the table `sales` to fully manage the project.

Options:

- A. GRANT ALL PRIVILEGES ON TABLE sales TO new.engineer@company.com;

- B. GRANT USAGE ON TABLE sales TO new.engineer@company.com;

- C. GRANT ALL PRIVILEGES ON TABLE new.engineer@company.com TO sales;

- D. GRANT SELECT ON TABLE sales TO new.engineer@company.com;

- E. GRANT SELECT CREATE MODIFY ON TABLE sales TO new.engineer@company.com;

 

Answer: 

A. GRANT ALL PRIVILEGES ON TABLE sales TO new.engineer@company.com;

Explanation: 

`GRANT ALL PRIVILEGES` provides the data engineer with complete control over the `sales` table, allowing them to manage all aspects of the ELT process, including modifications and querying. This level of access is required for the engineer to fully manage the project.