Study SAP-C02 Deployment Strategy for Business Requirements: key concepts, common traps, and exam decision cues.
Deployment questions in SAP-C02 are not just about shipping code. They are about choosing a release approach that matches risk tolerance, rollback speed, operational control, and repeatability. The best answer is usually the one that lowers blast radius while staying manageable.
| Need | Strongest first fit | Why |
|---|---|---|
| repeatable infrastructure deployment | CloudFormation or other IaC pattern | consistent and auditable change |
| low-risk application cutover | blue/green or canary style deployment | safer traffic shift and rollback |
| simple update with limited complexity | rolling deployment | gradual change with lower disruption |
| centralized configuration automation | AWS Systems Manager | config and ops automation layer |
| standardized build and release pipeline | AWS developer tools or CI/CD pattern | repeatable release flow |
| Pattern | Best cue |
|---|---|
| all-at-once | fastest, highest blast radius |
| rolling | moderate-risk progressive replacement |
| blue/green | cleaner rollback and safer cutover |
| IaC | infrastructure consistency, drift reduction, and auditability |
| Trap | Better rule |
|---|---|
| choosing the fastest deployment instead of the safest one the business requires | deployment design should match outage and rollback tolerance |
| treating manual configuration as good enough in a new solution | SAP-C02 strongly prefers repeatable automation |
| ignoring rollback behavior | a deployment design is incomplete if recovery is weak |
| separating app deployment from configuration management completely | both often matter to the final business outcome |
Deployment-design questions usually reward the safest repeatable release path. If the concern is quick rollback and low-risk cutover, think blue/green. If the concern is repeatable infrastructure, think infrastructure as code. If the concern is operational task automation, think Systems Manager. SAP-C02 usually prefers controlled deployment mechanics over “just update production” instincts.