Study SAP-C02 Performance Improvements: key concepts, common traps, and exam decision cues.
Performance-improvement questions are about diagnosing what is slow or strained today, then choosing the change that improves measurable outcomes. SAP-C02 rewards candidates who can connect business KPIs, technical bottlenecks, and the right AWS improvement path.
| Need | Strongest first fit | Why |
|---|---|---|
| no shared definition of acceptable performance | define KPIs and SLAs first | you cannot improve what is not measured |
| backend bottleneck or underpowered resource | rightsize or redesign the constrained layer | direct throughput improvement |
| slow global user experience | edge acceleration such as CloudFront or Global Accelerator | path optimization |
| old platform causing avoidable drag | adopt a better managed service | reduce platform overhead and improve fit |
| unknown bottleneck source | monitoring and profiling before change | avoid random tuning |
| Trap | Better rule |
|---|---|
| optimizing the loudest component instead of the actual bottleneck | measure first, then tune |
| treating rightsizing as only a cost exercise | it can also improve performance fit |
| ignoring edge services for distributed users | path and geography often matter more than backend scale |
| adopting new technology without linking it to the problem | better service fit should solve a measurable weakness |
Performance-improvement questions usually punish redesign before diagnosis. Start by confirming the KPI and measurable bottleneck. Then decide whether the real issue is geographic path, compute shape, data access, or another service fit problem. If users are far from the backend, think edge acceleration. Strong SAP-C02 answers tie technical tuning to business-facing performance signals.