Swapping the three Azure SQL Database recovery tiers
The wrong answers swap the recovery tiers of Azure SQL Database. Active geo-replication and failover groups are offered for an in-region zero-data-loss target, and geo-restore is offered for a sub-minute requirement. Each tier has its own scope. Zone redundancy handles an Availability Zone failure with an RTO typically under 30 seconds and an RPO of 0. Failover groups cover a regional outage with an RTO typically under 60 seconds and an RPO of 0 or more, set by replication lag. Geo-restore takes minutes or hours.
See it in a sample questionPairing Cosmos DB consistency levels with the wrong RPO
The wrong answers pair a Cosmos DB consistency level with the wrong recovery point. Session consistency is offered as RPO 0, and Strong consistency is offered on accounts with multiple write regions. Only Strong consistency gives an RPO of 0 during a region outage, and it cannot be configured when multiple write regions are enabled. Session, consistent prefix and eventual consistency carry an RPO of less than 15 minutes, while Bounded Staleness is described by K and T values instead.
See it in a sample questionMixing up planned, unplanned and Microsoft-managed storage failover
The wrong answers treat every storage account failover as one operation. A customer-managed planned failover converts the account to GRS, keeps geo-redundancy and demotes the original primary to the new secondary. A customer-managed unplanned failover converts the account to LRS in the new primary region and deletes the original primary. Microsoft-managed failover is a third thing: it is reserved for extreme circumstances and cannot be started for an individual storage account, so a design with an RTO of 1 hour cannot depend on it.
See it in a sample questionMisplacing Azure Site Recovery A2A settings and components
The wrong answers move Azure Site Recovery A2A settings and components to places the documentation does not put them. The cache storage account sits in the source region, not the target. Crash-consistent recovery points are created every five minutes and that interval cannot be modified; the replication policy sets only the app-consistent snapshot frequency and recovery-point retention, and the app-consistent default is zero hours, meaning disabled. Configuration servers belong to the VMware-to-Azure path, while A2A uses the Mobility service extension on the source VM.
See it in a sample questionCrediting zones and region pairs with cross-region failover
The wrong answers credit availability zones and paired regions with protection they do not provide. Zones have independent power, cooling and networking but do not protect against a full-region outage. Region pairing staggers planned updates and sets a recovery order, yet deploying to a pair does not automatically provide high availability, disaster recovery or failover, and RBAC and policy are not mirrored. Mission-critical workloads combine multiple zones with multiple regions.
See it in a sample question