AWS Certified Solutions Architect – Professional (SAP-C02) Study Guide: Domains and Study Plan
An AWS SAP-C02 study guide covering the four exam domains, architecture decisions in complex environments, and a practical preparation plan.
The AWS Certified Solutions Architect – Professional (SAP-C02) exam tests how to design, evaluate, and improve AWS solutions in complex business and organizational environments. In addition to new designs, it covers multi-account governance, existing-system improvement, migration, and modernization. The focus is weighing multiple constraints—not memorizing a longer list of services.
This guide covers the target candidate, the four exam domains, and a preparation plan. Objectives and service scope can change, so use the latest AWS SAP-C02 exam guide as your source of truth.
Who is this exam for?
- Solutions architects who advise across multiple applications or projects.
- Multi-account or migration leads who work with organizational governance, connectivity, and workload moves.
- Experienced cloud architects preparing to advance beyond SAA and handle more complex scenarios.
AWS describes the target candidate as having at least two years of experience using AWS to design and implement cloud solutions. This is a target-candidate profile, not a registration requirement. If common architecture patterns are still new to you, first build the foundation covered in SAA-C03.
Still choosing a certification path? See How to choose an IT certification. For practice setup, see the CertDrill getting started guide.
SAP-C02 vs SAA-C03
SAA-C03 focuses on architecture choices in common scenarios. SAP-C02 asks you to weigh options across more complex organizations and systems, often involving multiple applications, teams, and business goals. It is not just a longer service list: you need to explain how a solution is governed, operated, improved, or migrated.
| SAA-C03 | SAP-C02 | |
|---|---|---|
| Focus | Architecture choices for common scenarios | Cross-solution design and improvement in complex organizations |
| Typical constraints | Security, resilience, performance, and cost for a workload | Multiple accounts and applications, migration, and long-term operations |
| Preparation | Build architecture fundamentals | Apply experience to integrated scenarios |
Exam domains and weights
Weights are percentages of scored content and can help you plan study time. The official guide also lists task statements for each domain; use those objectives in your review.
| Domain | Official name | Main focus | Weight |
|---|---|---|---|
| 1 | Design Solutions for Organizational Complexity | Organizational complexity, multi-account design, networking, identity, and governance | 26% |
| 2 | Design for New Solutions | Designing solutions around business goals | 29% |
| 3 | Continuous Improvement for Existing Solutions | Improving operations, security, performance, and reliability | 25% |
| 4 | Accelerate Workload Migration and Modernization | Workload migration and modernization | 20% |
Domain 2 has the largest weight, but the other three domains make up most of the scored content together. Do not leave migration or existing-system improvement until the end.
How to study each domain
Domain 1: Design Solutions for Organizational Complexity
Focus on connectivity, security controls, reliability, and governance across multiple accounts. Be ready to explain how shared-services and workload accounts work together, how networks connect, and how identities and permissions are managed across accounts. Understand the roles of services such as Organizations, Control Tower, and Transit Gateway in the context of an overall design.
Common mix-up: drawing a multi-account diagram without explaining how policies are enforced, exceptions are handled, or traffic moves between accounts. Trace identity, network traffic, and governance controls separately.
Domain 2: Design for New Solutions
Design deployment, business continuity, security, reliability, performance, and cost approaches for business requirements. First identify constraints such as availability, compliance, latency, budget, and team capability; then compare architecture options.
Common mix-up: choosing an option that works technically but ignoring operations or non-functional requirements. Explain how each choice meets the constraints and what trade-offs it introduces.
Domain 3: Continuous Improvement for Existing Solutions
Improve operational excellence, security, performance, and reliability while working within existing systems and legacy constraints. Establish a baseline and identify bottlenecks before choosing changes that can be validated and managed safely. The Well-Architected Framework can provide one useful review structure.
Common mix-up: claiming an improvement without a baseline, or treating a rewrite as the answer to every problem. Start with evidence, then propose the smallest viable change, how to validate it, and how to roll it back.
Domain 4: Accelerate Workload Migration and Modernization
Understand migration drivers, workload assessment, migration strategies (often called the 6 Rs), and the scope of modernization. Plan data movement, cutover, and rollback. Different workloads can use different strategies; a full rewrite is not always necessary.
Common mix-up: choosing a migration strategy that does not match the business driver, or failing to define rollback conditions. For each workload, record the driver, strategy, risks, cutover conditions, and fallback plan.
Check your readiness with three questions
- In a multi-account environment, how would you manage identity and networking between shared services and workload accounts?
- When improving a legacy system, how would you validate the change and reduce release risk?
- If a migration cutover fails, what triggers rollback, and how will you protect data consistency?
If two answers are unclear, strengthen the matching domain before adding more scenario practice.
Suggested study order
- Build the SAA-C03 foundation: review common patterns for security, resilience, performance, and cost.
- Organizational complexity: multi-account design, identity, connectivity, and governance.
- New solutions: compare complete designs against business and non-functional requirements.
- Continuous improvement: baselines, bottlenecks, validation, and rollback.
- Migration and modernization: business drivers, migration strategies, cutover, and risk controls.
This is a suggested learning sequence, not a requirement to pass SAA-C03 before taking SAP-C02.
A three-step preparation plan
- Use the official guide. Mark familiar and weak areas against the latest domain task statements, then plan time by weight.
- Work through real scenarios. For each domain, record constraints, candidate solutions, key trade-offs, validation, and risks. Learn services in terms of the problems they solve.
- Practice and review mistakes. Use scenario questions and group misses by domain and cause. For recurring gaps, return to the matching official task statement and AWS documentation.
Frequently asked questions
Do I have to pass SAA-C03 before SAP-C02?
No. AWS does not require SAA-C03 first. However, the architecture fundamentals covered by SAA-C03 usually help when learning to handle SAP-C02 scenarios.
What makes SAP-C02 difficult?
The challenge is managing multiple constraints in long scenarios. You may need to consider organization, reliability, security, cost, migration, and operations together instead of matching the question to one service.
How long does preparation take?
There is no fixed timeline. People with hands-on architecture experience can start integrated scenario practice sooner. If you have less experience, build SAA-C03-level fundamentals first and plan further study based on practice results.
Start practicing
When you are ready, use exam code SAP-C02 to practice by domain, then use missed questions to revisit the matching exam objectives and AWS materials.