Exam Bundle

The on-call group receives a message after the defined duration would demonstrate the separate action Configure a duration-based warning or supported monitoring alert, which addresses “A job unexpectedly exceeds its runtime SLA without failing.” It does not verify the requirement “A retry event should not notify customers as if the entire workflow failed” following Differentiate task retries from terminal job run failure notifications.

That observation is a valid indicator for “A job succeeded but produced no records and needs a semantic data-quality alert” when using Publish a validated row-count metric and alert on the threshold. The scenario instead tests “A retry event should not notify customers as if the entire workflow failed”; the relevant result is Only final exhausted failure triggers the customer-facing incident notice.

That observation is a valid indicator for “The team must trigger remediation when a job's retry budget is exhausted” when using Use Jobs run-state monitoring with an authorized webhook or event action. The scenario instead tests “A retry event should not notify customers as if the entire workflow failed”; the relevant result is Only final exhausted failure triggers the customer-facing incident notice.

The alternative Pass the intended Databricks CLI profile or host configuration has a distinct purpose—A CLI script must use a production workspace rather than a developer's default profile. It would not establish the required outcome (A monitoring script needs the state of a specific current job run); the necessary verification concerns The response reports the authoritative run lifecycle state.

Use the Jobs API run listing with relevant filters and pagination belongs to the separate case “Automation needs to list recent failed runs for a configured job,” where The result includes the desired failed runs without missing later pages would be expected. That differs from the condition in this stem: “A monitoring script needs the state of a specific current job run.”

This action solves a different issue: “A monitoring identity should not have permissions to edit production jobs.” Its normal signal is The identity reads run status but fails job mutation requests. Here the requested behavior is “A monitoring script needs the state of a specific current job run,” so that signal is not sufficient.

CLI responses identify the correct production workspace pertains to a different control (Pass the intended Databricks CLI profile or host configuration) and a different need (A CLI script must use a production workspace rather than a developer's default profile). It cannot establish that Call the supported Jobs API run detail endpoint using its run ID met the stated goal.

This signal belongs to the adjacent case “A monitoring identity should not have permissions to edit production jobs,” whose remedy is Grant read/monitor privileges only to the service principal. The observed result for the present requirement is The response reports the authoritative run lifecycle state.

This signal belongs to the adjacent case “Automation needs to list recent failed runs for a configured job,” whose remedy is Use the Jobs API run listing with relevant filters and pagination. The observed result for the present requirement is The response reports the authoritative run lifecycle state.

Query the supported pipelines API for update details belongs to the separate case “A nightly dashboard should report active production pipeline update status,” where The response identifies pending, running and terminal update states would be expected. That differs from the condition in this stem: “Automation needs to list recent failed runs for a configured job.”

Pass the intended Databricks CLI profile or host configuration belongs to the separate case “A CLI script must use a production workspace rather than a developer's default profile,” where CLI responses identify the correct production workspace would be expected. That differs from the condition in this stem: “Automation needs to list recent failed runs for a configured job.”

Grant read/monitor privileges only to the service principal is appropriate when “A monitoring identity should not have permissions to edit production jobs”; it would be verified by The identity reads run status but fails job mutation requests. It does not directly satisfy “Automation needs to list recent failed runs for a configured job,” whose relevant acceptance evidence is The result includes the desired failed runs without missing later pages.

That observation is a valid indicator for “A CLI script must use a production workspace rather than a developer's default profile” when using Pass the intended Databricks CLI profile or host configuration. The scenario instead tests “Automation needs to list recent failed runs for a configured job”; the relevant result is The result includes the desired failed runs without missing later pages.

This signal belongs to the adjacent case “A monitoring script needs the state of a specific current job run,” whose remedy is Call the supported Jobs API run detail endpoint using its run ID. The observed result for the present requirement is The result includes the desired failed runs without missing later pages.

The identity reads run status but fails job mutation requests would demonstrate the separate action Grant read/monitor privileges only to the service principal, which addresses “A monitoring identity should not have permissions to edit production jobs.” It does not verify the requirement “Automation needs to list recent failed runs for a configured job” following Use the Jobs API run listing with relevant filters and pagination.

Grant read/monitor privileges only to the service principal belongs to the separate case “A monitoring identity should not have permissions to edit production jobs,” where The identity reads run status but fails job mutation requests would be expected. That differs from the condition in this stem: “A nightly dashboard should report active production pipeline update status.”

Pass the intended Databricks CLI profile or host configuration is appropriate when “A CLI script must use a production workspace rather than a developer's default profile”; it would be verified by CLI responses identify the correct production workspace. It does not directly satisfy “A nightly dashboard should report active production pipeline update status,” whose relevant acceptance evidence is The response identifies pending, running and terminal update states.

The alternative Use the Jobs API run listing with relevant filters and pagination has a distinct purpose—Automation needs to list recent failed runs for a configured job. It would not establish the required outcome (A nightly dashboard should report active production pipeline update status); the necessary verification concerns The response identifies pending, running and terminal update states.

The identity reads run status but fails job mutation requests would demonstrate the separate action Grant read/monitor privileges only to the service principal, which addresses “A monitoring identity should not have permissions to edit production jobs.” It does not verify the requirement “A nightly dashboard should report active production pipeline update status” following Query the supported pipelines API for update details.

That observation is a valid indicator for “Automation needs to list recent failed runs for a configured job” when using Use the Jobs API run listing with relevant filters and pagination. The scenario instead tests “A nightly dashboard should report active production pipeline update status”; the relevant result is The response identifies pending, running and terminal update states.

This signal belongs to the adjacent case “A CLI script must use a production workspace rather than a developer's default profile,” whose remedy is Pass the intended Databricks CLI profile or host configuration. The observed result for the present requirement is The response identifies pending, running and terminal update states.

Grant read/monitor privileges only to the service principal belongs to the separate case “A monitoring identity should not have permissions to edit production jobs,” where The identity reads run status but fails job mutation requests would be expected. That differs from the condition in this stem: “A CLI script must use a production workspace rather than a developer's default profile.”

Query the supported pipelines API for update details belongs to the separate case “A nightly dashboard should report active production pipeline update status,” where The response identifies pending, running and terminal update states would be expected. That differs from the condition in this stem: “A CLI script must use a production workspace rather than a developer's default profile.”

Call the supported Jobs API run detail endpoint using its run ID is appropriate when “A monitoring script needs the state of a specific current job run”; it would be verified by The response reports the authoritative run lifecycle state. It does not directly satisfy “A CLI script must use a production workspace rather than a developer's default profile,” whose relevant acceptance evidence is CLI responses identify the correct production workspace.

The identity reads run status but fails job mutation requests would demonstrate the separate action Grant read/monitor privileges only to the service principal, which addresses “A monitoring identity should not have permissions to edit production jobs.” It does not verify the requirement “A CLI script must use a production workspace rather than a developer's default profile” following Pass the intended Databricks CLI profile or host configuration.

The result includes the desired failed runs without missing later pages pertains to a different control (Use the Jobs API run listing with relevant filters and pagination) and a different need (Automation needs to list recent failed runs for a configured job). It cannot establish that Pass the intended Databricks CLI profile or host configuration met the stated goal.

This signal belongs to the adjacent case “A nightly dashboard should report active production pipeline update status,” whose remedy is Query the supported pipelines API for update details. The observed result for the present requirement is CLI responses identify the correct production workspace.

This action solves a different issue: “Automation needs to list recent failed runs for a configured job.” Its normal signal is The result includes the desired failed runs without missing later pages. Here the requested behavior is “A monitoring identity should not have permissions to edit production jobs,” so that signal is not sufficient.

The alternative Call the supported Jobs API run detail endpoint using its run ID has a distinct purpose—A monitoring script needs the state of a specific current job run. It would not establish the required outcome (A monitoring identity should not have permissions to edit production jobs); the necessary verification concerns The identity reads run status but fails job mutation requests.

Query the supported pipelines API for update details is appropriate when “A nightly dashboard should report active production pipeline update status”; it would be verified by The response identifies pending, running and terminal update states. It does not directly satisfy “A monitoring identity should not have permissions to edit production jobs,” whose relevant acceptance evidence is The identity reads run status but fails job mutation requests.

That observation is a valid indicator for “A CLI script must use a production workspace rather than a developer's default profile” when using Pass the intended Databricks CLI profile or host configuration. The scenario instead tests “A monitoring identity should not have permissions to edit production jobs”; the relevant result is The identity reads run status but fails job mutation requests.

That observation is a valid indicator for “A monitoring script needs the state of a specific current job run” when using Call the supported Jobs API run detail endpoint using its run ID. The scenario instead tests “A monitoring identity should not have permissions to edit production jobs”; the relevant result is The identity reads run status but fails job mutation requests.

The response identifies pending, running and terminal update states would demonstrate the separate action Query the supported pipelines API for update details, which addresses “A nightly dashboard should report active production pipeline update status.” It does not verify the requirement “A monitoring identity should not have permissions to edit production jobs” following Grant read/monitor privileges only to the service principal.