SAP-C02
AWS Certified Solutions Architect - Professional
SAP-C02 Exam Guide: Requirements, Study Strategy, and Scheduling Decisions
SAP-C02 is the AWS Certified Solutions Architect – Professional exam for candidates who design optimized AWS solutions using the AWS Well-Architected Framework. It validates advanced architecture judgment across organizational complexity, new solution design, continuous improvement, and migration or modernization. This guide helps experienced AWS practitioners decide whether their current work matches the target level, identify which domains need deliberate study, build a practical preparation sequence, and choose an exam delivery option without treating memorized questions as a substitute for architectural understanding.
What SAP-C02 validates
SAP-C02 validates advanced technical skills and experience in designing optimized AWS solutions based on the AWS Well-Architected Framework. The exam also evaluates whether a candidate can design for organizational complexity, create new solutions, continuously improve existing solutions, and accelerate workload migration and modernization.
This is a professional-level architecture assessment, not simply a catalogue of AWS service features. A strong candidate must interpret requirements, recognize constraints, assess trade-offs, and select an architecture that fits the situation. In practice, that means explaining why one design is more suitable than another when several options appear technically possible.
The certification is most relevant to people who perform a solutions architect role and need to make recommendations across applications or projects. AWS describes the target candidate as someone with 2 or more years of experience using AWS services to design and implement cloud solutions. That description is an official target profile, not a mandatory prerequisite to register.
AWS also identifies several areas as out of scope: frontend development for mobile apps, the 12-factor app methodology, and in-depth knowledge of operating systems. These exclusions help you allocate preparation time. You still need broad architecture knowledge, but you should not turn SAP-C02 preparation into a specialist operating-system or mobile-development course.
Who should schedule the exam
Schedule SAP-C02 when you can reason across multiple AWS services and competing business requirements, not merely recite isolated service definitions. Candidates whose work involves architecture decisions, implementation guidance, migration planning, resilience, security, governance, or cost and performance trade-offs are closer to the stated target profile than candidates with only introductory cloud exposure.
Use the target candidate description as a readiness check. Ask whether you have designed or implemented AWS solutions and whether you can evaluate application requirements before recommending a deployment approach. You should also be comfortable giving architectural guidance that extends across multiple applications or projects in a complex organization.
A recently completed associate-level course may improve terminology, but course completion alone does not demonstrate professional-level readiness. AWS states that training is recommended but not mandatory for an AWS Certification exam. The practical question is therefore not whether you attended a course; it is whether you can apply the concepts in unfamiliar scenarios.
Consider postponing the booking if your study sessions consist mainly of flashcards, service-name recognition, or short definitions. Those methods can support recall, but they do not reveal whether you can distinguish an acceptable design from the best design under organizational, operational, security, or migration constraints.
A useful self-assessment is to take several architecture scenarios and write a short decision record for each: requirements, constraints, proposed design, rejected alternatives, and the reason for rejection. If you cannot explain the trade-off without looking up every service interaction, build that foundation before committing to a date. This is a preparation recommendation, not an AWS eligibility rule.
How the exam is structured
SAP-C02 contains 75 questions in a 180 minutes exam appointment, and the AWS certification page lists the exam cost as USD 300. AWS’s exam guide explains that 65 questions affect your score and that 10 questions are unscored. The unscored questions are not identified, so treat every item as potentially scored while working through the exam.
The exam uses multiple-choice and multiple-response questions. A multiple-choice item has one correct response and three distractors. A multiple-response item has two or more correct responses among five or more options, and you must select all correct responses to receive credit.
Unanswered questions are scored as incorrect, while AWS states that there is no penalty for guessing. A practical approach is to mark difficult items, eliminate options that violate explicit requirements, select the best supported answer, and avoid leaving items blank. Do not try to identify unscored questions; the exam does not mark them for you.
Results are reported as a scaled score from 100–1,000, and the minimum passing score is 750. The result is pass or fail, with the score showing performance on the exam as a whole. Avoid translating a practice-test percentage directly into a predicted AWS score because the official result uses scaled scoring.
AWS explains that pretest questions help keep certifications current with evolving AWS technologies and architectural best practices. They do not affect your score, but they can resemble normal exam content. This is another reason to answer every question using the requirements and architecture principles presented in the item.
Which domains receive the most study time
Allocate study time according to the official domain weights, while still covering all four domains. Content Domain 2, Design for New Solutions, has the largest stated weight at 29%, followed by Content Domain 1, Design Solutions for Organizational Complexity, at 26%; Content Domain 3, Continuous Improvement for Existing Solutions, is 25%, and Content Domain 4, Accelerate Workload Migration and Modernization, is 20%.
The percentages are planning signals, not a reason to ignore the smallest domain. A candidate who is weak in migration and modernization may lose more readiness than the percentage alone suggests. Use the weights to set the initial calendar, then adjust after practice analysis based on the type of reasoning you miss.
For Content Domain 1, Design Solutions for Organizational Complexity, study how architecture decisions change when multiple teams, accounts, applications, environments, governance requirements, or organizational boundaries are involved. Focus on recognizing the requirement that drives the design rather than memorizing a single centralized or decentralized pattern.
For Content Domain 2, Design for New Solutions, practise turning a blank-slate requirement into a complete architecture. Work from business and technical constraints toward compute, storage, networking, security, data, operations, resilience, and cost decisions. Do not begin with a favourite service and force the requirements to fit it.
For Content Domain 3, Continuous Improvement for Existing Solutions, study the reasoning involved in reviewing an existing workload and improving its security, reliability, performance, operational model, or cost position. The key preparation habit is to identify the current limitation first; an attractive redesign is not necessarily the correct response to a narrowly stated problem.
For Content Domain 4, Accelerate Workload Migration and Modernization, prepare for decisions involving migration approaches, data transfer, dependencies, modernization priorities, and the balance between speed and long-term improvement. Separate a design that moves a workload quickly from one that changes its operating model, because scenario wording may make that distinction important.
Keep the domain labels beside your notes. A percentage without its domain name is easy to misread later, particularly when comparing study results. Record both the official domain and the error pattern, such as governance, resilience, migration sequencing, or cost reasoning.
What technologies and concepts to cover
AWS identifies a non-exhaustive technologies-and-concepts list for SAP-C02. It 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.
The list is a coverage map rather than a ranking. AWS states that it is subject to change and that the order and placement of items do not indicate their relative weight or importance on the exam. Use it to find gaps, not to predict a sequence of questions or to assign importance based on list position.
Study each area through architecture decisions. For compute, compare workload characteristics and operational requirements before choosing a model. For databases, connect data-access patterns, consistency, scale, availability, and operational responsibility. For networking, trace traffic paths, boundaries, connectivity, naming, and content delivery requirements rather than learning products in isolation.
For security, work through identity, access boundaries, encryption, detection, protection, and governance requirements. For cost management, examine the cost implication of architecture choices and the controls needed to make spending visible and manageable. For disaster recovery and high availability, distinguish the failure scope, recovery expectation, and operational process described by the scenario.
Microservices and component decoupling require more than knowing that queues or events exist. Practise deciding when decoupling addresses a stated dependency or scaling problem and when it adds unnecessary complexity. Serverless design principles should likewise be studied as design choices connected to workload behavior, operations, and constraints.
Read the official in-scope service material alongside the concepts list, then verify current service behavior in AWS documentation during study. The exam guide’s list is explicitly non-exhaustive, so treating it as a complete product boundary is a mistake.
How to study the official blueprint
Start with the SAP-C02 exam guide and convert its four domains into a working checklist. Read the target candidate description, exam content, domain headings, technologies and concepts, and in-scope or out-of-scope information before selecting secondary material. This prevents a popular service topic from displacing a tested architectural skill.
Create one page for each domain. On each page, record the domain name, its official weight, the decisions it represents, the AWS concepts involved, and the evidence that you understand them. Evidence might be a design diagram, a comparison table, a short architecture decision record, or a completed scenario with a written rationale.
Use service documentation to resolve uncertainty, not as a substitute for design practice. When you look up a service, capture the decision boundary: what requirement makes it suitable, what constraint makes it unsuitable, what operational burden it creates, and which adjacent services or controls matter.
Keep a separate “confusion log.” Record pairs that you repeatedly mix up, such as two approaches that both improve availability but operate at different failure scopes, or two migration choices that differ in speed, transformation, or operational effort. Revisit this log at the start of each study session.
Build notes around requirements and trade-offs rather than long product summaries. A useful note answers: What is the workload? What must be protected or optimized? What is the required operational model? What alternatives were rejected? Which words in the scenario would change the answer?
A practical scenario-reading method
Read the question for the business outcome and hard constraints before examining the options. Mark words that establish priority, such as minimizing operational effort, preserving an existing dependency, improving recovery, reducing cost, or meeting a governance boundary. Then remove choices that solve a different problem, even if they are valid AWS designs.
Next, identify the scope of the decision. Is the question asking for one component, a workload architecture, an organization-wide control, or a migration approach? Many difficult items become clearer when the answer is judged at the same scope as the requirement.
Finally, compare the remaining choices against the AWS Well-Architected reasoning implied by the scenario. Select the option that satisfies the stated requirements with the fewest unrequested compromises. Avoid adding requirements from your own experience; the item should be solved from the information provided.
A study roadmap that produces usable evidence
A staged roadmap is more reliable than reading every AWS service page once. Begin with a baseline, build domain knowledge, practise integrated architecture decisions, and finish with timed review. The stages below are recommendations for organizing preparation; AWS does not prescribe this exact schedule.
Stage one is a baseline assessment. Use representative practice scenarios or your own design exercises to identify whether errors come from missing service knowledge, misreading requirements, weak trade-off analysis, or poor time control. Do not use a single score as the only readiness measure. Review every answer, including correct guesses.
Stage two is foundation repair. Work through the technologies-and-concepts list and the four domain pages. Fill only the gaps revealed by your baseline or by the official blueprint. For each topic, produce a compact decision note and connect it to at least one neighboring concern, such as security with networking or migration with data transfer.
Stage three is domain practice. Study one domain at a time, but use cross-domain scenarios after each domain. For example, a new solution may also require organizational governance, continuous cost improvement, or a migration path. This prevents the artificial separation that can occur when studying the blueprint headings in isolation.
Stage four is integrated architecture practice. Draw a complete high-level design from a scenario, then challenge it: what happens during a component failure, how is access controlled, what is operated by the customer, how does the design scale, how is data moved, and what cost or governance consequence follows? Revise the design only when the scenario supports the change.
Stage five is exam simulation and review. Practise answering mixed questions under a time limit that reflects the official 180 minutes exam appointment. Review reasoning, not just the selected letter. For multiple-response questions, write down why each chosen option is correct and why each omitted option fails the stated requirement.
Stage six is final consolidation. Revisit the confusion log, domain weaknesses, and recurring wording traps. Avoid starting a large new service catalogue immediately before the exam. Use the final period to improve decision quality, pacing, and confidence in the sources you already understand.
A weekly session pattern
A repeatable session can contain four parts: blueprint review, targeted technical reading, scenario solving, and error analysis. Keep the technical reading tied to a decision you could be asked to make. The scenario and its post-answer explanation should take at least as much attention as the initial selection.
At the end of each session, write one sentence describing the trigger that would change your preferred architecture. This simple exercise turns memorized recommendations into conditional reasoning. It also exposes notes that are too vague to help with an unfamiliar question.
Once a week, review all domains rather than allowing the current topic to dominate. Give extra time to the weakest domain, but retain short mixed practice so that you continue switching between organization, new design, improvement, and migration contexts.
Mistakes that undermine preparation
The most damaging preparation errors are studying service names without requirements, treating the technologies list as exhaustive, and trusting answer patterns without understanding the trade-off. These habits create false confidence because they work on familiar examples but fail when the question changes the business priority or failure scope.
Do not infer exam importance from the order of the technologies-and-concepts list. AWS explicitly says that ordering does not indicate relative weight or importance. Do not infer readiness from a practice percentage without reviewing why answers were missed or guessed.
Do not leave questions unanswered. AWS states that unanswered SAP-C02 questions are scored as incorrect and that guessing is not penalized. A marked answer supported by elimination is preferable to an empty response, although guessing should be the fallback after careful reasoning.
Do not assume that every question has one correct choice. First identify whether the item is multiple-choice or multiple-response, then read the instruction about how many responses are required. In a multiple-response item, selecting only part of the correct set does not earn credit.
Do not prepare from leaked questions, exam dumps, or claims that memorization guarantees a pass. Such material is not a reliable way to learn architecture and may be inaccurate or unauthorized. Use the official exam guide, AWS service documentation, and legitimate practice exercises instead.
Do not over-study material that AWS identifies as out of scope. Frontend development for mobile apps, the 12-factor app methodology, and in-depth operating-system knowledge are not expected areas for the target candidate. Keep your preparation centered on architecture and AWS solution design.
How to choose the delivery option
AWS offers SAP-C02 at Pearson VUE testing centers or through online proctoring. AWS also 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.
Candidates schedule through their AWS Certification Account and complete scheduling through Pearson VUE. Before selecting an appointment, confirm the current location, identity, equipment, workspace, and language requirements shown in the scheduling flow. Availability can vary, so do not assume that a preferred time or language will be offered in every location.
Choose a testing center if a controlled external environment is more dependable for you than your home setup. Choose online proctoring only after checking the current technical and room requirements and confirming that your internet, computer, camera, microphone, and workspace meet them. These are practical recommendations; the official scheduling process controls the applicable requirements.
AWS lists English, Japanese, Korean, Brazilian Portuguese, Simplified Chinese, and Latin American Spanish as SAP-C02 exam languages. The exam-guide catalogue also lists AWS Certified Solutions Architect – Professional among the exams available in Spanish (Latin America). Verify the available language when scheduling because delivery and appointment availability can be constrained by language.
Do not book solely because an online appointment appears convenient. Select a date that leaves enough time to close your domain gaps and complete timed mixed practice. If the first simulation reveals that you cannot finish comfortably or make defensible selections, move the date if the applicable scheduling policy permits it rather than relying on last-minute memorization.
What to do after a practice review
Turn every missed or guessed question into a classified action. Label it as blueprint misunderstanding, service behavior gap, requirement-reading error, trade-off error, or pacing problem. Each label leads to a different remedy, so simply recording the correct answer wastes the most useful part of the review.
For a blueprint misunderstanding, return to the relevant domain and rewrite its decision summary. For a service behavior gap, consult the official service documentation and update the boundary note. For a requirement-reading error, rewrite the scenario in your own words and underline the decisive constraint.
For a trade-off error, compare the selected and correct options in a small table: requirement satisfied, operational burden, resilience, security, performance, cost, and migration or governance consequence. Do not fill cells with assumptions that the question does not support.
For a pacing problem, set a checkpoint strategy for the next practice session. The goal is not to rush every question; it is to avoid spending disproportionate time on one ambiguous item. Mark it, make the best supported selection, and return if time remains.
Review errors by domain as well as by service. A candidate may repeatedly miss networking questions because of requirement interpretation, not because every networking service is unknown. The correction should target the recurring reasoning failure.
Final readiness and next actions
Before scheduling or sitting SAP-C02, confirm four things: your experience or study work matches the professional target, every weighted domain has a documented preparation plan, you can solve mixed scenarios without relying on recall alone, and your selected delivery option is workable. These checks provide a more useful decision than a vague feeling of familiarity.
Read the current official SAP-C02 exam guide again, especially the content outline, response types, scoring notes, technologies list, and out-of-scope material. AWS can update certification information, and the technologies list is non-exhaustive and subject to change. Use the official pages linked below for the latest scheduling and exam information.
Prepare a one-page revision sheet containing the four domain names and weights, your recurring confusion pairs, the architecture trade-offs you most often miss, and the steps you use to read a scenario. Keep it concise enough to review without turning it into an unverified catalogue of claims.
When you are ready, schedule through the AWS Certification Account and Pearson VUE process, select the available language and delivery method, and keep the appointment details accessible. During the exam, answer every item, use the stated requirements as your authority, and remember that unscored questions are not identified.
If you fail, 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. Use any result feedback cautiously: AWS warns candidates to use caution when interpreting section-level feedback. Treat the result as a signal for targeted improvement rather than a diagnosis of every individual skill.
Conclusion
SAP-C02 preparation is strongest when it mirrors the work the certification is designed to validate: interpreting complex requirements, selecting an appropriate AWS architecture, and defending trade-offs across the Well-Architected Framework. Use the official domain weights to organize effort, the technologies list to expose gaps, and scenario review to test judgment. Then make the scheduling decision only after your practice evidence shows that you can apply those decisions consistently under the exam’s format and time constraints.