Hands-on AWS knowledge base for developers Managed Ops
Talk to Us

SAA-C03 Exam Domain Deep Dive: Design Secure Architectures

Export PDF Print-friendly layout with a copyright watermark; choose Save as PDF in the print dialog
SAA-C03 Exam Domain Deep Dive: Design Secure Architectures

TL;DR

  • Domain 1, Design Secure Architectures, is 30% of SAA-C03 — roughly 20 of the 65 questions, the largest single slice on the paper.
  • You get 130 minutes and need 720/1000 scaled, which is about two minutes per question; security questions are usually the shortest ones, so they're where you bank time for the long resiliency scenarios.
  • Build three labs before buying another practice exam: an explicit-deny IAM policy, an S3 gateway endpoint from a private subnet, and a KMS key policy that blocks cross-account use. Most wrong answers here come from policy evaluation order, not from services you've never heard of.

What Domain 1 actually tests (and how it leaks into the other three)

The public exam guide breaks Domain 1 into three task statements: design secure access to AWS resources, design secure workloads and applications, and determine appropriate data security controls. In practice that means IAM roles and trust policies, permission boundaries and SCPs, security groups versus NACLs, WAF and Shield at the edge, PrivateLink, and encryption with KMS.

Nobody fails because they don't know what KMS is. People fail because they can't rank the statements when two policies disagree. An explicit Deny in a bucket policy beats an Allow in an identity policy every time, an SCP caps everything underneath the account, and a session policy intersects rather than adds. That single mental model answers a surprising share of the security questions.

Domain Weight ~Questions of 65 Scenario shape
1 – Design Secure Architectures 30% 19–20 Cross-account S3 access, least-privilege role, KMS key policy vs IAM policy
2 – Design Resilient Architectures 26% 17 Multi-AZ failover, RPO/RTO for pilot light vs warm standby
3 – Design High-Performing Architectures 24% 15–16 Read replicas vs ElastiCache, placement groups, Global Accelerator
4 – Design Cost-Optimized Architectures 20% 13 Savings Plans vs Spot, S3 lifecycle rules, right-sizing an m5.xlarge

Study Domain 1 first even if you care most about cost. The security vocabulary shows up as wrong-answer bait in every other domain — an option offering "store credentials in the AMI" is a distractor you only recognise confidently after the IAM work.

Registering, paying, and the 130-minute clock

Registration is dull until it isn't. The steps that matter:

  1. Sign in to your AWS Certification account at aws.training (AWS Builder ID or an AWS account login both work).
  2. Schedule through Pearson VUE — test centre or online proctored. Online needs a webcam, a cleared desk, a room scan, and a government ID whose name matches your certification account character for character.
  3. Reschedule at least 48 hours ahead or you forfeit the fee.
  4. Book the official practice exam, take it timed, then book the real thing once you're clearing 80%+ on the practice paper.

Fees, in USD, and they do differ by country — verify on the certification page before you budget:

Item Cost (USD) Note
Exam fee 150 65 questions, 130 minutes, one attempt
Retake 150 No discount; 14-day wait between attempts
Official practice exam 20 Full-length, timed, scored out of 1000
Reschedule >48h ahead 0 Inside 48h you lose the fee
Recertification 150 Every 3 years, or pass a higher-level exam

The ID name mismatch is the one that ruins mornings. I've watched someone turned away at check-in because their ID read "Alex" and the account read "Alexander" — Pearson VUE doesn't negotiate. Fix the certification profile name a week ahead, not ten minutes before your slot.

Time management that holds up under the clock

Sixty-five questions in 130 minutes is two minutes each, but the distribution is not even. Security and cost questions often run three lines; resiliency ones can run a paragraph with three constraints. Flag anything with two "MOST" qualifiers, move on, and come back with the 25 minutes you saved. Also count the checkboxes on multiple-response questions — the prompt tells you how many to pick, and picking four when it says "Choose two" scores zero.

A study path that builds instead of watching

Six weeks at 6–8 hours per week is realistic for someone with a year of console work behind them. Four weeks is enough if you already write IAM policies in production. Zero cloud background? Budget ten, or take Cloud Practitioner first and stop pretending the associate exam is an entry point.

Week Focus Deliverable you can actually show
1 IAM evaluation logic, SCPs, permission boundaries A role that can read exactly one prefix of one bucket
2 KMS, S3 encryption, TLS in transit Bucket with SSE-KMS and a key policy denying cross-account use
3 Security groups vs NACLs, VPC endpoints, PrivateLink Private subnet reaching S3 with no NAT gateway
4 Multi-AZ, backup, Route 53 failover One-page RTO/RPO note per resilience pattern
5 Performance and cost The same workload priced two ways, side by side
6 Practice exam and error review A log of every question you got wrong and why

The week-1 lab is worth doing with the CLI rather than the console, because the simulator prints the decision AWS would make:

# Does the role actually get allowed, or does it just look like it?
aws iam simulate-principal-policy 
  --policy-source-arn arn:aws:iam::111122223333:role/app-reader 
  --action-names s3:GetObject s3:PutObject 
  --resource-arns arn:aws:s3:::my-app-assets-2026/index.html 
  --query 'EvaluationResults[].{action:EvalActionName,decision:EvalDecision}' 
  --output table


The output comes back as `allowed`, `implicitDeny` or `explicitDeny`. Learning to say out loud why a result is an implicit deny (nothing granted it) versus an explicit deny (some statement says `Deny`, and no allow can rescue it) is the highest-yield 20 minutes of prep you'll spend.

## Field note: the S3 gateway endpoint that existed but didn't route

We hit this in a shared-services VPC in us-east-1, 2026-11, around 01:20. An app on EC2 in a private subnet started failing to pull a config object, and the app log gave the real error:

```text
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL:
"https://s3.us-east-1.amazonaws.com/my-app-assets-2026/config.json"


My first config was wrong in the most boring way possible: I created the

Sources

Leave a Reply

Your email address will not be published. Required fields are marked *