Study SAP-C02 Operational Excellence Improvements: key concepts, common traps, and exam decision cues.
Operational excellence questions ask whether you can make an AWS environment easier to observe, easier to recover, and easier to change safely. SAP-C02 wants targeted improvements, not a vague promise to “monitor more.”
| Need | Strongest first fit | Why |
|---|---|---|
| weak visibility into failures | CloudWatch metrics, logs, and alerts | monitoring comes first |
| repeated manual fixes | automated remediation | remove human bottlenecks |
| risky deployments | stronger CI/CD and rollout strategy | safer change path |
| configuration drift | Systems Manager automation and config management | repeatable operations |
| uncertain recovery readiness | game days and failure exercises | tested recovery beats assumed recovery |
| Trap | Better rule |
|---|---|
| adding dashboards without actionable alerting | observability should lead to response |
| automating low-value tasks first | prioritize the manual steps that create risk or delay |
| improving deployment speed without rollback safety | change quality matters more than raw pace |
| assuming DR works because the architecture says it should | exercises and failure tests expose reality |
Operational-improvement questions usually reward reducing repeat pain first. If the same remediation keeps happening, automate it. If recovery confidence is assumed but untested, run exercises or game days. If monitoring exists but action is still manual, tie observability to repeatable response. SAP-C02 often prefers operational leverage over more dashboards alone.