A query retrieves historical resource measurements through the required retention window could validate a separate fix, for example when a DBA requests 30 days of historical performance for a database whose current dashboard shows only a week. Here the required proof is that a controlled deadlock produces a captured event with identifying session information. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

Several days of comparable metrics reveal the recurring noon departure from baseline could validate a separate fix, for example when a transaction database intermittently slows at noon but has no normal workload measurements. Here the required proof is that a controlled deadlock produces a captured event with identifying session information. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

A controlled test establishes whether storage saturation coincides with migration lag could validate a separate fix, for example when a large migration runs slowly only when an automatic platform backup overlaps it. Here the required proof is that a controlled deadlock produces a captured event with identifying session information. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

A duty-cycle test confirms acceptable startup latency and compute charges could validate a separate fix, for example when a platform architect must choose between Azure SQL Database serverless and provisioned compute for intermittent work. Here the required proof is that a supported service operates on the SQL virtual machine and patch compliance is monitored. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

Two test environments are deployed with the same approved resource definitions could validate a separate fix, for example when a bank requests reproducible Azure SQL deployments across multiple subscriptions with policy gates. Here the required proof is that a supported service operates on the SQL virtual machine and patch compliance is monitored. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

The chosen offering passes a feature-by-feature compatibility checklist for the application could validate a separate fix, for example when an application team must reduce the operational patch burden but retains legacy SQL Server features. Here the required proof is that a supported service operates on the SQL virtual machine and patch compliance is monitored. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

Hybrid HA/DR depends on supported SQL topology authentication and network latency across sites is a valid distinction for a different database situation, for example when a bank operates on-premises SQL Server with an Azure virtual machine as disaster recovery. Here the determining mechanism is that hA replicas replicate operational changes and might replicate accidental deletion or corruption. The alternative does not explain why the selected solution addresses this requirement.

An HA design is not proven until recovery paths are exercised under representative failures is a valid distinction for a different database situation, for example when a database migration will retire an on-premises primary but the new DR region was never tested. Here the determining mechanism is that hA replicas replicate operational changes and might replicate accidental deletion or corruption. The alternative does not explain why the selected solution addresses this requirement.

Managed Instance failover groups coordinate geo-secondary instances under platform restrictions is a valid distinction for a different database situation, for example when an organization operates a mission-critical SQL Managed Instance and wants cross-region continuity. Here the determining mechanism is that hA replicas replicate operational changes and might replicate accidental deletion or corruption. The alternative does not explain why the selected solution addresses this requirement.

Assign the function identity and scoped Azure SQL permissions and configure reliable triggers would instead apply to another SQL platform issue, such as when a small database estate runs SQL automation from Azure Functions using a managed identity. The present requirement calls for configure per-target execution monitoring and an alert routed to an approved action group; this alternative changes a different control and does not directly resolve the stated database issue.

Configure an elastic job agent with approved target groups and scheduled T-SQL steps would instead apply to another SQL platform issue, such as when an Azure SQL Database application needs nightly index and statistics updates on dozens of separate databases. The present requirement calls for configure per-target execution monitoring and an alert routed to an approved action group; this alternative changes a different control and does not directly resolve the stated database issue.

Choose elastic jobs or an approved external scheduler rather than an in-database SQL Agent service would instead apply to another SQL platform issue, such as when an Azure SQL Database deployment needs recurring processing but does not support SQL Server Agent. The present requirement calls for configure per-target execution monitoring and an alert routed to an approved action group; this alternative changes a different control and does not directly resolve the stated database issue.

Inspect data I/O log write and relevant database wait measurements would instead apply to another SQL platform issue, such as when an Azure SQL Database reports higher latency while CPU utilization remains low. The present requirement calls for use available query and resource metrics to compare pre-change and post-change memory behavior; this alternative changes a different control and does not directly resolve the stated database issue.

Collect connection success metrics and database error logs separately from query duration telemetry would instead apply to another SQL platform issue, such as when a security incident requires distinguishing SQL connection failures from query latency errors. The present requirement calls for use available query and resource metrics to compare pre-change and post-change memory behavior; this alternative changes a different control and does not directly resolve the stated database issue.

Configure an Extended Events session using appropriate event filters and targets would instead apply to another SQL platform issue, such as when a production SQL Server VM needs lightweight detailed event capture for intermittent deadlocks. The present requirement calls for use available query and resource metrics to compare pre-change and post-change memory behavior; this alternative changes a different control and does not directly resolve the stated database issue.

Creating a database user alone does not assign the logical server Entra administrator role can matter in a separate case, such as when a database team needs a security administrator to configure the Entra administrator for a logical SQL server. In this question, the principal consequence is that a token for a different cloud API cannot be assumed valid for Azure SQL sign-in. That different risk does not best characterize the missing control in the given scenario.

Keeping long-lived shared SQL passwords in application configuration weakens accountability can matter in a separate case, such as when an application administrator wants employees to sign in to Azure SQL using corporate identities without storing SQL passwords. In this question, the principal consequence is that a token for a different cloud API cannot be assumed valid for Azure SQL sign-in. That different risk does not best characterize the missing control in the given scenario.

Assuming Microsoft Entra-only database users replace all Windows-integrated dependencies may break clients can matter in a separate case, such as when a SQL Server on an Azure VM must continue to use Windows integrated logins for existing intranet applications. In this question, the principal consequence is that a token for a different cloud API cannot be assumed valid for Azure SQL sign-in. That different risk does not best characterize the missing control in the given scenario.

Leaving an emergency all-address rule creates unintended connection exposure after cutover can matter in a separate case, such as when a SQL logical server permits a broad IP firewall rule used during a former migration. In this question, the principal consequence is that a database-side TLS preference cannot make an obsolete client implement valid certificate checking. That different risk does not best characterize the missing control in the given scenario.

Storing encryption keys alongside ciphertext in broadly readable tables defeats separation of duties can matter in a separate case, such as when a finance database stores a small API token column that requires SQL-side encryption using managed secrets. In this question, the principal consequence is that a database-side TLS preference cannot make an obsolete client implement valid certificate checking. That different risk does not best characterize the missing control in the given scenario.

Assuming a restored test database is harmless can expose production personal information can matter in a separate case, such as when a staging SQL database was restored from production and contains confidential values. In this question, the principal consequence is that a database-side TLS preference cannot make an obsolete client implement valid certificate checking. That different risk does not best characterize the missing control in the given scenario.

Database-only movement does not necessarily transfer SQL Agent schedules or instance identities is a valid distinction for a different database situation, for example when an Azure SQL Managed Instance migration must preserve instance jobs and logins. Here the determining mechanism is that migration connectivity authorization and target readiness are required before the data stream can succeed. The alternative does not explain why the selected solution addresses this requirement.

Azure SQL Database feature boundaries can require application-level data access redesign is a valid distinction for a different database situation, for example when an application moves from SQL Server on a VM to Azure SQL Database and uses three-part naming. Here the determining mechanism is that migration connectivity authorization and target readiness are required before the data stream can succeed. The alternative does not explain why the selected solution addresses this requirement.

Online migration minimizes cutover downtime by replicating changes while source operations continue is a valid distinction for a different database situation, for example when a large customer database must move from SQL Server with only minutes of planned downtime. Here the determining mechanism is that migration connectivity authorization and target readiness are required before the data stream can succeed. The alternative does not explain why the selected solution addresses this requirement.

Permit the documented availability replica endpoint traffic through approved network controls would instead apply to another SQL platform issue, such as when a SQL Server VM Availability Group is unhealthy because replica endpoint traffic is blocked between nodes. The present requirement calls for validate application-level transaction health in addition to AG replica synchronization; this alternative changes a different control and does not directly resolve the stated database issue.

Investigate replication health and restore or reseed the secondary using supported procedures would instead apply to another SQL platform issue, such as when a SQL Server disaster recovery replica cannot recover because its availability databases have diverged after unsupported manual writes. The present requirement calls for validate application-level transaction health in addition to AG replica synchronization; this alternative changes a different control and does not directly resolve the stated database issue.

Configure supported active geo-replication and connect reports to the secondary would instead apply to another SQL platform issue, such as when an Azure SQL Database needs an independently readable secondary in another Region for business reporting. The present requirement calls for validate application-level transaction health in addition to AG replica synchronization; this alternative changes a different control and does not directly resolve the stated database issue.

The timeline identifies the connection-error spike separately from slow SQL execution could validate a separate fix, for example when a security incident requires distinguishing SQL connection failures from query latency errors. Here the required proof is that the dominant resource component is documented during a repeatable report run. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

Dashboards identify which database drives the observed peak could validate a separate fix, for example when a software team uses an Azure SQL logical server and wants to compare CPU across five databases. Here the required proof is that the dominant resource component is documented during a repeatable report run. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

A query retrieves historical resource measurements through the required retention window could validate a separate fix, for example when a DBA requests 30 days of historical performance for a database whose current dashboard shows only a week. Here the required proof is that the dominant resource component is documented during a repeatable report run. The alternative tests another database behavior and cannot establish whether the stated issue was corrected.

Validate cluster-compatible shared storage and the supported SQL FCI instance dependencies would instead apply to another SQL platform issue, such as when a SQL Server VM FCI stops during cluster failover because shared storage is unavailable on the survivor. The present requirement calls for repair Managed Instance peer subnet and connectivity prerequisites before creating the pair; this alternative changes a different control and does not directly resolve the stated database issue.

Investigate replication health and restore or reseed the secondary using supported procedures would instead apply to another SQL platform issue, such as when a SQL Server disaster recovery replica cannot recover because its availability databases have diverged after unsupported manual writes. The present requirement calls for repair Managed Instance peer subnet and connectivity prerequisites before creating the pair; this alternative changes a different control and does not directly resolve the stated database issue.

Repair copy job access and restore job sequencing and monitor shipping latency would instead apply to another SQL platform issue, such as when a SQL Server log shipping secondary stopped restoring transaction log backups after a shared folder change. The present requirement calls for repair Managed Instance peer subnet and connectivity prerequisites before creating the pair; this alternative changes a different control and does not directly resolve the stated database issue.