SAP-C02 Continuous Improvement Guide

Study SAP-C02 Continuous Improvement: key concepts, common traps, and exam decision cues.

This chapter is where SAP-C02 stops asking what you would build from scratch and starts asking how you would make a real AWS estate better. The exam rewards candidates who can diagnose what is weak today, then improve it with the right mix of automation, guardrails, observability, architecture change, and cost discipline.

Current weight in the exam guide

AWS currently weights this domain at 25% of scored content.

Work this domain in order

Lesson Focus
3.1 Operational Excellence Improvements Learn how monitoring, remediation, CI/CD, and config automation improve day-two operations.
3.2 Security Improvements Learn how least privilege, secrets, patching, backup, and automated detection strengthen the environment.
3.3 Performance Improvements Learn how KPIs, bottlenecks, edge services, and rightsizing shape performance tuning.
3.4 Reliability Improvements Learn how replication, self-healing, load balancing, and quota awareness reduce fragility.
3.5 Cost Optimization Opportunities Learn how reports, alarms, unused-resource cleanup, and price models lower waste.

Fast routing inside this chapter

If the question is really about… Go first to…
alerting, auto remediation, CI/CD improvement, or Systems Manager automation 3.1 Operational Excellence Improvements
secret handling, Config rules, patching, backup process, or security traceability 3.2 Security Improvements
KPIs, bottlenecks, edge acceleration, or performance rightsizing 3.3 Performance Improvements
SPOFs, growth trends, replication, self-healing, or HA tuning 3.4 Reliability Improvements
underutilized resources, billing alarms, CUR analysis, or tagging for allocation 3.5 Cost Optimization Opportunities

What strong answers usually do

  • start with the real weakness in the current state instead of proposing a full rebuild
  • prefer improvements that increase automation, observability, and repeatability together
  • use AWS managed analysis tools before guessing about waste or bottlenecks
  • improve one dimension without quietly making security, reliability, or operability worse

In this section

Revised on Sunday, May 10, 2026