Question 780
An Azure SQL operations team investigates: An organization wants to restore a historic backup taken well beyond its normal PITR period. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: An organization wants to restore a historic backup taken well beyond its normal PITR period. The specific supported administrative response is: Configure supported long-term retention policies for Azure SQL automated backups when legal requirements exceed ordinary PITR windows. The technical risk is: Ordinary short-term recovery retention cannot satisfy multi-year records preservation requirements. Confirm the correction with: Retention inventory and a restore rehearsal show the required historic backup can still be accessed within policy.
The acceptance evidence for this incident (An organization wants to restore a historic backup taken well beyond its normal PITR period.) is: Retention inventory and a restore rehearsal show the required historic backup can still be accessed within policy. It directly tests whether the remediation (Configure supported long-term retention policies for Azure SQL automated backups when legal requirements exceed ordinary PITR windows.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Native SQL server full differential and log backups (5.2) addresses another technical failure: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. The case states: An organization wants to restore a historic backup taken well beyond its normal PITR period. The most direct paired action and test is: Configure supported long-term retention policies for Azure SQL automated backups when legal requirements exceed ordinary PITR windows.
Disaster recovery runbook and rehearsal (5.1) addresses another technical failure: An untested disaster recovery plan may fail due to stale credentials, missing DNS or unfamiliar operational steps. This choice can be useful for that problem, but it does not establish the Long-term retention for compliance backups (5.2) control being assessed here.
Always on availability groups on azure SQL vms (5.3) would demonstrate or implement: A planned replica failover preserves database accessibility through the listener and reports expected synchronization health. This case instead tests Long-term retention for compliance backups (5.2); the choice measures or changes another part of the system.