Exam Bundle

A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint. That result is evidence for another corrective change: Configure and monitor Always On availability group health, synchronization and appropriate planned-failover readiness. The alternative problem is: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. The current Alpine Healthcare issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

The incident report records lag at failover and validates the recovered transaction state against the approved RPO. That result is evidence for another corrective change: Monitor replication state and evaluate potential data loss before an unplanned asynchronous geo failover, following business RPO policy. The alternative problem is: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. The current Alpine Healthcare issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

The promoted endpoint permits intended application writes and the sample transaction reconciliation matches the agreed recovery checkpoint. That result is evidence for another corrective change: Use the documented Managed Instance failover and post-failover validation procedure including replica state and application identity. The alternative problem is: A database DR test promotes the secondary SQL Managed Instance and then reconnects applications without validating data consistency or application write permission. The current Alpine Healthcare issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

Use the supported availability group listener and required DNS or multi-subnet client settings for application connections. That relates to a separate SQL administration problem: A team configures availability group replicas but hardcodes one VM hostname into the connection string and continues to fail after primary moves. The Northgate Telecom requirement is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. That approach does not directly establish the required fix; the requested acceptance evidence is: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

Inspect backup, copy and restore job history and restore the log shipping chain with suitable schedules and alerts. That relates to a separate SQL administration problem: An on-premises SQL Server log shipping secondary is consistently hours behind because copy and restore jobs fail without monitoring. The Northgate Telecom requirement is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. That approach does not directly establish the required fix; the requested acceptance evidence is: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

Implement supported cluster or failover-group role enforcement and application endpoint fencing before allowing writes after recovery. That relates to a separate SQL administration problem: A post-failover application continues writing to a former primary after network recovery because the architecture lacks split-brain protection and role validation. The Northgate Telecom requirement is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. That approach does not directly establish the required fix; the requested acceptance evidence is: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

The incident report records lag at failover and validates the recovered transaction state against the approved RPO. That result is evidence for another corrective change: Monitor replication state and evaluate potential data loss before an unplanned asynchronous geo failover, following business RPO policy. The alternative problem is: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. The current Northgate Telecom issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

A controlled replica disconnect is detected by the AG monitoring signal and the recovery runbook identifies the affected database. That result is evidence for another corrective change: Configure SQL Server availability group health and replica synchronization telemetry with actionable alerts. The alternative problem is: An availability group becomes unhealthy but operators watch only VM CPU metrics and miss replica connection and synchronization failures. The current Northgate Telecom issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

The designated secondary handles the expected reads and a promotion rehearsal meets documented capacity thresholds. That result is evidence for another corrective change: Monitor secondary compute, replica lag and connection capacity under representative read and disaster recovery workload. The alternative problem is: A region-paired Azure SQL deployment has a secondary database that is too small for reporting load and the team mistakes successful replication for recovery readiness. The current Northgate Telecom issue is instead: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. Its decisive acceptance evidence would be: After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary.

Use an appropriate failover group with stable read-write listener routing and supported failover policy when automatic app-level redirection is required. That relates to a separate SQL administration problem: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. The Northgate Telecom requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Monitor secondary compute, replica lag and connection capacity under representative read and disaster recovery workload. That relates to a separate SQL administration problem: A region-paired Azure SQL deployment has a secondary database that is too small for reporting load and the team mistakes successful replication for recovery readiness. The Northgate Telecom requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Configure SQL Server availability group health and replica synchronization telemetry with actionable alerts. That relates to a separate SQL administration problem: An availability group becomes unhealthy but operators watch only VM CPU metrics and miss replica connection and synchronization failures. The Northgate Telecom requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

The destination database remains synchronized and post-cutover logins and scheduled operations pass independent validation tests. That result is evidence for another corrective change: Follow the supported Managed Instance link workflow and separately migrate required instance-level dependencies and application configuration. The alternative problem is: A multi-instance hybrid migration uses an availability-group-based link to SQL Managed Instance but assumes all on-premises logins and server jobs are migrated automatically. The current Northgate Telecom issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

The designated secondary handles the expected reads and a promotion rehearsal meets documented capacity thresholds. That result is evidence for another corrective change: Monitor secondary compute, replica lag and connection capacity under representative read and disaster recovery workload. The alternative problem is: A region-paired Azure SQL deployment has a secondary database that is too small for reporting load and the team mistakes successful replication for recovery readiness. The current Northgate Telecom issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary. That result is evidence for another corrective change: Use an appropriate failover group with stable read-write listener routing and supported failover policy when automatic app-level redirection is required. The alternative problem is: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. The current Northgate Telecom issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Use an appropriate failover group with stable read-write listener routing and supported failover policy when automatic app-level redirection is required. That relates to a separate SQL administration problem: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. The Riverton Utilities requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Inspect backup, copy and restore job history and restore the log shipping chain with suitable schedules and alerts. That relates to a separate SQL administration problem: An on-premises SQL Server log shipping secondary is consistently hours behind because copy and restore jobs fail without monitoring. The Riverton Utilities requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Configure SQL Server availability group health and replica synchronization telemetry with actionable alerts. That relates to a separate SQL administration problem: An availability group becomes unhealthy but operators watch only VM CPU metrics and miss replica connection and synchronization failures. The Riverton Utilities requirement is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. That approach does not directly establish the required fix; the requested acceptance evidence is: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

The secondary transitions to the intended online writable state and accepts an application connection after log application. That result is evidence for another corrective change: Apply required remaining log backups and perform the supported final recovery step before opening the secondary for production access. The alternative problem is: A SQL Server log shipping database is left in an unrecovered state during a planned disaster switch and users cannot connect to it. The current Riverton Utilities issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

A controlled primary-node failure starts the SQL instance on the alternate node with the same database files accessible. That result is evidence for another corrective change: Implement a supported FCI storage and cluster topology with witness, network and service dependencies correctly configured. The alternative problem is: A SQL Server Failover Cluster Instance on Azure VMs lacks a properly configured shared storage or supported cluster storage solution, preventing failover. The current Riverton Utilities issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

The secondary restore lag declines into the accepted range and all three log shipping stages complete in sequence. That result is evidence for another corrective change: Inspect backup, copy and restore job history and restore the log shipping chain with suitable schedules and alerts. The alternative problem is: An on-premises SQL Server log shipping secondary is consistently hours behind because copy and restore jobs fail without monitoring. The current Riverton Utilities issue is instead: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. Its decisive acceptance evidence would be: The incident report records lag at failover and validates the recovered transaction state against the approved RPO.

Check the configured failover policy, grace period and supported automatic-failover scope and align the runbook with actual behavior. That relates to a separate SQL administration problem: An Azure SQL failover group is set to manual but the operations runbook claims automatic recovery will occur after any transient outage. The Riverton Utilities requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

Monitor replication state and evaluate potential data loss before an unplanned asynchronous geo failover, following business RPO policy. That relates to a separate SQL administration problem: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. The Riverton Utilities requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

Implement supported cluster or failover-group role enforcement and application endpoint fencing before allowing writes after recovery. That relates to a separate SQL administration problem: A post-failover application continues writing to a former primary after network recovery because the architecture lacks split-brain protection and role validation. The Riverton Utilities requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

The destination database remains synchronized and post-cutover logins and scheduled operations pass independent validation tests. That result is evidence for another corrective change: Follow the supported Managed Instance link workflow and separately migrate required instance-level dependencies and application configuration. The alternative problem is: A multi-instance hybrid migration uses an availability-group-based link to SQL Managed Instance but assumes all on-premises logins and server jobs are migrated automatically. The current Riverton Utilities issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

After controlled regional failover the application reconnects using the listener and commits approved transactions on the new primary. That result is evidence for another corrective change: Use an appropriate failover group with stable read-write listener routing and supported failover policy when automatic app-level redirection is required. The alternative problem is: An Azure SQL Database has active geo-replication configured but the application still connects only to the primary and cannot recover automatically when that region fails. The current Riverton Utilities issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

The incident report records lag at failover and validates the recovered transaction state against the approved RPO. That result is evidence for another corrective change: Monitor replication state and evaluate potential data loss before an unplanned asynchronous geo failover, following business RPO policy. The alternative problem is: A database team treats an Azure SQL active geo-replica as synchronously consistent and starts a data-critical failover without checking replication lag. The current Riverton Utilities issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

Use the supported availability group listener and required DNS or multi-subnet client settings for application connections. That relates to a separate SQL administration problem: A team configures availability group replicas but hardcodes one VM hostname into the connection string and continues to fail after primary moves. The Harborline Logistics requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

Apply required remaining log backups and perform the supported final recovery step before opening the secondary for production access. That relates to a separate SQL administration problem: A SQL Server log shipping database is left in an unrecovered state during a planned disaster switch and users cannot connect to it. The Harborline Logistics requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

Implement supported cluster or failover-group role enforcement and application endpoint fencing before allowing writes after recovery. That relates to a separate SQL administration problem: A post-failover application continues writing to a former primary after network recovery because the architecture lacks split-brain protection and role validation. The Harborline Logistics requirement is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. That approach does not directly establish the required fix; the requested acceptance evidence is: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

A controlled primary-node failure starts the SQL instance on the alternate node with the same database files accessible. That result is evidence for another corrective change: Implement a supported FCI storage and cluster topology with witness, network and service dependencies correctly configured. The alternative problem is: A SQL Server Failover Cluster Instance on Azure VMs lacks a properly configured shared storage or supported cluster storage solution, preventing failover. The current Harborline Logistics issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

A controlled outage follows the documented manual or automatic policy and the test record identifies the correct trigger. That result is evidence for another corrective change: Check the configured failover policy, grace period and supported automatic-failover scope and align the runbook with actual behavior. The alternative problem is: An Azure SQL failover group is set to manual but the operations runbook claims automatic recovery will occur after any transient outage. The current Harborline Logistics issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.

The destination database remains synchronized and post-cutover logins and scheduled operations pass independent validation tests. That result is evidence for another corrective change: Follow the supported Managed Instance link workflow and separately migrate required instance-level dependencies and application configuration. The alternative problem is: A multi-instance hybrid migration uses an availability-group-based link to SQL Managed Instance but assumes all on-premises logins and server jobs are migrated automatically. The current Harborline Logistics issue is instead: A SQL Server on Azure VM application requires database-level high availability but its Availability Group replica has not synchronized before a planned failover. Its decisive acceptance evidence would be: A planned failover completes when replicas are synchronized and the application resumes through the supported listener endpoint.