Study SAP-C02 Modernization and Enhancements: key concepts, common traps, and exam decision cues.
Modernization questions ask whether you can spot the changes that make an application meaningfully better after migration. SAP-C02 rewards candidates who reduce coupling, remove unnecessary server ownership, and adopt managed integration and data patterns where they actually improve the system.
| Need | Strongest first fit | Why |
|---|---|---|
| event-driven or short-lived compute | Lambda | serverless execution fit |
| background work or workflow decoupling | SQS, SNS, EventBridge, or Step Functions | reduces tight coupling |
| container-based modernization | ECS, EKS, or Fargate | application packaging and service model change |
| highly variable access pattern or specialized data need | purpose-built database | better fit than a generic one-size store |
| simplification of operational burden | managed services and serverless first | modernization should reduce drag |
| Trap | Better rule |
|---|---|
| modernizing everything at once | change only what creates real architectural value |
| using serverless when the execution model is a poor fit | modernization should fit the workload, not fashion |
| keeping tightly coupled workflows because they already work | decoupling often improves resilience and scale too |
| treating integration services as interchangeable | queues, fan-out events, and workflows solve different problems |
Modernization questions usually reward targeted change, not blanket rewrites. If background work should not block user requests, decouple it with messaging or workflow services. If the execution is short-lived and event-driven, think Lambda. If the existing design is acceptable, do not rewrite just to sound modern. SAP-C02 prefers meaningful fit improvements over architecture fashion.