AWS SAP-C02 30-, 60-, and 90-day study plan for Well-Architected, migration, trade-offs, review loops, and final-week priorities.
Use this study plan when you want a real route through AWS Certified Solutions Architect - Professional (SAP-C02) instead of jumping between advanced AWS services. SAP-C02 is a professional architecture exam, so the hard part is not remembering that a service exists. The hard part is choosing the safest enterprise design under constraints.
AWS’s current exam guide frames SAP-C02 around the AWS Well-Architected Framework, organizational complexity, new-solution design, continuous improvement, and migration or modernization. Expect long scenarios where several answers are technically possible but only one best fits the stated constraint.
I verified these current AWS exam facts on May 16, 2026.
| Item | Value |
|---|---|
| Exam | AWS Certified Solutions Architect - Professional |
| Exam code | SAP-C02 |
| Category | Professional |
| Questions | 75 total |
| Scoring | 65 scored + 10 unscored (unscored items are not identified) |
| Question types | Multiple choice and multiple response |
| Time | 180 minutes |
| Passing score | 750, scaled 100-1000 |
| Cost | 300 USD |
| Target candidate | 2 or more years of experience designing and implementing AWS cloud solutions |
AWS also notes that emerging topics can appear as unscored pretest questions. For SAP-C02, that means you should not ignore modern architecture controls around generative AI, responsible AI guardrails, access controls for agentic applications, and human approval workflows. Do not over-allocate time to those topics, but be ready to reason from first principles if they appear.
| Domain | Weight | How to allocate study time |
|---|---|---|
| Design for New Solutions | 29% | Spend the most time on deployment, continuity, security, reliability, performance, and cost choices for new workloads. |
| Design Solutions for Organizational Complexity | 26% | Drill multi-account governance, hybrid connectivity, centralized security, shared services, resilience, and cost visibility. |
| Continuous Improvement for Existing Solutions | 25% | Practice diagnosing current-state weaknesses and improving operations, security, performance, reliability, and cost without unnecessary rebuilds. |
| Accelerate Workload Migration and Modernization | 20% | Study migration assessment, wave planning, migration tooling, target architectures, and modernization depth. |
The weights are close enough that you cannot safely skip a domain. The right strategy is to spend slightly more time on new-solution and organizational-design scenarios, then use migration and continuous-improvement drills to expose weak service-choice assumptions.
| Starting point | Typical study time | Best-fit timeline |
|---|---|---|
| You regularly design multi-account AWS environments | 55-80 hours | 30-60 days |
| You hold SAA-C03 and work with AWS architecture, but not at enterprise scale | 80-120 hours | 60 days |
| You are strong in operations or security but weaker in architecture trade-offs | 100-140 hours | 60-90 days |
| You are new to hybrid networking, migration, governance, and DR design | 140+ hours | 90 days before scheduling |
Choose the longer route if you still guess between Transit Gateway, PrivateLink, VPC peering, Direct Connect, VPN, Route 53 Resolver, multi-account shared services, or centralized inspection. SAP-C02 is unforgiving when connectivity, identity, and recovery boundaries blur together.
Use the same loop every week. The goal is not to memorize isolated facts; it is to turn long requirements into architecture decisions.
flowchart LR
S["Scenario"] --> C["Constraint"]
C --> P["Pattern"]
P --> T["Trade-off"]
T --> E["Eliminate weaker answers"]
E --> M["Miss rule"]
| Step | What to do |
|---|---|
| Scenario | Read for business requirement, current state, constraint, and failure consequence before looking at service names. |
| Constraint | Label the dominant constraint: governance, connectivity, recovery, migration speed, cost, performance, security, or operations. |
| Pattern | Choose the architecture pattern before choosing the AWS service. |
| Trade-off | State what the selected answer improves and what it costs. |
| Eliminate | Remove answers that are plausible but violate scale, operational burden, RTO/RPO, security, or migration-depth constraints. |
| Miss rule | Write one sentence that would have helped you answer faster next time. |
Use this route only if you already have strong AWS architecture experience and can study most days.
| Week | Focus | What to produce |
|---|---|---|
| 1 | Organizational complexity | A multi-account and hybrid-connectivity map covering Organizations, Control Tower, shared services, TGW, DX, VPN, PrivateLink, Resolver, logging, and cost allocation. |
| 2 | New-solution design | A design checklist for deployment, continuity, security, reliability, performance, and cost decisions. |
| 3 | Continuous improvement | A current-state repair matrix for operations, security, reliability, performance, and cost improvements. |
| 4 | Migration, modernization, and mixed scenarios | A migration decision sheet covering 7Rs, wave planning, MGN, DMS, SCT, DataSync, Snow, Transfer Family, target architecture, and modernization depth. |
Every day should create one artifact, not just another pass through notes.
| Artifact | Why it matters |
|---|---|
| Constraint map | Forces you to answer the question being asked instead of the service you prefer. |
| Architecture chooser | Helps separate similar patterns such as PrivateLink, TGW, VPC peering, Cloud WAN, and service endpoints. |
| DR ladder | Converts RTO/RPO language into backup and restore, pilot light, warm standby, active/passive, or active/active design. |
| Migration wave table | Prevents treating all workloads as rehost or refactor candidates. |
| Miss log | Turns long-scenario mistakes into reusable elimination rules. |
This is the best default route for most candidates.
| Weeks | Focus | What to do |
|---|---|---|
| 1-2 | Organizational Complexity | Study network connectivity, security controls, resilience, multi-account environments, centralized logging, shared services, and cost visibility. |
| 3-4 | Design for New Solutions | Work through deployment, continuity, security, reliability, performance, and cost design. Practice choosing managed services when they reduce operational burden without violating constraints. |
| 5 | Continuous Improvement | Diagnose existing workloads. Improve one weak dimension without accidentally damaging security, reliability, cost, or operations. |
| 6 | Migration and Modernization | Drill assessment, 7Rs, wave planning, migration tools, target architecture, and modernization decisions. |
| 7 | Mixed long-scenario practice | Run timed sets. Group misses by constraint type, not by service name. |
| 8 | Final repair and scheduling decision | Reread weak lessons, review the cheat sheet, answer sample questions, and schedule only if misses are narrow. |
Use this route if SAP-C02 is your first professional-level cloud exam or if your AWS work is deep in one lane but shallow elsewhere.
| Phase | Weeks | Outcome |
|---|---|---|
| Enterprise foundation | 1-3 | You can design account structure, OU guardrails, identity boundaries, central logging, shared services, hybrid DNS, and network connectivity. |
| New-solution design | 4-6 | You can choose deployment, continuity, security, reliability, performance, and cost patterns from requirements. |
| Existing-solution improvement | 7-8 | You can diagnose a workload and improve it without proposing an unnecessary rebuild. |
| Migration and modernization | 9-10 | You can choose migration strategy, tools, target architecture, and modernization depth by dependency and business risk. |
| Exam execution | 11-12 | You can read long scenarios quickly, eliminate plausible distractors, and maintain pace across 75 questions in 180 minutes. |
| Domain | Drill questions until you can answer… |
|---|---|
| Design Solutions for Organizational Complexity | Which account, network, identity, security, logging, and cost-visibility boundary makes the design governable at scale? |
| Design for New Solutions | Which design best satisfies the business requirement with the least unsafe operational burden? |
| Continuous Improvement for Existing Solutions | What is broken in the current state, and what change improves it without introducing a larger risk? |
| Accelerate Workload Migration and Modernization | How far should the workload change now: rehost, replatform, repurchase, refactor, retire, retain, or relocate? |
SAP-C02 often tests patterns that look interchangeable until you focus on the constraint.
| Decision | Choose by asking… |
|---|---|
| Transit Gateway vs VPC peering vs Cloud WAN | Is this a few VPCs, a hub-and-spoke design, or a global network operating model? |
| PrivateLink vs public endpoint with controls | Does the consumer need private service access without exposing or routing through the provider VPC? |
| Direct Connect vs VPN | Is the requirement predictable private connectivity, lower latency, higher consistency, or a faster/lower-cost encrypted path? |
| Multi-AZ vs Multi-Region | Is the failure model an AZ failure, regional disruption, compliance boundary, or latency requirement? |
| Pilot light vs warm standby vs active/active | What RTO/RPO and cost posture does the business actually require? |
| SQS/SNS/EventBridge/Step Functions | Is the problem buffering, fanout, event routing, or workflow orchestration? |
| Aurora/RDS/DynamoDB/OpenSearch/ElastiCache | Is the access pattern relational, key-value, search/analytics, or caching? |
| Rehost vs replatform vs refactor | Does the requirement favor speed, managed operations, or application-level redesign? |
SAP-C02 questions are longer than associate-level questions. Practice a fixed reading method:
If two answers both work technically, choose the one that better matches the stated operating model. SAP-C02 frequently punishes designs that are powerful but too complex, too manual, too expensive, or too disruptive for the requirement.
Use the final week for cross-domain decision speed.
| Day | Work |
|---|---|
| 7 days out | Reread the cheat sheet and summarize each domain as one decision problem. |
| 6 days out | Drill organizational complexity: accounts, OUs, governance, hybrid connectivity, DNS, central logging, and cost allocation. |
| 5 days out | Drill new-solution design: deployment, continuity, security, reliability, performance, and cost. |
| 4 days out | Drill continuous improvement: operations, security, reliability, performance, and cost repairs. |
| 3 days out | Drill migration and modernization: assessment, wave planning, 7Rs, tools, target architecture, and modernization depth. |
| 2 days out | Run one mixed timed block and rebuild your miss log into short decision rules. |
| 1 day out | Review only weak rules, domain weights, high-yield comparisons, and official exam facts. |
You are close to ready when:
This is not enough for most candidates, but if you are already close:
Schedule only when your misses are explainable and narrow. If your reasoning still starts with “which AWS service do I remember?” instead of “what constraint must the architecture satisfy?”, keep studying. SAP-C02 rewards professional architecture judgment under time pressure.