DATABRICKS-DEA Question 109

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 — The driver logs for stack traces mentioning the failing process, combined with the Spark UI Executors tab for per-node memory and garbage-collection metrics. A . Driver logs surface the actual stack trace and error message that identify which process ran out of memory, while the Spark UI's Executors tab shows per-node memory usage and garbage-collection time that reveal whether individual executors were under memory pressure. Together these two sources give the most direct, process-level evidence needed to localize an out-of-memory failure. B . Compute cost reflects how much a node ran and what instance type it used, not how much memory it consumed or whether it failed, so a billing dashboard cannot distinguish a driver failure from an executor failure. Cost data is unrelated to memory diagnostics. C . The audit log is built for tracking user actions and commands for governance purposes and does not record memory allocation or process-level errors, so it cannot help localize an out-of-memory failure to the driver or an executor. D . An autoscaling history graph shows how many executors were attached at a given time, which is useful for capacity planning but does not report memory usage on any individual node, so it cannot show which process exhausted its memory.