Study SAP-C02 Reliability Improvements: key concepts, common traps, and exam decision cues.
Reliability-improvement questions ask whether you can look at an existing architecture and identify what will actually break first. SAP-C02 rewards candidates who remove single points of failure, design for growth trends, and strengthen self-healing behavior without overbuilding.
| Need | Strongest first fit | Why |
|---|---|---|
| one-instance or one-AZ fragility | load balancing and Multi-AZ design | removes basic SPOFs |
| weak recovery from component failure | self-healing and elastic patterns | system recovers without manual intervention |
| stateful data risk | replication and better durability pattern | data continuity matters too |
| fast growth pressure | trend-aware scaling and quota planning | reliability includes future load |
| hidden architecture fragility | architecture review against failure boundaries | exposes weak links |
| Trap | Better rule |
|---|---|
| fixing compute without fixing state or routing | reliability has several layers |
| ignoring growth trends | today’s stable design may fail tomorrow’s volume |
| assuming defaults always remove SPOFs | check actual AZ, replication, and dependency behavior |
| focusing only on failover and not self-healing | smaller failures happen more often than full disasters |
Reliability-improvement questions usually target the most realistic present failure point. Remove obvious single points of failure first. Then check whether quotas, scaling behavior, or growth trends will turn into the next outage. Finally, improve self-healing and readiness for common failure paths before jumping to rare edge cases. SAP-C02 prefers practical reliability wins.