Question 810
An Azure SQL operations team investigates: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. 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 backup job reports success but the recovery team has never tested restoring from the cloud storage URL. The specific supported administrative response is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts. The technical risk is: Unreachable Blob storage, expired credentials or unverified backup integrity can make a cloud backup unusable in a disaster. Confirm the correction with: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials.
The acceptance evidence for this incident (A backup job reports success but the recovery team has never tested restoring from the cloud storage URL.) is: A restore test retrieves the Blob backup and validates the resulting database without exposing storage credentials. It directly tests whether the remediation (Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.) 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: A backup job reports success but the recovery team has never tested restoring from the cloud storage URL. The most direct paired action and test is: Use supported SQL Server BACKUP TO URL and RESTORE FROM URL workflows with correctly scoped storage access and verified backup artifacts.
Read-scale replicas versus writable ha requirements (5.1) addresses another technical failure: A read-only secondary cannot simply accept all transactional writes after switchover without supported role promotion and client redirection. This choice can be useful for that problem, but it does not establish the SQL server backup and restore to azure blob storage (5.2) control being assessed here.
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 SQL server backup and restore to azure blob storage (5.2); a passing result for this alternative could leave that requirement unresolved.