Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Databricks Certified Data Engineer Professional · Databricks
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
- Correct answer : A — Open the Executors tab, locate the row for that executor's ID, and click the link in its Thread Dump column to capture a snapshot of every thread's current state. A . The Executors tab exposes a Thread Dump link per executor that captures a live snapshot of every thread's stack trace and state on that JVM, which is exactly the mechanism designed for identifying where a specific executor is stuck. B . A task-level Logs link streams stdout/stderr application log lines for that task, but log output only shows what the code explicitly printed; it does not capture the live thread stack state needed to see exactly where execution is currently blocked. C . The SQL tab's Explain option renders the logical or physical query plan for an operator; it describes what the query intends to compute, not the live runtime thread state of a particular executor process. D . The DAG visualization on the Jobs tab shows stage dependencies and progress, and hovering over a node does not surface per-executor CPU/memory gauges or thread stack traces for diagnosing a hang.