CCNA Cloud Concepts Questions — Page 2 of 4

MCQmedium

A company wants to migrate their on-premises applications to AWS but is concerned about losing visibility into their infrastructure. Which AWS service provides a centralized inventory of all AWS resources and tracks configuration changes over time?

A.AWS CloudTrail

B.AWS Config

C.Amazon CloudWatch

D.AWS Systems Manager Inventory

AnswerB

Config maintains a complete inventory of AWS resources with full configuration history, enabling compliance evaluation, change tracking, and resource relationship mapping.

Why this answer

AWS Config is the correct service because it provides a centralized inventory of all AWS resources and continuously tracks configuration changes over time. It enables you to assess, audit, and evaluate the configurations of your AWS resources against desired policies, giving you full visibility into infrastructure state and history.

Exam trap

The trap here is that candidates often confuse AWS Config with AWS CloudTrail, mistakenly thinking CloudTrail's API logging provides configuration tracking, but CloudTrail only records who made the call, not the resulting configuration state or history.

How to eliminate wrong answers

Option A is wrong because AWS CloudTrail records API activity and user actions for auditing, but it does not provide a resource inventory or track configuration state changes over time. Option C is wrong because Amazon CloudWatch monitors performance metrics, logs, and alarms, but it is not designed to inventory resources or track configuration history. Option D is wrong because AWS Systems Manager Inventory collects software inventory and patch data from managed instances, but it does not provide a centralized inventory of all AWS resources or track configuration changes across the entire AWS environment.

Practice this question →

MCQmedium

A solutions architect is reviewing a system to ensure the right instance types are selected for each workload, that resource selection is based on data rather than assumptions, and that performance is monitored and improved over time. Which pillar of the AWS Well-Architected Framework is being applied?

A.Reliability

B.Performance Efficiency

C.Cost Optimisation

D.Operational Excellence

AnswerB

Performance Efficiency is about selecting the right resources for each workload, monitoring performance, and continuously improving efficiency as AWS introduces new services and features.

Why this answer

The Performance Efficiency pillar focuses on using computing resources efficiently to meet system requirements and maintaining that efficiency as demand changes and technologies evolve. The scenario describes selecting instance types based on data, monitoring performance, and iteratively improving—all core activities of this pillar. It directly aligns with the AWS Well-Architected Framework's design principle of 'democratizing advanced technologies' and the pillar's focus on right-sizing and continuous improvement.

Exam trap

The trap here is that candidates confuse 'monitoring and improving performance over time' with Operational Excellence, but Operational Excellence is about process improvement and automation, not specifically about data-driven resource selection and right-sizing for performance.

How to eliminate wrong answers

Option A is wrong because Reliability focuses on a system's ability to recover from failures and meet demand, not on selecting instance types based on performance data or iterative improvement. Option C is wrong because Cost Optimization focuses on minimizing costs and avoiding unnecessary spend, not on monitoring performance metrics or ensuring resource selection is data-driven for performance. Option D is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value and continuously improve processes and procedures, not specifically on selecting the right instance types for performance or data-driven resource selection.

Practice this question →

MCQmedium

An operations team documents all operational procedures as runbooks, deploys infrastructure using AWS CloudFormation templates stored in version control, and continuously refines their processes based on lessons learned from incidents. Which pillar of the AWS Well-Architected Framework does this represent?

A.Reliability

B.Security

C.Operational Excellence

D.Cost Optimisation

AnswerC

Operational Excellence is characterised by operations as code (CloudFormation templates in version control), annotated documentation (runbooks), and refining operations procedures through lessons learned — exactly what this team is doing.

Why this answer

Operational Excellence focuses on running and monitoring systems to deliver business value, and continually improving processes and procedures. Documenting runbooks, using infrastructure as code (CloudFormation) with version control, and refining processes from incident lessons are core practices of this pillar, as they enable repeatable, auditable, and continuously improving operations.

Exam trap

The trap here is that candidates often confuse 'operational documentation and process improvement' with 'reliability' because both involve incident response, but Reliability is about system resilience and recovery, not the continuous improvement of operational procedures themselves.

How to eliminate wrong answers

Option A is wrong because Reliability focuses on a workload's ability to recover from failures and meet demand, not on documenting procedures or continuous process improvement. Option B is wrong because Security focuses on protecting data, systems, and assets through identity, access controls, and encryption, not on operational runbooks or version-controlled infrastructure templates. Option D is wrong because Cost Optimisation focuses on avoiding unnecessary costs and maximizing resource efficiency, not on operational documentation or process refinement.

Practice this question →

MCQmedium

A retail company runs its e-commerce platform on AWS. The platform uses multiple Amazon EC2 instances behind an Application Load Balancer. To ensure the application remains available during an Availability Zone failure, the company distributes the instances across three Availability Zones. The load balancer automatically reroutes traffic away from an unhealthy zone. This design primarily addresses which pillar of the AWS Well-Architected Framework?

A.Security

B.Performance Efficiency

C.Cost Optimization

D.Reliability

AnswerD

The Reliability pillar encompasses the ability of a workload to perform its intended function correctly and consistently when it is expected to. This includes building resilience to withstand failures, such as deploying across multiple Availability Zones and using automatic failover. This design directly supports the Reliability pillar.

Why this answer

Distributing EC2 instances across multiple Availability Zones and using an Application Load Balancer to automatically reroute traffic away from unhealthy zones ensures that the application remains available even if an entire AZ fails. This design directly addresses the 'Reliability' pillar of the AWS Well-Architected Framework, which focuses on the ability of a workload to recover from infrastructure or service disruptions and dynamically acquire computing resources to meet demand.

Exam trap

The trap here is that candidates may confuse high availability (a Reliability concept) with elasticity (a Performance Efficiency concept) or assume that distributing across AZs is a cost-saving measure, when in fact it increases cost but is a fundamental Reliability best practice.

How to eliminate wrong answers

Option A is wrong because Security focuses on protecting data, systems, and assets through identity and access management, detective controls, and infrastructure protection, not on distributing instances across AZs for high availability. Option B is wrong because Performance Efficiency focuses on using computing resources efficiently to meet system requirements and maintaining that efficiency as demand changes and technologies evolve, not on fault tolerance or disaster recovery. Option C is wrong because Cost Optimization focuses on avoiding unnecessary costs, matching supply with demand, and using the most cost-effective resources, not on designing for availability zone failure recovery.

Practice this question →

MCQmedium

A company wants to ensure its cloud architecture can handle sudden spikes in traffic without manual intervention. Which cloud concept best describes this capability?

A.High availability

B.Fault tolerance

C.Elasticity

D.Durability

AnswerC

Elasticity automatically scales resources to match demand spikes and valleys.

Why this answer

Elasticity is the ability to automatically scale compute resources up or down in response to demand. This allows workloads to handle traffic spikes without pre-provisioning and to scale down when demand subsides, optimizing cost.

Practice this question →

MCQmedium

A solutions architect is reviewing an application design to ensure the system can automatically recover from failures, scale horizontally to increase availability, and prevent failures from cascading to other components. Which pillar of the AWS Well-Architected Framework is the architect applying?

A.Performance Efficiency

B.Operational Excellence

C.Security

D.Reliability

AnswerD

The Reliability pillar covers automatic recovery from failure, horizontal scaling for availability, and designing against cascading failures with circuit breakers and loose coupling. These are the exact concerns described in the question.

Why this answer

The question focuses on automatic recovery from failures, horizontal scaling for availability, and preventing cascading failures. These are core design principles of the Reliability pillar, which ensures a workload performs its intended function correctly and consistently when expected. The Reliability pillar specifically addresses foundations like distributed system design, recovery procedures, and change management to handle and recover from infrastructure or service disruptions.

Exam trap

The trap here is that candidates confuse Operational Excellence (which includes incident response and operations management) with Reliability (which specifically governs failure recovery, scaling for availability, and preventing cascading failures), leading them to select Operational Excellence when the question explicitly describes automatic recovery and horizontal scaling.

How to eliminate wrong answers

Option A is wrong because Performance Efficiency focuses on using computing resources efficiently to meet system requirements, and maintaining that efficiency as demand changes and technologies evolve; it does not directly address failure recovery or cascading failure prevention. Option B is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value, and on continually improving processes and procedures; while it includes incident response, the primary goal of automatic recovery and horizontal scaling for availability is a Reliability concern. Option C is wrong because Security focuses on protecting information, systems, and assets through confidentiality, integrity, and availability controls (CIA triad), but the specific mechanisms of automatic recovery and horizontal scaling are not security controls; they are reliability mechanisms.

Practice this question →

MCQmedium

A company is calculating the Total Cost of Ownership (TCO) for migrating to AWS vs. staying on-premises. Which costs are typically REDUCED when migrating to AWS?

A.Software licensing costs always decrease when moving to AWS

B.Physical hardware, data center facilities, and infrastructure management costs

C.Developer salaries and application development costs

D.Data transfer costs are eliminated in the cloud

AnswerB

Moving to AWS eliminates purchasing servers, renting/owning data center space, paying for power and cooling, and infrastructure management labor — these costs become variable and are shared across AWS's massive customer base.

Why this answer

AWS TCO analysis typically shows reduction in: hardware acquisition and depreciation (no physical servers), data center facility costs (power, cooling, space), hardware maintenance and support contracts, and staff time for infrastructure management. AWS shifts these from fixed capital costs to variable operational costs, and eliminates many administrative tasks that managed services handle automatically.

Practice this question →

MCQmedium

A startup is evaluating a migration from its on-premises infrastructure to AWS. The CTO notes that AWS can offer significantly lower per-unit costs for compute and storage compared to the startup's own data center. The CTO explains that AWS achieves this by pooling the demand of millions of customers, which allows AWS to negotiate better hardware prices and spread the fixed costs of data centers, power, cooling, and operational staff across a massive customer base. This specific cost advantage of cloud computing is best described by which fundamental concept?

A.Elasticity

B.Economies of scale

C.High availability

D.Fault tolerance

AnswerB

Economies of scale refer to the cost advantages that enterprises obtain due to their scale of operation. AWS leverages its massive customer base to negotiate lower prices for hardware, reduce per-unit operational costs, and pass those savings to customers. This directly matches the scenario described.

Why this answer

Economies of scale (Option B) is the correct concept because it directly describes how AWS achieves lower per-unit costs by aggregating demand from millions of customers. This massive scale allows AWS to negotiate bulk discounts on hardware, spread fixed costs (data centers, power, cooling, staff) over a huge customer base, and operate at a cost structure that individual startups cannot match. The CTO's description of pooling demand and spreading fixed costs is the textbook definition of economies of scale in cloud computing.

Exam trap

The trap here is that candidates often confuse 'economies of scale' with 'elasticity' because both involve scaling, but elasticity is about dynamic resource adjustment to meet variable demand, not the cost advantage from aggregated purchasing power.

How to eliminate wrong answers

Option A (Elasticity) is wrong because elasticity refers to the ability to automatically scale compute resources up or down based on demand, not the cost advantage from aggregated purchasing power. Option C (High availability) is wrong because high availability focuses on ensuring systems remain operational and accessible despite failures, typically through redundancy across Availability Zones, not on cost reduction from scale. Option D (Fault tolerance) is wrong because fault tolerance is the ability of a system to continue operating without interruption when one or more components fail, which is a resilience characteristic, not a cost-efficiency mechanism.

Practice this question →

MCQeasy

A retail company uses Amazon EC2 Auto Scaling to automatically launch hundreds of EC2 instances when CPU utilization exceeds 70% during a flash sale. When traffic subsides, the Auto Scaling group terminates the excess instances. This ability to dynamically provision and release compute resources in response to changes in demand best demonstrates which fundamental characteristic of cloud computing?

A.Broad network access

B.Resource pooling

C.Rapid elasticity

D.Measured service

AnswerC

Rapid elasticity is the ability to provision and release cloud resources quickly, often automatically, to scale in and out with demand. The Auto Scaling behavior shown in the scenario is a direct example of this characteristic.

Why this answer

Option C is correct because the scenario describes the ability to automatically scale compute resources up and down in response to real-time demand changes, which is the definition of rapid elasticity. In AWS, this is implemented through EC2 Auto Scaling, which dynamically launches or terminates instances based on CloudWatch alarms (e.g., CPU utilization > 70%). This on-demand provisioning and release of resources without manual intervention is a core characteristic of cloud computing as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates confuse resource pooling (the multi-tenant sharing of infrastructure) with rapid elasticity (the dynamic scaling of resources), because both involve 'pooling' or 'sharing' in a broad sense, but only rapid elasticity describes the automatic scaling up and down in response to demand.

How to eliminate wrong answers

Option A is wrong because broad network access refers to resources being accessible over the network via standard protocols (e.g., HTTPS, SSH), not the dynamic scaling of compute capacity. Option B is wrong because resource pooling describes the multi-tenant model where physical and virtual resources are pooled to serve multiple customers, not the ability to scale in response to demand. Option D is wrong because measured service involves metering and billing for resource usage (e.g., per-hour or per-GB charges), not the automatic provisioning and release of instances.

Practice this question →

MCQmedium

A company runs a critical e-commerce application in a single AWS Region. The architecture team wants to ensure the application remains available even if an entire data center fails. They plan to deploy the application across multiple physically separate and independent locations within that Region. Which component of the AWS global infrastructure should the team use to achieve this goal?

A.Availability Zones

B.Edge Locations

C.AWS Local Zones

D.AWS Regions

AnswerA

Availability Zones are isolated locations within a Region, each with independent power, cooling, and networking. Deploying across multiple AZs provides high availability and fault tolerance against data center failures.

Why this answer

Availability Zones (AZs) are physically separate and independent data centers within an AWS Region, each with isolated power, cooling, and networking. By deploying the application across multiple AZs, the architecture ensures that if one entire data center fails, the application continues to run in the other AZs, meeting the goal of high availability within a single Region.

Exam trap

The trap here is that candidates often confuse Availability Zones with Edge Locations or Regions, mistakenly thinking Edge Locations provide compute failover or that deploying across Regions is required for high availability within a single geographic area.

How to eliminate wrong answers

Option B (Edge Locations) is wrong because Edge Locations are used for content caching and delivery via Amazon CloudFront, not for hosting compute or storage resources to survive a data center failure. Option C (AWS Local Zones) is wrong because Local Zones extend a Region closer to end users for low-latency workloads, but they are not designed as independent failure domains within the same Region; they rely on the parent Region for core services. Option D (AWS Regions) is wrong because Regions are separate geographic areas, not physically separate locations within a single Region; deploying across Regions would address multi-Region disaster recovery, not the stated requirement of surviving a data center failure within one Region.

Practice this question →

MCQeasy

A company deploys their web application across multiple isolated locations within the same AWS Region, each with independent power, cooling, and networking. This design ensures that a failure in one location does not affect the others. What are these isolated locations called?

A.AWS Regions

B.Availability Zones

C.Edge Locations

D.VPC Subnets

AnswerB

AZs are one or more discrete data centres within a Region, each with independent power, cooling, and networking. Deploying across multiple AZs means a failure in one AZ does not affect workloads in the others.

Why this answer

Availability Zones (AZs) are isolated locations within an AWS Region that consist of one or more data centers with independent power, cooling, and networking. This design ensures that a failure in one AZ does not affect the others, providing high availability and fault tolerance for applications. The scenario directly describes the defining characteristics of an Availability Zone.

Exam trap

The trap here is that candidates confuse Availability Zones with AWS Regions, thinking that any isolated location must be a different Region, but the question explicitly states 'within the same AWS Region,' which points directly to Availability Zones.

How to eliminate wrong answers

Option A is wrong because AWS Regions are separate geographic areas (e.g., us-east-1, eu-west-2) that are isolated from each other, but the question specifies multiple isolated locations within the same AWS Region, not different Regions. Option C is wrong because Edge Locations are used for content delivery and caching via Amazon CloudFront, not for deploying web applications with independent power, cooling, and networking; they are not designed for compute or storage in the same way as AZs. Option D is wrong because VPC Subnets are logical subdivisions of a VPC's IP address range within a single Availability Zone, not physically isolated locations with independent infrastructure.

Practice this question →

MCQeasy

A multinational company hosts its customer relationship management (CRM) application on AWS. Sales team members access the CRM from various locations using desktop computers, laptops, tablets, and smartphones. They connect over the internet through standard web browsers. Which essential characteristic of cloud computing does this scenario best illustrate?

A.Resource pooling

B.Measured service

C.Broad network access

D.Rapid elasticity

AnswerC

Correct. Broad network access means capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous client platforms (e.g., mobile phones, tablets, laptops, and workstations). The scenario explicitly describes access from multiple device types over the internet.

Why this answer

This scenario best illustrates broad network access because the CRM application is accessed over the internet by sales team members using a variety of devices (desktops, laptops, tablets, smartphones) through standard web browsers. Broad network access is the cloud computing characteristic that defines the ability to access resources via standard protocols (e.g., HTTPS, TLS) from heterogeneous client platforms, which is exactly what is described here.

Exam trap

The trap here is that candidates often confuse broad network access with resource pooling because both involve 'many users,' but broad network access is about device and protocol diversity, not shared infrastructure.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's ability to serve multiple customers from shared physical and virtual resources, dynamically assigned according to demand; the scenario does not mention multi-tenancy or shared infrastructure. Option B is wrong because measured service involves metering and monitoring resource usage (e.g., CPU hours, data transfer) for billing and optimization; the scenario focuses on access methods, not usage tracking or pay-per-use. Option D is wrong because rapid elasticity is the ability to automatically scale resources up or down in response to demand; the scenario does not describe any scaling events or variable workload patterns.

Practice this question →

MCQmedium

A company runs an e-commerce application on a fleet of Amazon EC2 instances. The application experiences unpredictable traffic spikes during flash sales. To handle this, the company configures an Amazon EC2 Auto Scaling group to automatically add instances when CPU utilization exceeds 70% and remove instances when utilization drops below 30%. The company only pays for the instances that are running. This ability to dynamically add and remove compute capacity based on real-time demand best demonstrates which essential characteristic of cloud computing?

A.Elasticity

B.On-demand self-service

C.Measured service

D.Resource pooling

AnswerA

Correct. Elasticity is the ability to automatically scale resources up or down based on demand, matching supply to need and minimizing cost. The Auto Scaling group directly implements this characteristic.

Why this answer

The scenario describes an Auto Scaling group that adds EC2 instances when CPU exceeds 70% and removes them when it drops below 30%, paying only for running instances. This ability to automatically scale compute capacity up and down in response to real-time demand is the defining characteristic of elasticity in cloud computing, which allows resources to be provisioned and de-provisioned dynamically to match workload fluctuations.

Exam trap

The trap here is that candidates confuse elasticity with on-demand self-service, but on-demand self-service is about provisioning resources without manual intervention, whereas elasticity is specifically about scaling resources up and down to match demand.

How to eliminate wrong answers

Option B (On-demand self-service) is wrong because it refers to the ability to provision computing resources without human interaction, typically via a web console or API, not the dynamic scaling of capacity in response to load. Option C (Measured service) is wrong because it describes the metering and billing of cloud resource usage (e.g., per-hour or per-GB charges), not the automatic adjustment of capacity. Option D (Resource pooling) is wrong because it refers to the multi-tenant model where physical and virtual resources are pooled to serve multiple customers, not the ability to scale resources up or down on demand.

Practice this question →

MCQmedium

A startup wants to ensure its web application automatically handles traffic spikes during product launches without over-provisioning resources during quiet periods. Which AWS capability best addresses this requirement?

A.High availability through multiple AZs

B.Elasticity through AWS Auto Scaling

C.Durability through S3 data replication

D.Agility through rapid resource provisioning

AnswerB

Auto Scaling automatically adjusts the number of EC2 instances based on demand, handling spikes without manual intervention or permanent over-provisioning.

Why this answer

AWS Auto Scaling enables the startup to automatically adjust the number of Amazon EC2 instances in response to real-time demand, scaling up during traffic spikes and scaling down during quiet periods. This elasticity eliminates the need to over-provision resources, optimizing both cost and performance for variable workloads.

Exam trap

The trap here is that candidates confuse high availability (Option A) with elasticity, but high availability only maintains uptime across failures, not automatic capacity adjustment based on demand.

How to eliminate wrong answers

Option A is wrong because high availability through multiple Availability Zones (AZs) ensures fault tolerance and uptime, but does not automatically adjust capacity based on traffic changes. Option C is wrong because durability through S3 data replication protects data against loss, but does not address compute resource scaling for traffic spikes. Option D is wrong because agility through rapid resource provisioning describes the speed of deploying resources, but without automation it still requires manual intervention to scale, whereas Auto Scaling provides automated, policy-driven elasticity.

Practice this question →

MCQmedium

A company's CTO asks about the AWS Cloud Adoption Framework (AWS CAF). Which statement about AWS CAF is accurate?

A.AWS CAF is a compliance framework similar to SOC 2 or PCI DSS

B.AWS CAF organizes guidance into six perspectives covering Business, People, Governance, Platform, Security, and Operations

C.AWS CAF is only relevant for large enterprises migrating more than 1,000 servers

D.AWS CAF replaces the AWS Well-Architected Framework for architecture guidance

AnswerB

CAF provides a structured approach to cloud adoption with perspectives addressing business outcomes, organizational change, governance, technical platform, security, and operations.

Why this answer

Option B is correct because the AWS Cloud Adoption Framework (AWS CAF) organizes its guidance into six distinct perspectives: Business, People, Governance, Platform, Security, and Operations. These perspectives help organizations identify and address gaps in their cloud readiness across both business and technical domains, providing actionable best practices for cloud adoption.

Exam trap

The trap here is that candidates confuse AWS CAF with a compliance or security framework (like SOC 2 or PCI DSS) because of the word 'framework,' or assume it is only for large migrations, when in fact it is a holistic adoption guidance tool applicable to any organization regardless of size or migration scope.

How to eliminate wrong answers

Option A is wrong because AWS CAF is not a compliance framework like SOC 2 or PCI DSS; it is a strategic advisory framework that helps organizations plan and execute cloud adoption, not a certification or audit standard. Option C is wrong because AWS CAF is designed for organizations of all sizes and migration scales, not exclusively for large enterprises migrating more than 1,000 servers; it provides guidance for any cloud adoption journey. Option D is wrong because AWS CAF does not replace the AWS Well-Architected Framework; the Well-Architected Framework focuses on architectural best practices for building workloads, while AWS CAF addresses organizational readiness and transformation processes.

Practice this question →

MCQmedium

A company's application runs on multiple AWS services across different geographic regions. The development team needs to access and manage these resources from their office using standard web browsers and API calls over the internet. The team does not need any dedicated private network connections. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.Rapid elasticity

B.Broad network access

C.Resource pooling

D.Measured service

AnswerB

Broad network access is the correct characteristic. It means resources are available over the network and can be accessed by standard protocols (HTTP, HTTPS, SSH, etc.) from various devices, which matches the team using web browsers and APIs over the internet.

Why this answer

Broad network access is the correct answer because the scenario describes accessing AWS resources over the internet using standard web browsers and API calls, without requiring dedicated private network connections. This characteristic ensures that cloud services are available from any standard device (e.g., laptops, smartphones) using standard protocols such as HTTPS (port 443) and RESTful APIs, which is exactly what the development team needs.

Exam trap

The trap here is that candidates confuse 'broad network access' with 'rapid elasticity' because both involve scalability, but broad network access is specifically about ubiquitous network accessibility via standard protocols, not about scaling resources.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down based on demand, not to accessing resources over the internet. Option C is wrong because resource pooling means the provider's computing resources are pooled to serve multiple customers using a multi-tenant model, which is unrelated to network accessibility. Option D is wrong because measured service involves metering and billing for resource usage (e.g., pay-per-use), not the ability to access services via standard browsers and APIs.

Practice this question →

MCQmedium

Which AWS concept describes the strategy of designing applications so that any individual component can fail without causing the entire system to fail?

A.Economies of scale

B.Design for failure

C.Managed services adoption

D.Infrastructure as code

AnswerB

Design for failure assumes components will fail and builds applications to continue operating despite failures through redundancy, loose coupling, and isolation of failure domains.

Why this answer

B is correct because the 'design for failure' principle is a core AWS Well-Architected Framework concept that mandates building applications with no single point of failure. By distributing workloads across multiple Availability Zones and using services like Elastic Load Balancing (ELB) and Auto Scaling, a failure in one component (e.g., an EC2 instance) is isolated and automatically replaced, ensuring the system remains available. This contrasts with traditional monolithic designs where a single component failure can cascade into a full outage.

Exam trap

The trap here is that candidates confuse 'design for failure' with 'high availability' or 'disaster recovery,' but the question specifically asks about preventing a single component failure from causing total system failure—a core tenet of fault isolation, not just uptime metrics.

How to eliminate wrong answers

Option A is wrong because 'economies of scale' refers to the cost advantages AWS achieves by aggregating usage across many customers, which it passes on as lower pay-as-you-go prices; it is a pricing benefit, not a fault-tolerance design strategy. Option C is wrong because 'managed services adoption' (e.g., using Amazon RDS instead of self-managed databases) reduces operational overhead but does not inherently guarantee that a component failure won't bring down the entire system—fault isolation must still be architected. Option D is wrong because 'infrastructure as code' (e.g., using AWS CloudFormation or Terraform) automates provisioning and configuration management, but it does not by itself prevent a single component failure from causing a system-wide outage; it is an operational practice, not a resilience design pattern.

Practice this question →

MCQmedium

A company currently owns and operates its own data center. They are considering moving to AWS. Which economic benefit describes the elimination of the costs associated with purchasing, maintaining, and cooling physical servers?

A.Economies of scale

B.Stop spending money running and maintaining data centers

C.Go global in minutes

D.Increase speed and agility

AnswerB

By moving to AWS, companies eliminate costs for physical hardware, cooling, power, physical security, and data center staff — redirecting that spend to business value.

Why this answer

Option B is correct because moving to AWS eliminates the capital and operational expenses associated with owning and operating physical servers, including procurement, maintenance, cooling, and facility management. This aligns with the AWS value proposition of shifting from a capital expenditure (CapEx) model to an operational expenditure (OpEx) model, where customers pay only for the resources they consume.

Exam trap

The trap here is that candidates often confuse 'economies of scale' (a broad pricing benefit) with the specific elimination of data center operational costs, leading them to incorrectly select option A.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to the cost advantages AWS achieves through massive infrastructure aggregation, which are passed to customers as lower pay-as-you-go prices, not the direct elimination of data center costs. Option C is wrong because going global in minutes describes the ability to deploy infrastructure in multiple AWS Regions quickly, which is a benefit of global reach, not the removal of physical server costs. Option D is wrong because increase speed and agility refers to the ability to provision and iterate resources rapidly using automation and self-service, not the specific elimination of data center operational expenses.

Practice this question →

MCQeasy

AWS can offer lower pay-as-you-go pricing than a single company could achieve operating its own data centre because AWS aggregates usage from hundreds of thousands of customers. Which cloud computing benefit does this describe?

A.Trade capital expense for variable expense

B.Benefit from massive economies of scale

C.Increase speed and agility

D.Go global in minutes

AnswerB

AWS aggregates demand from hundreds of thousands of customers, achieving purchasing power and operational efficiencies that translate into lower prices than any individual company could achieve building and running their own data centres.

Why this answer

The scenario describes AWS aggregating usage from hundreds of thousands of customers to achieve lower per-unit costs than a single company could achieve operating its own data center. This is the direct definition of economies of scale, where the massive scale of AWS's infrastructure (e.g., purchasing power for hardware, optimized data center design) reduces the average cost per customer, enabling lower pay-as-you-go pricing.

Exam trap

The trap here is that candidates confuse 'economies of scale' with 'trade capital expense for variable expense' (Option A), because both relate to cost savings, but the question specifically describes the cost reduction from aggregated customer usage, not the payment model shift.

How to eliminate wrong answers

Option A is wrong because trading capital expense for variable expense describes the shift from upfront hardware purchases to pay-as-you-go operational costs, not the cost reduction from aggregated usage. Option C is wrong because increasing speed and agility refers to the ability to rapidly provision resources (e.g., via AWS CloudFormation or APIs), not the cost benefit from aggregated customer usage. Option D is wrong because going global in minutes describes the ability to deploy resources across AWS Regions (e.g., using Route 53 or CloudFront) for low-latency global reach, not the cost advantage from aggregated usage.

Practice this question →

Multi-Selectmedium

A company wants to adopt AWS and is performing a readiness assessment. The AWS Cloud Adoption Framework (CAF) identifies which two areas that most cloud migrations fail to address adequately?

Select 2 answers

A.Platform and Security perspectives

B.People and Governance perspectives

C.Business and Operations perspectives

D.Platform and Operations perspectives

AnswersB, C

CAF identifies People (organizational change, training, culture) and Governance (risk management, finance management, program management) as frequently underaddressed — technical teams focus on Platform and Security while neglecting these enabling factors.

Why this answer

The AWS Cloud Adoption Framework (CAF) identifies that most cloud migrations fail because organizations neglect the People and Governance perspectives. The People perspective focuses on change management, training, and organizational culture, while the Governance perspective ensures that policies, compliance, and oversight mechanisms are in place to manage cloud risks and costs. Without addressing these two areas, even technically sound migrations can stall due to lack of stakeholder buy-in or uncontrolled spending.

Exam trap

The trap here is that candidates often assume the most critical failure areas are technical (Platform, Security, Operations) because those are the most visible, but the CAF explicitly calls out People and Governance as the root causes of migration failures.

Practice this question →

Drag & Dropmedium

Drag and drop the steps to create an IAM user with programmatic access and attach a policy in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

IAM user creation involves enabling programmatic access, attaching policies, and securely storing credentials.

Practice this question →

MCQeasy

A developer needs to launch a test EC2 instance for a new prototype. The developer logs into the AWS Management Console, selects an instance type, and launches the instance without contacting AWS support or waiting for approval. Which cloud computing characteristic does this demonstrate?

A.Broad network access

B.On-demand self-service

C.Resource pooling

D.Measured service

AnswerB

On-demand self-service allows users to provision compute capabilities as needed automatically, without requiring human interaction from each service provider. Launching EC2 instances via the console without contacting AWS support exemplifies this.

Why this answer

The scenario describes a developer independently provisioning an EC2 instance through the AWS Management Console without requiring human interaction with AWS support. This directly aligns with the NIST definition of on-demand self-service, a core characteristic of cloud computing where users can unilaterally provision computing capabilities as needed automatically.

Exam trap

The trap here is that candidates confuse 'on-demand self-service' with 'broad network access' because both involve network-based interaction, but the key differentiator is the absence of human intervention in the provisioning process, not the method of access.

How to eliminate wrong answers

Option A is wrong because broad network access refers to capabilities being available over the network and accessed through standard mechanisms (e.g., HTTPS, SSH), not the ability to provision resources without approval. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the user's ability to self-provision. Option D is wrong because measured service involves cloud systems automatically controlling and optimizing resource use by leveraging a metering capability, which is about usage monitoring and billing, not the self-service provisioning action.

Practice this question →

MCQmedium

A company has a hybrid cloud environment with both on-premises servers and AWS. They want a consistent management experience across both environments. Which AWS service extends the same AWS Systems Manager capabilities to non-AWS servers?

A.AWS Outposts

B.AWS Systems Manager with hybrid activations

C.AWS Direct Connect

D.Amazon EC2 Systems Manager

AnswerB

Systems Manager hybrid activations register on-premises servers and VMs as managed instances, extending Run Command, Patch Manager, Inventory, and Session Manager to non-AWS infrastructure.

Why this answer

AWS Systems Manager with hybrid activations allows you to manage on-premises servers and other non-AWS compute resources using the same Systems Manager capabilities (e.g., Run Command, Patch Manager, Inventory) as you use for EC2 instances. By installing the SSM Agent on the non-AWS server and registering it via a hybrid activation, the server appears as a managed instance in Systems Manager, providing a consistent management plane across hybrid environments.

Exam trap

The trap here is that candidates often confuse AWS Outposts (which extends AWS infrastructure) with the ability to manage existing non-AWS servers, or they mistakenly think Amazon EC2 Systems Manager (the old name) can natively manage on-premises servers without hybrid activations.

How to eliminate wrong answers

Option A is wrong because AWS Outposts is a fully managed service that extends AWS infrastructure, services, and APIs to on-premises locations, but it does not extend Systems Manager capabilities to existing non-AWS servers; it requires running AWS-designed hardware. Option C is wrong because AWS Direct Connect is a dedicated network connection from on-premises to AWS, which improves bandwidth and latency but does not provide any management or Systems Manager functionality. Option D is wrong because Amazon EC2 Systems Manager is the former name of AWS Systems Manager, and it only manages EC2 instances natively; it does not inherently support non-AWS servers without hybrid activations.

Practice this question →

MCQeasy

Under the AWS Shared Responsibility Model, which of the following is the customer's responsibility when using Amazon RDS?

A.Patching the underlying EC2 instances hosting the database

B.Managing the physical storage media and hardware

C.Managing database user accounts and controlling data access

D.Applying database engine minor version patches

AnswerC

Customers are responsible for their data, creating database users, setting permissions, and controlling which applications and users can access the database.

Why this answer

Under the AWS Shared Responsibility Model, AWS manages the infrastructure, including the underlying EC2 instances, physical storage, and database engine minor version patches for Amazon RDS. The customer is responsible for managing database user accounts, controlling data access, and securing the data itself, as these are within the customer's control and not managed by AWS.

Exam trap

The trap here is that candidates often confuse the customer's responsibility for managing database user accounts with AWS's responsibility for patching the database engine, leading them to incorrectly select option D as the customer's task.

How to eliminate wrong answers

Option A is wrong because AWS is responsible for patching the underlying EC2 instances that host the RDS database, as RDS is a managed service where AWS handles the host OS and infrastructure. Option B is wrong because managing physical storage media and hardware is AWS's responsibility under the shared model, as they control the data center and physical infrastructure. Option D is wrong because applying database engine minor version patches is managed by AWS for RDS, though customers can schedule maintenance windows; the actual patching is AWS's responsibility.

Practice this question →

100

MCQmedium

A company uses Amazon EC2 instances to run its workloads. The company's IT team does not know the exact physical server where each instance runs, and instances from multiple customers may be hosted on the same physical hardware. The team only specifies the AWS Region and Availability Zone. Which essential characteristic of cloud computing does this scenario BEST represent?

A.On-demand self-service

B.Resource pooling

C.Rapid elasticity

D.Measured service

AnswerB

Resource pooling is the correct answer. The scenario describes how AWS pools its physical infrastructure to serve multiple customers simultaneously, with customers having no control over the exact physical location of their resources beyond a high-level abstraction like region or Availability Zone. This is a direct example of resource pooling.

Why this answer

Resource pooling is the correct answer because the scenario describes how AWS aggregates compute resources from multiple physical hosts into a shared pool, which is then dynamically assigned and reassigned to customers based on demand. The IT team has no control over or knowledge of the exact physical server, and instances from different customers can run on the same hardware, which is the defining behavior of resource pooling as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates often confuse resource pooling with on-demand self-service because both involve abstraction, but resource pooling specifically addresses the multi-tenant sharing of physical infrastructure, whereas on-demand self-service is about the user's ability to provision resources without provider intervention.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing capabilities (like launching an EC2 instance) automatically without requiring human interaction with the service provider, not to the multi-tenant sharing of physical hardware. Option C is wrong because rapid elasticity describes the ability to scale resources up or down quickly and automatically (e.g., using Auto Scaling groups), not the underlying multi-tenant infrastructure. Option D is wrong because measured service involves metering and reporting resource usage (e.g., CloudWatch metrics and billing), not the pooling of physical hardware across multiple customers.

Practice this question →

101

MCQmedium

A software development team uses AWS CloudFormation to define their test environments as infrastructure as code. Each developer can launch a complete environment containing multiple Amazon EC2 instances, an Application Load Balancer, and an Amazon RDS database in under five minutes. They run their test suite for a few hours and then delete the entire CloudFormation stack, releasing all resources. Which essential characteristic of cloud computing does this workflow best illustrate?

A.On-demand self-service

B.Rapid elasticity

C.Resource pooling

D.Measured service

AnswerB

Rapid elasticity is the ability to quickly scale resources up and down in response to demand. The developers can create a full environment in minutes and tear it down just as quickly, directly illustrating this characteristic.

Why this answer

Option B is correct because the ability to provision and de-provision a complete environment—including EC2 instances, an ALB, and an RDS database—in minutes and then release all resources after a few hours directly demonstrates rapid elasticity. This characteristic allows cloud resources to scale out and in quickly, matching demand without manual intervention, which is exactly what the CloudFormation stack lifecycle achieves.

Exam trap

The trap here is that candidates confuse 'on-demand self-service' (the ability to provision without human interaction) with 'rapid elasticity' (the ability to scale resources up and down quickly), but the question's focus on the speed of provisioning and de-provisioning the entire environment points to elasticity, not just self-service.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user provisioning resources without human interaction, but the question emphasizes the speed of scaling out and in, not the self-service aspect. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical resources are shared among customers, which is not illustrated by the team's ability to rapidly create and delete environments. Option D is wrong because measured service involves metering and billing for resource usage, which is not the focus of this workflow; the team deletes the stack after testing, and the key takeaway is the elasticity of resource allocation, not the measurement.

Practice this question →

102

MCQmedium

A company runs a web application on Amazon EC2 instances. The application experiences unpredictable traffic spikes during marketing campaigns. The company configures an Amazon EC2 Auto Scaling group to automatically add instances when CPU utilization exceeds 70% and remove instances when it drops below 30%. This allows the company to handle peak loads without manual intervention and avoid paying for idle capacity during low traffic periods. Which essential characteristic of cloud computing does this configuration BEST demonstrate?

A.On-demand self-service

B.Broad network access

C.Rapid elasticity

D.Measured service

AnswerC

Rapid elasticity is the ability to quickly and automatically scale computing resources up or down to match demand. The Auto Scaling group adding and removing EC2 instances based on CPU thresholds is a direct example of this characteristic.

Why this answer

The Auto Scaling group dynamically adjusts the number of EC2 instances in response to CPU utilization thresholds, scaling out during traffic spikes and scaling in during low traffic. This ability to rapidly provision and release compute resources to match demand is the defining characteristic of rapid elasticity, which allows the company to handle peak loads without manual intervention and avoid paying for idle capacity.

Exam trap

The trap here is that candidates often confuse rapid elasticity with on-demand self-service, but on-demand self-service is about the ability to provision resources without human interaction, while rapid elasticity is about automatically scaling resources up or down to match demand in near real-time.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user provisioning computing resources without requiring human interaction with the service provider, not the automatic scaling behavior described. Option B is wrong because broad network access describes resources accessible over the network via standard protocols (e.g., HTTP, HTTPS) from various devices, not the dynamic scaling of compute capacity. Option D is wrong because measured service involves metering and reporting resource usage for billing and optimization, whereas the scenario focuses on automatic scaling to match demand, not on usage tracking or cost allocation.

Practice this question →

103

MCQmedium

A startup is migrating its infrastructure to AWS. The CTO notices that the hourly rate for an Amazon EC2 instance is significantly lower than the cost of purchasing and maintaining a comparable physical server in their own data center. The CTO explains that AWS can offer lower prices because it aggregates demand from thousands of customers and optimizes its data center operations. Which benefit of cloud computing does this scenario primarily illustrate?

A.High availability

B.Elasticity

C.Economies of scale

D.Global reach

AnswerC

Economies of scale occur when a provider achieves lower per-unit costs by operating at a massive scale. AWS passes these savings to customers in the form of lower usage-based prices. The CTO's explanation directly matches this concept.

Why this answer

The scenario describes AWS aggregating demand from thousands of customers to optimize data center operations, which directly reduces per-unit costs. This is the definition of economies of scale, where larger operational scale leads to lower average costs. The CTO's observation that the hourly EC2 rate is lower than purchasing a physical server illustrates how cloud providers pass these savings to customers.

Exam trap

The trap here is that candidates confuse 'economies of scale' with 'elasticity' because both involve scaling, but elasticity is about dynamic resource adjustment while economies of scale is about cost advantages from large-scale operations.

How to eliminate wrong answers

Option A is wrong because high availability refers to systems remaining operational despite failures (e.g., using Multi-AZ deployments), not to cost reduction from aggregated demand. Option B is wrong because elasticity is the ability to scale resources up or down automatically based on demand (e.g., using Auto Scaling groups), not the cost advantage from provider scale. Option D is wrong because global reach means deploying resources across multiple geographic regions (e.g., using AWS Regions and Edge Locations), not the cost benefits of shared infrastructure.

Practice this question →

104

MCQmedium

A startup runs an e-commerce website on AWS. During flash sales, traffic can increase 10x in a few minutes. The startup uses an Auto Scaling group to automatically launch additional EC2 instances when CPU utilization exceeds 70% and terminate them when utilization drops below 30%. This approach ensures that the application always has enough capacity to handle the load without manual intervention, and they only pay for what they use. Which cloud computing concept does this scenario BEST illustrate?

A.High availability

B.Elasticity

C.Fault tolerance

D.Disaster recovery

AnswerB

Elasticity is the correct answer. It refers to the ability to dynamically scale infrastructure resources up and down based on real-time demand. The Auto Scaling group automatically adjusts the number of EC2 instances in response to CPU utilization, which is a textbook example of elasticity.

Why this answer

Option B is correct because elasticity is the ability of a cloud system to automatically scale resources up or down based on demand. The Auto Scaling group dynamically adds EC2 instances when CPU utilization exceeds 70% and terminates them when it drops below 30%, ensuring capacity matches load without manual intervention. This pay-per-use model is a hallmark of elasticity, not just high availability or fault tolerance.

Exam trap

The trap here is that candidates confuse elasticity with high availability, but elasticity is about scaling resources to match demand, while high availability is about maintaining uptime through redundancy and failover mechanisms.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring the application remains accessible despite failures, typically through redundancy across multiple Availability Zones, not on dynamically scaling capacity in response to load changes. Option C is wrong because fault tolerance refers to a system's ability to continue operating without interruption after a component failure, often using redundant components in an active-active configuration, whereas this scenario describes scaling based on demand, not failure recovery. Option D is wrong because disaster recovery involves predefined plans and procedures to restore operations after a catastrophic event, such as data loss or region-wide outage, not the automatic scaling of resources during normal traffic spikes.

Practice this question →

105

MCQeasy

A government agency runs all of its computing workloads on hardware located in its own secure facility. No resources are hosted with a third-party cloud provider. The agency manages all servers, networking equipment, and storage. Which cloud deployment model describes this architecture?

A.Public cloud

B.Hybrid cloud

C.Private cloud

D.Community cloud

AnswerC

Private cloud means the infrastructure is dedicated to a single organisation and is not shared with others. Operating all workloads on agency-owned hardware in an agency-managed facility is private cloud.

Why this answer

Option C is correct because a private cloud deployment model is defined by cloud resources being used exclusively by a single organization, typically hosted on-premises in the organization's own data center. In this scenario, the government agency owns and manages all hardware, networking, and storage within its own secure facility, with no third-party cloud provider involvement, which aligns precisely with the private cloud model.

Exam trap

The trap here is that candidates often confuse 'on-premises' with 'private cloud,' forgetting that a private cloud requires cloud characteristics like self-service, resource pooling, and rapid elasticity, not just isolated hardware; however, in this question, the agency's fully managed on-premises environment still qualifies as a private cloud because it meets the NIST definition of exclusive use by a single organization.

How to eliminate wrong answers

Option A is wrong because a public cloud model involves resources hosted and managed by a third-party cloud provider (e.g., AWS, Azure, GCP) and shared with multiple tenants, which contradicts the agency's exclusive use of its own on-premises hardware. Option B is wrong because a hybrid cloud model requires a combination of on-premises infrastructure (private cloud) and public cloud resources, with orchestration or data transfer between them; the agency has no public cloud component. Option D is wrong because a community cloud model is shared by several organizations with common concerns (e.g., compliance, security), not a single agency, and often involves third-party hosting; this scenario describes exclusive use by one organization.

Practice this question →

106

MCQeasy

Before moving to AWS, a company over-provisioned their data centre servers to handle projected peak traffic, resulting in expensive idle capacity most of the time. After migrating, the company uses Auto Scaling to match capacity exactly to actual demand. Which cloud benefit does this represent?

A.Trade capital expense for variable expense

B.Benefit from economies of scale

C.Stop guessing about capacity

D.Increase speed and agility

AnswerC

Cloud computing allows organisations to provision as much or as little capacity as needed and scale up or down automatically. This eliminates both the waste of over-provisioning and the performance problems of under-provisioning.

Why this answer

Option C is correct because the scenario directly describes the cloud benefit of 'Stop guessing about capacity.' Before AWS, the company over-provisioned servers to handle projected peak traffic, leading to idle capacity. With Auto Scaling, AWS dynamically adjusts compute resources to match actual demand, eliminating the need to predict capacity in advance.

Exam trap

The trap here is that candidates confuse 'Stop guessing about capacity' with 'Trade capital expense for variable expense,' because both involve cost optimization, but the question specifically highlights the elimination of over-provisioning due to demand prediction, not the payment model shift.

How to eliminate wrong answers

Option A is wrong because 'Trade capital expense for variable expense' refers to shifting from upfront hardware costs (CAPEX) to pay-as-you-go operational costs (OPEX), not to matching capacity to demand. Option B is wrong because 'Benefit from economies of scale' describes how AWS aggregates usage across many customers to lower per-unit costs, which is unrelated to Auto Scaling's demand-matching behavior. Option D is wrong because 'Increase speed and agility' focuses on rapid provisioning of resources, not on eliminating capacity guessing; Auto Scaling does improve agility, but the core benefit illustrated here is removing the need to predict capacity.

Practice this question →

107

MCQmedium

A company migrates their self-managed MySQL database running on a virtual machine to Amazon RDS for MySQL, taking advantage of managed backups and Multi-AZ without changing the database schema or application code. Which migration strategy does this represent?

A.Rehost

B.Replatform

C.Refactor

D.Repurchase

AnswerB

Replatforming involves moving to a managed cloud service to gain benefits (automated backups, Multi-AZ) without rearchitecting the application. Moving from a self-managed MySQL VM to Amazon RDS is the classic replatform example.

Why this answer

This is a Replatform (also called 'lift and reshape' or 'platform modernization') migration because the company moves the MySQL database from a self-managed VM to Amazon RDS without changing the database schema or application code. They gain managed backups and Multi-AZ, which are RDS-specific features, but the core database engine and application interface remain unchanged, so no refactoring of the application is required.

Exam trap

The trap here is that candidates confuse Rehost with Replatform because both involve minimal code changes, but Rehost keeps the workload on the same type of infrastructure (e.g., EC2), while Replatform moves to a managed service like RDS that offloads administrative tasks.

How to eliminate wrong answers

Option A is wrong because Rehost (lift-and-shift) would involve moving the MySQL database as-is to an EC2 instance, not to a managed service like RDS that provides automated backups and Multi-AZ. Option C is wrong because Refactor would require changing the database schema, application code, or both (e.g., moving from MySQL to DynamoDB or Aurora Serverless), which is not done here. Option D is wrong because Repurchase involves replacing the database with a different commercial product (e.g., moving from MySQL to Oracle Database), which is not the case as the company stays on MySQL.

Practice this question →

108

MCQmedium

A company uses Amazon EC2 instances and Amazon S3 for its workloads. The finance team reviews the monthly AWS bill and notices it includes line items for EC2 instance hours, data transfer out from EC2, and S3 storage usage. The bill shows exactly how many hours each instance ran and how much data was transferred. The company uses this detailed usage data to allocate costs to different departments and to optimize resource utilization. This scenario best demonstrates which essential characteristic of cloud computing?

A.Measured service

B.On-demand self-service

C.Broad network access

D.Resource pooling

AnswerA

This is correct because measured service is the characteristic where cloud providers meter usage and provide detailed reports, enabling customers to understand and optimize costs. The scenario of receiving a detailed per-hour and per-gigabyte bill directly illustrates this concept.

Why this answer

The correct answer is A (Measured service) because the scenario explicitly describes how the company uses detailed usage data—EC2 instance hours, data transfer out, and S3 storage—to allocate costs and optimize resource utilization. This aligns with the cloud computing characteristic where resource usage is metered, monitored, and reported transparently, enabling pay-per-use billing and cost allocation.

Exam trap

The trap here is that candidates may confuse 'Measured service' with 'Resource pooling' because both involve resource usage, but measured service specifically refers to the metering and reporting of usage for billing and optimization, not the multi-tenant sharing aspect.

How to eliminate wrong answers

Option B (On-demand self-service) is wrong because the scenario focuses on cost allocation and optimization based on usage data, not on the ability to provision resources automatically without human interaction. Option C (Broad network access) is wrong because the scenario does not mention network accessibility from diverse devices or platforms; it is about billing and usage tracking. Option D (Resource pooling) is wrong because the scenario does not describe multi-tenant resource sharing or location independence; it is about metered usage and cost allocation.

Practice this question →

109

MCQmedium

Which benefit of cloud computing allows organizations to avoid the capital expense of buying hardware and instead pay only for what they use?

A.Economies of scale

B.Stop spending money running and maintaining data centers

C.Trade capital expense for variable expense

D.Increase speed and agility

AnswerC

Cloud computing converts upfront CapEx (hardware purchases) into variable OpEx (pay-as-you-go) spending.

Why this answer

Trading capital expense (CapEx) for variable/operational expense (OpEx) is a core cloud benefit. Instead of investing in data centers and servers upfront, organizations pay only for the computing resources they consume, converting large fixed costs into smaller, flexible operating expenses.

Practice this question →

110

MCQmedium

A company moves its infrastructure to AWS. The company's IT team notices that they have no control over which specific physical server their virtual machines run on, and they are unaware of the exact hardware location except at the regional level. The underlying physical resources are shared across multiple AWS customers. Which essential characteristic of cloud computing does this scenario BEST describe?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerC

Resource pooling is correct. The cloud provider pools its computing resources to serve multiple consumers using a multi-tenant model. The customer has no visibility or control over the exact physical location of the resources, only a higher-level abstraction such as region or availability zone. This characteristic allows for efficient utilization and cost savings.

Why this answer

Option C is correct because resource pooling is the cloud characteristic where the provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to customer demand. The scenario describes the customer having no control over the exact physical server or hardware location beyond the regional level, which is the essence of resource pooling. This allows AWS to achieve economies of scale while abstracting the underlying hardware from the customer.

Exam trap

The trap here is that candidates confuse resource pooling with rapid elasticity because both involve dynamic allocation, but resource pooling is about multi-tenant sharing of physical infrastructure, while rapid elasticity is about the speed of scaling resources up or down.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a customer's ability to provision computing capabilities automatically without requiring human interaction with each service provider, not to the lack of visibility into physical hardware. Option B is wrong because broad network access describes capabilities that are available over the network and accessed through standard mechanisms (e.g., HTTPS, SSH) by heterogeneous client platforms, not the sharing of physical infrastructure. Option D is wrong because rapid elasticity refers to the ability to quickly scale resources up or out and down or in, often automatically, to meet fluctuating demand, not to the abstraction or sharing of physical servers.

Practice this question →

111

MCQmedium

A company wants its employees to access cloud applications and manage cloud resources from anywhere using a variety of devices, including laptops, smartphones, and tablets. Which essential characteristic of cloud computing does this requirement directly represent?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Measured service

AnswerB

Broad network access means that resources are available over the network and can be accessed by standard mechanisms that promote use by heterogeneous client platforms (e.g., mobile phones, tablets, laptops, and workstations). This directly matches the requirement to access cloud resources from a variety of devices.

Why this answer

The requirement for employees to access cloud applications and manage resources from anywhere using laptops, smartphones, and tablets directly represents broad network access. This essential characteristic means that cloud services are available over standard network protocols (e.g., HTTP/HTTPS, SSH) and can be accessed by heterogeneous client platforms, including mobile devices, workstations, and tablets, without requiring location-specific infrastructure.

Exam trap

The trap here is that candidates confuse 'broad network access' with 'on-demand self-service' because both involve user interaction, but the question's emphasis on 'from anywhere using a variety of devices' is a direct match for the NIST definition of broad network access, not the automated provisioning aspect of self-service.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing capabilities (e.g., spinning up an EC2 instance) automatically without requiring human interaction with the service provider, not the ability to access from multiple devices. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the access method or device diversity. Option D is wrong because measured service means that cloud systems automatically control and optimize resource use by leveraging a metering capability (e.g., billing per API call or GB-hour), which is unrelated to device or network accessibility.

Practice this question →

112

MCQeasy

Which of the following best describes an AWS Region?

A.A single data center used by AWS

B.A group of edge locations used for content delivery

C.A geographic area containing multiple Availability Zones

D.A virtual private network segment within AWS

AnswerC

A Region is a geographic area with multiple, isolated Availability Zones.

Why this answer

An AWS Region is a distinct geographic area that consists of multiple, isolated, and physically separate Availability Zones (AZs). Each AZ contains one or more data centers with redundant power, networking, and connectivity. This design ensures high availability and fault tolerance, as resources can be distributed across AZs within a Region to withstand failures in a single data center.

Exam trap

The trap here is that candidates confuse an Availability Zone (a single data center or cluster) with an AWS Region, or mistakenly think a Region is just a single data center, when in fact a Region always contains at least two AZs for high availability.

How to eliminate wrong answers

Option A is wrong because a single data center is not an AWS Region; a Region comprises multiple Availability Zones, each of which may contain one or more data centers. Option B is wrong because a group of edge locations is used for content delivery via AWS CloudFront, not for compute or storage services that define a Region. Option D is wrong because a virtual private network segment within AWS refers to a Virtual Private Cloud (VPC), which is a logically isolated network within a Region, not the Region itself.

Practice this question →

113

MCQmedium

A startup uses AWS Lambda for its backend processing. The company is billed only for the number of function invocations and the compute time consumed, rounded up to the nearest millisecond. There are no minimum fees or upfront commitments. This billing model is a direct example of which essential characteristic of cloud computing?

A.On-demand self-service

B.Resource pooling

C.Measured service

D.Broad network access

AnswerC

Measured service is the characteristic where cloud systems automatically control and optimize resource use by leveraging a metering capability. Charging only for the actual compute time consumed (down to the millisecond) with no minimum fees is a direct demonstration of this metering and pay-per-use model.

Why this answer

The AWS Lambda billing model—charging only for function invocations and compute time rounded to the nearest millisecond, with no minimum fees or upfront commitments—directly exemplifies measured service. This essential characteristic of cloud computing means that resource usage is metered, monitored, and reported transparently, allowing customers to pay only for what they consume. In Lambda, the metering is granular: each invocation is counted, and duration is measured in 1-millisecond increments, enabling precise cost allocation.

Exam trap

The trap here is that candidates confuse 'measured service' with 'on-demand self-service' because both involve user control, but measured service specifically refers to the metering and pay-per-use billing model, not the ability to provision resources without human interaction.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources automatically without requiring human interaction with the service provider, not to the billing model itself. Option B is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned to serve multiple customers, which is an underlying infrastructure characteristic, not a billing feature. Option D is wrong because broad network access means that resources are available over the network and accessed through standard protocols (e.g., HTTPS, SSH), which is unrelated to how usage is metered and billed.

Practice this question →

114

MCQmedium

A development team needs to spin up a new Amazon RDS database instance for a proof-of-concept application. The team can log into the AWS Management Console, select the database engine, configure settings, and launch the instance within minutes, without needing to submit a ticket or wait for IT operations to provision hardware. Which essential characteristic of cloud computing does this scenario BEST demonstrate?

A.Resource pooling

B.Measured service

C.On-demand self-service

D.Rapid elasticity

AnswerC

On-demand self-service is a key characteristic of cloud computing that enables users to provision computing resources automatically as needed, without requiring human interaction with the service provider. The team's ability to launch an RDS instance directly via the console, without waiting for IT staff, is a direct example of this characteristic.

Why this answer

The scenario describes a user independently provisioning an RDS instance through the AWS Management Console without any human interaction with IT operations. This directly aligns with the on-demand self-service characteristic of cloud computing, where users can provision computing resources automatically as needed without requiring service provider interaction.

Exam trap

The trap here is confusing the ability to quickly provision resources (on-demand self-service) with the ability to scale them dynamically (rapid elasticity), as both involve speed but address different phases of resource lifecycle.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's ability to serve multiple customers from shared physical resources using multi-tenant models, not the user's ability to provision resources independently. Option B is wrong because measured service involves monitoring, controlling, and reporting resource usage for billing and optimization, which is not demonstrated by the act of spinning up an instance. Option D is wrong because rapid elasticity describes the ability to scale resources up or down quickly in response to demand, not the initial self-provisioning of a single instance.

Practice this question →

115

MCQeasy

A company's sales team uses a cloud-based CRM application hosted on AWS. Sales representatives access the application from various devices—office desktops, company-issued laptops, and personal smartphones—using only standard web browsers and internet connections. No special client software or dedicated network connections are required. Which essential characteristic of cloud computing does this scenario best illustrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerB

Broad network access means capabilities are available over the network and accessed through standard mechanisms from a variety of client devices. The sales team uses multiple device types and standard web browsers, which is a direct example of this characteristic.

Why this answer

The scenario describes sales representatives accessing the CRM application from various devices (desktops, laptops, smartphones) using only standard web browsers and internet connections, without requiring special client software or dedicated network connections. This directly illustrates 'broad network access,' which is the ability for resources to be accessed over the network by a wide range of client platforms (e.g., mobile phones, laptops, workstations) using standard protocols (HTTP/HTTPS). The key is that the service is available from anywhere with an internet connection, not limited to a specific location or device type.

Exam trap

The trap here is that candidates confuse 'broad network access' with 'on-demand self-service' because both involve user interaction, but the key differentiator is that broad network access focuses on accessibility from multiple device types over standard networks, whereas on-demand self-service is about automated provisioning without provider intervention.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources (like spinning up EC2 instances) automatically without requiring human interaction with the service provider, not simply accessing an application from different devices. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, which is an internal implementation detail not observable by the sales team. Option D is wrong because rapid elasticity involves the ability to quickly scale resources up or down (e.g., adding more compute capacity during peak load), which is not demonstrated by the sales team merely accessing a static CRM application from various devices.

Practice this question →

116

MCQmedium

A company wants to migrate 50 virtual machines from their on-premises data centre to AWS as quickly as possible to reduce data centre costs. They plan to move the VMs without making any changes to the applications. Which cloud migration strategy does this represent?

A.Refactor

B.Replatform

C.Rehost

D.Retire

AnswerC

Rehosting (lift and shift) moves applications to the cloud with no changes. It is the fastest strategy for migrating VMs and is chosen when speed and minimising disruption are the primary goals.

Why this answer

Option C (Rehost) is correct because the company is migrating 50 virtual machines to AWS without making any changes to the applications, which is the defining characteristic of a 'lift and shift' migration. This strategy involves moving the VMs as-is, typically using AWS Server Migration Service (SMS) or AWS Application Migration Service (AWS MGN), to quickly reduce on-premises data center costs without application refactoring.

Exam trap

The trap here is that candidates confuse Rehost (no changes) with Replatform (minimal changes), often selecting Replatform because they think moving to AWS inherently requires some modification, but the exam explicitly defines Rehost as migrating without any application changes.

How to eliminate wrong answers

Option A is wrong because Refactor involves re-architecting the application to be cloud-native (e.g., converting a monolithic app to microservices), which contradicts the requirement of no changes to applications. Option B is wrong because Replatform involves making minimal changes to leverage cloud-managed services (e.g., moving a database to Amazon RDS), which still requires some application modifications, not a pure lift-and-shift. Option D is wrong because Retire means decommissioning applications that are no longer needed, but the question states the company wants to migrate 50 VMs, not eliminate them.

Practice this question →

117

MCQmedium

A startup company is evaluating the benefits of migrating to AWS. The CEO wants to experiment with a new application idea by quickly launching a small server, testing the application for a few days, and then decommissioning it. The company does not want to go through a lengthy procurement process to purchase hardware. Which cloud computing concept does this scenario best demonstrate?

A.Elasticity

B.Agility

C.High availability

D.Pay-as-you-go

AnswerB

Agility is the ability to rapidly provision and decommission resources with minimal effort, enabling fast experimentation and time-to-market. This matches the CEO's need to quickly launch a server for a trial and then shut it down without long procurement cycles.

Why this answer

The scenario describes the ability to rapidly provision a small server, test an application for a few days, and then decommission it without the delay of hardware procurement. This directly demonstrates agility, which in cloud computing refers to the speed and ease with which resources can be deployed, modified, and removed to respond to changing business needs. AWS services like EC2 allow instances to be launched in minutes via the AWS Management Console, CLI, or SDK, and terminated just as quickly, bypassing traditional hardware acquisition cycles.

Exam trap

The trap here is that candidates confuse the rapid provisioning and decommissioning (agility) with the cost model (pay-as-you-go) or the scaling capability (elasticity), but the question specifically emphasizes the speed of setup and teardown without procurement delays, which is the definition of agility.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, not the speed of initial provisioning or decommissioning for a short-term experiment. Option C is wrong because high availability focuses on ensuring applications remain accessible and fault-tolerant across multiple Availability Zones, which is not relevant to quickly launching and decommissioning a single server. Option D is wrong because pay-as-you-go is a pricing model where you pay only for what you use, which is a benefit of the scenario but not the primary concept being demonstrated; the core idea is the rapid provisioning and decommissioning, which is agility.

Practice this question →

118

MCQmedium

A company wants to understand the AWS Well-Architected Framework's sixth pillar added in 2021. Which pillar focuses on minimizing the environmental impact of cloud workloads?

A.Cost Optimization

B.Sustainability

C.Governance

D.Resilience

AnswerB

Sustainability was added as the sixth pillar in 2021, focused on minimizing environmental impacts through higher utilization, managed services, right-sizing, and selecting lower-carbon Regions.

Why this answer

The AWS Well-Architected Framework added a sixth pillar, Sustainability, in 2021. This pillar provides design principles and best practices to minimize the environmental impact of cloud workloads, such as optimizing utilization, reducing energy consumption, and selecting efficient hardware and regions.

Exam trap

The trap here is that candidates confuse the Sustainability pillar with Cost Optimization, assuming reducing costs automatically reduces environmental impact, but the Sustainability pillar specifically targets carbon footprint and energy efficiency, not just financial savings.

How to eliminate wrong answers

Option A is wrong because Cost Optimization focuses on managing costs and eliminating unnecessary spending, not specifically on environmental impact. Option C is wrong because Governance is not a pillar of the AWS Well-Architected Framework; the framework includes pillars like Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. Option D is wrong because Resilience is not a pillar; it is a characteristic often associated with the Reliability pillar, which addresses workload recovery and fault tolerance, not environmental impact.

Practice this question →

119

MCQeasy

Under the AWS Shared Responsibility Model, what is AWS responsible for when a customer uses AWS Lambda?

A.Writing the Lambda function code

B.Managing the underlying OS, runtime, and execution environment

C.Configuring IAM roles and permissions for Lambda functions

D.Encrypting the data processed by the function

AnswerB

For Lambda, AWS manages the entire infrastructure stack including OS, runtime patching, scaling infrastructure, and execution environment — customers only manage their function code.

Why this answer

AWS Lambda is a serverless compute service where AWS manages the underlying infrastructure, including the operating system, runtime environment, and execution environment. Under the Shared Responsibility Model, AWS is responsible for the security of the cloud, which for Lambda includes patching the runtime, managing the hypervisor, and ensuring the execution environment is isolated between customers. The customer is only responsible for the code and configuration they provide.

Exam trap

The trap here is that candidates often confuse 'serverless' with 'no responsibility for anything,' but AWS still manages the underlying runtime and execution environment while the customer remains responsible for code, IAM, and data encryption.

How to eliminate wrong answers

Option A is wrong because writing the Lambda function code is entirely the customer's responsibility under the model, as the customer controls the application logic. Option C is wrong because configuring IAM roles and permissions for Lambda functions is a customer responsibility, as the customer defines access policies for their resources. Option D is wrong because encrypting data processed by the function is a customer responsibility, as the customer must implement encryption (e.g., using AWS KMS or client-side encryption) for data at rest or in transit.

Practice this question →

120

MCQhard

A company is designing a resilient multi-tier web application on AWS. The architect wants to implement the Well-Architected Framework Reliability pillar design principle of 'automatically recover from failure.' Which combination of services implements this most completely?

A.Manual restart procedures documented in a runbook

B.EC2 Auto Scaling + ELB health checks + RDS Multi-AZ

C.AWS CloudTrail + Amazon CloudWatch

D.AWS Config rules with manual remediation

AnswerB

Auto Scaling automatically replaces failed instances, ELB health checks remove unhealthy targets from rotation, and RDS Multi-AZ automatically fails over the database — full automatic recovery without human intervention.

Why this answer

Option B is correct because it combines EC2 Auto Scaling to automatically replace unhealthy instances, ELB health checks to detect failures and route traffic away from them, and RDS Multi-AZ to automatically failover to a standby database in a different Availability Zone. This trio directly implements the 'automatically recover from failure' principle by enabling self-healing at both the compute and database tiers without manual intervention.

Exam trap

The trap here is that candidates often confuse monitoring services (like CloudTrail and CloudWatch) with recovery services, failing to recognize that detection alone does not satisfy the 'automatically recover' principle unless paired with an automated action mechanism such as Auto Scaling or Multi-AZ failover.

How to eliminate wrong answers

Option A is wrong because manual restart procedures documented in a runbook require human action to detect and respond to failures, which violates the 'automatically recover' principle that demands automated, not manual, recovery. Option C is wrong because AWS CloudTrail and Amazon CloudWatch provide logging, monitoring, and alerting capabilities but do not perform any automated recovery actions themselves; they only detect and notify about failures. Option D is wrong because AWS Config rules with manual remediation detect configuration drift but require a human to execute the remediation steps, whereas the principle requires automatic recovery without human intervention.

Practice this question →

121

MCQhard

A company architect is reviewing their architecture for the Operational Excellence pillar of the Well-Architected Framework. Which practice is a core recommendation of this pillar?

A.Encrypt all data at rest using AWS KMS

B.Perform operations as code using infrastructure-as-code and automated runbooks

C.Use Reserved Instances to minimize cost

D.Deploy across multiple Availability Zones

AnswerB

Operational Excellence's 'perform operations as code' means defining infrastructure and procedures in code, version-controlling them, and executing operations through automated pipelines — reducing human error.

Why this answer

The Operational Excellence pillar focuses on running and monitoring systems to deliver business value and continually improve supporting processes and procedures. Performing operations as code—using infrastructure-as-code (e.g., AWS CloudFormation, AWS CDK) and automated runbooks (e.g., AWS Systems Manager Automation)—is a core recommendation because it enables consistent, repeatable, and auditable operations, reducing human error and enabling rapid recovery.

Exam trap

The trap here is that candidates often confuse the pillars—associating automation with Reliability or Security—when the Well-Architected Framework explicitly places 'operations as code' under Operational Excellence.

How to eliminate wrong answers

Option A is wrong because encrypting data at rest with AWS KMS is a recommendation of the Security pillar, not Operational Excellence. Option C is wrong because using Reserved Instances to minimize cost is a recommendation of the Cost Optimization pillar. Option D is wrong because deploying across multiple Availability Zones is a recommendation of the Reliability pillar, specifically for high availability and fault tolerance.

Practice this question →

122

MCQhard

A company wants to improve their application's reliability by ensuring it can handle the failure of a single Availability Zone. According to AWS Well-Architected Framework, what architectural pattern achieves this?

A.Deploy all resources to the largest EC2 instance type available

B.Use Amazon S3 for all data storage

C.Distribute resources across multiple Availability Zones with automatic failover

D.Enable AWS CloudTrail in all regions

AnswerC

Multi-AZ deployment with load balancing and automated failover ensures the application survives the loss of any single AZ — the core reliability pattern in the AWS Well-Architected Framework.

Why this answer

Option C is correct because distributing resources across multiple Availability Zones (AZs) with automatic failover is the core pattern for high availability and fault tolerance as defined by the AWS Well-Architected Framework. By deploying application instances and data in at least two AZs and using services like an Application Load Balancer (ALB) with cross-zone load balancing or Amazon RDS Multi-AZ, the application can automatically redirect traffic to healthy resources if a single AZ fails, ensuring continued operation without manual intervention.

Exam trap

The trap here is that candidates often confuse high availability (multi-AZ) with disaster recovery (multi-Region) or assume that a single service like S3 or CloudTrail can solve application-level reliability, when the question specifically asks for the architectural pattern to handle an AZ failure.

How to eliminate wrong answers

Option A is wrong because deploying all resources to the largest EC2 instance type (e.g., u-24tb1.metal) only provides vertical scaling and does not address Availability Zone failure; a single AZ outage would still take down all instances regardless of size. Option B is wrong because while Amazon S3 is highly durable and stores data across multiple AZs by default, it is a storage service and does not provide the compute or application-level failover pattern needed to handle an AZ failure for the entire application. Option D is wrong because AWS CloudTrail is a governance, compliance, and auditing service that records API calls; enabling it in all regions does not provide any mechanism for application reliability or failover across Availability Zones.

Practice this question →

123

MCQmedium

According to the AWS Well-Architected Framework, what does the Performance Efficiency pillar primarily focus on?

A.Protecting information and systems from unauthorized access

B.Minimizing the cost of running cloud workloads

C.Using computing resources efficiently to meet performance requirements

D.Automating operational tasks to reduce human error

AnswerC

Performance Efficiency focuses on selecting the right resource types, monitoring performance, and making architectural decisions that maintain efficiency as demand evolves.

Why this answer

The Performance Efficiency pillar of the AWS Well-Architected Framework focuses on using computing resources efficiently to meet system requirements and maintain that efficiency as demand changes and technologies evolve. This includes selecting the right resource types and sizes, monitoring performance, and making architectural trade-offs to optimize for speed and throughput.

Exam trap

The trap here is that candidates confuse 'efficiency' with 'cost savings,' but Performance Efficiency is about meeting performance requirements with the right resources, not about minimizing spend, which belongs to the Cost Optimization pillar.

How to eliminate wrong answers

Option A is wrong because protecting information and systems from unauthorized access is the focus of the Security pillar, not Performance Efficiency. Option B is wrong because minimizing the cost of running cloud workloads is the focus of the Cost Optimization pillar, which deals with financial governance and resource waste reduction. Option D is wrong because automating operational tasks to reduce human error is the focus of the Operational Excellence pillar, which covers runbooks, deployments, and incident response.

Practice this question →

124

MCQmedium

A development team needs to provision a new Amazon EC2 instance for a proof-of-concept project. The team has an AWS account with appropriate IAM permissions. One developer logs into the AWS Management Console, selects an Amazon Machine Image (AMI), chooses an instance type, configures security groups, and launches the instance. The entire process takes less than 10 minutes and does not require any interaction with AWS support or IT administrators. Which essential characteristic of cloud computing does this scenario best illustrate?

A.On-demand self-service

B.Resource pooling

C.Measured service

D.Broad network access

AnswerA

Correct. The developer provisions the instance entirely through self-service steps in the AWS Management Console without any human intervention from AWS staff or internal IT, which is the definition of on-demand self-service.

Why this answer

This scenario best illustrates on-demand self-service because the developer was able to provision an EC2 instance entirely through the AWS Management Console without any human interaction with AWS support or IT administrators. The ability to independently configure and launch compute resources—selecting an AMI, instance type, and security groups—within minutes, without requiring manual approval or provisioning, is the defining characteristic of on-demand self-service as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates confuse the speed of provisioning (which is a benefit of on-demand self-service) with resource pooling or measured service, but the question specifically tests the ability to provision resources without human interaction, which is the core of on-demand self-service.

How to eliminate wrong answers

Option B (Resource pooling) is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand; the scenario focuses on the consumer's ability to provision resources independently, not on how the provider shares resources across customers. Option C (Measured service) is wrong because measured service involves metering and billing for resource usage (e.g., per-hour or per-GB charges), which is not demonstrated in the quick provisioning process described. Option D (Broad network access) is wrong because broad network access means resources are accessible over the network via standard mechanisms (e.g., HTTPS, SSH) from a wide range of devices; while the console is accessed over the internet, the core action is self-service provisioning, not network accessibility.

Practice this question →

125

Drag & Dropmedium

Drag and drop the steps to troubleshoot an EC2 instance that is not reachable via SSH in the correct order.

Drag steps to the numbered slots on the right, or tap a step then tap a slot.

Steps

Order

Why this order

Troubleshooting connectivity: security group, NACL, public IP, routing, and system logs.

Practice this question →

126

Matchingmedium

Match each AWS service to its primary category.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts

Matches

Compute

Storage

Database

Networking & Content Delivery

Compute

Why these pairings

These are core AWS services and their categories.

Practice this question →

127

MCQmedium

A company is migrating its on-premises data center to AWS. The Chief Financial Officer (CFO) wants to understand how this migration will change the company's financial structure. Historically, the company purchased servers, networking equipment, and software licenses upfront, with costs depreciating over several years. The CFO notes that the move to AWS will replace these large upfront capital expenditures with smaller, recurring operational expenses based on actual usage. Which essential characteristic of cloud computing enables this shift from capital expenditure (CAPEX) to operational expenditure (OPEX)?

A.Elasticity

B.Measured service

C.High availability

D.Resource pooling

AnswerB

Measured service is the characteristic that enables cloud providers to track resource consumption and bill customers based on actual usage. This consumption-based model turns IT expenses into operational expenditures (OPEX) by eliminating upfront hardware purchases.

Why this answer

Measured service is the cloud characteristic that allows providers to track and bill customers for actual resource usage (e.g., compute hours, storage GB-months, data transfer). This pay-as-you-go model directly replaces the need for large upfront capital purchases (CAPEX) with variable, usage-based operational expenses (OPEX), as the CFO requires. Without measured service, AWS would have no mechanism to meter consumption and charge proportionally, making the financial shift impossible.

Exam trap

The trap here is that candidates confuse elasticity (scaling) with the financial model shift, but elasticity only changes how much you use, not how you pay—measured service is what enables the per-unit billing that turns CAPEX into OPEX.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, which affects operational agility and cost optimization but does not inherently change the financial structure from CAPEX to OPEX—elasticity can exist in both models. Option C is wrong because high availability ensures that applications remain accessible despite failures, typically through redundancy across Availability Zones; it is a reliability characteristic that impacts uptime and design, not the fundamental billing or financial classification of expenses.

Practice this question →

128

MCQmedium

A company's application has components that tightly depend on each other, making it difficult to scale individual components or update one without affecting others. The architects want to refactor to a more resilient architecture. What AWS design principle addresses this?

A.Design for failure by adding redundant instances

B.Implement loose coupling through asynchronous messaging between components

C.Use larger instance types to handle all components on fewer servers

D.Enable AWS Auto Scaling to handle traffic variability

AnswerB

Loose coupling via SQS, SNS, EventBridge, or API contracts allows independent scaling, deployment, and failure isolation — the core pattern for resilient microservices architectures.

Why this answer

Option B is correct because loose coupling through asynchronous messaging (e.g., using Amazon SQS or Amazon SNS) decouples components so that they can scale independently and updates can be made to one component without affecting others. This directly addresses the tight dependency described in the question, where scaling or updating one component impacts the entire application. By introducing message queues or pub/sub patterns, components communicate indirectly, improving resilience and fault isolation.

Exam trap

The trap here is that candidates often confuse high availability (redundancy) with architectural decoupling, assuming that adding more instances of tightly coupled components solves the scaling and update problem, when in fact loose coupling is required to break the dependencies.

How to eliminate wrong answers

Option A is wrong because adding redundant instances (e.g., deploying multiple EC2 instances behind an Auto Scaling group) addresses high availability and fault tolerance at the instance level, but does not solve the architectural problem of tight coupling between components—redundancy alone does not decouple interdependent services. Option C is wrong because using larger instance types (vertical scaling) consolidates components onto fewer servers, which actually increases tight coupling and creates a single point of failure, making the architecture less resilient, not more. Option D is wrong because AWS Auto Scaling handles traffic variability by adjusting capacity, but it does not address the tight coupling between components; scaling individual components independently requires decoupling, which Auto Scaling alone cannot provide.

Practice this question →

129

MCQeasy

A company uses Amazon WorkMail for corporate email. Employees access email through a web browser or mobile app. The company does not manage any servers, email software, or storage infrastructure. Which cloud service model does this represent?

A.Infrastructure as a Service (IaaS)

B.Platform as a Service (PaaS)

C.Software as a Service (SaaS)

D.Hybrid cloud

AnswerC

SaaS is a fully managed application delivered over the internet. Amazon WorkMail is SaaS — AWS manages everything from the servers to the email application software. Customers simply use the service.

Why this answer

Amazon WorkMail is a fully managed email service where users access their email via a web browser or mobile app without managing any underlying servers, email software, or storage infrastructure. This aligns with the Software as a Service (SaaS) model, where the provider delivers the entire application and the consumer only uses the software over the internet.

Exam trap

The trap here is that candidates may confuse 'no server management' with IaaS, thinking that because email is hosted in the cloud it must be IaaS, but the key distinction is that SaaS delivers a complete application without any consumer control over the underlying infrastructure.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) provides virtualized computing resources (e.g., EC2 instances, storage volumes) where the consumer manages the operating system, applications, and middleware, which is not the case here as no servers or storage are managed. Option B is wrong because Platform as a Service (PaaS) provides a runtime environment and development tools for building and deploying applications, but WorkMail is a ready-to-use email application, not a platform for custom development. Option D is wrong because Hybrid cloud refers to a combination of on-premises and cloud infrastructure, but the scenario describes a fully cloud-based email service with no on-premises management.

Practice this question →

130

MCQmedium

A company's development team regularly creates temporary test environments. Each time, they log into the AWS Management Console, select the required Amazon EC2 instance types and storage, and launch the resources without needing to contact AWS support or their IT department. The team also terminates the resources when testing is complete. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.Broad network access

B.On-demand self-service

C.Resource pooling

D.Measured service

AnswerB

On-demand self-service allows users to provision computing resources automatically without requiring human interaction from the cloud provider. The team independently launches and terminates resources through the AWS Management Console, directly demonstrating this characteristic.

Why this answer

The scenario describes the development team provisioning and terminating EC2 instances and storage directly through the AWS Management Console without requiring human intervention from AWS support or their IT department. This is the precise definition of on-demand self-service, one of the five essential characteristics of cloud computing as defined by NIST SP 800-145, where a consumer can unilaterally provision computing capabilities as needed automatically.

Exam trap

The trap here is that candidates may confuse 'broad network access' (access from anywhere via the internet) with the ability to self-provision, but the key differentiator is the lack of human intervention required, not the method of access.

How to eliminate wrong answers

Option A is wrong because broad network access refers to capabilities being available over the network and accessed through standard mechanisms (e.g., HTTPS, SSH) that promote use by heterogeneous client platforms (e.g., mobile phones, laptops), not the ability to provision resources without human interaction. Option C is wrong because resource pooling describes the provider's computing resources being pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; the scenario does not illustrate multi-tenancy or dynamic assignment across customers.

Practice this question →

131

MCQmedium

A company migrates its on-premises applications to AWS. The finance team wants to allocate costs to different departments based on the exact amount of compute, storage, and network resources each department consumes. They also want to set automatic alerts when a department's usage exceeds a predefined budget. Which essential characteristic of cloud computing enables this level of visibility and control over resource consumption?

A.Rapid elasticity

B.On-demand self-service

C.Measured service

D.Resource pooling

AnswerC

Measured service means that cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction. AWS meters consumption of compute, storage, and network resources, providing detailed reports and enabling cost allocation, budgets, and alerts. This directly supports the finance team's requirements.

Why this answer

Measured service is the correct answer because it refers to the cloud provider's ability to meter and report resource usage (compute hours, storage GB, data transfer) at a granular level. This metering data enables the finance team to allocate exact costs per department and set automated budget alerts via services like AWS Budgets or Cost Explorer, directly supporting the requirement for visibility and control over consumption.

Exam trap

The trap here is that candidates confuse 'on-demand self-service' (the ability to provision resources) with 'measured service' (the ability to track and bill for that usage), but the question specifically asks about visibility and control over consumption, not provisioning.

How to eliminate wrong answers

Option A is wrong because rapid elasticity describes the ability to automatically scale resources up or down based on demand, not the metering or cost allocation of those resources. Option B is wrong because on-demand self-service allows users to provision resources without human interaction, but it does not inherently provide the usage metering, cost tracking, or alerting capabilities needed for departmental cost allocation.

Practice this question →

132

MCQmedium

A gaming company wants to deploy its multiplayer game to players in North America, Europe, and Asia. The company needs to ensure that players in all three regions experience low latency when connecting to game servers, and the game servers must be located as close as possible to the players. The company chooses AWS to host the game servers. Which benefit of cloud computing does this scenario best illustrate?

A.Rapid elasticity – because AWS can automatically scale the number of game servers based on player demand.

B.Global reach – because AWS has regions around the world, allowing the company to deploy game servers geographically close to players.

C.Pay-as-you-go – because the company only pays for game server compute hours used.

D.Resource pooling – because multiple players share the same underlying server resources.

AnswerB

Correct. Global reach (or global infrastructure) is a key benefit of cloud computing. AWS operates Regions across the globe, enabling customers to deploy applications near their users for low-latency access. This matches the gaming company's requirement to serve players in North America, Europe, and Asia with minimal latency.

Why this answer

This scenario best illustrates global reach because AWS operates multiple geographic regions worldwide, enabling the gaming company to deploy game servers in North America, Europe, and Asia. By placing infrastructure close to players, the company minimizes network latency and improves the real-time multiplayer experience. This is a core benefit of cloud computing that on-premises solutions cannot easily replicate without significant investment.

Exam trap

The trap here is that candidates may confuse rapid elasticity with global reach, since both involve scaling, but the question's emphasis on 'close to players' directly points to geographic distribution, not dynamic capacity adjustment.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to automatically scaling resources up or down based on demand, which is not the primary focus here—the question emphasizes geographic proximity, not scaling. Option C is wrong because pay-as-you-go describes the consumption-based pricing model, but the scenario specifically highlights low latency through regional deployment, not cost savings. Option D is wrong because resource pooling involves multi-tenancy and shared infrastructure, which is unrelated to the goal of placing servers close to players for latency reduction.

Practice this question →

133

MCQhard

A company is evaluating the AWS Sustainability pillar in the Well-Architected Framework. Which action aligns with AWS cloud sustainability best practices?

A.Provisioning maximum instance sizes to ensure peak performance at all times

B.Running workloads 24/7 even when not needed to maintain warm state

C.Right-sizing instances and using managed services to maximize resource utilization

D.Replicating all data to multiple regions for maximum redundancy

AnswerC

Right-sizing reduces wasted capacity and energy, while managed services share infrastructure across many customers at higher utilization rates than dedicated servers — both reduce environmental impact.

Why this answer

Option C is correct because right-sizing instances and using managed services directly aligns with the AWS Sustainability pillar, which focuses on minimizing the environmental impact of cloud workloads. By matching instance capacity to actual demand and leveraging services like AWS Lambda or Amazon RDS, you reduce wasted compute cycles and energy consumption, improving resource utilization and lowering carbon footprint.

Exam trap

The trap here is that candidates often confuse the Sustainability pillar with the Reliability pillar, assuming that maximizing redundancy or always-on resources is always beneficial, but the exam specifically tests that sustainability prioritizes minimizing resource consumption and waste.

How to eliminate wrong answers

Option A is wrong because provisioning maximum instance sizes for peak performance at all times leads to over-provisioning, which wastes energy and resources, contradicting the sustainability goal of minimizing environmental impact. Option B is wrong because running workloads 24/7 when not needed keeps idle resources consuming power and generating heat, increasing carbon emissions without business value. Option D is wrong because replicating all data to multiple regions for maximum redundancy introduces unnecessary data transfer and storage costs, increasing energy use and carbon footprint, whereas sustainability best practices recommend replicating only critical data based on business requirements.

Practice this question →

134

MCQmedium

Which AWS service provides a managed workflow for human review tasks, allowing machine learning models to request human oversight for low-confidence predictions?

A.Amazon SageMaker Ground Truth

B.Amazon Augmented AI (A2I)

C.Amazon Mechanical Turk

D.Amazon Rekognition Custom Labels

AnswerB

A2I provides human review workflows for ML predictions, routing low-confidence or high-risk decisions to human reviewers with configurable thresholds and reviewer pools.

Why this answer

Amazon Augmented AI (A2I) is the correct service because it provides a managed workflow for human review of machine learning predictions, specifically when models have low confidence. It integrates with services like Amazon Rekognition and Amazon Textract to automatically route low-confidence predictions to human reviewers, enabling a human-in-the-loop (HITL) process without custom infrastructure.

Exam trap

The trap here is that candidates confuse Amazon Augmented AI (A2I) with Amazon SageMaker Ground Truth, because both involve human tasks, but Ground Truth is for labeling training data while A2I is for reviewing live predictions.

How to eliminate wrong answers

Option A is wrong because Amazon SageMaker Ground Truth is a data labeling service for creating training datasets, not a workflow for reviewing low-confidence predictions from deployed models. Option C is wrong because Amazon Mechanical Turk is a crowdsourcing marketplace for human tasks, but it lacks the managed integration with ML models and confidence thresholds that A2I provides for automated human review workflows. Option D is wrong because Amazon Rekognition Custom Labels is a service for training custom image analysis models, not a human review workflow for low-confidence predictions.

Practice this question →

135

MCQmedium

A company runs a nightly batch processing job on a single on-premises server. The job takes 4 hours to complete, and if the server fails during processing, the job must start over from the beginning. The company is migrating this workload to AWS. The solutions architect proposes running the job across multiple Amazon EC2 instances that process different chunks of data simultaneously. The architect also plans to configure the system so that if any single instance fails, its chunk is automatically reprocessed by another instance, ensuring the overall job still completes. Which benefit of cloud computing does this architecture primarily demonstrate?

A.Elasticity

B.High availability

C.Horizontal scaling

D.Global reach

AnswerC

Correct. Horizontal scaling (scaling out) means adding more instances to share the workload. The architect splits the job into chunks and runs them on multiple EC2 instances, improving both performance (parallelism) and fault tolerance (chunks are reprocessed if an instance fails).

Why this answer

Option C is correct because the architecture distributes the workload across multiple EC2 instances, each processing a separate chunk of data. This is the definition of horizontal scaling (scaling out). If an instance fails, its chunk is automatically reprocessed by another instance, which demonstrates the fault tolerance and parallelism that horizontal scaling enables, not just adding more capacity.

Exam trap

The trap here is that candidates confuse fault tolerance (handling instance failure) with high availability, but the question emphasizes distributing work across multiple instances to complete the job faster and handle failures, which is the core benefit of horizontal scaling, not just keeping the system running.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, such as adding instances during peak load and removing them when idle. The scenario describes a fixed nightly job with a fixed number of instances, not dynamic scaling. Option B is wrong because high availability focuses on ensuring the system remains operational and accessible despite failures, typically through redundancy across Availability Zones.

While the architecture does handle instance failure, the primary benefit demonstrated is distributing work across multiple instances (scaling out), not maintaining uptime of the overall system. Option D is wrong because global reach refers to deploying resources in multiple geographic regions to reduce latency or comply with data residency requirements. The scenario involves a single batch job on EC2 instances, with no mention of multi-region deployment or latency optimization.

Practice this question →

136

MCQmedium

A company develops a mobile application that allows employees to upload sales reports to an Amazon S3 bucket. The application must work reliably from any location, including from corporate offices, remote home offices, and international travel locations. The solution uses standard HTTPS requests over the internet. Which essential characteristic of cloud computing does this scenario best illustrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerB

Broad network access means that cloud resources are available over the network and can be accessed by standard mechanisms (such as HTTPS) from a wide range of devices, including mobile phones, laptops, and workstations. This allows users to upload data from corporate offices, home offices, and while traveling.

Why this answer

Broad network access is the correct answer because the scenario describes a mobile application that must work reliably from any location—corporate offices, remote home offices, and international travel locations—using standard HTTPS requests over the internet. This directly aligns with the NIST definition of broad network access, which states that capabilities are available over the network and accessed through standard mechanisms (e.g., HTTPS) by heterogeneous client platforms (such as mobile phones, laptops, and tablets). The ability to access the S3 bucket from diverse geographic locations via the public internet is the core characteristic being illustrated.

Exam trap

The trap here is that candidates often confuse 'broad network access' with 'rapid elasticity' because both involve network-based access, but the key distinction is that broad network access is about the ability to access resources from anywhere using standard protocols, while rapid elasticity is about automatic scaling of resources to meet demand.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources (like S3 buckets or EC2 instances) automatically without requiring human interaction with the service provider, which is not the focus of the scenario—the scenario emphasizes access from any location, not self-provisioning. Option C is wrong because resource pooling describes how the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; the scenario does not illustrate multi-tenancy or resource sharing among customers. Option D is wrong because rapid elasticity refers to the ability to quickly scale resources up or down in response to demand, often automatically; while S3 is elastic, the scenario highlights reliable access from any location, not scaling behavior.

Practice this question →

137

MCQeasy

What is the primary purpose of an AWS Virtual Private Cloud (VPC)?

A.To provide a CDN for distributing content globally

B.To create a logically isolated virtual network in the AWS Cloud

C.To manage user authentication and access control

D.To monitor AWS resource usage and performance metrics

AnswerB

VPC provides a private, isolated virtual network where customers control IP addressing, subnets, routing, and security — a fundamental networking layer for all AWS deployments.

Why this answer

The primary purpose of an AWS Virtual Private Cloud (VPC) is to create a logically isolated virtual network within the AWS Cloud, where you can launch AWS resources in a defined virtual network that closely resembles a traditional on-premises network. This isolation is achieved through IP address ranges (CIDR blocks), subnets, route tables, and network gateways, giving you full control over your virtual networking environment, including selection of your own IP address range, creation of subnets, and configuration of route tables and network gateways.

Exam trap

The trap here is that candidates often confuse the VPC's role of providing network isolation with other AWS services like CloudFront (CDN), IAM (access control), or CloudWatch (monitoring), leading them to select options that describe those services instead of the core networking purpose of a VPC.

How to eliminate wrong answers

Option A is wrong because a CDN (Content Delivery Network) is provided by AWS CloudFront, not by a VPC; a VPC is a networking construct, not a content distribution service. Option C is wrong because user authentication and access control are managed by AWS Identity and Access Management (IAM), not by a VPC; VPCs handle network-level isolation and connectivity, not identity management. Option D is wrong because monitoring AWS resource usage and performance metrics is the function of Amazon CloudWatch, not a VPC; VPCs provide network isolation and control, not monitoring or metrics collection.

Practice this question →

138

MCQmedium

A finance team works with architects to eliminate unused EC2 instances, right-size over-provisioned resources, replace On-Demand instances with Reserved Instances for stable workloads, and adopt managed services to reduce operational overhead. Which AWS Well-Architected Framework pillar guides these activities?

A.Operational Excellence

B.Reliability

C.Cost Optimisation

D.Security

AnswerC

The Cost Optimisation pillar covers eliminating unused resources, right-sizing instances, selecting appropriate pricing models (Reserved vs On-Demand), and using managed services to reduce total cost.

Why this answer

Option C is correct because the Cost Optimization pillar of the AWS Well-Architected Framework focuses on eliminating unused resources, right-sizing over-provisioned instances, using Reserved Instances for predictable workloads, and adopting managed services to reduce operational overhead. These activities directly target cost efficiency by aligning resource usage with demand and avoiding waste.

Exam trap

The trap here is that candidates may confuse Cost Optimization with Operational Excellence, as both involve improving efficiency, but Cost Optimization specifically targets financial savings through resource and pricing optimization, not process automation or reliability improvements.

How to eliminate wrong answers

Option A is wrong because Operational Excellence focuses on automating operations, monitoring, and improving processes, not specifically on cost reduction activities like eliminating unused instances or right-sizing. Option B is wrong because Reliability focuses on ensuring workloads recover from failures and meet availability requirements, not on cost-saving measures like Reserved Instances or managed services adoption. Option D is wrong because Security focuses on protecting data and systems through identity, access controls, and encryption, not on cost optimization activities.

Practice this question →

139

MCQmedium

Which AWS service provides managed, automated workflows for coordinating migration tasks such as tracking migration status, grouping servers into migration waves, and coordinating cutover?

A.AWS Application Discovery Service

B.AWS Migration Hub

C.AWS Control Tower

D.AWS Organizations

AnswerB

Migration Hub provides centralized tracking of migration progress across multiple tools and migration waves, grouping applications and monitoring each stage from discovery through cutover.

Why this answer

AWS Migration Hub is the correct service because it provides a single location to track the progress of application migrations across multiple AWS and partner solutions. It offers managed, automated workflows for grouping servers into migration waves, tracking migration status, and coordinating cutover activities, which directly matches the question's requirements.

Exam trap

The trap here is that candidates often confuse AWS Migration Hub with AWS Application Discovery Service, thinking that discovery and migration tracking are the same service, but Discovery Service only handles the initial data collection phase, not the ongoing workflow coordination.

How to eliminate wrong answers

Option A is wrong because AWS Application Discovery Service is used to gather information about on-premises data centers (server specifications, dependencies) to plan migrations, but it does not provide the automated workflows for tracking status, grouping into waves, or coordinating cutover. Option C is wrong because AWS Control Tower is a service for setting up and governing a secure, multi-account AWS environment using pre-built blueprints and guardrails, not for managing migration task workflows. Option D is wrong because AWS Organizations is a service for centrally managing billing, access, compliance, and security across multiple AWS accounts, and it does not include migration tracking or wave coordination capabilities.

Practice this question →

140

MCQmedium

A company is migrating an on-premises application to AWS. The application will run on Amazon EC2 instances and use an Amazon RDS for MySQL database. The security team needs to understand which security controls remain the company's responsibility after the migration. Under the AWS Shared Responsibility Model, which of the following is the customer's responsibility?

A.Patching the MySQL database engine for the Amazon RDS instance.

B.Patching the guest operating system on the Amazon EC2 instances.

C.Providing physical security at the AWS data center facilities.

D.Replacing failed network switches in the AWS global network.

AnswerB

Correct. The customer is responsible for the security of the guest OS on EC2 instances, including applying patches and updates. AWS manages the hypervisor and physical infrastructure.

Why this answer

Under the AWS Shared Responsibility Model, the customer is responsible for patching the guest operating system on Amazon EC2 instances because EC2 is an Infrastructure as a Service (IaaS) offering where AWS manages the hypervisor and physical infrastructure, but the customer has full control over the OS, applications, and configurations. In contrast, for Amazon RDS, AWS handles patching of the database engine (e.g., MySQL) and the underlying OS, making option A AWS's responsibility. Physical security at AWS data centers is always AWS's responsibility, not the customer's.

Exam trap

The trap here is that candidates often confuse the responsibility for patching in managed services like RDS versus unmanaged services like EC2, assuming the customer must patch everything in RDS, when in fact AWS handles the database engine and OS patching for RDS.

How to eliminate wrong answers

Option A is wrong because Amazon RDS is a managed service where AWS automatically applies patches to the MySQL database engine and the underlying OS, so the customer does not need to patch the database engine themselves. Option C is wrong because physical security at AWS data center facilities is exclusively AWS's responsibility under the Shared Responsibility Model, covering aspects like access controls, surveillance, and environmental safeguards.

Practice this question →

141

MCQmedium

Which statement correctly describes the difference between horizontal scaling and vertical scaling in cloud computing?

A.Horizontal scaling means increasing instance size; vertical scaling means adding more instances

B.Horizontal scaling adds more instances; vertical scaling increases the size of existing instances

C.Both scaling types produce identical results and are interchangeable in cloud architectures

D.Vertical scaling is always preferred because it reduces the number of instances to manage

AnswerB

Horizontal scaling (out/in) adds or removes instances from a fleet. Vertical scaling (up/down) resizes a single instance to be more or less powerful — requires a restart for EC2 instances.

Why this answer

Option B is correct because horizontal scaling (scaling out) involves adding more instances of a resource, such as EC2 instances, to distribute the load, while vertical scaling (scaling up) increases the size or capacity of an existing instance, for example by moving from a t2.micro to a t2.large. This distinction is fundamental in AWS cloud architectures, where horizontal scaling improves fault tolerance and availability, and vertical scaling is limited by the maximum instance size.

Exam trap

The trap here is that candidates often confuse the terms 'horizontal' and 'vertical' scaling, mistakenly thinking horizontal means increasing size (like a horizontal bar getting wider) rather than adding more units, leading them to select Option A.

How to eliminate wrong answers

Option A is wrong because it reverses the definitions: horizontal scaling adds more instances, not increases instance size, and vertical scaling increases instance size, not adds more instances. Option C is wrong because the two scaling types produce different results: horizontal scaling improves redundancy and distributes load across multiple instances, while vertical scaling increases the capacity of a single instance but creates a single point of failure; they are not interchangeable in all architectures. Option D is wrong because vertical scaling is not always preferred; it can lead to downtime during resizing and is limited by hardware constraints, whereas horizontal scaling offers better elasticity and fault tolerance, making it the preferred approach for many cloud-native applications.

Practice this question →

142

MCQeasy

A company has migrated all of its workloads to AWS and has decommissioned all of its on-premises data centres. All compute, storage, databases, and networking are now managed in AWS. Which cloud deployment model describes this architecture?

A.Hybrid cloud

B.Private cloud

C.Multi-cloud

D.Public cloud

AnswerD

Public cloud means all resources are owned by the cloud provider and shared with many customers. A company running entirely on AWS with no on-premises infrastructure is operating fully in the public cloud.

Why this answer

Option D is correct because the company has migrated all workloads to AWS and decommissioned all on-premises data centers, meaning all infrastructure is hosted entirely on AWS's shared infrastructure. This is the definition of a public cloud deployment model, where resources are owned and operated by a third-party cloud provider (AWS) and delivered over the internet to multiple tenants. No private or on-premises components remain, so the architecture is purely public cloud.

Exam trap

The trap here is that candidates confuse 'public cloud' with 'multi-cloud' or 'hybrid cloud' because they think using AWS alone implies a private cloud, but AWS is a public cloud provider by definition, and the absence of on-premises infrastructure eliminates hybrid or multi-cloud models.

How to eliminate wrong answers

Option A is wrong because a hybrid cloud requires a mix of on-premises (private) and public cloud resources connected via a network (e.g., VPN or Direct Connect), but the company has decommissioned all on-premises data centers. Option B is wrong because a private cloud involves dedicated infrastructure for a single organization, either on-premises or hosted, but AWS's infrastructure is multi-tenant and shared, not dedicated solely to this company. Option C is wrong because multi-cloud involves using multiple public cloud providers (e.g., AWS and Azure), but the company uses only AWS for all workloads.

Practice this question →

143

MCQmedium

A company deploys their web application across two Availability Zones using an Application Load Balancer. If one AZ experiences an outage, traffic is automatically routed to the other AZ and the application continues to function. Which cloud benefit does this demonstrate?

A.Economies of scale

B.On-demand self-service

C.High availability and fault tolerance

D.Rapid elasticity

AnswerC

Deploying across multiple AZs with automatic load balancing failover provides high availability — the system continues to function when one AZ fails. Cloud infrastructure makes this achievable without expensive duplicate on-premises data centres.

Why this answer

This scenario demonstrates high availability and fault tolerance because the application is deployed across two Availability Zones with an Application Load Balancer (ALB) distributing traffic. If one AZ fails, the ALB automatically reroutes traffic to the healthy AZ, ensuring continuous operation. This design eliminates a single point of failure and maintains service availability, which is the core of fault tolerance in AWS.

Exam trap

The trap here is that candidates confuse high availability/fault tolerance with rapid elasticity, because both involve automatic responses to changing conditions, but elasticity handles scaling capacity while fault tolerance handles failure recovery.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost advantages gained from large-scale operations (e.g., AWS passing on lower per-unit costs to customers), not to traffic rerouting during an AZ outage. Option B is wrong because on-demand self-service means users can provision and configure resources without human interaction (e.g., launching an EC2 instance via the AWS Management Console), not automatic failover between AZs. Option D is wrong because rapid elasticity is the ability to scale resources up or down automatically based on demand (e.g., using Auto Scaling groups to add EC2 instances during traffic spikes), not the automatic rerouting of traffic to a healthy AZ during an outage.

Practice this question →

144

MCQmedium

A company based in Germany needs to store and process customer data that, by law, must remain within the European Union (EU). The company plans to use AWS services. Which AWS Global Infrastructure element is the MOST important for the company to evaluate when choosing where to deploy its resources?

A.Availability Zones

B.Edge Locations

C.AWS Regions

D.Local Zones

AnswerC

AWS Regions are distinct geographic areas that are completely isolated from each other. Choosing a Region within the EU (e.g., eu-central-1 in Frankfurt) ensures that the customer's data remains in the EU, satisfying data residency laws. This is the foundational decision before considering other infrastructure components.

Why this answer

AWS Regions are geographically isolated areas that contain multiple Availability Zones. Since the company must ensure customer data remains within the EU by law, choosing the correct AWS Region (e.g., eu-central-1 in Frankfurt) is the primary mechanism to guarantee data residency. Only by deploying resources in an EU-based Region can the company meet legal data sovereignty requirements.

Exam trap

The trap here is that candidates confuse Availability Zones with geographic regions, thinking that choosing a specific AZ ensures data stays in a country, when in fact AZs are within a single Region and do not provide cross-border data sovereignty guarantees.

How to eliminate wrong answers

Option A is wrong because Availability Zones are physically separate data centers within a single AWS Region; they do not provide data residency control across national borders. Option B is wrong because Edge Locations are content delivery endpoints for CloudFront and do not offer compute or storage services for primary data processing; they cannot be used to enforce data residency requirements.

Practice this question →

145

MCQeasy

A company used to spend $2 million upfront purchasing servers and building a data centre before launching a new product. With AWS, they provision resources as needed and pay monthly based on actual usage. Which cloud benefit does this represent?

A.Stop guessing about capacity

B.Benefit from economies of scale

C.Trade capital expense for variable expense

D.Increase speed and agility

AnswerC

Cloud computing replaces large upfront hardware investments (capital expenditure) with pay-as-you-go operating expense. This reduces financial risk, improves cash flow, and eliminates idle sunk-cost capacity.

Why this answer

This scenario describes shifting from a large upfront capital expenditure (CapEx) on servers and data centers to a variable operational expenditure (OpEx) based on actual usage. AWS's pay-as-you-go model directly enables this trade, allowing the company to align costs with consumption rather than paying for idle capacity. This is the core benefit of trading capital expense for variable expense.

Exam trap

The trap here is that candidates confuse the financial benefit of 'trading capital expense for variable expense' with the operational benefit of 'stop guessing about capacity,' as both involve avoiding over-provisioning, but the question specifically focuses on the payment model shift.

How to eliminate wrong answers

Option A is wrong because 'Stop guessing about capacity' refers to eliminating the need to over-provision or under-provision infrastructure, not the financial shift from upfront to usage-based spending. Option B is wrong because 'Benefit from economies of scale' describes how AWS's massive purchasing power lowers per-unit costs for customers, not the change in payment model from CapEx to OpEx. Option D is wrong because 'Increase speed and agility' relates to rapidly provisioning resources via APIs and automation, not the financial restructuring of costs.

Practice this question →

146

MCQmedium

A startup is building a photo-sharing application on AWS. The startup expects to store billions of photos over time. The CEO is surprised that the per-GB price for Amazon S3 storage is the same for the startup as it is for a multinational corporation with petabytes of data. Which characteristic of cloud computing does this pricing model best demonstrate?

A.Elasticity

B.Economies of scale

C.High availability

D.Global reach

AnswerB

Correct. AWS benefits from massive aggregation of customer usage, which lowers infrastructure and operational costs. These cost savings are reflected in simple, low prices that apply equally to all customers, regardless of their individual size.

Why this answer

The pricing model where the per-GB cost for Amazon S3 is the same for a small startup as for a large enterprise demonstrates economies of scale. AWS aggregates demand from millions of customers, allowing it to negotiate lower prices for hardware, power, and bandwidth, then passes those savings on to all customers equally. This means the startup benefits from the same low unit cost as a multinational corporation, without needing to invest in its own infrastructure.

Exam trap

The trap here is that candidates confuse 'economies of scale' with 'elasticity,' mistakenly thinking that the ability to scale storage up or down explains why the price is the same for all customers, when in fact elasticity is about dynamic resource adjustment, not uniform pricing.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand, not to pricing equality across customers of different sizes. Option C is wrong because high availability ensures that services remain accessible despite failures, typically through redundancy across Availability Zones, and has no direct relationship to uniform per-GB pricing. Option D is wrong because global reach describes the ability to deploy resources in multiple geographic regions worldwide, which affects latency and compliance, not the per-unit cost structure of storage.

Practice this question →

147

MCQmedium

What is the purpose of an AWS Region when designing a global cloud architecture?

A.To provide a single physical location for all AWS resources worldwide

B.To define geographic boundaries for deploying resources, meeting compliance requirements, and minimizing end-user latency

C.To automatically replicate all data and compute resources across the globe

D.To limit the availability of AWS services to specific enterprise customers

AnswerB

Regions enable data residency compliance (keeping data in specific countries), low-latency access for users in specific geographies, and fault isolation from disasters affecting other regions.

Why this answer

An AWS Region is a distinct geographic area that contains multiple, isolated Availability Zones. Its purpose is to allow customers to deploy resources close to their end users to minimize latency, and to meet data residency and compliance requirements by keeping data within specific geographic boundaries. Each Region operates independently, ensuring fault isolation and regulatory adherence.

Exam trap

The trap here is that candidates often confuse an AWS Region with a single data center or Availability Zone, or mistakenly believe that AWS automatically replicates data across Regions for high availability, when in fact cross-Region replication is opt-in and incurs additional costs.

How to eliminate wrong answers

Option A is wrong because an AWS Region is not a single physical location; it consists of multiple, physically separate Availability Zones within a geographic area, and AWS has many Regions worldwide. Option C is wrong because AWS does not automatically replicate data or compute resources across Regions; cross-Region replication must be explicitly configured by the customer using services like S3 Cross-Region Replication or RDS cross-Region read replicas. Option D is wrong because AWS Regions are available to all AWS customers, not limited to specific enterprise customers, though some services may have regional availability or require special requests for certain Regions.

Practice this question →

148

MCQmedium

A company uses a continuous integration and continuous deployment (CI/CD) pipeline to deploy applications on AWS. The development teams frequently create feature branches in the code repository. The company wants to automatically provision a complete, isolated environment (including compute, storage, and networking) for each new feature branch, with no manual intervention. The environment must be ready within minutes of the branch creation. Which characteristic of cloud computing does this requirement primarily demonstrate?

A.On-demand self-service

B.Rapid elasticity

C.High availability

D.Measured service

AnswerA

Correct. On-demand self-service allows users to provision computing resources automatically without requiring human interaction with the service provider. In this scenario, the CI/CD pipeline automatically provisions the environment without manual intervention, demonstrating this characteristic.

Why this answer

Option A is correct because the requirement to automatically provision a complete, isolated environment for each new feature branch without manual intervention directly demonstrates the on-demand self-service characteristic of cloud computing. This characteristic allows users to provision computing resources automatically as needed, without requiring human interaction with service providers. In this scenario, the CI/CD pipeline triggers the creation of compute, storage, and networking resources via AWS APIs (e.g., CloudFormation, AWS CDK, or Terraform) the moment a branch is created, fulfilling the 'no manual intervention' and 'ready within minutes' conditions.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with 'automated provisioning' because both involve speed, but elasticity is about scaling existing resources in response to load, not creating new isolated environments from scratch.

How to eliminate wrong answers

Option B (Rapid elasticity) is wrong because rapid elasticity refers to the ability to scale resources up or down quickly in response to demand, not to the automated provisioning of isolated environments per feature branch. Option C (High availability) is wrong because high availability focuses on ensuring systems remain operational and accessible despite failures, typically through redundancy across multiple Availability Zones, which is unrelated to the automated creation of per-branch environments.

Practice this question →

149

MCQmedium

A company runs a web application on Amazon EC2 instances behind an Application Load Balancer. The application experiences unpredictable traffic patterns, with sudden spikes during promotional events and low traffic at other times. The company configures an Auto Scaling group to automatically add EC2 instances when CPU utilization exceeds 70% and remove instances when utilization drops below 30%. The system handles the spike without any manual intervention and reduces capacity when demand decreases. Which fundamental characteristic of cloud computing does this scenario best illustrate?

A.On-demand self-service

B.Broad network access

C.Resource pooling

D.Rapid elasticity

AnswerD

Rapid elasticity is the ability to quickly and automatically scale computing resources up or down to match demand. The Auto Scaling configuration that adds and removes EC2 instances based on CPU utilization directly demonstrates this cloud characteristic.

Why this answer

The scenario describes the Auto Scaling group automatically adding EC2 instances during traffic spikes and removing them when demand drops, which directly demonstrates rapid elasticity—the ability to scale computing resources up and down quickly and automatically in response to demand. This is a core characteristic of cloud computing defined by the National Institute of Standards and Technology (NIST), where resources appear unlimited and can be provisioned in any quantity at any time.

Exam trap

AWS often tests the distinction between rapid elasticity and resource pooling, where candidates mistakenly choose resource pooling because they confuse the dynamic assignment of resources (pooling) with the automatic scaling of capacity (elasticity).

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user provisioning computing capabilities (e.g., launching an EC2 instance) without requiring human interaction with the cloud provider, not the automatic scaling of resources based on load. Option B is wrong because broad network access describes capabilities being available over the network and accessed through standard mechanisms (e.g., HTTP/HTTPS, SSH) by heterogeneous client platforms, not the dynamic adjustment of capacity. Option C is wrong because resource pooling means the provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; this scenario focuses on scaling for a single customer's workload, not multi-tenant resource sharing.

Practice this question →

150

MCQmedium

A development team needs to create a temporary Amazon RDS database for testing a new feature. The team uses the AWS Management Console to launch a db.t3.micro MySQL instance, configures the security group, and connects the application within minutes. When the testing is complete, they terminate the instance without any interaction with AWS support or IT administrators. This ability to provision and manage resources entirely through self-service interfaces best describes which essential characteristic of cloud computing?

A.On-demand self-service

B.Resource pooling

C.Rapid elasticity

D.Measured service

AnswerA

Correct. On-demand self-service describes the ability of a user to provision and manage cloud resources (like an RDS database) through a web console, API, or CLI without requiring human interaction with the cloud provider. The team independently launched and terminated the database instance, demonstrating this characteristic.

Why this answer

Option A is correct because the scenario describes the development team provisioning and terminating an RDS instance entirely through the AWS Management Console without requiring any human interaction with AWS support or IT administrators. This aligns with the NIST definition of on-demand self-service, where a consumer can unilaterally provision computing capabilities as needed automatically without requiring human interaction with each service provider.

Exam trap

The trap here is that candidates often confuse 'rapid elasticity' with the ability to quickly create and delete resources, but rapid elasticity specifically refers to automatic scaling in response to demand, not manual provisioning and termination.

How to eliminate wrong answers

Option B (Resource pooling) is wrong because resource pooling refers to the provider's computing resources being pooled to serve multiple consumers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand; the scenario does not describe multi-tenancy or location independence. Option C (Rapid elasticity) is wrong because rapid elasticity involves the ability to quickly scale resources up or down, often automatically, in response to demand; the scenario only shows provisioning and terminating a single instance, not scaling. Option D (Measured service) is wrong because measured service refers to cloud systems automatically controlling and optimizing resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service; the scenario does not mention monitoring, billing, or metering of resource usage.

Practice this question →