AWS SAP-C02: Architect at Scale — Trade-offs at Every Layer
The professional exam expects you to design complex, multi-account, hybrid architectures — not just select individual services. Integration patterns and migration strategies dominate.
Check Your Readiness →Most candidates understand AWS Certified Solutions Architect - Professional concepts — and still fail. This exam tests how you apply knowledge under pressure.
SAP-C02 requires synthesis across multiple AWS domains simultaneously. Every question presents a complex scenario with multiple valid options — the correct answer is the one that best balances all specified constraints including cost, operational complexity, resilience, and security.
Rehost all servers using lift-and-shift to minimize risk
Assess each workload against the 7 Rs — some servers may be candidates for retirement, replatforming, or refactoring that deliver better outcomes than a blanket lift-and-shift approach
Use Warm Standby since it's cost-effective and provides fast recovery
RTO of 1 minute requires Multi-Site Active/Active or Multi-Region Active-Active — Warm Standby typically achieves minutes-to-tens-of-minutes RTO, which doesn't meet the requirement
Create separate VPCs and peer them all
Use AWS Transit Gateway for hub-and-spoke networking at scale; VPC peering doesn't scale to many accounts and requires N*(N-1)/2 connections
Enterprise architectures on AWS use AWS Organizations with multiple accounts for security isolation, billing separation, and compliance. Candidates who design everything in one account miss the organizational architecture layer.
Rehosting (lift-and-shift) is fast but misses cloud benefits. Replatforming makes targeted changes (e.g., switch to RDS). Refactoring redesigns for cloud-native. Selecting the wrong migration strategy for the business context is a common error.
Backup & Restore has the longest RTO/RPO. Pilot Light maintains core services warm. Warm Standby maintains a scaled-down full environment. Multi-Site Active/Active has near-zero RTO/RPO. Matching the wrong strategy to the RPO requirement is a fundamental error.
SAP-C02 rewards architecturally sound simplicity. Candidates who design highly complex solutions when a simpler managed service approach meets the stated requirements score lower than those who identify the elegantly simple answer.
At enterprise scale, SCPs restrict what accounts can do regardless of IAM policies. Candidates who don't account for SCP restrictions when designing cross-account access patterns produce incorrect security designs.
Professional-level AWS tests synthesis and trade-offs, not individual service knowledge. Test whether you can architect at enterprise scale.