Level 1: Exam Blueprint & AWS Global Infrastructure

Welcome to the start of your SAA-C03 journey. Before you touch a single AWS service in depth, you need to understand two things: what the exam actually tests, and where AWS physically runs the cloud. These form the mental map for every level that follows.

1. Understanding the SAA-C03 Exam Blueprint

The AWS Certified Solutions Architect – Associate (SAA-C03) exam is organized into four domains. AWS publishes exact weightings — memorize these, because they tell you where to invest your study time.

1. Domain 1: Design Secure Architectures — 30%
   • Covers IAM, security groups, encryption, secure access to workloads.
2. Domain 2: Design Resilient Architectures — 26%
   • Covers high availability, fault tolerance, disaster recovery, decoupling.
3. Domain 3: Design High-Performing Architectures — 24%
   • Covers compute, storage, database, and networking solutions for performance.
4. Domain 4: Design Cost-Optimized Architectures — 20%
   • Covers cost-effective storage, compute, and pricing model selection.

Action step: Write these four domains and percentages on a card. Every future level maps to one (or more) of them. This level's infrastructure content underpins Domains 2 and 3 — you can't design for resilience or performance without knowing what a Region or Availability Zone actually is.

Misconception to avoid

Many learners assume the exam is mostly about memorizing service names. It is not. SAA-C03 is scenario-based: you're given a business requirement (e.g., "minimize latency for users in Europe and Asia") and asked to pick the best architecture. Domain weighting tells you how often a theme appears, not which service to pick — that judgment comes from understanding trade-offs, which starts today with infrastructure choices.

2. AWS Global Infrastructure: The Big Picture

AWS runs infrastructure across the planet in three key building blocks: Regions, Availability Zones (AZs), and Edge Locations. Think of it like a global chain of warehouses, each with backup power, connected by delivery routes.

Regions

• A Region is a physical, geographically isolated area of the world (e.g., us-east-1 in Northern Virginia, eu-west-1 in Ireland, ap-southeast-2 in Sydney).
• Each Region is completely independent — data doesn't move between Regions unless you explicitly configure it to.
• AWS has dozens of Regions worldwide, and this number keeps growing.
• Why it matters: Choosing a Region affects (a) latency to your users, (b) legal/compliance requirements (data residency laws), and (c) which services and pricing are available (not every service launches in every Region simultaneously).

Analogy: Think of Regions as separate countries with their own postal systems. A letter mailed within Ireland won't automatically show up in Sydney — you have to deliberately ship it there.

Availability Zones (AZs)

• An Availability Zone is one or more discrete data centers within a Region, each with independent power, cooling, and networking.
• AZs within the same Region are connected by high-speed, low-latency private links.
• Each Region has a minimum of three AZs — an AWS design principle you should know cold for the exam.
• AZs are physically separated (often several kilometers apart) so that a flood, fire, or power outage in one AZ is unlikely to affect another.

Analogy: If a Region is a city, AZs are separate buildings in different neighborhoods of that city, each with its own generator and water supply. If one building loses power, the others keep running.

Why it matters: This is the foundation of high availability (Domain 2). If you deploy your application across multiple AZs, a single data center failure won't take your whole system down. A single-AZ deployment is a classic architectural anti-pattern the exam will test you on.

Edge Locations

• Edge Locations are smaller AWS sites, far more numerous than Regions, positioned close to end users in major cities worldwide.
• They are used by services like Amazon CloudFront (content delivery network) and AWS Global Accelerator to cache content and route traffic closer to users, reducing latency.
• Edge Locations do not run your full application — they cache static content (images, videos, HTML) or accelerate network paths. They are not a substitute for Regions or AZs.

Analogy: If Regions are big central warehouses and AZs are separate loading docks within the warehouse complex, Edge Locations are the local corner stores where popular items are pre-stocked so customers don't wait for a shipment from the main warehouse.

3. Worked Example: Choosing Infrastructure for a Real Scenario

Scenario: A company based in Germany runs an e-commerce site. Its customers are 70% in the EU and 30% in Japan. German and EU law (GDPR) requires customer data to stay within the EU. The company also wants the site to survive the failure of a single data center.

Reasoning steps, the way the exam expects:

1. Identify the compliance constraint. GDPR-related data residency means the primary data store must live in an EU Region — e.g., eu-central-1 (Frankfurt) or eu-west-1 (Ireland). This rules out storing customer data in a Japan Region like ap-northeast-1.
2. Address resilience within the Region. To survive a single data center failure, deploy across multiple Availability Zones within that chosen EU Region — never rely on a single AZ for production workloads.
3. Address latency for the Japanese customers. You don't need to move the compliance-sensitive data to Japan. Instead, use Edge Locations (via CloudFront) to cache static assets (product images, JS/CSS files) closer to Japanese users. This reduces load times without violating data residency rules, because only cached copies of non-sensitive content sit at the edge — the authoritative customer data never leaves the EU Region.
4. Final architecture: EU Region (Frankfurt) as the single source of truth, deployed across 3 AZs for resilience, with CloudFront Edge Locations globally for performance. Compliance, resilience, and performance are each solved by a different infrastructure layer — this is the core skill the exam rewards.

Edge case AWS experts flag

• Not all services are AZ-aware or multi-AZ by default. Some services (like certain older EC2-based setups) require you to explicitly configure multi-AZ; others (like Amazon S3) are Regional services that automatically replicate across multiple AZs behind the scenes without you managing it. Don't assume "using AWS" automatically means "highly available" — architecture decisions still matter.
• A Region having 3+ AZs doesn't mean your resources are automatically spread across them. You must explicitly design (e.g., via Auto Scaling Groups or load balancers) to place resources in multiple AZs.
• Latency reduction via Edge Locations only helps for cacheable/static content or accelerated routing — it does not reduce database write latency or solve compliance placement issues.

4. What the Exam Asks About This Level

On the real SAA-C03 exam, expect questions that:

• Give you a business scenario with a geographic or compliance constraint and ask you to choose the correct Region.
• Describe a system that went down when "a data center had a power failure" and ask you to identify the fix (answer: deploy across multiple AZs).
• Ask you to distinguish CloudFront/Edge Locations from Regions/AZs — recognizing that edge caching improves performance but is not a resilience or compliance mechanism.
• Test whether you know the minimum number of AZs per Region (three) and that Regions are isolated from one another by design.
• Reference domain weightings indirectly — questions about resilience, security, performance, and cost are proportioned roughly to the percentages above, so security-flavored (Domain 1) and resilience-flavored (Domain 2) questions will be the most frequent.

Key Takeaways

• SAA-C03 has four domains: Secure (30%), Resilient (26%), High-Performing (24%), Cost-Optimized (20%).
• A Region is an isolated geographic area; choose it based on latency and legal/compliance needs.
• An Availability Zone is an independent data center (or set of them) within a Region; every Region has at least three AZs.
• Deploying across multiple AZs is the standard technique for high availability — never rely on a single AZ.
• Edge Locations (used by CloudFront) cache content near users to cut latency, but they don't store your primary data or provide compliance/resilience guarantees.
• Real-world architecture problems usually require combining all three infrastructure layers correctly, as shown in the worked example.