Exam Bundle

The restored environment reports the expected guest and engine patch levels and completes application regression and rollback checks. That result is evidence for another corrective change: Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. The alternative problem is: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The current Alpine Healthcare issue is instead: A hybrid SQL Server estate is moved to Azure without checking collation, network latency or client drivers required by its linked workloads. Its decisive acceptance evidence would be: Connectivity, collation-sensitive queries and required drivers pass controlled pre-production checks against the documented inventory.

The migrated test workload executes its scheduled Agent job on the managed instance and the dependency inventory has no unsupported features. That result is evidence for another corrective change: Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. The alternative problem is: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The current Alpine Healthcare issue is instead: A hybrid SQL Server estate is moved to Azure without checking collation, network latency or client drivers required by its linked workloads. Its decisive acceptance evidence would be: Connectivity, collation-sensitive queries and required drivers pass controlled pre-production checks against the documented inventory.

A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable. That result is evidence for another corrective change: Design range-based table partitioning using a suitable partition function and scheme aligned with retention and query-access requirements. The alternative problem is: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. The current Alpine Healthcare issue is instead: A hybrid SQL Server estate is moved to Azure without checking collation, network latency or client drivers required by its linked workloads. Its decisive acceptance evidence would be: Connectivity, collation-sensitive queries and required drivers pass controlled pre-production checks against the documented inventory.

Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. That relates to a separate SQL administration problem: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The Alpine Healthcare requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Alpine Healthcare requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Compare Azure SQL Database, Managed Instance and SQL Server on Azure VMs against operational responsibility, feature parity, networking and performance needs. That relates to a separate SQL administration problem: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. The Alpine Healthcare requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Two clean deployments produce equivalent configuration for the shared policy while only approved environment parameters differ. That result is evidence for another corrective change: Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. The alternative problem is: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The current Alpine Healthcare issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

The restored environment reports the expected guest and engine patch levels and completes application regression and rollback checks. That result is evidence for another corrective change: Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. The alternative problem is: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The current Alpine Healthcare issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

The original instance remains in place, its governance metadata is visible through Azure Arc, and no unplanned data migration occurs. That result is evidence for another corrective change: Use Azure Arc-enabled SQL Server to inventory and manage eligible existing SQL Server instances while designing migration as a separate process. The alternative problem is: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. The current Alpine Healthcare issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. That relates to a separate SQL administration problem: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The Brookside Manufacturing requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Use Azure SQL Database as the fully managed relational platform after confirming database-level compatibility, scale and feature requirements. That relates to a separate SQL administration problem: A transactional web application is placed on a full SQL Server virtual machine even though it requires no operating system or instance administration. The Brookside Manufacturing requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Use Azure Arc-enabled SQL Server to inventory and manage eligible existing SQL Server instances while designing migration as a separate process. That relates to a separate SQL administration problem: A database team assumes Azure Arc-enabled SQL Server creates an Azure SQL Database and automatically migrates all on-premises data. The Brookside Manufacturing requirement is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. That approach does not directly establish the required fix; the requested acceptance evidence is: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Two clean deployments produce equivalent configuration for the shared policy while only approved environment parameters differ. That result is evidence for another corrective change: Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. The alternative problem is: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The current Brookside Manufacturing issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

The migrated test workload executes its scheduled Agent job on the managed instance and the dependency inventory has no unsupported features. That result is evidence for another corrective change: Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. The alternative problem is: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The current Brookside Manufacturing issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

A test tenant is routed to the correct shard, writes remain isolated, and a shard move is validated without cross-tenant data loss. That result is evidence for another corrective change: Evaluate explicit sharding with a stable tenant-to-shard routing strategy and independent databases instead of relying on intra-database partitions. The alternative problem is: A tenant application has outgrown the write capacity of one logical database but architects assume table partitioning creates independent database servers. The current Brookside Manufacturing issue is instead: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. Its decisive acceptance evidence would be: The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected.

Identify the operational database and Microsoft Fabric integration roles separately, checking supported Azure SQL Database in Fabric capabilities for the use case. That relates to a separate SQL administration problem: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. The Brookside Manufacturing requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Select Azure SQL Managed Instance when instance compatibility and SQL Server Agent are required, after checking the feature and networking constraints. That relates to a separate SQL administration problem: A startup deploys a small Azure SQL Database but requires instance-level SQL Server Agent jobs, which the chosen single database cannot host. The Brookside Manufacturing requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Brookside Manufacturing requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

A test partition switch or range maintenance operation affects only the intended date partition and query plans remain suitable. That result is evidence for another corrective change: Design range-based table partitioning using a suitable partition function and scheme aligned with retention and query-access requirements. The alternative problem is: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. The current Brookside Manufacturing issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

The deployed Azure SQL resource properties match the reviewed template and an unapproved parameter change is rejected. That result is evidence for another corrective change: Use a governed deployment pipeline with parameterized templates, separate service identities and recorded change approvals. The alternative problem is: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. The current Brookside Manufacturing issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

A test ERP workload runs with the required Windows and SQL Server instance features and its VM administration responsibilities are documented. That result is evidence for another corrective change: Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. The alternative problem is: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The current Brookside Manufacturing issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Use a governed deployment pipeline with parameterized templates, separate service identities and recorded change approvals. That relates to a separate SQL administration problem: A team publishes all database deployments from an engineer's workstation and cannot prove that a requested SQL resource configuration was reviewed. The Oakridge Public Services requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Deploy SQL Server on Azure Virtual Machines for the documented operating-system and instance feature requirements rather than assuming PaaS parity. That relates to a separate SQL administration problem: A legacy ERP system needs supported instance-level functionality and controls over the guest operating system, but the proposal uses a single Azure SQL database. The Oakridge Public Services requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Design range-based table partitioning using a suitable partition function and scheme aligned with retention and query-access requirements. That relates to a separate SQL administration problem: A table containing billions of date-keyed sales rows has growing retention maintenance costs because data cannot be managed by date range. The Oakridge Public Services requirement is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. That approach does not directly establish the required fix; the requested acceptance evidence is: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

The restored environment reports the expected guest and engine patch levels and completes application regression and rollback checks. That result is evidence for another corrective change: Plan supported guest operating-system and SQL Server cumulative update maintenance with backups, rollback and a tested outage window. The alternative problem is: An infrastructure team restores a SQL Server VM image but fails to patch SQL Server, assuming Azure host maintenance upgrades the guest software. The current Oakridge Public Services issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

The transaction workload remains on its intended database platform and reporting uses the documented supported Fabric integration path. That result is evidence for another corrective change: Identify the operational database and Microsoft Fabric integration roles separately, checking supported Azure SQL Database in Fabric capabilities for the use case. The alternative problem is: An analytics team confuses an operational Azure SQL Database mirrored into Microsoft Fabric with a replacement for all transactional application database responsibilities. The current Oakridge Public Services issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Two clean deployments produce equivalent configuration for the shared policy while only approved environment parameters differ. That result is evidence for another corrective change: Use versioned Azure Resource Manager or Bicep templates with parameters and approvals to deploy consistent Azure SQL infrastructure. The alternative problem is: A team manually creates Azure SQL resources in the portal and gets different firewall, backup and SKU settings in each environment. The current Oakridge Public Services issue is instead: An architect chooses an Azure SQL deployment solely by monthly price and ignores instance isolation, maintenance ownership and unsupported features. Its decisive acceptance evidence would be: A workload capability matrix records the selected platform and a pilot validates each nonnegotiable dependency.

Configure suitable elastic pool size and per-database resource limits based on aggregate and peak usage observations. That relates to a separate SQL administration problem: An application requires predictable resource isolation but several databases in one elastic pool consume each other's shared headroom without monitoring. The Timberline Foods requirement is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. That approach does not directly establish the required fix; the requested acceptance evidence is: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.

Evaluate a compatible serverless compute tier with auto-pause or autoscaling settings and explicitly test connection warm-up behavior. That relates to a separate SQL administration problem: A sporadic Azure SQL Database remains provisioned at peak compute capacity overnight even though long idle periods are predictable. The Timberline Foods requirement is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. That approach does not directly establish the required fix; the requested acceptance evidence is: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.

Choose a partition function and aligned indexes based on the actual date predicate and verify partition elimination in execution plans. That relates to a separate SQL administration problem: A table is partitioned by an arbitrary identifier although nearly all expensive reports filter on monthly transaction dates. The Timberline Foods requirement is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. That approach does not directly establish the required fix; the requested acceptance evidence is: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.

A representative report reads the relevant date partitions instead of scanning unrelated monthly ranges. That result is evidence for another corrective change: Choose a partition function and aligned indexes based on the actual date predicate and verify partition elimination in execution plans. The alternative problem is: A table is partitioned by an arbitrary identifier although nearly all expensive reports filter on monthly transaction dates. The current Timberline Foods issue is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. Its decisive acceptance evidence would be: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.

Compute utilization and billing follow the idle and burst pattern while peak requests meet the stated restart-latency requirement. That result is evidence for another corrective change: Evaluate a compatible serverless compute tier with auto-pause or autoscaling settings and explicitly test connection warm-up behavior. The alternative problem is: A sporadic Azure SQL Database remains provisioned at peak compute capacity overnight even though long idle periods are predictable. The current Timberline Foods issue is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. Its decisive acceptance evidence would be: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.

The database reports adequate free storage after the approved change and no growth operation fails its service limit. That result is evidence for another corrective change: Review independent service-tier compute and storage quotas and scale the supported storage setting or tier as required. The alternative problem is: A managed SQL service's storage approaches its limit and the scaling plan assumes that increasing vCores always increases the allowable data size. The current Timberline Foods issue is instead: A database experiences sustained CPU throttling on an underprovisioned Azure SQL Database but administrators increase storage only. Its decisive acceptance evidence would be: Post-scale CPU pressure and request latency improve under a representative test while storage and cost remain within approved bounds.