DATABRICKS-DEA Question 97

Community Discussion

Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.

• Chose A0

  - Correct answer : A — Open the job's run history and compare the total duration bars across recent runs against the historical baseline shown in the Matrix or Runs list view. A . The run history views display each run's total duration alongside prior runs, so lining up recent bars against the historical pattern is the direct way to confirm a 12-minute job is now consistently taking 40 minutes. This does not require leaving the Jobs UI at all. B . Stage-level shuffle metrics can help explain why a run is slow, but they are not needed just to confirm that a duration trend exists, and reading only the most recent run would miss the comparison against the historical baseline entirely. C . The Jobs UI does report run duration for every run, so this understates what the UI provides and sends the engineer to a source that does not track run-over-run trends the way the run history view does. D . Repair run reruns only the tasks that failed in a specific past run, and since every recent run already succeeded there is nothing to repair; it also would not establish a historical duration baseline.