Noos
PT EN
RAN-DBDEA-00165
Ranvier · DBDEA

Exam DBDEA Topics: troubleshooting Difficulty: medium

A scheduled notebook task fails with an uncaught Python exception. The job run page shows only the exception type and a truncated message, and the engineer needs the complete traceback together with the driver's stdout and stderr output to debug it. Where should the engineer look?

Options (Reading Mode) Click to filter discussion →
  1. A. In the cluster's driver logs, opened from the Driver Logs tab or from delivered log storage
  2. B. Only on the engineer's local machine, because driver stdout and stderr are never retained by the platform
  3. C. In the Spark UI's Jobs and Stages tabs, which capture the complete Python stack trace of the failure
  4. D. In the cluster metrics charts, because Ganglia-style dashboards record application-level tracebacks
Reveal answer

Correct answer: In the cluster's driver logs, opened from the Driver Logs tab or from delivered log storage

Reference: https://docs.databricks.com/aws/en/compute/configure

02 — The Myelin Layer · Canonical Discussion

Where the exam tries to trick you — and how those who passed solved it.

0 Passed

contributed to this question

Answer Distractor Matrix Click an option to filter or open its dissection.
✦ Consolidated Synthesis (Wiki) rev. #1 (baseline) · CC BY-SA 4.0
Start synthesis for this question →

No community synthesis consolidated for this question yet. Below is the verifiable official starting point — if you passed the exam, open the option dissection.

Official Answer (A): In the cluster's driver logs, opened from the Driver Logs tab or from delivered log storage

⚓ Official Documentation Anchor: https://docs.databricks.com/aws/en/compute/configure
Ranvier · DBDEA

Contribute to this Question

Your contribution builds your Orbital Sheath

Peer contributions

No public contribution yet. Be the first who passed to explain why the distractors trick candidates — your contribution builds your Orbital Sheath.