Exam Bundle

The task runs on schedule after the engineer's account is disabled and the operations team receives completion evidence. That result is evidence for another corrective change: Move the work to a managed scheduled automation mechanism with a service identity, ownership metadata and alerting. The alternative problem is: A database task's schedule is stored as a local engineer's calendar reminder, so it stops running when that employee leaves. The current Granite SaaS issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

A simulated invalid schema change is rejected before data mutation and a valid change passes the recovery and verification gates. That result is evidence for another corrective change: Add approved dry-run checks, a backup or restore checkpoint and stop-on-failure conditions before the database task proceeds. The alternative problem is: A patch automation workflow runs destructive schema changes without a preflight validation, health gate or recovery checkpoint. The current Granite SaaS issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

The job history lists each approved target exactly once and contains no unexpected production database. That result is evidence for another corrective change: Maintain elastic job target groups through a controlled inventory and verify membership and execution scope before each rollout. The alternative problem is: A database elastic job runs on only one test database because the production target group was never updated after adding new databases. The current Granite SaaS issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

Make the task idempotent or record a durable execution checkpoint before allowing retries in the governed workflow. That relates to a separate SQL administration problem: A maintenance automation runbook retries a failed data patch and applies the same update twice because it has no idempotency check. The Meadowbrook Finance requirement is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. That approach does not directly establish the required fix; the requested acceptance evidence is: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

Record structured task identity, target resource, input version, start and end times and step results in protected logs. That relates to a separate SQL administration problem: An operations team stores only the last successful task timestamp and cannot determine which automated SQL change caused an incident. The Meadowbrook Finance requirement is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. That approach does not directly establish the required fix; the requested acceptance evidence is: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

Maintain elastic job target groups through a controlled inventory and verify membership and execution scope before each rollout. That relates to a separate SQL administration problem: A database elastic job runs on only one test database because the production target group was never updated after adding new databases. The Meadowbrook Finance requirement is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. That approach does not directly establish the required fix; the requested acceptance evidence is: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

The task executes the intended procedure but cannot modify a restricted finance table on a target database. That result is evidence for another corrective change: Create or map a narrowly privileged job identity and grant only required procedure permissions on each approved target. The alternative problem is: A scheduled Azure SQL task retains broad database owner permissions even though it only needs to invoke one maintenance procedure. The current Meadowbrook Finance issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

The simulated shard failure generates a target-specific alert while successful databases remain distinguishable in the run summary. That result is evidence for another corrective change: Alert on per-target job execution outcomes and record failed database targets rather than using agent availability as proof of success. The alternative problem is: An elastic job fails on one shard but the automation dashboard reports green because it checks only the job-agent heartbeat. The current Meadowbrook Finance issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

The task runs on schedule after the engineer's account is disabled and the operations team receives completion evidence. That result is evidence for another corrective change: Move the work to a managed scheduled automation mechanism with a service identity, ownership metadata and alerting. The alternative problem is: A database task's schedule is stored as a local engineer's calendar reminder, so it stops running when that employee leaves. The current Meadowbrook Finance issue is instead: An Azure SQL maintenance workflow sends all task notifications to a terminated employee's personal mailbox and incidents go unnoticed. Its decisive acceptance evidence would be: A forced task failure reaches the active on-call channel and leaves a retrievable notification and acknowledgement record.

Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. That relates to a separate SQL administration problem: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The Alpine Healthcare requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Distinguish availability-zone protection from cross-region disaster recovery and choose an appropriate separate geographic strategy. That relates to a separate SQL administration problem: A team assumes zone redundancy protects against complete regional failure and omits any cross-region recovery strategy. The Alpine Healthcare requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Select legally permitted primary and secondary regions and document data sovereignty, encryption and recovery access requirements. That relates to a separate SQL administration problem: An organization accepts the default deployment region without checking data residency requirements for its geo-replicated recovery copy. The Alpine Healthcare requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

A controlled accidental deletion is recovered to a selected pre-deletion timestamp and the restored database is usable. That result is evidence for another corrective change: Include point-in-time restore and appropriate retention planning alongside high-availability features to handle user or application mistakes. The alternative problem is: An Azure SQL Database application has no backup-restore runbook because its developers assume built-in platform availability prevents logical data deletion. The current Alpine Healthcare issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

A simulated loss of the primary location still allows a database restore or failover in the designated independent recovery location. That result is evidence for another corrective change: Design offsite protected backups or a suitable secondary system outside the primary failure domain and validate restoration access. The alternative problem is: A hybrid SQL Server estate uses local backups but its stated disaster scenario includes destruction of the primary data center. The current Alpine Healthcare issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

The test run records expected operator decisions and the application passes validation after the supported failover sequence. That result is evidence for another corrective change: Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. The alternative problem is: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The current Alpine Healthcare issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Design offsite protected backups or a suitable secondary system outside the primary failure domain and validate restoration access. That relates to a separate SQL administration problem: A hybrid SQL Server estate uses local backups but its stated disaster scenario includes destruction of the primary data center. The Northgate Telecom requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Plan the recovery time objective using application routing, database failover, detection and client reconnection behavior end to end. That relates to a separate SQL administration problem: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. The Northgate Telecom requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. That relates to a separate SQL administration problem: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The Northgate Telecom requirement is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. That approach does not directly establish the required fix; the requested acceptance evidence is: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

A node-failure drill preserves a valid cluster quorum and does not expose two independently writable primary nodes. That result is evidence for another corrective change: Design a supported Windows Server Failover Clustering or availability group quorum strategy appropriate to topology and failure domains. The alternative problem is: A high-availability plan lists a passive standby SQL Server VM but never accounts for quorum, cluster witness or split-brain prevention. The current Northgate Telecom issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

The test run records expected operator decisions and the application passes validation after the supported failover sequence. That result is evidence for another corrective change: Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. The alternative problem is: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The current Northgate Telecom issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

The promoted recovery database sustains the required transaction throughput and client latency instead of merely accepting connections. That result is evidence for another corrective change: Size the recovery replica and network path for the documented recovery workload and run representative failover load tests. The alternative problem is: A cross-region failover plan assumes secondary read replicas will always have identical performance capacity to the primary without sizing them. The current Northgate Telecom issue is instead: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. Its decisive acceptance evidence would be: A controlled failover or recovery test shows the last recoverable transaction is within the agreed five-minute loss window.

Distinguish availability-zone protection from cross-region disaster recovery and choose an appropriate separate geographic strategy. That relates to a separate SQL administration problem: A team assumes zone redundancy protects against complete regional failure and omits any cross-region recovery strategy. The Northgate Telecom requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. That relates to a separate SQL administration problem: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The Northgate Telecom requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

Select an HA/DR design with a measured recovery point objective that fits five minutes, not backup frequency alone. That relates to a separate SQL administration problem: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. The Northgate Telecom requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

A node-failure drill preserves a valid cluster quorum and does not expose two independently writable primary nodes. That result is evidence for another corrective change: Design a supported Windows Server Failover Clustering or availability group quorum strategy appropriate to topology and failure domains. The alternative problem is: A high-availability plan lists a passive standby SQL Server VM but never accounts for quorum, cluster witness or split-brain prevention. The current Northgate Telecom issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

The promoted recovery database sustains the required transaction throughput and client latency instead of merely accepting connections. That result is evidence for another corrective change: Size the recovery replica and network path for the documented recovery workload and run representative failover load tests. The alternative problem is: A cross-region failover plan assumes secondary read replicas will always have identical performance capacity to the primary without sizing them. The current Northgate Telecom issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

A controlled accidental deletion is recovered to a selected pre-deletion timestamp and the restored database is usable. That result is evidence for another corrective change: Include point-in-time restore and appropriate retention planning alongside high-availability features to handle user or application mistakes. The alternative problem is: An Azure SQL Database application has no backup-restore runbook because its developers assume built-in platform availability prevents logical data deletion. The current Northgate Telecom issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

Select an HA/DR design with a measured recovery point objective that fits five minutes, not backup frequency alone. That relates to a separate SQL administration problem: A business declares that it can lose no more than five minutes of transactions but its only recovery plan is a nightly backup. The Riverton Utilities requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

Select legally permitted primary and secondary regions and document data sovereignty, encryption and recovery access requirements. That relates to a separate SQL administration problem: An organization accepts the default deployment region without checking data residency requirements for its geo-replicated recovery copy. The Riverton Utilities requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

Document asynchronous replication's nonzero possible recovery point and test the actual lag against accepted business objectives. That relates to a separate SQL administration problem: A healthcare database chooses asynchronous geo replication for resilience but reports a guaranteed zero-data-loss outcome without a synchronous commit contract. The Riverton Utilities requirement is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. That approach does not directly establish the required fix; the requested acceptance evidence is: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

The promoted recovery database sustains the required transaction throughput and client latency instead of merely accepting connections. That result is evidence for another corrective change: Size the recovery replica and network path for the documented recovery workload and run representative failover load tests. The alternative problem is: A cross-region failover plan assumes secondary read replicas will always have identical performance capacity to the primary without sizing them. The current Riverton Utilities issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

The test run records expected operator decisions and the application passes validation after the supported failover sequence. That result is evidence for another corrective change: Document both automatic and manual failover modes with decision authority, dependency checks, service routing and recovery verification. The alternative problem is: A business continuity plan assumes that successful automatic failover means no manual approval, client cache updates or data validation will ever be needed. The current Riverton Utilities issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.

A controlled accidental deletion is recovered to a selected pre-deletion timestamp and the restored database is usable. That result is evidence for another corrective change: Include point-in-time restore and appropriate retention planning alongside high-availability features to handle user or application mistakes. The alternative problem is: An Azure SQL Database application has no backup-restore runbook because its developers assume built-in platform availability prevents logical data deletion. The current Riverton Utilities issue is instead: A financial application must resume within fifteen minutes after an entire region failure but operations has no estimate of DNS and client reconnection delays. Its decisive acceptance evidence would be: A region-failure exercise completes an authenticated business transaction within the fifteen-minute RTO including routing and client recovery.