Exam Bundle

An audit compares the deployed schedule to its reviewed script and an approved rollback restores the prior execution window. That result is evidence for another corrective change: Manage Agent job and schedule changes through controlled scripts and versioned configuration with documented approval. The alternative problem is: A team changes SQL Server Agent schedules through ad hoc T-SQL commands but never records who approved the change or its rollback. The current Timberline Foods issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

A controlled failed job produces a recorded failed outcome and a delivered notification to the designated on-call operator. That result is evidence for another corrective change: Configure Agent job failure alerts and notifications with the required Database Mail and operator settings where supported. The alternative problem is: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. The current Timberline Foods issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

The overnight run produces one verified import result and no duplicate execution or repeated rows appear in the job history. That result is evidence for another corrective change: Consolidate schedule definitions and implement idempotent task behavior or mutual exclusion for the recurring import. The alternative problem is: An Agent job has multiple overlapping schedules and duplicate nightly imports, causing a unique key violation every morning. The current Timberline Foods issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

Configure Agent job failure alerts and notifications with the required Database Mail and operator settings where supported. That relates to a separate SQL administration problem: A SQL Server Agent backup job fails each weekend but operators receive no notification and discover the missing backups only during an audit. The Eastshore Energy requirement is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

Consolidate schedule definitions and implement idempotent task behavior or mutual exclusion for the recurring import. That relates to a separate SQL administration problem: An Agent job has multiple overlapping schedules and duplicate nightly imports, causing a unique key violation every morning. The Eastshore Energy requirement is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

Manage Agent job and schedule changes through controlled scripts and versioned configuration with documented approval. That relates to a separate SQL administration problem: A team changes SQL Server Agent schedules through ad hoc T-SQL commands but never records who approved the change or its rollback. The Eastshore Energy requirement is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

The complete integrity task finishes within its approved window and its history shows no unintended repeated partial runs. That result is evidence for another corrective change: Split maintenance operations into bounded jobs or adjust the supported schedule and timeout policy based on measured duration. The alternative problem is: A long-running Agent integrity check is terminated by a standard timeout and reruns from the beginning, consuming the whole maintenance period. The current Eastshore Energy issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

The test Azure SQL Database receives the expected maintenance result without attempting to start an unsupported embedded Agent service. That result is evidence for another corrective change: Identify SQL Server Agent dependencies and redesign suitable recurring tasks using supported elastic jobs or Azure automation services. The alternative problem is: A migration from SQL Server to Azure SQL Database assumes every SQL Server Agent job will continue to run inside the single database service. The current Eastshore Energy issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

The scheduled maintenance completes while the job identity cannot perform an unrelated privileged server administration action. That result is evidence for another corrective change: Choose a least-privilege job owner or supported proxy/credential configuration and scope each job step's required permissions. The alternative problem is: A nightly Agent job uses a high-privilege SQL login for routine index maintenance even though a narrower execution context is possible. The current Eastshore Energy issue is instead: An operations team suspects an Agent job never started but examines application tables instead of checking service and job execution history. Its decisive acceptance evidence would be: The incident identifies the missing execution trigger and the next approved run generates an expected logged completion.

Add bounded concurrency, supported idempotent retries and diagnostic categorization to the Azure SQL provisioning workflow. That relates to a separate SQL administration problem: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. The Timberline Foods requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Set and verify the intended tenant, subscription, resource group and resource identifier before each Azure CLI deployment. That relates to a separate SQL administration problem: An Azure CLI deployment script succeeds in one subscription but modifies a similarly named database in another because its context is implicit. The Timberline Foods requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Detect configuration drift, update the approved declarative source and review the resulting deployment change set before reconciling. That relates to a separate SQL administration problem: A Bicep resource redeployment unexpectedly resets a database administrator setting that was edited manually after the last release. The Timberline Foods requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures. That result is evidence for another corrective change: Add bounded concurrency, supported idempotent retries and diagnostic categorization to the Azure SQL provisioning workflow. The alternative problem is: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. The current Timberline Foods issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

A deliberately failed dependency causes the pipeline to fail and a corrected deployment passes private DNS and SQL connection tests. That result is evidence for another corrective change: Monitor operation status and nested deployment errors, then require health and connectivity checks before declaring the release successful. The alternative problem is: An Azure resource deployment is recorded as finished even though a dependent private endpoint and DNS zone association failed. The current Timberline Foods issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

The redeployment preserves the intended governance configuration and a subsequent drift report shows no unauthorized change. That result is evidence for another corrective change: Detect configuration drift, update the approved declarative source and review the resulting deployment change set before reconciling. The alternative problem is: A Bicep resource redeployment unexpectedly resets a database administrator setting that was edited manually after the last release. The current Timberline Foods issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Provide distinct reviewed environment parameters and validated region-specific conditions for infrastructure automation. That relates to a separate SQL administration problem: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. The Granite SaaS requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Use non-destructive declarative update semantics and explicitly guard replacements and deletions with policy and approvals. That relates to a separate SQL administration problem: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. The Granite SaaS requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Remove plaintext secrets and reference supported secure parameter or key-store mechanisms with scoped deployment identities. That relates to a separate SQL administration problem: A database infrastructure template hardcodes production connection passwords in a parameter file committed to the repository. The Granite SaaS requirement is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. That approach does not directly establish the required fix; the requested acceptance evidence is: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections. That result is evidence for another corrective change: Combine resource deployment confirmation with target identity, DNS, firewall and database readiness post-deployment tests. The alternative problem is: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. The current Granite SaaS issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

The test rollout changes only intended region resources and a deployment diff confirms no unintended SKU changes elsewhere. That result is evidence for another corrective change: Provide distinct reviewed environment parameters and validated region-specific conditions for infrastructure automation. The alternative problem is: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. The current Granite SaaS issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures. That result is evidence for another corrective change: Add bounded concurrency, supported idempotent retries and diagnostic categorization to the Azure SQL provisioning workflow. The alternative problem is: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. The current Granite SaaS issue is instead: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. Its decisive acceptance evidence would be: A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template.

Provide distinct reviewed environment parameters and validated region-specific conditions for infrastructure automation. That relates to a separate SQL administration problem: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. The Granite SaaS requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

Use non-destructive declarative update semantics and explicitly guard replacements and deletions with policy and approvals. That relates to a separate SQL administration problem: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. The Granite SaaS requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

Use parameterized Bicep or ARM templates and a reviewed pipeline to provision reproducible SQL database resources. That relates to a separate SQL administration problem: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. The Granite SaaS requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

The test rollout changes only intended region resources and a deployment diff confirms no unintended SKU changes elsewhere. That result is evidence for another corrective change: Provide distinct reviewed environment parameters and validated region-specific conditions for infrastructure automation. The alternative problem is: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. The current Granite SaaS issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections. That result is evidence for another corrective change: Combine resource deployment confirmation with target identity, DNS, firewall and database readiness post-deployment tests. The alternative problem is: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. The current Granite SaaS issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures. That result is evidence for another corrective change: Add bounded concurrency, supported idempotent retries and diagnostic categorization to the Azure SQL provisioning workflow. The alternative problem is: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. The current Granite SaaS issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

Detect configuration drift, update the approved declarative source and review the resulting deployment change set before reconciling. That relates to a separate SQL administration problem: A Bicep resource redeployment unexpectedly resets a database administrator setting that was edited manually after the last release. The Oakridge Public Services requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

Combine resource deployment confirmation with target identity, DNS, firewall and database readiness post-deployment tests. That relates to a separate SQL administration problem: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. The Oakridge Public Services requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

Monitor operation status and nested deployment errors, then require health and connectivity checks before declaring the release successful. That relates to a separate SQL administration problem: An Azure resource deployment is recorded as finished even though a dependent private endpoint and DNS zone association failed. The Oakridge Public Services requirement is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. That approach does not directly establish the required fix; the requested acceptance evidence is: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

A harmless property update completes without replacing the database resource or losing a test record. That result is evidence for another corrective change: Use non-destructive declarative update semantics and explicitly guard replacements and deletions with policy and approvals. The alternative problem is: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. The current Oakridge Public Services issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

A deliberately failed dependency causes the pipeline to fail and a corrected deployment passes private DNS and SQL connection tests. That result is evidence for another corrective change: Monitor operation status and nested deployment errors, then require health and connectivity checks before declaring the release successful. The alternative problem is: An Azure resource deployment is recorded as finished even though a dependent private endpoint and DNS zone association failed. The current Oakridge Public Services issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.

The test rollout changes only intended region resources and a deployment diff confirms no unintended SKU changes elsewhere. That result is evidence for another corrective change: Provide distinct reviewed environment parameters and validated region-specific conditions for infrastructure automation. The alternative problem is: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. The current Oakridge Public Services issue is instead: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. Its decisive acceptance evidence would be: The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied.