SOA-C03 study plan

Your step-by-step plan

1. Map the blueprint and book a date

   Day 1

   Read the official AWS exam guide and the five domains with their weights. Book a provisional date now: a fixed date turns open-ended study into a plan and is the strongest predictor of actually sitting. Note that the three top domains, Monitoring and Remediation, Reliability and Business Continuity, and Deployment and Automation, are tied at the top and together are roughly two-thirds of the exam, so plan the heaviest study there.

2. Build the operations decision maps

   Week 1

   Before drilling any domain, build the decision trees the whole exam rests on: the monitoring role split (metric filter, alarm, composite alarm, EventBridge, runbook), the disaster-recovery ladder against RTO and RPO, the CloudFormation feature split (drift detection, change set, StackSets), least privilege and the multi-account guardrails, and the networking stateful-versus-stateless and endpoint splits. Use the recall prompts in this guide: cover the answer, choose the service from the constraint, then reveal. If you cannot pick from the requirement alone, you do not own it yet.

3. Go deep on monitoring, remediation and continuity (Domains 1 and 2)

   Weeks 1 to 3

   These two are tied at the top, so they get the most time. Drill the CloudWatch agent and metric-filter details, the alarm-to-runbook remediation chain with no human in the loop, and the disaster-recovery tiers matched to a named RTO and RPO. Practise on scenario questions and read the worked explanation on every one, including the ones you got right, watching for the named operational constraint that picks the answer.

4. Lock provisioning and automation (Domain 3)

   Weeks 3 to 4

   Deployment and automation is reliable marks if you drill it as decision trees. Fix the CloudFormation feature split (drift detection, change set, StackSets, stack policy), the Systems Manager toolset (Patch Manager, State Manager, Run Command, Parameter Store, Session Manager) and event-driven automation with Lambda, EventBridge and Step Functions. Do the drift-versus-change-set and StackSets-versus-nested-stacks calls by hand until the constraint alone decides them.

5. Cover security operations and networking (Domains 4 and 5)

   Week 4

   Security at sixteen percent and Networking at eighteen percent are learnable and dependable marks. Drill least privilege and the SCP guardrail, the detection-service map (GuardDuty, Inspector, Macie, Config, Security Hub), and on the network side the stateful-versus-stateless split, the gateway-versus-interface endpoint decision and Reachability Analyzer for path troubleshooting. Tie every choice back to the constraint named.

6. Drill weak domains, then space the review

   Week 5

   Use your per-domain accuracy to attack the two domains dragging you down, not to re-read what you already know. Then space it: revisit each domain's recall prompts after a few days and again a week later. Spacing roughly doubles what sticks compared with cramming, and it is the cheapest gain available before the exam.

7. Sit a timed mock and calibrate

   Weeks 5 to 6

   Take at least one full timed mock under exam conditions to rehearse pacing and the flag-and-return habit across the full question set in the time allowed. Treat the score as a per-domain readiness signal, not a single number, and review every missed question, naming the constraint you misread, before you book or sit.

Frequently asked questions