A regulated workload runs in one Region with an RTO of about an hour and an RPO of a few minutes, but the business will only fund a recovery Region that keeps costs minimal until a disaster is declared. The team replicates the database continuously to a small standby instance in the second Region but keeps the application tier switched off there. At failover they will start and scale up the application tier. Which disaster recovery strategy does this design represent?
- ABackup and restore, because data is copied to the second Region and the application is rebuilt from those backups only after a disaster is declared.
- BPilot light, because the core data is replicated live to an always-on database while the application tier stays off until it is started at failover. Correct
- CWarm standby, because a scaled-down but fully running copy of the whole stack already serves a fraction of traffic in the second Region at all times.
- DMulti-site active-active, because the second Region holds a replica of the data and can take over production traffic during a Regional event.
Why A is wrong: Backup and restore keeps no live infrastructure running in the recovery Region and rebuilds everything from snapshots, so it cannot deliver the few-minute RPO a continuously replicated standby database provides.
Why B is correct: Pilot light keeps only the critical core, typically the replicated database, running continuously while the rest of the stack is dormant and brought up at failover, which matches the live standby database and switched-off application tier exactly.
Why C is wrong: Warm standby runs the application tier continuously at reduced capacity, but here the application tier is switched off, so the design stops short of a full always-on stack.
Why D is wrong: Active-active runs full production capacity serving live traffic in both Regions at once, whereas this design keeps the application tier off in the second Region until failover, so it is not active-active.