SAP-C02 Exam Guide: Scope, Study Decisions, and Scheduling
AWS Certified Solutions Architect - Professional (SAP-C02) validates advanced skills for designing optimized AWS solutions using the AWS Well-Architected Framework. It is aimed at solutions architects who can evaluate requirements, recommend architectures, and provide guidance across complex organizations; AWS describes the target candidate as having 2 or more years of experience using AWS services to design and implement cloud solutions. This guide helps you decide whether your experience matches the exam, which domains need the most study time, and how to prepare without relying on memorized question material.
What SAP-C02 actually validates
SAP-C02 tests architectural judgment rather than isolated service recall. The exam evaluates whether you can design for organizational complexity, design new solutions, continuously improve existing solutions, and accelerate workload migration and modernization within the scope of the AWS Well-Architected Framework.
The target candidate can evaluate cloud application requirements and make architectural recommendations for deployment on AWS. The role also includes providing expert guidance across multiple applications and projects in a complex organization. That distinction matters: preparation should connect services to business, operational, security, cost, reliability, and migration constraints instead of treating each service as a separate vocabulary list.
A candidate with only introductory AWS knowledge may recognize many services but still struggle with SAP-C02 scenarios. The professional-level standard assumes that you can weigh competing requirements, identify the constraint that matters most, and select an architecture that remains suitable when scale, governance, resilience, or migration complexity changes.
Who should consider this exam
SAP-C02 is a sensible target for an experienced solutions architect or an engineer who regularly makes cross-service AWS design decisions. It is less suitable as a first AWS certification because the exam assumes practical familiarity with designing and implementing cloud solutions, not just awareness of AWS terminology.
Use the target-candidate description as a readiness check rather than a formal prerequisite. AWS does not require AWS training to take a certification exam, and the supplied AWS guidance describes training as recommended, not mandatory. Your more useful question is whether you can explain why one design is preferable to another under explicit constraints.
Before scheduling, write down several architectures you have designed, reviewed, migrated, or operated. For each one, record the requirements, trade-offs, failure risks, security boundaries, cost drivers, and areas you would improve. If those explanations remain vague, strengthen design reasoning before investing heavily in exam-specific practice.
The exam guide identifies frontend development for mobile apps, the 12-factor app methodology, and in-depth operating-system knowledge as out of scope. This does not mean application architecture is irrelevant; it means preparation should stay focused on AWS solution architecture rather than deep mobile frontend implementation or operating-system internals.
How the exam is structured and scored
SAP-C02 contains 75 questions: 65 scored questions and 10 unscored questions. The unscored questions are not identified, so treat every item as real during the appointment. AWS uses the unscored content to evaluate questions for possible future use as scored questions.
The exam uses multiple-choice questions with one correct answer and three distractors, and multiple-response questions with two or more correct answers among five or more options. For multiple-response items, you must select all correct responses to receive credit. Read the requested number of selections carefully rather than assuming that one attractive answer is enough.
Unanswered questions are scored as incorrect, and AWS states that guessing is not penalized. Therefore, use an elimination process, select the best supported response, and do not leave items blank when you have reached the end of your review time. This is a test-taking recommendation based on the official scoring rules, not a claim that guessing replaces preparation.
Results are reported as a scaled score of 100–1,000, with a minimum passing score of 750. The score represents performance on the exam as a whole; section-level feedback should be interpreted cautiously. Do not turn a domain percentage or a practice result into a supposed pass prediction.
Which domains deserve the most study time
The blueprint divides SAP-C02 into four domains. The percentages are useful for allocating study effort, but they are not a substitute for the task statements: Domain 2 has the largest share, while all four domains require connected architectural reasoning.
Content Domain 1: Design Solutions for Organizational Complexity is weighted at 26%. Study multi-account and multi-application concerns, governance boundaries, identity and access design, centralized or delegated controls, networking between environments, and how an organization can operate consistently without eliminating necessary team autonomy.
Content Domain 2: Design for New Solutions is weighted at 29%. This is the largest domain, so give it substantial attention. Practice translating requirements into architectures involving compute, databases, storage, networking, security, availability, cost management, serverless design, and microservices or component decoupling. Focus on selecting an appropriate pattern for the stated workload rather than selecting the most feature-rich service.
Content Domain 3: Continuous Improvement for Existing Solutions is weighted at 25%. Prepare to assess an existing design, identify its weaknesses, and recommend improvements for reliability, performance, security, operations, and cost. The word existing is important: the best answer may involve incremental change, observability, governance, or a migration step rather than a complete rebuild.
Content Domain 4: Accelerate Workload Migration and Modernization is weighted at 20%. Study discovery, dependency analysis, migration sequencing, data transfer, modernization choices, hybrid connectivity, cutover risk, and post-migration improvement. A technically elegant target architecture is not automatically the best migration plan if it increases business disruption or cannot be delivered within the stated constraints.
AWS’s technologies-and-concepts list includes compute, cost management, databases, disaster recovery, high availability, management and governance, microservices and component decoupling, migration and data transfer, networking, connectivity and content delivery, security, serverless design principles, and storage. AWS says this list is non-exhaustive and subject to change, and its ordering does not indicate relative exam weight.
How to turn the blueprint into a study plan
Start with the official exam guide and convert each domain task into a checklist of decisions you can explain. Then assess yourself with architecture scenarios, validate weak areas against AWS documentation, and repeat the scenarios after you have corrected your reasoning. A study plan should expose decision gaps, not merely increase the number of notes you own.
First, perform a diagnostic without looking up answers. Sort each missed or uncertain topic into one of three causes: missing service knowledge, misunderstanding of a requirement, or weak trade-off analysis. These causes require different remedies. Documentation helps with the first; structured scenario review is more useful for the second and third.
Next, build service relationships rather than isolated summaries. For a major workload pattern, map the likely compute, data, network, identity, observability, resilience, and cost choices. Write one sentence explaining when each alternative becomes preferable. For example, do not memorize a service as simply ‘highly available’; identify the availability requirement, failure boundary, operational model, and data behavior that make a design appropriate.
After the first pass, use timed scenario sets. Review every option, including the options you rejected, and identify the wording that made each one weaker. Maintain an error log with the requirement, your initial choice, the decisive constraint, and the AWS concept that resolved the question. This prevents repeated mistakes caused by familiar-looking distractors.
Finish with mixed-domain practice. The real challenge is often a scenario that combines governance, networking, security, resilience, cost, and migration concerns. A final study phase that covers only one service family at a time can hide weaknesses in prioritization.
A practical SAP-C02 roadmap
A flexible roadmap works better than a rigid calendar because your starting experience will determine how long each phase takes. Use the sequence below as a study order, and move forward only when you can explain architecture choices in your own words and support them with AWS documentation.
Phase 1: establish scope. Read the SAP-C02 exam guide, domain outline, technologies-and-concepts page, and in-scope service information. Mark unfamiliar terms, but do not attempt to memorize the entire service catalogue. Identify whether your main gap is architecture experience, AWS service behavior, or exam-item reasoning.
Phase 2: strengthen foundations by workload. Review identity and security, networking and connectivity, compute, storage, databases, integration, serverless design, observability, governance, cost management, disaster recovery, and migration. For each area, compare common options using requirements such as latency, durability, access pattern, compliance, scale, operational effort, and failure recovery.
Phase 3: study by domain. Begin with Content Domain 2: Design for New Solutions because it carries the highest official weight, then cover Content Domain 1: Design Solutions for Organizational Complexity, Content Domain 3: Continuous Improvement for Existing Solutions, and Content Domain 4: Accelerate Workload Migration and Modernization. Do not skip the smaller domain; migration and modernization scenarios often depend on knowledge from the other domains.
Phase 4: practise architecture narratives. Take a scenario and state the requirements, constraints, candidate patterns, rejected alternatives, and final recommendation. Then ask what would change if the priority shifted from cost to resilience, from speed to governance, or from a greenfield build to a migration. This exercise builds the conditional reasoning the exam expects.
Phase 5: simulate the decision process. Use legitimate practice material that tests understanding, not leaked or memorized items. Review explanations against official AWS sources, practise both response types, and make a scheduling decision only after your results show consistent reasoning across mixed domains.
How to answer long architecture scenarios
Read SAP-C02 scenarios as requirement-prioritization problems. Before inspecting every answer choice, identify the workload, the hard constraints, the desired outcome, and any explicit exclusions. This reduces the chance that a familiar AWS service will distract you from the requirement that controls the decision.
Separate mandatory requirements from preferences. Words such as must, cannot, lowest operational effort, minimal downtime, centralized, isolated, near real time, and existing investment can change the correct architecture. Write a short constraint list when a scenario is dense, then test each candidate against that list.
Eliminate answers that solve the wrong layer. A response may improve application scaling while ignoring data consistency, or improve security while violating connectivity, recovery, or operational requirements. The strongest choice normally addresses the complete scenario with the least unnecessary complexity, not the greatest number of AWS services.
For multiple-response questions, verify every selected option independently. Do not select a statement merely because it is generally true. It must satisfy the scenario, and all required correct responses must be included for credit. For multiple-choice questions, compare the remaining options against the single most important requirement before choosing.
When two answers appear plausible, look for differences in scope, management responsibility, failure isolation, migration effort, or cost behavior. AWS architectural questions often distinguish a broadly suitable pattern from the pattern that best fits the exact organization and workload described.
Common preparation mistakes to avoid
The most damaging mistake is studying service names without studying trade-offs. SAP-C02 is not well served by a catalogue of definitions. Replace passive reading with design comparisons, failure analysis, and written explanations of why an alternative is unsuitable under the scenario’s constraints.
Do not treat the technologies-and-concepts list as a ranked syllabus. AWS explicitly says the list is non-exhaustive and that its order and placement do not indicate relative weight or importance. Use the domain outline and task descriptions to organize study, then use the list to find knowledge areas you might otherwise overlook.
Avoid overfitting to a single architecture pattern. A design that is excellent for a new application may be inappropriate for a regulated multi-account organization, an existing monolith, or a workload with strict migration downtime limits. Practise changing one requirement at a time and explaining how that changes the recommendation.
Do not confuse a high practice score with proof of readiness. Investigate why each answer is correct, especially when you guessed correctly. Also avoid relying on exam dumps, leaked questions, or memorization; they do not build the architectural judgment the exam measures and should not be used as a guarantee of passing.
Finally, do not spend all your preparation time on your favorite services. Use your error log and the domain weights to decide where the next study session will produce the greatest improvement.
What delivery and scheduling details are confirmed
AWS offers SAP-C02 at Pearson VUE testing centers or through online proctoring. Candidates schedule AWS Certification exams from their AWS Certification Account and complete scheduling through Pearson VUE. Confirm appointment conditions, identity requirements, and available locations in the official scheduling flow before committing to a date.
The AWS certification page lists the exam as 180 minutes long, with 75 questions, and a cost of USD 300. Treat the certification page and the scheduling interface as the authority for current commercial and appointment information, because availability and policy details can change.
AWS states that online-proctored appointments are available for AWS Certification exams and that most appointments are available 24 hours a day, seven days a week, subject to language and availability constraints. Check the actual options shown for your location and preferred language rather than assuming that every slot or language is available everywhere.
AWS lists English, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Latin American Spanish as SAP-C02 exam languages. The exam-guide index also identifies AWS Certified Solutions Architect - Professional among the exams available in Spanish (Latin America). Verify the language selection during scheduling, especially if translated terminology affects your preparation materials.
If you fail an AWS Certification exam, the AWS Certification FAQs state that AWS requires a 14-calendar-day waiting period before a retake, permits unlimited attempts, and requires payment of the full registration fee for each attempt. Plan a retake only after reviewing the official policy and your score feedback; do not schedule on the assumption that a quick repeat will repair an unexamined knowledge gap.
How to choose a test date and finalise readiness
Choose a date after your preparation evidence is stable, not simply when you finish reading. You should be able to work through mixed-domain scenarios, distinguish one-answer from all-that-apply response requirements, explain your rejected options, and finish practice sessions with time to review unanswered items.
Use a final readiness review that mirrors the exam’s scope. Revisit organizational complexity, new-solution design, continuous improvement, and migration and modernization. Check cross-cutting areas including security, networking, cost management, high availability, disaster recovery, governance, data stores, and operational design. Consult current AWS documentation for details that may have changed.
Prepare a short decision framework for the appointment: identify requirements, rank constraints, eliminate violations, compare operational and architectural trade-offs, and select the response that best satisfies the stated outcome. This framework is more durable than trying to remember isolated question wording.
Schedule through the official AWS Certification Account and Pearson VUE process once you have confirmed the delivery method, language, location or online-proctoring conditions, and current fee. Keep the exam guide available during final review so that preparation remains aligned with the published scope rather than with unsupported claims about likely questions.
What to do after the exam
Use the result as evidence about overall performance and future study priorities, not as a reason to infer exact performance from individual domain impressions. AWS reports a pass or fail designation and a scaled score of 100–1,000; section-level feedback should be interpreted cautiously.
If you pass, preserve the reasoning that helped you: document architecture decisions, review Well-Architected trade-offs, and apply the same discipline to real AWS designs. Certification validates the exam scope, but continued capability comes from making and reviewing decisions under changing requirements.
If you do not pass, wait for the permitted retake interval, inspect the available result information, and rebuild your plan around the causes of error. Separate service gaps from scenario-reading and prioritization problems. A retake is most useful when it follows targeted improvement rather than repetition of the same study routine.
Conclusion
SAP-C02 preparation should end with a scheduling decision grounded in evidence: relevant architecture experience, coverage of all four domains, reliable handling of both response types, and the ability to justify trade-offs across complex AWS workloads. Use the official exam guide as the scope anchor, the domain weights to allocate effort, and scenario review to develop judgment. Before booking, confirm current delivery, language, appointment, fee, and policy details through AWS and Pearson VUE rather than relying on third-party claims.
