cert-bank

Guides

이 글을 한국어로 읽기

SAP-C03 Study Guide: Every Option Could Work, So Study the Constraint That Breaks the Tie

On the AWS Solutions Architect – Professional exam, wrong options are rarely broken designs. Most of them would work. They lose because they cost more than needed, take more effort to run, miss a recovery target by ten minutes, or ignore the fact that the company has two hundred accounts. So the skill being tested is not "which services exist" but "which requirement in this long paragraph decides". This guide is organized around that skill: the constraints that break ties, and the account-level thinking the exam assumes from the first question.

Study guide · AWS Certified Solutions Architect – Professional (SAP-C03)

SAP-C03 Study Guide: Every Option Could Work, So Study the Constraint That Breaks the Tie

What you are signing up for

SAP-C03 replaces SAP-C02 from 17 November 2026 (the last day for SAP-C02 is 16 November 2026). It has 75 questions: 65 scored and 10 unscored that you cannot tell apart. The exam guide does not state the time limit (SAP-C02 allowed 180 minutes), so check the exam page when you book. The passing score is 720 of 1,000, lower than the 750 that SAP-C02 required. Questions are multiple choice or multiple response; in multiple response you must pick every correct option to get the point.

DomainWeight
Architecture Design and Implementation Built for the Cloud25%
Security, Compliance, and Governance25%
Cost-Optimized Architecture Design15%
Resilience, Migration, and Business Continuity15%
Operational Excellence and Automation20%

The four SAP-C02 domains became five. Much of the old content was regrouped rather than dropped, so networking, migration and disaster recovery knowledge still counts.

The stem is the hard part

In the 509 SAP-C03 questions we wrote for this question bank, the average question stem is about 45 words, against about 33 for our SAA-C03 questions, and that is before the options, which are often full sentences themselves. Long stems hide two or three requirements in one paragraph. Use a fixed reading order: read the last sentence first (what is actually asked), then collect the constraints (must, least operational overhead, lowest cost, RTO and RPO, Regions, accounts), and only then read the options. Cross out any option that breaks a hard constraint before you compare the rest.

When the stem saysIt usually rules out
Least operational overheadSelf-managed fleets, custom scripts, anything you must patch, when a managed or serverless option meets the need.
Most cost-effectiveBoth the over-built design and the cheapest design that misses a stated requirement. It means cheapest among those that meet everything.
An RTO in minutesBackup and restore. Look at pilot light, warm standby or active-active, chosen by the exact number.
Must not be deleted by anyoneGovernance-mode locks and IAM-only protection; it points to compliance-mode locks (S3 Object Lock, Backup Vault Lock).
Before resources are createdDetective controls such as Config rules; it points to proactive controls such as CloudFormation Hooks.
A job that runs for hoursLambda (15-minute maximum per invocation); look at containers or a Step Functions workflow.

When two options still both work, reread the stem for the qualifier you skipped. It is almost always the reason one of them is wrong.

Think in accounts, not in VPCs

The Associate exam mostly happens inside one account. SAP-C03 assumes an organization. In our bank, 110 of the 509 stems (about one in five) mention accounts, and AWS Organizations is the single most frequent service, tagged on 62 questions, ahead of Amazon S3. Before you study any individual service in depth, be able to explain these pieces and how they fit:

  • Landing zone: an OU structure with separate security, log archive and workload accounts, usually set up and governed with AWS Control Tower and Account Factory.
  • Guardrails: service control policies (SCPs) cap what principals in member accounts can do; resource control policies (RCPs) cap what can be done to resources in those accounts; permissions boundaries cap a single role. None of them grants anything.
  • Sharing: AWS RAM shares resources such as Transit Gateways and subnets; cross-account roles with external IDs give access the other way; Lake Formation shares data catalogs.
  • Reaching every account: service-managed CloudFormation StackSets with automatic deployment put the same baseline into every current and future member account in the targeted OUs; an organization trail and Config aggregator collect the evidence centrally.
Going deeper: why SCPs and RCPs together form a data perimeter

An SCP is evaluated against the principal making a request: it limits what identities in your member accounts can do, wherever the resource lives. An RCP is evaluated against the resource being accessed: it limits what any principal, including one from outside your organization, can do to resources in your member accounts (for the services that support RCPs). Each closes a gap the other leaves open. An SCP cannot stop an outside account from reading a bucket whose policy was opened by mistake; an RCP with a condition such as aws:PrincipalOrgID can. An RCP cannot stop your own developer from copying data to a bucket in a foreign account; an SCP that limits which resources your principals may write to can. Both are filters only, and neither applies to the management account, which is why that account should run no workloads at all.

Beginner tip: if you have never used Organizations, create one with a single extra member account (and delete what you create afterwards). Attach an SCP to the member account that denies every Region except one, then sign in to the member account and try to create a resource in another Region; then try the same from the management account. Seeing the request fail in one place and succeed in the other teaches the two rules the exam leans on most: SCPs only take away, and they do not touch the management account.

SAP-C03: where the multi-account guardrails act
Management account
AWS Organizations and Control Tower · Runs no workloads · SCPs and RCPs do not apply to it
OUs and member accounts
Security, log archive and workload accounts · SCPs cap what principals can do · RCPs cap what is done to resources · Same baseline via StackSets
A single role
Permissions boundaries cap it · None of these guardrails grants anything
Each layer only narrows what the one above allows; none of them grants permissions, and none reaches the management account.

Numbers decide more questions than names

Many SAP-C03 questions can be settled by arithmetic before you think about services. An RTO of 15 minutes eliminates restoring from backups. A data set that cannot cross the network in time eliminates online transfer. A requirement for no data loss eliminates anything that replicates asynchronously. Write the numbers from the stem in the margin of your scratch sheet and test each option against them.

Going deeper: doing the bandwidth math in your head

A 1 Gbps link moves at most 125 MB per second, which is about 10.8 TB per day if it ran at full speed around the clock with nothing else on it. Real links share traffic and never reach the theoretical rate, so assume well under that. Now take a stem with 400 TB to move in three weeks over a busy 1 Gbps line: even at full theoretical speed it would take more than five weeks, so online tools such as AWS DataSync cannot meet the deadline on their own, and the answer is an offline transfer (or more bandwidth, if an option offers it). The same quick division tells you when DataSync over an existing Direct Connect link is perfectly fine. Offline transfer options change over time, so check which ones AWS currently offers rather than memorizing device names.

New ground in SAP-C03

124 of our 509 questions are new for SAP-C03; the rest are SAP-C02 questions that still fit a SAP-C03 task. The additions in AWS's comparison of SAP-C02 and SAP-C03 cluster in a few areas:

  • Generative AI and agents: Amazon Bedrock (tagged on 28 of our questions), knowledge bases for retrieval-augmented generation, AgentCore, guardrails, model evaluation, and their cost levers.
  • DevSecOps: image scanning as a pipeline gate, artifact signing, building once and promoting the same artifact across accounts.
  • Proven resilience: AWS Fault Injection Service and AWS Resilience Hub are new to the in-scope service list; failover tests, chaos experiments and immutable backups against ransomware carry over from SAP-C02 into one task.
  • Newer architecture topics: post-quantum cryptography, IPv6 and dual-stack migration, lakehouse designs.

You do not need to be a machine learning engineer. Expect architect questions: how to give many accounts governed, private access to models, how to keep RAG answers grounded, and which inference option fits the traffic.

A six-week plan by weight

  1. Weeks 1–2: Domain 1. Event-driven messaging, containers and ingress, hybrid connectivity and DNS, network architecture, data stores, then the generative AI patterns.
  2. Week 3: Domain 2. Federation, least privilege and data perimeters, KMS and certificates, the multi-account guardrails above, centralized logging.
  3. Week 4: Domain 5. Infrastructure and policy as code, CI/CD with security gates, observability, automated remediation.
  4. Week 5: Domains 3 and 4. Purchase options and data transfer costs, then migration (the 7 Rs, DMS, DataSync) and disaster recovery patterns.
  5. Week 6: full timed practice. For each miss, write one sentence naming the constraint you overlooked.

Practise

Practise in the question bank: every question explains each option, right and wrong. Start with the domain you just studied, then take a timed mock exam.

Exam facts as published for SAP-C03 at the time of writing. Dates, question counts and the passing score can change; check the official AWS exam guide and exam page before you book.