Exam Bundle

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

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 Granite SaaS issue is instead: A multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. Its decisive acceptance evidence would be: The test rollout changes only intended region resources and a deployment diff confirms no unintended SKU changes elsewhere.

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 multiregion database rollout uses one shared production parameter set for every environment and accidentally changes the secondary SQL region's SKU. Its decisive acceptance evidence would be: The test rollout changes only intended region resources and a deployment diff confirms no unintended SKU changes elsewhere.

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 Granite SaaS requirement is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Granite SaaS requirement is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Granite SaaS issue is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. Its decisive acceptance evidence would be: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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

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 CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. Its decisive acceptance evidence would be: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Oakridge Public Services requirement is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Oakridge Public Services requirement is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Oakridge Public Services requirement is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. That approach does not directly establish the required fix; the requested acceptance evidence is: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. Its decisive acceptance evidence would be: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

The CLI execution log identifies the correct target ID and the unchanged comparison subscription passes a post-run inventory check. That result is evidence for another corrective change: Set and verify the intended tenant, subscription, resource group and resource identifier before each Azure CLI deployment. The alternative problem is: An Azure CLI deployment script succeeds in one subscription but modifies a similarly named database in another because its context is implicit. The current Oakridge Public Services issue is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. Its decisive acceptance evidence would be: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied. That result is evidence for another corrective change: Use an appropriate automation identity and narrowly scoped Azure PowerShell commands to apply approved resource changes. The alternative problem is: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. The current Oakridge Public Services issue is instead: A CI pipeline reports a SQL deployment as successful immediately after ARM accepts it but client applications cannot connect to the new SQL endpoint. Its decisive acceptance evidence would be: A simulated unreachable endpoint causes the deployment job to fail and the next healthy environment passes functional SQL connections.

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 Oakridge Public Services requirement is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

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 automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

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 Oakridge Public Services requirement is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template. That result is evidence for another corrective change: Use parameterized Bicep or ARM templates and a reviewed pipeline to provision reproducible SQL database resources. The alternative problem is: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. The current Oakridge Public Services issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

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 Oakridge Public Services issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied. That result is evidence for another corrective change: Use an appropriate automation identity and narrowly scoped Azure PowerShell commands to apply approved resource changes. The alternative problem is: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. The current Oakridge Public Services issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

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 Westhaven Retail requirement is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

Use an appropriate automation identity and narrowly scoped Azure PowerShell commands to apply approved resource changes. That relates to a separate SQL administration problem: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. The Westhaven Retail requirement is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

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 Westhaven Retail requirement is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. That approach does not directly establish the required fix; the requested acceptance evidence is: A harmless property update completes without replacing the database resource or losing a test record.

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 Westhaven Retail issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

The automation scales only the intended SQL resource and a test request against a protected neighboring resource is denied. That result is evidence for another corrective change: Use an appropriate automation identity and narrowly scoped Azure PowerShell commands to apply approved resource changes. The alternative problem is: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. The current Westhaven Retail issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

The deployed database works through its authorized secret source and no reusable database password exists in the reviewed repository. That result is evidence for another corrective change: Remove plaintext secrets and reference supported secure parameter or key-store mechanisms with scoped deployment identities. The alternative problem is: A database infrastructure template hardcodes production connection passwords in a parameter file committed to the repository. The current Westhaven Retail issue is instead: An automation script deletes and recreates Azure SQL resources whenever a harmless property changes, risking unnecessary data loss. Its decisive acceptance evidence would be: A harmless property update completes without replacing the database resource or losing a test record.

Use an appropriate automation identity and narrowly scoped Azure PowerShell commands to apply approved resource changes. That relates to a separate SQL administration problem: An administrator runs Azure PowerShell under a personal account with excessive rights for a recurring database scale adjustment. The Westhaven Retail requirement is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. That approach does not directly establish the required fix; the requested acceptance evidence is: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.

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 Westhaven Retail requirement is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. That approach does not directly establish the required fix; the requested acceptance evidence is: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.

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 Westhaven Retail requirement is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. That approach does not directly establish the required fix; the requested acceptance evidence is: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.

A clean development and test deployment produce the intended SKU, identity and network properties from the same versioned template. That result is evidence for another corrective change: Use parameterized Bicep or ARM templates and a reviewed pipeline to provision reproducible SQL database resources. The alternative problem is: A team deploys Azure SQL Database infrastructure by manually copying portal screenshots, creating inconsistent database settings across stages. The current Westhaven Retail issue is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. Its decisive acceptance evidence would be: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.

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 Westhaven Retail issue is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. Its decisive acceptance evidence would be: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.

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 Westhaven Retail issue is instead: A subscription rollout hits deployment quota errors because concurrent scripts create many database resources without retry or failure classification. Its decisive acceptance evidence would be: The controlled load completes after transient throttling without duplicate SQL resources or unreviewed permanent failures.