Try each one before opening the answer. Every option is explained, with the Databricks documentation page that proves it.
Question 1 · choose 1
A monitoring script built years ago reads state.result_state from Jobs API run responses to decide whether runs failed. A reviewer flags this field. Which field should the script read instead?
AThe repair_history array of the run
BThe status object of the run
CThe job_parameters array of the run
DThe trigger field of the run
Show the answer and why
AThe repair_history array of the run
Incorrect
Repair history lists repair attempts, not the run's current status.
BThe status object of the run
Correct
The Jobs API marks the state object as deprecated and says to use the status field.
CThe job_parameters array of the run
Incorrect
Parameters are the values passed to the run.
DThe trigger field of the run
Incorrect
The trigger says what started the run.
Run responses from the Jobs API keep a deprecated state object for compatibility; new code should use the status field to read the run's lifecycle and termination details.
A For each task ran its nested notebook once for each of 400 input tables, and seven iterations failed. The on-call engineer wants to list only those seven iterations and read the output of each. Where in the Jobs UI is this?
AIn the workspace Runs tab, filtered by the Error code of the failures
BIn the Graph view, which draws each iteration as its own task node
CIn the For each task's run history, using Only failed iterations
DIn the matrix view, which adds a row of cells for every iteration
Show the answer and why
AIn the workspace Runs tab, filtered by the Error code of the failures
Incorrect
The Runs tab lists job and pipeline runs, not the iterations inside one task run.
BIn the Graph view, which draws each iteration as its own task node
Incorrect
The graph shows one For each node with the nested task inside it, not a node per iteration.
CIn the For each task's run history, using Only failed iterations
Correct
The run history of a For each task is a table of the nested task's iterations; Only failed iterations narrows it, and an iteration's start or end time opens its output.
DIn the matrix view, which adds a row of cells for every iteration
Incorrect
The matrix view has one cell per task; clicking the For each cell opens the same table of iterations.
The task run history of a For each task is presented as a table of the nested task's iterations, opened from the For each node on the Job run details page or from its cell in the matrix view. Only failed iterations filters the table, and clicking the Start time or End time of an iteration shows its output.
In one run of a 20-task job, an engineer wants to see which tasks ran at the same time and which long task held up the end of the run. Which view of the job run details is made for this?
AThe Graph view, which draws how the tasks depend on each other
BThe Timeline view, which lays out the tasks' run times in order
CThe Finished runs count graph on the workspace Runs tab
DThe workspace Runs list, with its column of each run's duration
Show the answer and why
AThe Graph view, which draws how the tasks depend on each other
Incorrect
The graph shows dependencies and task details, not when each task ran.
BThe Timeline view, which lays out the tasks' run times in order
Correct
The timeline view helps identify tasks that take a long time and shows dependencies and overlap.
CThe Finished runs count graph on the workspace Runs tab
Incorrect
This graph counts finished runs over time, not tasks within a run.
DThe workspace Runs list, with its column of each run's duration
Incorrect
The Runs list shows whole runs, not the tasks inside one run.
The Job run details page has Graph, Timeline and List views. The timeline view helps identify tasks that take a long time to complete and shows dependencies and overlap, which helps debug and optimize a job.
A non-admin data engineer opens the Runs tab filtered to Jobs, but the Finished runs count graph shows nothing for them. What should they do?
AAsk for CAN MANAGE on every job
BSwitch the filter from Jobs to All
COpen the matrix view of a job
DClick Run as and select me
Show the answer and why
AAsk for CAN MANAGE on every job
Incorrect
The graph depends on the Run as filter, not job permissions.
BSwitch the filter from Jobs to All
Incorrect
The graph is not shown when All is selected.
COpen the matrix view of a job
Incorrect
The matrix view does not show the finished runs graph.
DClick Run as and select me
Correct
For non-admins, the graph appears after filtering Run as to me.
The Finished runs count graph appears when the list is filtered to Jobs or Pipelines. Admins see it for all runs; non-admins must click Run as and select me.