A European software company signs its first customers in Australia and must serve them with acceptable latency within three weeks. Which characteristic of the AWS Cloud makes this timeline realistic?
Intermediate · Choose one
Explanation
Answer: A. Because AWS already operates the Region, entering a new geography is a deployment decision rather than a construction project. The company reuses the same services, APIs, and automation it already has, so the schedule is limited by its own release process rather than by procurement, shipping, and data center build-out.
B. Pricing varies by Region and is published in advance. There is no discount triggered by adopting an additional Region.
C. AWS does not copy workloads or data between Regions. Regions are isolated, and expanding into another one is an explicit customer action.
D. AWS Support provides guidance and troubleshooting. Deploying and operating the customer's workload remains the customer's responsibility under the shared responsibility model.
12
Which TWO outcomes are direct benefits of the AWS global infrastructure rather than of a specific AWS service? (Choose TWO.)
Intermediate · Select 2 answers
Explanation
Answer: A and D. The global infrastructure gives customers a choice of geography. Deploying into a Region near the user population shortens the network path and lowers latency, and choosing a Region inside a particular country or economic area keeps data within that jurisdiction, which is how residency and sovereignty requirements are met. Both benefits come from where the infrastructure is, independent of which services run on it.
B. Third-party licensing still applies in the cloud. Customers either bring their own licenses or consume license-included offerings, and both carry cost.
C. Managed database services automate minor version patching, and major version upgrades are a customer-initiated action. Either way this is a service feature, not an infrastructure benefit.
E. Reviewing source code for defects is done by application security tooling in a development pipeline. It has nothing to do with the physical footprint of AWS.
13
A company moves from managing its own database servers to a managed AWS database service. Its database administrators stop performing hardware maintenance, operating system patching, and backup scripting. What is the primary business benefit of this change?
Intermediate · Choose one
Explanation
Answer: B. AWS frames this as stopping money spent on undifferentiated heavy lifting: racking, stacking, powering, patching, and backing up are necessary but they do not distinguish the company from its competitors. Handing that work to AWS lets the same people work on schema design, query performance, and product features instead.
A. Managed services do not fix bugs in the customer's own application or schema. Application-level defects remain entirely the customer's problem.
C. A managed service such as Amazon RDS typically runs the same engine, sometimes trailing the newest community release. The benefit is reduced operational burden, not extra engine functionality.
D. Security remains a shared responsibility. AWS secures the underlying infrastructure, while the customer still handles access control, encryption choices, network exposure, and data classification.
14
Which statement correctly describes the relationship between the AWS Cloud and a company's ability to recover from a disaster?
Intermediate · Choose one
Explanation
Answer: A. On premises a recovery site means buying and maintaining a second set of hardware that sits idle. In AWS the recovery environment can be minimal or scripted and scaled up only when it is needed, so the customer pays for full recovery capacity only during a test or a real event. That economic change is why the cloud makes stronger recovery objectives affordable.
B. Resilience and recovery of the customer's workload sit on the customer side of the shared responsibility model. AWS is responsible for the resilience of the underlying infrastructure.
C. Cross-Region failover is something the customer designs and configures. AWS does not move a customer's workload between Regions on its own.
D. Individual components, and occasionally larger scopes, can and do fail. Multi-Availability Zone and multi-Region designs exist precisely because failure is assumed.
15
An on-premises company can adopt a new database or analytics technology only when it next refreshes its hardware, which happens every four to five years. Which characteristic of the AWS Cloud removes this constraint?
Intermediate · Choose one
Explanation
Answer: B. In the cloud, technology adoption is decoupled from the hardware purchasing cycle. Because databases, analytics engines, and machine learning capabilities are consumed as services, trying one costs only the hours it runs and can happen this week rather than at the next capital cycle. This is the practical effect of increased speed and agility combined with the democratization of advanced technologies, where complex capabilities are delegated to the provider instead of being built and hosted in house.
A. AWS never moves a customer's workload onto a different service. Deciding what to adopt and re-platforming onto it remain customer responsibilities under the shared responsibility model.
C. AWS operates its own infrastructure and has no involvement in the lifespan of hardware in a customer's data center. The constraint is removed by no longer depending on that hardware, not by prolonging it.
D. There is no refresh cycle for the customer to schedule. AWS refreshes the underlying hardware, and customers move to newer instance generations or services whenever it suits them.
16
A company's on-premises application is sized for peak load and runs at roughly 15 percent average utilization. After migrating, the company runs the same application on AWS with automatic scaling. Which TWO benefits does it gain? (Choose TWO.)
Intermediate · Select 2 answers
Explanation
Answer: C and E. Automatic scaling in the cloud attacks the two problems of peak-sized ownership at once. Capacity now follows demand, so the roughly 85 percent of capacity that used to sit idle on average is simply not running, and the spend shifts from a fixed up-front hardware purchase to a variable charge that tracks consumption.
A. Compliance is never automatic. AWS provides compliant infrastructure and evidence, but the customer must configure and operate the workload to meet the applicable framework.
B. Monitoring becomes more important, not less. Scaling decisions are driven by metrics, and the customer still needs visibility into application health.
D. Sub-millisecond latency for every user is physically impossible over long distances. Latency improves when workloads move closer to users, but it is bounded by geography.
17
A company describes its new AWS architecture as "reliable." Which behavior best demonstrates that claim?
Intermediate · Choose one
Explanation
Answer: A. Reliability is the ability of a workload to perform its intended function correctly and consistently when it is expected to, including recovering from infrastructure or service disruptions and dynamically acquiring the resources it needs to meet demand. Automatic recovery, not the absence of failures, is the observable evidence.
B. Newer instance generations often improve price and performance, but running modern hardware does not by itself make a workload recover from failure.
C. Copying data into five Regions is expensive and rarely justified. Reliability is about meeting stated availability and recovery objectives, not about maximizing replication.
D. Flat spending is a cost characteristic. A cheap workload that fails under load is not reliable, and an elastic workload's bill will legitimately rise with demand.
18
A team argues that because its application runs on AWS, it no longer needs to design for failure. Which response is correct?
Intermediate · Choose one
Explanation
Answer: C. AWS provides resilient building blocks, but assembling them into a resilient workload is the customer's responsibility under the shared responsibility model. A single instance in a single Availability Zone remains a single point of failure regardless of how good the underlying infrastructure is, which is why the design guidance is to distribute across Availability Zones and to recover automatically.
A. AWS makes no such guarantee. Hardware, networks, and software fail, and AWS design guidance explicitly tells customers to assume failures will occur.
B. Managed services reduce operational work but are not immune to disruption. Service level agreements for services such as Amazon EC2 and Amazon RDS assume a correctly architected consumer, typically across multiple Availability Zones.
D. Most AWS services are Regional and do not replicate across Regions by default. For customer workloads and data, cross-Region replication is an explicit customer configuration.
19
Which statement correctly distinguishes scalability from elasticity?
Hard · Choose one
Explanation
Answer: A. Scalability is a capability: the architecture can grow to handle more work, whether by adding instances horizontally or by moving to larger instances vertically. Elasticity is the dynamic behavior layered on top: capacity is added automatically when demand rises and, crucially, removed when it falls. A system can be scalable without being elastic, for example if scaling requires a manual change.
B. Self-managed fleets can be made elastic with automatic scaling, and managed services vary in how they scale. The distinction is behavioral, not service-category based.
C. Both concepts apply across compute, storage, databases, and networking. Neither is restricted to one resource type.
D. Never failing and recovering after failure describe fault tolerance and high availability. Neither term is about handling changes in load.
20
An architecture runs two application servers behind a load balancer in two Availability Zones. If one server fails, the load balancer routes all traffic to the survivor and users see a brief error for in-flight requests before retrying successfully. Which term most precisely describes this behavior?
Hard · Choose one
Explanation
Answer: A. High availability accepts a small, bounded disruption while the system detects the failure and redirects traffic, and it keeps overall downtime minimal. That is exactly what happens here: in-flight requests fail, health checks remove the bad target, and service continues. Fault tolerance would be the stronger claim that no request was affected at all.
B. Elasticity is capacity changing in response to demand. Here capacity changed because of a failure, and the surviving fleet was not resized to match load.
C. Fault tolerance means the failure is absorbed with no impact on any request. Because in-flight requests errored and had to be retried, the stronger claim does not hold.
D. Durability concerns whether stored data survives over time. It is a storage property and does not describe the availability of the compute tier.