Question 790
An Azure SQL operations team investigates: A recovery technician chooses a differential backup that does not match the restored base full backup. 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 recovery technician chooses a differential backup that does not match the restored base full backup. The specific supported administrative response is: Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms. The technical risk is: An incomplete log chain or wrong recovery model can prevent recovery to the desired point after a failure. Confirm the correction with: A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass.
The acceptance evidence for this incident (A recovery technician chooses a differential backup that does not match the restored base full backup.) is: A restore chain replay reaches a chosen timestamp and DBCC or application integrity checks pass. It directly tests whether the remediation (Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Encrypted native backup keys and recovery (5.2) addresses another technical failure: A perfectly copied encrypted backup is unusable when its decryption protector is missing at the recovery site. The case states: A recovery technician chooses a differential backup that does not match the restored base full backup. The most direct paired action and test is: Plan native SQL Server full, differential and transaction log backup chains with frequency tied to recovery objectives on supported platforms.
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. The required paired action and test concerns Native SQL server full differential and log backups (5.2); a passing result for this alternative could leave that requirement unresolved.
Ha dr design from rpo and rto (5.1) addresses another technical failure: A design with acceptable availability but unknown possible data loss can violate agreed recovery commitments. The paired-answer requirement concerns Native SQL server full differential and log backups (5.2); this alternative does not provide the matching intervention and separate acceptance evidence.