ISC2 Certified Cloud Security Professional (CCSP) Practice Question

A pilot-light disaster-recovery pattern keeps only the most critical components-typically the databases and minimal supporting services-running continuously in a secondary region, with continuous or near-real-time replication. This enables a recovery-point objective (RPO) measured in minutes, satisfying the 15-minute requirement. During an actual outage, automation spins up the remaining application tiers and scales resources, allowing service restoration within a few hours, thereby meeting the four-hour recovery-time objective (RTO). Because most application servers are started only during failover, steady-state costs remain much lower than in warm-standby or active/active solutions. A warm-standby pattern could meet the same RPO/RTO but runs more resources all the time, increasing cost. A simple backup-and-restore approach might meet the 15-minute RPO if very frequent backups are configured, but the time needed to provision infrastructure and restore large data sets often exceeds a four-hour RTO. An active/active multi-site architecture clearly meets (or exceeds) the recovery objectives but incurs the highest continuous cost.