Study SAP-C02 Business Continuity Solution Design: key concepts, common traps, and exam decision cues.
Business continuity questions for new solutions ask whether you can design recovery deliberately instead of bolting it on later. SAP-C02 wants you to connect recovery targets, replication choices, DNS failover, and testing discipline into one coherent design.
| Need | Strongest first fit | Why |
|---|---|---|
| recover from backup with longer downtime tolerance | backup and restore design | lowest-cost continuity path |
| scale up from a reduced environment | warm standby | faster recovery with lower steady-state cost than active-active |
| maintain stronger regional continuity | multi-Region or highly ready failover pattern | lower downtime during major failure |
| route traffic away from unhealthy endpoints | Route 53 health checks and routing policies | traffic steering is part of continuity |
| prove recovery design works | regular DR and restore testing | untested continuity is weak continuity |
| Trap | Better rule |
|---|---|
| designing backup without recovery routing | continuity often needs both data and traffic movement |
| answering every continuity question with multi-Region active-active | match the pattern to the actual RTO / RPO |
| ignoring DR testing | SAP-C02 often rewards tested readiness over theoretical design |
| forgetting that dependencies must also fail over | data, secrets, DNS, and app components move together |
RTO and RPOContinuity-design questions usually require you to connect recovery targets to actual failover mechanics. If there is always-on reduced capacity in another Region, think warm standby. If DNS should steer away from unhealthy endpoints, think Route 53 health checks and failover routing. Strong SAP-C02 answers include recovery objectives, a failover mechanism, and evidence that the design is tested.