Question 710
An Azure SQL operations team investigates: An architect evaluates a Fabric task orchestration approach instead of installing an operating-system job scheduler inside the service. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (An architect evaluates a Fabric task orchestration approach instead of installing an operating-system job scheduler inside the service.) is: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience. It directly tests whether the remediation (For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: An architect evaluates a Fabric task orchestration approach instead of installing an operating-system job scheduler inside the service. The specific supported administrative response is: For SQL database in Microsoft Fabric, use supported Fabric pipelines, notebooks or recurring orchestration rather than assuming a traditional SQL Server Agent service. The technical risk is: Moving automation from SQL Server to a Fabric-managed SQL database without adapting its scheduling mechanism can leave tasks unexecuted. Confirm the correction with: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
Incorrect Answers
Troubleshooting job steps and retry behavior (4.1) would demonstrate or implement: A controlled rerun identifies the previous failing step and completes after the specific cause is corrected. The case states: the targeted corrective action AND the evidence that verifies it. The most direct paired action and test is: The Fabric pipeline or scheduled task runs against the intended database and its status is visible in the Fabric monitoring experience.
Azure cli SQL resource provisioning (4.2) addresses another technical failure: A command without correct scope can deploy resources to the wrong region or subscription despite succeeding. This choice can be useful for that problem, but it does not establish the Fabric SQL database pipelines and recurring tasks (4.3) control being assessed here.
Elastic jobs across azure SQL databases (4.3) addresses another technical failure: SQL Server Agent is not a feature of Azure SQL Database, and per-database ad hoc scripts can be hard to govern at scale. The required paired action and test concerns Fabric SQL database pipelines and recurring tasks (4.3); a passing result for this alternative could leave that requirement unresolved.