Objective 3.2

CLF-C02

Define the AWS global infrastructure.

Objective 3.2 sits in Cloud Technology and Services, which carries 34% of the Cloud Practitioner exam. The questions below are original, written from the official objective title above, and each explanation cites the Amazon Web Services (AWS) page it rests on.

Objective title verbatim from the official objectives. Amazon Web Services (AWS) exam page ↗

A worked example

Shown solved, with the whole explanation open: this is what every question here carries.

3-2Cloud Technology and Services

A team creates a DB instance in eu-west-1 and expects to see it listed in us-east-1. Why does it not appear there?

Each Region is isolated from the othersCorrect · your answerCorrect. Each AWS Region is designed to be isolated from the other AWS Regions, and resources are not automatically replicated across them.
Console caching delays the listingThe console reads the same regional endpoint the CLI does. Refreshing will not surface something that was never created in that Region.
The instance is still provisioningProvisioning time affects status, not location. The instance would show as creating in its own Region long before it finished.
Cross-Region views need an IAM policyPermissions decide what you may do in a Region. They never merge two Regions into a single view of your inventory.

Correct.

Checked against docs.aws.amazon.com, August 2026

Concept

Geographic separation only buys fault isolation if the boundary is real. A provider that quietly synchronizes state between sites has sold you one large failure domain wearing several names.

Why A

Resources belong to the Region they were created in and are not copied elsewhere unless you arrange it. A list call runs against whichever Region you are pointed at and returns only what lives there.

Source

Each AWS Region is designed to be isolated from the other AWS Regions. This design achieves the greatest possible fault tolerance and stability. When you view your resources, you see only the resources that are tied to the AWS Region that you specified. This is because AWS Regions are isolated from each other, and we don't automatically replicate resources across AWS Regions…

AWS Docs: Regions, Availability Zones, and Local Zones, checked August 2026
#regions#global-infrastructure#isolation

Now you: objective 3.2 questions

No account needed. The explanation opens when you answer.

Sample question 1 of 3

3-2Cloud Technology and Services

An application keeps all of its DB instances in a single Availability Zone. What is the consequence of a failure in that location?

Sample question 2 of 3

3-2Cloud Technology and Services

A media company needs to run compute and storage within one metropolitan area for low latency, still managed from its existing Region. Which option fits?

Sample question 3 of 3

3-2Cloud Technology and Services

A hospital must keep patient processing inside its own building but wants the same AWS APIs it already uses in the Region. Which option fits?

That’s 3 of the full Cloud Practitioner bank.

Keep going free: 10 questions per certification in bank practice, with no account.

Continue practicing

Read the sources

These are the official pages the questions above cite. Reading them is studying the objective from the primary source, which is what the explanations point you toward anyway.

More objectives in Cloud Technology and Services