100% Latest & Updated Databricks Certified Data Engineer Associate Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 470
A multi-task job reports failed, and the gold task was skipped because silver did not complete. Which configuration or engineering action would most directly implement the requirement?
- Compare run timeline and task events for start delay versus actual execution.
- Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join.
- Inspect recent job run history with input volumes, duration and compute configuration.
- Open the run graph, identify the failed silver node and inspect its logs before retrying gold.
Explanation
Correct Answer
D:Open the run graph, identify the failed silver node and inspect its logs before retrying gold. Fixing the silver failure allows the downstream gold task to run on a successful rerun.
Incorrect Answers
A:If a reporting workflow shows longer total time even though its transformation task duration is unchanged, “Compare run timeline and task events for start delay versus actual execution” may be the appropriate response. Open the run graph, identify the failed silver node and inspect its logs before retrying gold.
B:A Spark SQL job creates a very large shuffle between a fact table and a tiny dimension. In those circumstances, “Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join” fits. Open the run graph, identify the failed silver node and inspect its logs before retrying gold.
C:When a customer event job normally completes in 12 minutes but now takes 35 while processing similar input volume, “Inspect recent job run history with input volumes, duration and compute configuration” could be relevant. Open the run graph, identify the failed silver node and inspect its logs before retrying gold.
Question 471
A multi-task job reports failed, and the gold task was skipped because silver did not complete. Which test would establish that the change worked as intended?
- Fixing the silver failure allows the downstream gold task to run on a successful rerun.
- Representative customer filters scan less relevant data after clustering is applied.
- The offending skewed key or partition is identified and an appropriate strategy can be tested.
- The maintenance history shows eligible optimize/analyze/vacuum activity according to the service.
Explanation
Correct Answer
A:Fixing the silver failure allows the downstream gold task to run on a successful rerun.
Incorrect Answers
B:When a transaction table receives frequent small writes and common queries filter on customer_id, “Representative customer filters scan less relevant data after clustering is applied” could be relevant. Fixing the silver failure allows the downstream gold task to run on a successful rerun.
C:If a Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes, “The offending skewed key or partition is identified and an appropriate strategy can be tested” may be the appropriate response. Fixing the silver failure allows the downstream gold task to run on a successful rerun.
D:A Unity Catalog managed table should receive automated maintenance without scheduling a custom OPTIMIZE notebook. In those circumstances, “The maintenance history shows eligible optimize/analyze/vacuum activity according to the service” fits. Fixing the silver failure allows the downstream gold task to run on a successful rerun.
Question 472
A multi-task job reports failed, and the gold task was skipped because silver did not complete. The team observes: Engineers keep rerunning the skipped gold node without resolving source failure. Which configuration or design gap best explains the symptom?
- The table was not eligible or predictive optimization was not enabled for the intended scope.
- The investigation used a single current wall time without the historical baseline.
- The root cause is a Monday-specific source or task behavior that cluster size alone did not address.
- The real failure was in an upstream prerequisite task.
Explanation
Correct Answer
D:The real failure was in an upstream prerequisite task. Open the run graph, identify the failed silver node and inspect its logs before retrying gold.
Incorrect Answers
A:When a Unity Catalog managed table should receive automated maintenance without scheduling a custom OPTIMIZE notebook, “The table was not eligible or predictive optimization was not enabled for the intended scope” could be relevant. The real failure was in an upstream prerequisite task.
B:If a customer event job normally completes in 12 minutes but now takes 35 while processing similar input volume, “The investigation used a single current wall time without the historical baseline” may be the appropriate response. The real failure was in an upstream prerequisite task.
C:A morning billing run misses its SLA on Mondays but meets it the rest of the week. In those circumstances, “The root cause is a Monday-specific source or task behavior that cluster size alone did not address” fits. The real failure was in an upstream prerequisite task.
Question 473
An ingestion workflow has a steadily increasing failure rate despite unchanged task definitions. Which architecture or engineering decision best fits this scenario?
- Align run-history metrics with deployment commit and resource configuration.
- Track Lakeflow Jobs failure-rate and task-status trends across runs.
- Investigate memory pressure and shuffle spill counters in Spark UI.
- Investigate skewed join keys and stage-level task metrics.
Explanation
Correct Answer
B:Track Lakeflow Jobs failure-rate and task-status trends across runs. The incident report identifies which task and error class is worsening.
Incorrect Answers
A:If a once-fast pipeline slowed after an approved code release and must be compared with its previous revision, “Align run-history metrics with deployment commit and resource configuration” may be the appropriate response. Track Lakeflow Jobs failure-rate and task-status trends across runs.
C:When a data transformation repeatedly writes huge local temporary spill files during aggregation, “Investigate memory pressure and shuffle spill counters in Spark UI” could be relevant. Track Lakeflow Jobs failure-rate and task-status trends across runs.
D:If a Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes, “Investigate skewed join keys and stage-level task metrics” may be the appropriate response. Track Lakeflow Jobs failure-rate and task-status trends across runs.
Question 474
An ingestion workflow has a steadily increasing failure rate despite unchanged task definitions. Which implementation step is most appropriate before production use?
- Inspect recent job run history with input volumes, duration and compute configuration.
- Use Spark UI task distributions and shuffle read records to identify the oversized partition.
- Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join.
- Review Jobs UI run history and failed task details over a bounded period.
Explanation
Correct Answer
D:Review Jobs UI run history and failed task details over a bounded period. The incident report identifies which task and error class is worsening.
Incorrect Answers
A:A customer event job normally completes in 12 minutes but now takes 35 while processing similar input volume. In those circumstances, “Inspect recent job run history with input volumes, duration and compute configuration” fits. Review Jobs UI run history and failed task details over a bounded period.
B:When a Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes, “Use Spark UI task distributions and shuffle read records to identify the oversized partition” could be relevant. Review Jobs UI run history and failed task details over a bounded period.
C:If a Spark SQL job creates a very large shuffle between a fact table and a tiny dimension, “Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join” may be the appropriate response. Review Jobs UI run history and failed task details over a bounded period.
Question 475
An ingestion workflow has a steadily increasing failure rate despite unchanged task definitions. Which acceptance test provides the strongest evidence that the intended outcome has been achieved?
- The first slow run corresponds to a traceable change and comparable input workload.
- The additional time is attributed to queuing or startup rather than an invented SQL regression.
- A compatible dependency fixes the import error while bounded driver collection fixes the memory error.
- The incident report identifies which task and error class is worsening.
Explanation
Correct Answer
D:The incident report identifies which task and error class is worsening.
Incorrect Answers
A:When a once-fast pipeline slowed after an approved code release and must be compared with its previous revision, “The first slow run corresponds to a traceable change and comparable input workload” could be relevant. The incident report identifies which task and error class is worsening.
B:If a reporting workflow shows longer total time even though its transformation task duration is unchanged, “The additional time is attributed to queuing or startup rather than an invented SQL regression” may be the appropriate response. The incident report identifies which task and error class is worsening.
C:A notebook run fails to import a Python package after a cluster runtime upgrade, then a later run exhausts driver memory. In those circumstances, “A compatible dependency fixes the import error while bounded driver collection fixes the memory error” fits. The incident report identifies which task and error class is worsening.
Question 476
An ingestion workflow has a steadily increasing failure rate despite unchanged task definitions. The team observes: A weekly average hides a cluster of repeated failures in one source task. Which root cause should be addressed first given this evidence?
- The team summarized only successful run durations and ignored failures.
- A hot key concentrates data into one shuffle partition.
- The aggregation working set exceeds effective task memory or partition balance.
- The compute resource cannot be provisioned under current capacity or policy.
Explanation
Correct Answer
A:The team summarized only successful run durations and ignored failures. Review Jobs UI run history and failed task details over a bounded period.
Incorrect Answers
B:A Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes. In those circumstances, “A hot key concentrates data into one shuffle partition” fits. The team summarized only successful run durations and ignored failures.
C:When a data transformation repeatedly writes huge local temporary spill files during aggregation, “The aggregation working set exceeds effective task memory or partition balance” could be relevant. The team summarized only successful run durations and ignored failures.
D:If a new job cluster remains in a starting state and the job never reaches the first notebook cell, “The compute resource cannot be provisioned under current capacity or policy” may be the appropriate response. The team summarized only successful run durations and ignored failures.
Question 477
An upstream notebook succeeded but a downstream report task is stuck waiting and no one knows why. Which technical design is most appropriate for the stated constraint?
- Inspect DAG dependency edges and run status, not just the dashboard's last refresh time.
- Separate incompatible library dependencies from driver-memory failures using task and cluster evidence.
- Investigate memory pressure and shuffle spill counters in Spark UI.
- Investigate skewed join keys and stage-level task metrics.
Explanation
Correct Answer
A:Inspect DAG dependency edges and run status, not just the dashboard's last refresh time. The exact unsatisfied dependency is visible and corrected without changing reporting logic.
Incorrect Answers
B:When a notebook run fails to import a Python package after a cluster runtime upgrade, then a later run exhausts driver memory, “Separate incompatible library dependencies from driver-memory failures using task and cluster evidence” could be relevant. Inspect DAG dependency edges and run status, not just the dashboard's last refresh time.
C:If a data transformation repeatedly writes huge local temporary spill files during aggregation, “Investigate memory pressure and shuffle spill counters in Spark UI” may be the appropriate response. Inspect DAG dependency edges and run status, not just the dashboard's last refresh time.
D:A Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes. In those circumstances, “Investigate skewed join keys and stage-level task metrics” fits. Inspect DAG dependency edges and run status, not just the dashboard's last refresh time.
Question 478
An upstream notebook succeeded but a downstream report task is stuck waiting and no one knows why. Which action should the engineer perform to establish the intended control?
- Define a supported CLUSTER BY key and run or enable the documented optimization workflow.
- Filter past runs by day and compare per-task durations and input counts.
- Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join.
- Open the task graph and check every required predecessor and run-if condition.
Explanation
Correct Answer
D:Open the task graph and check every required predecessor and run-if condition. The exact unsatisfied dependency is visible and corrected without changing reporting logic.
Incorrect Answers
A:When a transaction table receives frequent small writes and common queries filter on customer_id, “Define a supported CLUSTER BY key and run or enable the documented optimization workflow” could be relevant. Open the task graph and check every required predecessor and run-if condition.
B:If a morning billing run misses its SLA on Mondays but meets it the rest of the week, “Filter past runs by day and compare per-task durations and input counts” may be the appropriate response. Open the task graph and check every required predecessor and run-if condition.
C:A Spark SQL job creates a very large shuffle between a fact table and a tiny dimension. In those circumstances, “Use Spark UI and SQL physical plan to compare sort-merge shuffle with eligible broadcast join” fits. Open the task graph and check every required predecessor and run-if condition.
Question 479
An upstream notebook succeeded but a downstream report task is stuck waiting and no one knows why. Which observation best proves the workload meets its requirement?
- An approved capacity or policy correction lets the cluster start and execute the task.
- The exact unsatisfied dependency is visible and corrected without changing reporting logic.
- The slowdown can be assigned to the specific run and task where elapsed time increased.
- The additional time is attributed to queuing or startup rather than an invented SQL regression.
Explanation
Correct Answer
B:The exact unsatisfied dependency is visible and corrected without changing reporting logic.
Incorrect Answers
A:If a new job cluster remains in a starting state and the job never reaches the first notebook cell, “An approved capacity or policy correction lets the cluster start and execute the task” may be the appropriate response. The exact unsatisfied dependency is visible and corrected without changing reporting logic.
C:When a customer event job normally completes in 12 minutes but now takes 35 while processing similar input volume, “The slowdown can be assigned to the specific run and task where elapsed time increased” could be relevant. The exact unsatisfied dependency is visible and corrected without changing reporting logic.
D:If a reporting workflow shows longer total time even though its transformation task duration is unchanged, “The additional time is attributed to queuing or startup rather than an invented SQL regression” may be the appropriate response. The exact unsatisfied dependency is visible and corrected without changing reporting logic.
Question 480
An upstream notebook succeeded but a downstream report task is stuck waiting and no one knows why. The team observes: The dashboard appears stale although all SQL statements are valid. Which underlying cause most directly explains this failure?
- A prerequisite or condition branch prevented the reporting task from running.
- A hot key concentrates data into one shuffle partition.
- The root cause is a Monday-specific source or task behavior that cluster size alone did not address.
- The analysis confused end-to-end job time with SQL execution time.
Explanation
Correct Answer
A:A prerequisite or condition branch prevented the reporting task from running. Open the task graph and check every required predecessor and run-if condition.
Incorrect Answers
B:When a Spark join stage has one task that runs far longer than peer tasks and processes most shuffle bytes, “A hot key concentrates data into one shuffle partition” could be relevant. A prerequisite or condition branch prevented the reporting task from running.
C:If a morning billing run misses its SLA on Mondays but meets it the rest of the week, “The root cause is a Monday-specific source or task behavior that cluster size alone did not address” may be the appropriate response. A prerequisite or condition branch prevented the reporting task from running.
D:A reporting workflow shows longer total time even though its transformation task duration is unchanged. In those circumstances, “The analysis confused end-to-end job time with SQL execution time” fits. A prerequisite or condition branch prevented the reporting task from running.
Certified Data Engineer Associate Practice Tests