Study DOP-C02 high availability for Multi-AZ, multi-Region, failover design, and single-point-of-failure removal.
High-availability questions on DOP-C02 are really about fault-domain design. AWS is testing whether the workload can survive the failure you were told to care about without paying for broader resilience than the business actually needs.
When the prompt says:
The strongest answer usually matches the named failure domain instead of automatically choosing the biggest topology.
| Requirement | Strongest first fit | Why |
|---|---|---|
| Survive a single Availability Zone loss | Multi-AZ placement with balanced traffic and redundant dependencies | Matches the named failure boundary |
| Survive regional disruption | Multi-Region service and routing design | Broader blast-radius protection |
| Remove SPOF in traffic distribution | Cross-AZ load balancing and health-checked targets | Prevents one-zone concentration |
| Protect stateful tiers | Service-appropriate replication/failover pattern | Stateless patterns alone are not enough |
DOP-C02 likes distractors that make compute resilient while quietly leaving the data tier exposed. If the database, queue, shared file system, or routing layer is still a single failure point, the architecture is not really highly available.
When the question is about availability, ask which failure domain is in scope first. Then verify that compute, data, and traffic-routing layers all respect that same boundary.