Study SAP-C02 Optimal Migration Approach: key concepts, common traps, and exam decision cues.
Once SAP-C02 decides a workload should move, the next question is how. The exam wants you to choose the right transfer or migration mechanism for the data type, application state, network path, identity requirement, and governance model involved.
| Need | Strongest first fit | Why |
|---|---|---|
| large-scale data transfer or sync | DataSync, Transfer Family, Snow Family, or S3 Transfer Acceleration | tool depends on distance, data shape, and path |
| server migration into AWS | AWS Application Migration Service | server rehost move |
| database migration or conversion | AWS DMS and SCT | data movement plus schema conversion path |
| hybrid connectivity for migration | DX, VPN, and Route 53 planning | network and name resolution matter |
| identity continuity during move | IAM Identity Center or Directory Service integration | auth model must move too |
| governance during migration | Control Tower and Organizations | landing zone and account model affect the move |
| Trap | Better rule |
|---|---|
| treating data, apps, and databases as one transfer problem | they often need different mechanisms |
| picking tools before checking network and identity dependencies | migrations break when supporting controls are ignored |
| using one governance model for every migration | landing-zone and account structure should match the target estate |
| assuming database migration is only data copy | schema conversion and compatibility often matter too |
Migration-approach questions usually reward matching the tool to the migration pattern. If the issue is server rehosting, think Application Migration Service. If the issue is database transfer and replication, think AWS DMS. If the migration stem includes identity, private connectivity, or account setup, include those dependencies in the plan instead of treating migration as only copy mechanics.