A would instead validate the other design where a cloud team needs centralized protection and scheduled recovery points for Windows Azure virtual machines. That evidence is consistent with protect the eligible Azure VMs with Azure Backup in a suitable vault, because policy-managed VM backup produces recoverable points without custom scripts. It does not demonstrate that the target case achieves the restored workload passes its database/application consistency checks.

B would instead validate the other design where a small internal VM workload can tolerate several hours of recovery and a restore from a nightly recovery point. That evidence is consistent with use policy-based Azure Backup and document its achievable RPO/RTO, because backup restore is suitable when recovery objectives allow restore time and recovery-point age. It does not demonstrate that the target case achieves the restored workload passes its database/application consistency checks.

C would instead validate the other design where a company wants ransomware-resistant backup copies that operators cannot casually delete. That evidence is consistent with use a vault design with soft delete and immutability controls where supported, because protected vault settings add deletion resistance beyond ordinary access controls. It does not demonstrate that the target case achieves the restored workload passes its database/application consistency checks.

“Configure long-term backup retention for the eligible Azure SQL database” relies on this Azure capability: long-term retention preserves scheduled backups beyond normal short-term recovery windows. This workload involves A team needs to restore a managed Azure SQL database to a specific minute after an accidental delete. The decisive Azure design mechanism is: platform backups support restoring a new database to a supported point in the retention window. Thus “Use Azure SQL Database point-in-time restore within configured short-term retention” is the applicable architecture choice.

“Protect the eligible Azure VMs with Azure Backup in a suitable vault” relies on this Azure capability: policy-managed VM backup produces recoverable points without custom scripts. This workload involves A team needs to restore a managed Azure SQL database to a specific minute after an accidental delete. The decisive Azure design mechanism is: platform backups support restoring a new database to a supported point in the retention window. Thus “Use Azure SQL Database point-in-time restore within configured short-term retention” is the applicable architecture choice.

“Use Azure Database for PostgreSQL Flexible Server point-in-time restore” relies on this Azure capability: managed PostgreSQL backups support restoration to a new server at a supported timestamp. This workload involves A team needs to restore a managed Azure SQL database to a specific minute after an accidental delete. The decisive Azure design mechanism is: platform backups support restoring a new database to a supported point in the retention window. Thus “Use Azure SQL Database point-in-time restore within configured short-term retention” is the applicable architecture choice.

A would instead validate the other design where a financial organization must keep Azure SQL Database backup copies for many years. That evidence is consistent with configure long-term backup retention for the eligible Azure SQL database, because long-term retention preserves scheduled backups beyond normal short-term recovery windows. It does not demonstrate that the target case achieves a recovered database contains the expected records immediately before the incident.

C would instead validate the other design where a cloud team needs centralized protection and scheduled recovery points for Windows Azure virtual machines. That evidence is consistent with protect the eligible Azure VMs with Azure Backup in a suitable vault, because policy-managed VM backup produces recoverable points without custom scripts. It does not demonstrate that the target case achieves a recovered database contains the expected records immediately before the incident.

D would instead validate the other design where a PostgreSQL workload needs recovery to a point before a mistaken transaction, within its retention period. That evidence is consistent with use Azure Database for PostgreSQL Flexible Server point-in-time restore, because managed PostgreSQL backups support restoration to a new server at a supported timestamp. It does not demonstrate that the target case achieves a recovered database contains the expected records immediately before the incident.

“Use the managed instance's automated backup and supported point-in-time restore” relies on this Azure capability: managed Instance offers managed database backups with restore within available retention. This workload involves A financial organization must keep Azure SQL Database backup copies for many years. The decisive Azure design mechanism is: long-term retention preserves scheduled backups beyond normal short-term recovery windows. Thus “Configure long-term backup retention for the eligible Azure SQL database” is the applicable architecture choice.

“Configure Azure Blob object replication with the applicable prerequisites” relies on this Azure capability: object replication asynchronously copies eligible blobs and versions to another account. This workload involves A financial organization must keep Azure SQL Database backup copies for many years. The decisive Azure design mechanism is: long-term retention preserves scheduled backups beyond normal short-term recovery windows. Thus “Configure long-term backup retention for the eligible Azure SQL database” is the applicable architecture choice.

“Use Azure Database for PostgreSQL Flexible Server point-in-time restore” relies on this Azure capability: managed PostgreSQL backups support restoration to a new server at a supported timestamp. This workload involves A financial organization must keep Azure SQL Database backup copies for many years. The decisive Azure design mechanism is: long-term retention preserves scheduled backups beyond normal short-term recovery windows. Thus “Configure long-term backup retention for the eligible Azure SQL database” is the applicable architecture choice.

A would instead validate the other design where a PostgreSQL workload needs recovery to a point before a mistaken transaction, within its retention period. That evidence is consistent with use Azure Database for PostgreSQL Flexible Server point-in-time restore, because managed PostgreSQL backups support restoration to a new server at a supported timestamp. It does not demonstrate that the target case achieves a dated long-term backup remains listed and restorable under the retention policy.

B would instead validate the other design where a firm needs to restore Azure SQL Managed Instance databases after an application deployment failure. That evidence is consistent with use the managed instance's automated backup and supported point-in-time restore, because managed Instance offers managed database backups with restore within available retention. It does not demonstrate that the target case achieves a dated long-term backup remains listed and restorable under the retention policy.

C would instead validate the other design where a distributed application needs copies of selected block blobs at a second storage account via asynchronous policy. That evidence is consistent with configure Azure Blob object replication with the applicable prerequisites, because object replication asynchronously copies eligible blobs and versions to another account. It does not demonstrate that the target case achieves a dated long-term backup remains listed and restorable under the retention policy.

“Use a vault design with soft delete and immutability controls where supported” relies on this Azure capability: protected vault settings add deletion resistance beyond ordinary access controls. This workload involves A proposed Azure workload has the following constraint: A PostgreSQL workload needs recovery to a point before a mistaken transaction, within its retention period. The decisive Azure design mechanism is: managed PostgreSQL backups support restoration to a new server at a supported timestamp. Thus “Use Azure Database for PostgreSQL Flexible Server point-in-time restore” is the applicable architecture choice.

“Use the managed instance's automated backup and supported point-in-time restore” relies on this Azure capability: managed Instance offers managed database backups with restore within available retention. This workload involves A proposed Azure workload has the following constraint: A PostgreSQL workload needs recovery to a point before a mistaken transaction, within its retention period. The decisive Azure design mechanism is: managed PostgreSQL backups support restoration to a new server at a supported timestamp. Thus “Use Azure Database for PostgreSQL Flexible Server point-in-time restore” is the applicable architecture choice.

“Select an appropriate Azure Cosmos DB continuous backup mode and restore plan” relies on this Azure capability: continuous backup supports point-in-time restore under the mode's documented limits. This workload involves A proposed Azure workload has the following constraint: A PostgreSQL workload needs recovery to a point before a mistaken transaction, within its retention period. The decisive Azure design mechanism is: managed PostgreSQL backups support restoration to a new server at a supported timestamp. Thus “Use Azure Database for PostgreSQL Flexible Server point-in-time restore” is the applicable architecture choice.

A would instead validate the other design where a company wants ransomware-resistant backup copies that operators cannot casually delete. That evidence is consistent with use a vault design with soft delete and immutability controls where supported, because protected vault settings add deletion resistance beyond ordinary access controls. It does not demonstrate that the target case achieves the restored server contains the state before the unwanted transaction.

C would instead validate the other design where a firm needs to restore Azure SQL Managed Instance databases after an application deployment failure. That evidence is consistent with use the managed instance's automated backup and supported point-in-time restore, because managed Instance offers managed database backups with restore within available retention. It does not demonstrate that the target case achieves the restored server contains the state before the unwanted transaction.

D would instead validate the other design where a globally distributed Cosmos DB application needs restore to a chosen time after document corruption. That evidence is consistent with select an appropriate Azure Cosmos DB continuous backup mode and restore plan, because continuous backup supports point-in-time restore under the mode's documented limits. It does not demonstrate that the target case achieves the restored server contains the state before the unwanted transaction.

“Select an appropriate Azure Cosmos DB continuous backup mode and restore plan” relies on this Azure capability: continuous backup supports point-in-time restore under the mode's documented limits. This workload involves During a cloud design workshop, stakeholders explain: A firm needs to restore Azure SQL Managed Instance databases after an application deployment failure. The decisive Azure design mechanism is: managed Instance offers managed database backups with restore within available retention. Thus “Use the managed instance's automated backup and supported point-in-time restore” is the applicable architecture choice.

“Use Azure SQL Database point-in-time restore within configured short-term retention” relies on this Azure capability: platform backups support restoring a new database to a supported point in the retention window. This workload involves During a cloud design workshop, stakeholders explain: A firm needs to restore Azure SQL Managed Instance databases after an application deployment failure. The decisive Azure design mechanism is: managed Instance offers managed database backups with restore within available retention. Thus “Use the managed instance's automated backup and supported point-in-time restore” is the applicable architecture choice.

“Configure Azure Files share snapshots or supported Azure Backup file-share protection” relies on this Azure capability: share recovery points allow file and directory restoration from prior states. This workload involves During a cloud design workshop, stakeholders explain: A firm needs to restore Azure SQL Managed Instance databases after an application deployment failure. The decisive Azure design mechanism is: managed Instance offers managed database backups with restore within available retention. Thus “Use the managed instance's automated backup and supported point-in-time restore” is the applicable architecture choice.

A would instead validate the other design where a hybrid file workload needs frequent recoverable snapshots of a managed Azure file share. That evidence is consistent with configure Azure Files share snapshots or supported Azure Backup file-share protection, because share recovery points allow file and directory restoration from prior states. It does not demonstrate that the target case achieves the restored instance database passes functional checks at the requested recovery point.

B would instead validate the other design where a team needs to restore a managed Azure SQL database to a specific minute after an accidental delete. That evidence is consistent with use Azure SQL Database point-in-time restore within configured short-term retention, because platform backups support restoring a new database to a supported point in the retention window. It does not demonstrate that the target case achieves the restored instance database passes functional checks at the requested recovery point.

C would instead validate the other design where a globally distributed Cosmos DB application needs restore to a chosen time after document corruption. That evidence is consistent with select an appropriate Azure Cosmos DB continuous backup mode and restore plan, because continuous backup supports point-in-time restore under the mode's documented limits. It does not demonstrate that the target case achieves the restored instance database passes functional checks at the requested recovery point.

“Use Azure SQL Database point-in-time restore within configured short-term retention” relies on this Azure capability: platform backups support restoring a new database to a supported point in the retention window. This workload involves A globally distributed Cosmos DB application needs restore to a chosen time after document corruption. The decisive Azure design mechanism is: continuous backup supports point-in-time restore under the mode's documented limits. Thus “Select an appropriate Azure Cosmos DB continuous backup mode and restore plan” is the applicable architecture choice.

“Use Azure Backup file recovery from an appropriate VM recovery point” relies on this Azure capability: file-level recovery can extract individual files without a full VM reconstruction. This workload involves A globally distributed Cosmos DB application needs restore to a chosen time after document corruption. The decisive Azure design mechanism is: continuous backup supports point-in-time restore under the mode's documented limits. Thus “Select an appropriate Azure Cosmos DB continuous backup mode and restore plan” is the applicable architecture choice.

“Configure long-term backup retention for the eligible Azure SQL database” relies on this Azure capability: long-term retention preserves scheduled backups beyond normal short-term recovery windows. This workload involves A globally distributed Cosmos DB application needs restore to a chosen time after document corruption. The decisive Azure design mechanism is: continuous backup supports point-in-time restore under the mode's documented limits. Thus “Select an appropriate Azure Cosmos DB continuous backup mode and restore plan” is the applicable architecture choice.

A would instead validate the other design where an application owner must restore a single modified file from a supported Azure VM backup. That evidence is consistent with use Azure Backup file recovery from an appropriate VM recovery point, because file-level recovery can extract individual files without a full VM reconstruction. It does not demonstrate that the target case achieves restored documents reflect the chosen point before the damaging writes.

C would instead validate the other design where a team needs to restore a managed Azure SQL database to a specific minute after an accidental delete. That evidence is consistent with use Azure SQL Database point-in-time restore within configured short-term retention, because platform backups support restoring a new database to a supported point in the retention window. It does not demonstrate that the target case achieves restored documents reflect the chosen point before the damaging writes.

D would instead validate the other design where a financial organization must keep Azure SQL Database backup copies for many years. That evidence is consistent with configure long-term backup retention for the eligible Azure SQL database, because long-term retention preserves scheduled backups beyond normal short-term recovery windows. It does not demonstrate that the target case achieves restored documents reflect the chosen point before the damaging writes.