Objective: keep three location questions separate
Using lesson 02’s requirement-first method, distinguish geographic placement, within-Region fault isolation, and content delivery near users. An AWS Region is a geographic grouping of infrastructure. An Availability Zone is one or more discrete data centers within a Region. CloudFront uses edge locations for content distribution. These terms describe different scopes, so they cannot be exchanged just because they all refer to places. You should be able to explain which place matters for a stated constraint and what additional question is still unresolved.
Placement and failure boundaries
AZs have separate physical infrastructure, and designing across multiple AZs can improve isolation from failures affecting one zone. This is an architecture-dependent benefit, not a guarantee against every failure. Multiple servers in one AZ increase the server count without changing the AZ boundary. Multiple AZs remain within a Region, so a requirement concerning an entire Region needs a separate evaluation. Avoid memorizing changing infrastructure counts; the useful conceptual distinction is scope and separation, not the number currently listed on a marketing page.
Worked example: an educational site’s constraints
Fictional teaching case: an educational site must keep its selected primary records in an approved Region and wants to reduce exposure to a single-zone disruption. It also distributes public lesson illustrations to distant readers. First mark primary placement as a geographic constraint and identify a suitable approved Region. Next evaluate a multi-AZ design for the zone-level fault-isolation objective while keeping that regional constraint. Finally treat public illustration delivery as a separate path: CloudFront can serve content through edge locations and obtain uncached content from the configured origin. The origin remains the definitive source. The conclusion is three distinct questions, not one location choice that proves everything. Check it by asking whether an edge hit tells you that the primary records moved; it does not.
Counterexample: more copies without a new boundary
Suppose the site duplicates an application instance but leaves every copy in the same AZ. The instance count changed, but all remain inside the named zone disruption scope. Now suppose someone adds an edge cache and calls it interregional continuity for all primary records. That also exceeds the evidence: content delivery does not establish a complete recovery design or satisfy every residency rule. Regional continuity proposals must be evaluated against both their failure requirement and data-location constraints. A diagram with more boxes is not proof that these requirements are met.
Transfer check and check basis
Before reading on, classify this statement: “An AZ must be exactly one data center, so a second building always means a second AZ.” Check basis: incorrect; an AZ can contain one or more discrete data centers. The label and actual placement scope matter. Then ask whether two AZs establish recovery after loss of the whole Region. Check basis: that is a different failure scope and remains a separate requirement. Use aws-clf-q-021–024 and cards aws-clf-card-16–18. Explain the constraint without supplying an unverified infrastructure count, a blanket SLA, or a production architecture recommendation.
Try it, then explain it.
Complete a short set without looking at the example. After each answer, explain which evidence or rule supports your decision and why the alternatives do not fit.
Sources & authorship
Original OpenExam explanations and examples. References support the concepts; they are not the source of copied questions. Independent educator review is pending.
What is Amazon CloudFront? - Amazon CloudFrontGlobal Infrastructure Regions & AZs