A data engineer needs to review the historical execution details for a specific job. Where in the Lakeflow Jobs UI should they navigate to see a list of all runs for that job?

Open the 'Data' page and select the output table of the job.

Go to the 'Clusters' page and select the cluster used by the job.

Open the job's detail page and click the 'Runs' tab.

Navigate to the 'SQL Warehouses' page and view the job's query history.

A data engineer notices that the execution time of a job has been gradually increasing over the last 10 runs. What does this pattern indicate?

A trend of worsening performance

A random fluctuation with no trend

A trend of improving performance

A data engineer is looking at the run history view for a job and sees a run with a status of 'Succeeded' but a duration of 0 seconds. What is the most likely explanation?

The job was triggered but skipped all tasks because the input data was empty.

The run history view is displaying the duration incorrectly due to a UI bug.

The job failed to start and the status is incorrectly marked as 'Succeeded'.

The job's cluster was terminated before the run could begin.

A junior data engineer needs to check the execution time of a specific job named 'daily_ingestion' that ran this morning. They are already logged into the Databricks workspace. What is the most direct way to find this information?

Navigate to Workflows, select the 'daily_ingestion' job, and open the 'Run history' tab.

Check the notebook's revision history to see when it was last executed.

Go to the SQL warehouse and query the system table for job run metrics.

Open the cluster's event log to find the job's start and end times.

DatabricksCertified Data Engineer Associate

Domain 6Objective 1

Identify Trends in Job Performance Using the Lakeflow Jobs Run History View to Compare Current Execution Times Against Historical Baselines. DATA-ENGINEER-ASSOCIATE Practice Questions (Page 1)

Part of the Troubleshooting, Monitoring, and Optimization domain, which accounts for 10% of the DATA-ENGINEER-ASSOCIATE exam. Databricks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~4–6 in this domain), expect 1–1 from this objective — we provide 23 practice questions to prepare you well beyond it. (estimate)

23questions here

5free pages

4concepts

10%of the exam

Questions 1–5

1foundation · easy
A data engineer needs to review the historical execution details for a specific job. Where in the Lakeflow Jobs UI should they navigate to see a list of all runs for that job?
Select an answer first
2foundation · easy
A data engineer notices that the execution time of a job has been gradually increasing over the last 10 runs. What does this pattern indicate?
Select an answer first
3foundation · easy
In the Lakeflow Jobs run history view, which of the following is a key metric displayed for each run?
Select an answer first
4application · medium
A data engineer is looking at the run history view for a job and sees a run with a status of 'Succeeded' but a duration of 0 seconds. What is the most likely explanation?
Select an answer first
5application · easy
A junior data engineer needs to check the execution time of a specific job named 'daily_ingestion' that ran this morning. They are already logged into the Databricks workspace. What is the most direct way to find this information?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to DATA-ENGINEER-ASSOCIATE

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Databricks. “DATA-ENGINEER-ASSOCIATE” is a trademark of its owner, used for identification only.