Question 770
An Azure SQL operations team investigates: A restoration request includes a timestamp outside the available PITR window and needs an alternative plan. 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: A restoration request includes a timestamp outside the available PITR window and needs an alternative plan. The specific supported administrative response is: Use supported Azure SQL automated backup and point-in-time restore to recover a new database state at an eligible time within retention. The technical risk is: A normal PITR restore is not a guaranteed instant in-place undo and cannot recover timestamps beyond retained backups. Confirm the correction with: The restored database contains records consistent with the selected timestamp and application validation passes.
The acceptance evidence for this incident (A restoration request includes a timestamp outside the available PITR window and needs an alternative plan.) is: The restored database contains records consistent with the selected timestamp and application validation passes. It directly tests whether the remediation (Use supported Azure SQL automated backup and point-in-time restore to recover a new database state at an eligible time within retention.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Native restore sequence with norecovery and recovery (5.2) addresses another technical failure: Recovering the database too early or restoring an incompatible log backup can prevent remaining backup application. The case states: A restoration request includes a timestamp outside the available PITR window and needs an alternative plan. The most direct paired action and test is: Use supported Azure SQL automated backup and point-in-time restore to recover a new database state at an eligible time within retention.
Monitoring replica health and lag across ha dr (5.3) would demonstrate or implement: Telemetry and a safe failover exercise demonstrate acceptable replication delay, data consistency and application routing. The required paired action and test concerns Automated point-in-time restore for azure SQL (5.2); a passing result for this alternative could leave that requirement unresolved.
Azure SQL database active geo-replication (5.3) addresses another technical failure: An asynchronous geo-secondary may lag behind the primary and individual database failover does not automatically coordinate a multi-database application. The paired-answer requirement concerns Automated point-in-time restore for azure SQL (5.2); this alternative does not provide the matching intervention and separate acceptance evidence.