Which Deployment Model Should a Company Use to Deploy an Application Globally?
A company wants to use the AWS Cloud to deploy an application globally. Which architecture deployment model should the company use to meet this requirement?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The question tests the difference between AWS Regions and Availability Zones; the trap is choosing Multi-AZ, which buys resilience inside one Region but not worldwide reach.
A company that needs to run an application globally must use a Multi-Region deployment because AWS Regions are separate geographic areas spread around the world, whereas Availability Zones are isolated data centers contained inside a single Region. This page confirms Multi-Region as the correct choice and explains why Multi-AZ, Single-Region and Single-AZ fall short of a global requirement.
The most common wrong answer is C (Multi-AZ), because candidates equate "high availability" with "global" — but multiple AZs still sit inside one Region, so users on other continents are not served locally.
Community Discussion (9 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
AWS Regions are physically separate geographic clusters (for example, us-east-1, eu-west-1, ap-southeast-1), so running workloads in more than one Region is the only way to actually place an application "globally" on AWS infrastructure. A Multi-Region deployment puts compute, data and endpoints closer to users on different continents, cutting latency and providing redundancy against a full regional failure. AWS's own global infrastructure documentation describes Regions as the top-level geographic unit of the cloud, which is exactly the dimension the question is asking about. Because the requirement is worldwide reach rather than merely high availability, Multi-Region (A) is the deployment model that satisfies it.
Why the Other Options Are Wrong
B (Single-Region) confines every resource to one geographic area, so users elsewhere incur long-haul latency and the whole application is exposed to a regional outage. C (Multi-AZ) spreads resources across isolated Availability Zones for high availability and fault tolerance, but all those AZs still live inside one Region — resilience is improved, global presence is not. D (Single-AZ) is even weaker: it offers neither cross-Region reach nor meaningful AZ-level redundancy. Only A addresses the actual wording of the requirement, which is deploy the application globally.
Community Comment Notes
Every voter in the distribution selected A, and the reasoning aligns with the official blueprint. Aghajee explains that a Multi-Region architecture distributes the application across different AWS Regions for redundancy and "better availability and performance for users in different parts of the world." spicymchaggis cautions that a Multi-AZ approach, while improving resilience, "is not the most appropriate architecture for deploying an application globally." petercorn sums it up succinctly with "Globally=multi-region," and AustinP simply confirms A while noting the question set gets rough later on. No commenter argued for Single-Region, Multi-AZ or Single-AZ, so there is no dissent to weigh against the technical analysis.
Official Reference
Exam Strategy
When a CLF-C02 question contains the word "global," map it immediately to Regions (Multi-Region), and map durability, high availability or fault tolerance within one geography to Availability Zones (Multi-AZ or Single-AZ). Read the requirement verbatim — "globally" is the keyword that eliminates every single-Region option.
Frequently Asked Questions
Why isn't Multi-AZ enough for an application that must deploy globally?
Multi-AZ spreads resources across Availability Zones inside one Region, which improves availability but keeps the application in a single geographic area, so it does not provide global reach or reduced latency for worldwide users.
Does a Multi-Region architecture also improve resilience?
Yes. Besides serving global users from nearby Regions, Multi-Region design isolates workloads from a full regional outage, which a Single-Region or Multi-AZ deployment cannot do.
Related Analysis
Practice All CLF-C02 Questions
Access 120 questions with complete answers and detailed explanations.
View Full CLF-C02 Practice Test →