Courseiva

CCNA Cloud Concepts Questions

75 of 238 questions · Page 1/4 · Cloud Concepts · Answers revealed

Practice these questionsDomain overviewAll questions
1
MCQmedium

A company is migrating a large enterprise workload to AWS. They want to understand all the migration strategies available. Which framework categorizes cloud migration strategies as the '7 Rs'?

A.AWS Well-Architected Framework pillars
B.AWS Cloud Adoption Framework perspectives
C.AWS Migration Strategy 7 Rs
D.AWS Service Control Policy levels
AnswerC

The 7 Rs (Retire, Retain, Rehost, Replatform, Repurchase, Refactor, Relocate) provide a structured way to categorize migration strategies for each application in an enterprise portfolio.

Why this answer

Option C is correct because the '7 Rs' (Retire, Retain, Rehost, Replatform, Repurchase, Refactor, Relocate) is a specific set of migration strategies defined by AWS to categorize how workloads can be moved to the cloud. This framework is directly referenced in AWS documentation and training as the 'AWS Migration Strategy 7 Rs' and is the standard taxonomy for discussing migration approaches.

Exam trap

The trap here is that candidates confuse the '7 Rs' with the AWS Well-Architected Framework pillars or the AWS CAF perspectives, because all three are numbered frameworks used in AWS cloud adoption discussions, but only the 7 Rs specifically categorize migration strategies.

How to eliminate wrong answers

Option A is wrong because the AWS Well-Architected Framework pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability) focus on designing and operating reliable, secure, efficient, and cost-effective systems in the cloud, not on categorizing migration strategies. Option B is wrong because the AWS Cloud Adoption Framework (AWS CAF) perspectives (Business, People, Governance, Platform, Security, Operations) provide guidance on organizational capabilities and processes for cloud adoption, not a taxonomy of migration strategies. Option D is wrong because AWS Service Control Policy (SCP) levels refer to the hierarchical application of permission boundaries in AWS Organizations (e.g., root, OU, account level), and have no relation to migration strategy categorization.

Practice this question →
2
MCQmedium

A company runs a monthly data processing job that requires 100 Amazon EC2 instances to complete within 4 hours. The job is not needed at any other time. The company previously ran this job on its on-premises servers, which required maintaining enough capacity to handle the peak load year-round, leading to low average utilization. The company has now migrated the job to AWS. Each month, the company automatically provisions the 100 instances, runs the job, and then terminates the instances. Which essential characteristic of cloud computing does this scenario best illustrate?

A.Resource pooling
B.Measured service
C.On-demand self-service
D.Rapid elasticity
AnswerD

Rapid elasticity is the ability to quickly and automatically scale resources up and down in response to demand. By provisioning 100 instances only when needed and terminating them after use, the company avoids over-provisioning and pays only for what it uses, directly illustrating this essential characteristic.

Why this answer

This scenario best illustrates rapid elasticity because the company provisions 100 EC2 instances only when needed for the monthly job, scaling up from zero to 100 instances in minutes and then scaling back down to zero after the job completes. Rapid elasticity allows cloud resources to be quickly scaled out (increased) and scaled in (decreased) to match demand, eliminating the need to maintain idle capacity for peak loads.

Exam trap

The trap here is that candidates often confuse 'on-demand self-service' (the ability to provision resources without manual approval) with 'rapid elasticity' (the ability to quickly scale resources up and down to match fluctuating demand), but the key clue in the question is the dynamic scaling from zero to 100 instances and back, which directly tests the elasticity concept.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's multi-tenant model where computing resources are pooled to serve multiple customers, not the customer's ability to scale resources up and down on demand. Option B is wrong because measured service involves metering and billing for resource usage (e.g., per hour or per GB), which is a characteristic of cloud computing but not the primary focus of this scenario. Option C is wrong because on-demand self-service allows users to provision resources without human interaction, which is true here, but the key differentiator is the ability to rapidly scale from zero to 100 instances and back, which is the essence of elasticity, not just self-service provisioning.

Practice this question →
3
MCQmedium

A cloud provider uses shared physical infrastructure to serve many customers. Each customer's compute and storage resources are logically isolated and secure, but the underlying hardware is pooled across all customers. Which essential characteristic of cloud computing does this scenario BEST describe?

A.On-demand self-service
B.Resource pooling
C.Broad network access
D.Rapid elasticity
AnswerB

Resource pooling is the correct answer. The scenario explicitly describes shared physical infrastructure serving many customers with logical isolation, which is the essence of resource pooling in cloud computing.

Why this answer

Resource pooling is the correct characteristic because the scenario describes a multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand. The cloud provider's shared infrastructure (compute, storage, network) is pooled to serve multiple customers, with logical isolation ensuring each customer's data remains secure despite the shared underlying hardware. This directly matches the NIST SP 800-145 definition of resource pooling.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'on-demand self-service' because both involve shared infrastructure, but the key distinction is that resource pooling focuses on the provider's multi-tenant architecture, not the consumer's ability to provision resources without human interaction.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a consumer's ability to provision computing capabilities unilaterally without requiring human interaction with each service provider, not to the sharing of physical infrastructure. Option C is wrong because broad network access describes capabilities being available over the network and accessed through standard mechanisms (e.g., mobile phones, laptops), which is unrelated to the pooling of hardware resources across multiple customers.

Practice this question →
4
MCQmedium

A company runs its web application on a fleet of Amazon EC2 instances. The operations team does not know which specific physical servers host their instances, nor does the team have any control over the underlying hardware. However, the team can be confident that if one physical server fails, AWS will automatically launch replacement instances on different hosts. The team can also specify the general geographic region (e.g., us-west-2) but not the exact data center. This scenario best describes which essential characteristic of cloud computing?

A.Rapid elasticity
B.Resource pooling
C.Measured service
D.On-demand self-service
AnswerB

Resource pooling is the correct characteristic. The cloud provider pools its infrastructure to serve multiple customers, and customers do not know the exact physical location of their resources. The scenario explicitly states that the team does not know which physical servers host their instances and can only specify a region, matching resource pooling.

Why this answer

Resource pooling is correct because the scenario describes how the cloud provider's physical and virtual resources (servers, hosts, data centers) are aggregated into a shared pool to serve multiple customers. The operations team cannot control or know the exact physical host or data center, but AWS abstracts that complexity and can automatically launch replacement instances on different hosts if one fails. This multi-tenant model, where the customer has no visibility or control over the underlying physical location beyond a high-level region, is the defining characteristic of resource pooling.

Exam trap

The trap here is that candidates confuse the automatic failover and lack of hardware control with 'rapid elasticity' or 'on-demand self-service,' but the key is the abstraction of physical resources and multi-tenancy, which is the textbook definition of resource pooling.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down in response to demand, not to the abstraction of physical hardware or automatic failover. Option C is wrong because measured service involves metering and billing for resource usage (e.g., per-hour or per-GB charges), which is not mentioned in the scenario about hardware abstraction and automatic replacement. Option D is wrong because on-demand self-service means a user can provision computing capabilities (like launching an EC2 instance) without requiring human interaction with the provider, whereas the scenario focuses on the lack of control over physical hosts and automatic failover, not the provisioning process.

Practice this question →
5
MCQmedium

A company is evaluating cloud adoption. Which of the following is a benefit of moving to the cloud over traditional on-premises infrastructure? (Select all that apply in context: which single answer best captures the operational model shift?)

A.Shift from operational expenditure (OpEx) to capital expenditure (CapEx)
B.Shift from capital expenditure (CapEx) to operational expenditure (OpEx)
C.Increased requirement for physical infrastructure management
D.Reduced ability to scale resources based on demand
AnswerB

Cloud computing replaces large upfront capital purchases (servers, storage) with ongoing operational costs, improving budget flexibility and eliminating stranded hardware risk.

Why this answer

Moving to the cloud shifts infrastructure costs from upfront capital expenditure (CapEx) for hardware to operational expenditure (OpEx) for pay-as-you-go services. This operational model change allows companies to avoid large initial investments and instead pay for compute and storage resources based on actual usage, aligning costs with business growth.

Exam trap

The trap here is that candidates often confuse the direction of the cost shift (CapEx to OpEx) or mistakenly think cloud adoption increases physical management, but AWS's shared responsibility model clearly offloads infrastructure management to the provider.

How to eliminate wrong answers

Option A is wrong because it reverses the actual shift: cloud adoption moves from CapEx to OpEx, not the other way around. Option C is wrong because cloud providers handle physical infrastructure management (e.g., AWS manages data centers, networking, and hardware maintenance), reducing the customer's burden. Option D is wrong because cloud platforms enable rapid, elastic scaling (e.g., AWS Auto Scaling, EC2 instance resizing) rather than reducing the ability to scale based on demand.

Practice this question →
6
MCQeasy

A development team needs to create a new Amazon RDS MySQL database for a temporary testing environment. A developer logs into the AWS Management Console, selects the desired instance type, storage, and network settings, and clicks 'Create database'. The database is available within 10 minutes, and the developer did not need to submit a request or wait for IT approval. Which essential characteristic of cloud computing does this process best demonstrate?

A.Rapid elasticity
B.On-demand self-service
C.Broad network access
D.Resource pooling
AnswerB

This is correct. On-demand self-service is the ability to provision resources without requiring human interaction. The developer directly created the database through the console without needing to wait for IT approval, which is the defining characteristic demonstrated here.

Why this answer

The developer was able to create and provision the RDS MySQL database entirely through the AWS Management Console without any human interaction or approval from IT. This is the core definition of on-demand self-service: a user can provision computing resources as needed automatically, without requiring service provider interaction. The process took only 10 minutes and required no ticket submission, which directly aligns with the NIST definition of on-demand self-service.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with the speed of provisioning (10 minutes), but rapid elasticity specifically refers to automatic scaling of resources based on load, not the initial creation of a resource without human approval.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to scale resources up or down automatically in response to demand, not the ability to provision a resource without human approval. Option C is wrong because broad network access describes the ability to access resources over the network using standard protocols (e.g., HTTPS, SSH), which is not demonstrated by the provisioning workflow described. Option D is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned to multiple customers, not the user's ability to self-provision a database instance.

Practice this question →
7
MCQmedium

A company runs a web application on AWS that experiences unpredictable traffic spikes. The operations team wants the infrastructure to automatically add compute capacity when demand increases and remove it when demand decreases, without manual intervention. The team also wants to pay only for the compute resources they actually use. Which cloud computing concept does this scenario best describe?

A.High availability
B.Elasticity
C.Fault tolerance
D.Pay-as-you-go
AnswerB

Elasticity is the ability to provision and de-provision computing resources automatically to match workload demands. This concept allows the company to handle traffic spikes without manual intervention and only pay for resources consumed, directly matching the scenario.

Why this answer

Elasticity is the ability of a cloud system to automatically scale resources up or down based on demand. In this scenario, AWS services like Auto Scaling groups and Amazon EC2 can add instances during traffic spikes and terminate them when demand drops, ensuring the infrastructure matches workload requirements without manual intervention.

Exam trap

The trap here is that candidates confuse 'pay-as-you-go' (a billing model) with 'elasticity' (the operational capability to scale), but the question explicitly asks for the concept that enables automatic scaling, not just the cost benefit.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring the application remains accessible despite failures (e.g., across multiple Availability Zones), not on dynamically adjusting capacity in response to demand changes. Option C is wrong because fault tolerance is about designing systems to continue operating without interruption when components fail, not about scaling resources up or down. Option D is wrong because pay-as-you-go is a pricing model where you pay only for resources consumed, but it does not describe the automatic scaling behavior; elasticity enables pay-as-you-go by allowing resources to be added and removed dynamically.

Practice this question →
8
MCQmedium

A company is migrating a three-tier web application to AWS. The application will run on Amazon EC2 instances using a custom Linux distribution, and a self-managed MySQL database will be installed on the same instances. The company's security team needs to understand which security responsibilities belong to AWS and which belong to the company under the AWS Shared Responsibility Model. According to this model, who is responsible for applying operating system security patches to the EC2 instances and for updating the MySQL database software?

A.AWS is responsible for both the operating system patches and the MySQL database updates.
B.The company is responsible for both the operating system patches and the MySQL database updates.
C.AWS is responsible for the operating system patches, and the company is responsible for the MySQL database updates.
D.The company is responsible for the operating system patches, and AWS is responsible for the MySQL database updates.
AnswerB

This is correct. Since the company controls the EC2 instance's guest OS and the MySQL database, it is responsible for all patching and updates of that software.

Why this answer

Under the AWS Shared Responsibility Model, AWS is responsible for the security of the cloud (e.g., physical infrastructure, hypervisor), while the customer is responsible for security in the cloud (e.g., guest OS, applications, and data). Since the company is using a custom Linux distribution on EC2 instances and installing a self-managed MySQL database, both the operating system patches and the MySQL database updates fall under the customer's responsibility. AWS does not manage or patch the guest operating system or any software installed by the customer on EC2 instances.

Exam trap

The trap here is that candidates often confuse self-managed software on EC2 with AWS-managed services (like RDS) and incorrectly assume AWS handles patching for any database or OS running on EC2.

How to eliminate wrong answers

Option A is wrong because AWS is never responsible for patching the guest operating system or customer-installed software on EC2 instances; AWS only manages the hypervisor and underlying infrastructure. Option C is wrong because AWS does not apply operating system patches to the guest OS on EC2 instances; the customer is responsible for all patches on the custom Linux distribution. Option D is wrong because the customer is responsible for both the OS and the MySQL database updates, not just the OS; AWS has no role in updating self-managed database software.

Practice this question →
9
MCQeasy

AWS builds and operates large physical data centres and uses virtualisation to serve thousands of customers simultaneously on shared hardware while keeping each customer's data logically isolated. Which cloud computing characteristic does this describe?

A.On-demand self-service
B.Measured service
C.Resource pooling
D.Rapid elasticity
AnswerC

Resource pooling is the cloud characteristic where the provider's resources are pooled to serve multiple customers simultaneously using virtualisation and multi-tenancy, with each customer's data remaining logically isolated.

Why this answer

Resource pooling is the correct answer because AWS uses virtualization to aggregate physical hardware from its data centers into a shared pool of compute, storage, and network resources that can be dynamically assigned and reassigned to multiple customers. Each customer's data remains logically isolated through hypervisor-level isolation (e.g., using Xen or Nitro hypervisors), but the underlying hardware is shared, which is the essence of resource pooling as defined by NIST SP 800-145.

Exam trap

The trap here is that candidates confuse resource pooling with rapid elasticity, because both involve dynamic allocation, but resource pooling is about the shared infrastructure model, 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 user's ability to provision computing resources automatically without requiring human interaction with the service provider, not the sharing of physical hardware. Option B is wrong because measured service involves metering resource usage (e.g., CPU hours, GB-months) for billing and monitoring, not the multi-tenant sharing of infrastructure. Option D is wrong because rapid elasticity describes the ability to scale resources up or out quickly and automatically in response to demand, not the underlying multi-tenant architecture.

Practice this question →
10
MCQmedium

A gaming company launches a new online multiplayer game. During peak hours (evenings and weekends), the player count spikes dramatically, requiring dozens of Amazon EC2 instances to handle the load. During off-peak hours, the player count drops to near zero. The company configures an Amazon EC2 Auto Scaling group that automatically adds instances when CPU utilization exceeds 70% and removes instances when utilization drops below 30%. Which characteristic of cloud computing does this configuration best demonstrate?

A.High availability
B.Elasticity
C.Fault tolerance
D.Global reach
AnswerB

Elasticity is the cloud computing characteristic that allows resources to be provisioned and de-provisioned automatically to match changing demand. The Auto Scaling configuration that adds and removes EC2 instances based on CPU utilization directly illustrates this concept.

Why this answer

Elasticity is the ability of a cloud system to automatically scale resources up or down based on demand. In this scenario, the Auto Scaling group dynamically adds EC2 instances when CPU utilization exceeds 70% and removes them when it drops below 30%, directly matching the fluctuating player load. This demonstrates elasticity because resources are provisioned and de-provisioned in real-time to match the exact workload, minimizing cost during low usage and ensuring performance during spikes.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, but elasticity is specifically 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 system remains operational despite failures (e.g., using multiple Availability Zones), not on dynamically adjusting capacity based on load. Option C is wrong because fault tolerance is the ability to continue operating without interruption when a component fails (e.g., using redundant instances or failover), not the automatic scaling of resources in response to demand. Option D is wrong because global reach refers to deploying resources across multiple geographic regions to serve a worldwide user base, not to the automatic scaling of instances within a single region based on CPU utilization.

Practice this question →
11
MCQeasy

A startup founder is evaluating whether to build their own data center or use AWS. Which cloud benefit eliminates the need for guessing future infrastructure requirements and making large upfront investments?

A.Stop spending money running and maintaining data centers
B.Trade capital expense for variable expense and stop guessing capacity
C.Benefit from massive economies of scale
D.Increase speed and agility for innovation
AnswerB

Cloud computing converts large upfront hardware investment to pay-per-use operational expense, while on-demand provisioning eliminates over-provisioning and capacity planning guesswork.

Why this answer

Option B is correct because it directly addresses the startup founder's concern about eliminating the need to guess future infrastructure requirements and make large upfront investments. AWS's pay-as-you-go model allows you to trade capital expense (upfront hardware costs) for variable expense (paying only for what you use), and you no longer have to predict capacity needs—you can scale up or down based on actual demand. This is a core pillar of the AWS Well-Architected Framework's Cost Optimization pillar.

Exam trap

The trap here is that candidates often confuse 'stop spending money running data centers' (Option A) with the specific financial and capacity-planning benefit described, but the question explicitly asks about eliminating the need to guess capacity and make large upfront investments, which is uniquely addressed by the 'trade capital expense for variable expense' concept.

How to eliminate wrong answers

Option A is wrong because while AWS does eliminate the need to run and maintain physical data centers, this benefit focuses on operational overhead reduction, not on eliminating the need to guess future capacity or avoid large upfront investments. Option C is wrong because economies of scale refer to AWS's ability to offer lower prices due to its massive aggregated usage, but this does not directly address the startup's specific concern about capacity guessing and upfront capital. Option D is wrong because increased speed and agility refers to the ability to rapidly provision resources and experiment, which is a separate benefit from the financial and capacity-planning flexibility described in the question.

Practice this question →
12
MCQmedium

A multinational corporation has a policy that all cloud resources must be provisioned through a centralized IT team. This has caused delays, as developers sometimes wait days for a test environment to be created. The company wants to migrate to AWS to allow individual project teams to provision their own resources (such as Amazon EC2 instances and Amazon S3 buckets) directly through the AWS Management Console or API, without any manual approval process from IT. Which characteristic of cloud computing does this desired capability best represent?

A.High availability
B.Elasticity
C.On-demand self-service
D.Resource pooling
AnswerC

On-demand self-service is a core cloud characteristic where users can provision and manage computing resources without requiring human interaction from the service provider. This directly matches the company's goal of allowing teams to create resources through the AWS Management Console or API without waiting for IT approval.

Why this answer

Option C is correct because the scenario describes developers provisioning AWS resources (EC2 instances, S3 buckets) directly via the AWS Management Console or API without requiring IT approval. This is the core definition of on-demand self-service, one of the five essential characteristics of cloud computing as defined by NIST SP 800-145: a consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider.

Exam trap

The trap here is that candidates often confuse on-demand self-service with elasticity, because both involve rapid provisioning, but elasticity specifically refers to scaling up/down based on load, not the removal of human approval for initial resource creation.

How to eliminate wrong answers

Option A is wrong because high availability refers to systems that are continuously operational for a desirably long length of time, often achieved through redundancy across multiple Availability Zones; it does not address the ability to provision resources without manual approval. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand, not the capability to provision resources on-demand without human intervention. Option D 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; it does not relate to the self-service provisioning workflow described.

Practice this question →
13
MCQmedium

Which statement accurately describes the relationship between AWS Regions and Availability Zones?

A.Each Availability Zone contains multiple Regions
B.Each Region is a single large data center
C.Each Region contains multiple Availability Zones connected with low-latency networking
D.Availability Zones in the same Region share the same power infrastructure
AnswerC

Regions are geographic areas with typically 3+ AZs, each AZ being physically isolated data centers interconnected with high-bandwidth, low-latency private fiber within the Region.

Why this answer

Option C is correct because an AWS Region is a geographical area that consists of multiple, isolated Availability Zones (AZs), each containing one or more data centers. These AZs within a Region are connected via redundant, low-latency networking (typically less than 2 milliseconds round-trip time) to enable high availability and fault tolerance for applications.

Exam trap

The trap here is that candidates often confuse Regions with Availability Zones, mistakenly thinking a Region is a single data center or that AZs share critical infrastructure like power, when in fact AWS deliberately isolates them to ensure fault tolerance.

How to eliminate wrong answers

Option A is wrong because it reverses the relationship: an Availability Zone does not contain multiple Regions; rather, each Region contains multiple Availability Zones. Option B is wrong because a Region is not a single large data center; it is a collection of multiple, physically separate Availability Zones, each with one or more data centers. Option D is wrong because Availability Zones in the same Region are designed with independent power infrastructure (including separate power grids and backup generators) to prevent a single point of failure from affecting multiple AZs.

Practice this question →
14
MCQmedium

A mid-size company is planning to migrate its IT infrastructure to the AWS Cloud. The Chief Information Officer (CIO) expresses concern that multiple customers' virtual servers might run on the same physical hardware, potentially increasing the risk of data exposure. Which cloud computing characteristic describes this shared infrastructure model, where computing resources are pooled to serve multiple customers using a multi-tenant model?

A.On-demand self-service
B.Resource pooling
C.Measured service
D.Broad network access
AnswerB

Resource pooling is the cloud characteristic where the provider's computing resources are pooled to serve multiple customers using a multi-tenant model. This directly addresses the CIO's concern about shared physical hardware, and AWS implements strong isolation mechanisms to prevent data exposure.

Why this answer

Resource pooling is the correct answer because it directly describes the multi-tenant model where the provider's computing resources (such as physical servers, storage, and network) are pooled to serve multiple customers. In AWS, this is achieved through hypervisor-level isolation (e.g., Xen or Nitro hypervisors) that allows multiple virtual servers (EC2 instances) to run on the same physical host while maintaining strict memory and I/O separation, preventing data exposure between tenants.

Exam trap

The trap here is that candidates often confuse resource pooling with multi-tenancy as a security risk, but AWS's shared responsibility model and hypervisor isolation ensure that resource pooling does not inherently increase data exposure risk.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to the ability for users to provision resources automatically without human interaction, not the shared infrastructure model. Option C is wrong because measured service involves metering and billing for resource usage (e.g., per-hour or per-GB charges), not the pooling of resources across customers. Option D is wrong because broad network access describes the ability to access resources over the network via standard protocols (e.g., HTTPS, SSH), not the multi-tenant sharing of physical hardware.

Practice this question →
15
MCQmedium

A company runs a web application on AWS that experiences unpredictable traffic spikes. The company wants to configure its infrastructure to automatically increase compute capacity during peak times and decrease it during low traffic, minimizing costs. Which cloud computing concept does this scenario BEST represent?

A.Elasticity
B.High availability
C.Fault tolerance
D.Vertical scaling
AnswerA

Correct. Elasticity allows automatic scaling of resources to match demand, which directly addresses the need to handle traffic spikes and reduce costs during low usage.

Why this answer

Elasticity is the ability of a cloud system to automatically provision and de-provision compute resources in response to real-time demand. In this scenario, AWS Auto Scaling groups can dynamically launch EC2 instances during traffic spikes and terminate them when demand drops, directly matching capacity to load while minimizing cost. This contrasts with static provisioning, which would either over-provision (wasting money) or under-provision (causing outages).

Exam trap

The trap here is that candidates confuse elasticity with high availability, because both involve handling increased load, but elasticity specifically addresses dynamic resource scaling to match demand, not just distributing traffic across redundant components.

How to eliminate wrong answers

Option B (High availability) is wrong because it focuses on ensuring application uptime across multiple Availability Zones using services like Elastic Load Balancing and Route 53 health checks, not on dynamically adjusting capacity to match workload changes. Option C (Fault tolerance) is wrong because it describes the ability to continue operating without interruption after a component failure (e.g., using Multi-AZ RDS or EC2 Auto Recovery), not the scaling of resources in response to traffic. Option D (Vertical scaling) is wrong because it involves increasing the size of a single instance (e.g., moving from t3.medium to t3.large), which has a hard upper limit and does not automatically handle unpredictable spikes or reduce costs by removing resources.

Practice this question →
16
MCQmedium

A healthcare organization stores sensitive patient records in Amazon S3. The organization's compliance team learns that AWS stores data from multiple customers on the same physical hardware. They are concerned that data from different customers could be mixed or accessed by another customer. Which fundamental characteristic of cloud computing explains how AWS allows customers to share physical infrastructure while keeping each customer's data logically isolated?

A.Rapid elasticity
B.Resource pooling
C.On-demand self-service
D.Measured service
AnswerB

Resource pooling allows the provider to serve multiple customers from a shared pool of physical resources while logically isolating each customer's data and workloads. AWS uses multi-tenant architectures and security controls to ensure that one customer cannot access another customer's data, even when stored on the same hardware.

Why this answer

Resource pooling is the correct answer because it describes how AWS aggregates computing resources (including storage) from multiple customers into a shared pool, then logically isolates each customer's data through software-defined boundaries. In Amazon S3, this isolation is achieved via bucket policies, IAM roles, and object ACLs that enforce strict access controls, ensuring that even though physical hardware is shared, no customer can access another's data. This characteristic directly addresses the compliance team's concern about data mixing or unauthorized cross-tenant access.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'multi-tenancy' or assume it means data is physically separated, but the exam tests that resource pooling specifically enables logical isolation through software controls, not physical hardware separation.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down based on demand, not to the logical isolation of data on shared infrastructure. Option C is wrong because on-demand self-service describes a customer's ability to provision resources automatically without human interaction, which does not explain how data isolation is maintained across tenants. Option D is wrong because measured service involves metering resource usage for billing and optimization, not the mechanisms that prevent data leakage between customers on shared hardware.

Practice this question →
17
MCQmedium

A company runs a stateless web application on a single Amazon EC2 instance in the us-east-1a Availability Zone. The application stores session data in an external Amazon ElastiCache cluster. Due to a power failure in the data center hosting us-east-1a, the EC2 instance becomes unavailable. The company wants to redesign the architecture so that the application recovers automatically in minutes if a single Availability Zone fails. Which design principle should the company implement?

A.Deploy the application across multiple AWS Regions and use Amazon Route 53 latency-based routing to failover.
B.Place the EC2 instance in an Auto Scaling group with a minimum capacity of 1, and configure the Auto Scaling group to span multiple Availability Zones.
C.Use a larger EC2 instance type with dedicated tenancy to reduce the risk of hardware failure.
D.Enable termination protection on the EC2 instance to prevent accidental stopping.
AnswerB

This is correct because an Auto Scaling group that spans multiple Availability Zones will automatically replace a failed instance in a healthy Availability Zone, ensuring the application remains available even if one AZ goes down.

Why this answer

Option B is correct because placing the EC2 instance in an Auto Scaling group with a minimum capacity of 1 and spanning multiple Availability Zones ensures that if us-east-1a fails, the Auto Scaling group automatically launches a new instance in a healthy Availability Zone (e.g., us-east-1b). Since the application is stateless and session data is stored externally in ElastiCache, the new instance can immediately serve traffic without data loss, achieving recovery within minutes.

Exam trap

The trap here is that candidates may confuse high-availability designs (multi-AZ Auto Scaling) with disaster recovery designs (multi-Region), or mistakenly think that instance-level protections like termination protection or larger instance types can mitigate an Availability Zone failure.

How to eliminate wrong answers

Option A is wrong because deploying across multiple AWS Regions and using Route 53 latency-based routing is overkill for a single-AZ failure and introduces unnecessary complexity and cost; it does not address the immediate need for automatic recovery within minutes from an AZ failure. Option C is wrong because using a larger EC2 instance type with dedicated tenancy does not protect against an Availability Zone power failure; it only reduces the risk of hardware failure on a single host, not the entire AZ. Option D is wrong because termination protection prevents accidental termination of the instance, but it does not help recover from an AZ failure—the instance remains unavailable and cannot be automatically replaced.

Practice this question →
18
Drag & Dropmedium

Drag and drop the steps to launch an EC2 instance 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

Launching an EC2 instance involves selecting the OS (AMI), hardware (instance type), networking, storage, and security before launch.

Practice this question →
19
MCQmedium

A company is migrating its workloads to AWS. The IT team is concerned that they will lose visibility into which specific physical server is running their application. A solutions architect explains that AWS abstracts the underlying hardware, allowing customers to focus on their applications without managing physical infrastructure. The architect also notes that AWS pools resources from a large number of data centers to serve multiple customers, and changes the physical location of resources dynamically. Which essential characteristic of cloud computing does this scenario best describe?

A.Rapid elasticity
B.Measured service
C.Resource pooling
D.On-demand self-service
AnswerC

Correct. This scenario directly illustrates resource pooling. The cloud provider combines physical resources from multiple data centers into a shared pool, dynamically allocating them to customers. Customers do not know the exact physical server hosting their workload, which matches the IT team's concern and the architect's explanation.

Why this answer

The scenario describes AWS pooling compute resources from multiple data centers to serve multiple customers, with the physical location of resources changing dynamically. This directly aligns with the 'resource pooling' characteristic of cloud computing, where 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 customer has no knowledge or control over the exact physical location of the provided resources (e.g., which specific server runs their application), which matches the concern in the question.

Exam trap

The trap here is that candidates confuse 'resource pooling' (the multi-tenant sharing of physical infrastructure) with 'rapid elasticity' (the ability to scale resources), because both involve dynamic resource changes, but the key distinction is that pooling is about shared physical hardware and location abstraction, not scaling speed.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to quickly scale resources up or down based on demand, not the abstraction of physical hardware or pooling of resources across data centers. Option B is wrong because measured service involves metering and billing for resource usage (e.g., pay-per-use), not the multi-tenant pooling of infrastructure or the lack of visibility into physical servers.

Practice this question →
20
MCQmedium

A financial services company runs a high-frequency stock trading platform on AWS. The platform must continue processing trades without any interruption, even if an entire AWS Availability Zone experiences a complete outage. The architecture is designed with duplicate infrastructure in multiple Availability Zones, and all components are active simultaneously. The system is engineered so that if one AZ fails, the remaining AZs continue processing trades instantly, with zero downtime for end users. Which cloud computing concept does this requirement BEST represent?

A.Elasticity
B.High availability
C.Fault tolerance
D.Durability
AnswerC

Fault tolerance is the property that enables a system to continue functioning correctly even when some of its components fail. The scenario's demand for 'zero downtime' and 'instant' continuation of processing after an AZ failure directly matches the definition of fault tolerance. This is typically achieved through active-active redundant deployments.

Why this answer

This requirement describes a system that continues to operate without any interruption even when an entire AWS Availability Zone fails. That is the definition of fault tolerance: the system is designed to survive component failures with zero impact on service. The architecture uses duplicate active infrastructure in multiple AZs so that if one AZ fails, the remaining AZs instantly take over with no downtime, which is fault tolerance, not just high availability.

Exam trap

The trap here is that candidates often confuse high availability with fault tolerance, but high availability allows for a brief failover period (e.g., seconds of downtime), while fault tolerance requires zero downtime and instant continuity, which is the exact requirement in this question.

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 survive failures. Option B is wrong because high availability ensures minimal downtime (e.g., 99.99% uptime) but typically allows for a brief failover delay, whereas this requirement demands zero downtime and instant continuity, which is fault tolerance. Option D is wrong because durability refers to the long-term preservation of data without loss, not to the system's ability to continue processing during a failure.

Practice this question →
21
MCQeasy

A startup runs its web application on a few Amazon EC2 instances. Over time, the company scales its infrastructure, adding hundreds more instances to support a growing user base. The company notices that the per-hour cost per instance does not increase as it uses more resources. In fact, AWS has steadily lowered prices for compute and storage services over the years. Which cloud computing concept does this scenario best illustrate?

A.Elasticity
B.Pay-as-you-go pricing
C.Economies of scale
D.High availability
AnswerC

Correct. Economies of scale describe how AWS, by serving millions of customers worldwide, can purchase hardware, operate data centers, and negotiate contracts at massive volumes, achieving lower costs per unit. These savings are then reflected in lower prices for all customers, regardless of their individual consumption level.

Why this answer

Option C is correct because the scenario describes how AWS's per-hour cost per instance does not increase as usage scales, and AWS has steadily lowered prices over time. This directly illustrates economies of scale, where AWS's massive infrastructure investments and operational efficiencies allow it to pass cost savings to customers as usage grows. The key is that the cost per unit (instance-hour) decreases or remains stable at scale, which is the hallmark of economies of scale, not just the ability to scale resources.

Exam trap

The trap here is that candidates confuse 'pay-as-you-go pricing' (a billing model) with 'economies of scale' (a cost advantage from large-scale operations), because both involve cost savings, but the question specifically describes the per-hour cost per instance not increasing and AWS lowering prices over time, which is a direct result of economies of scale, not the pay-as-you-go model itself.

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 cost behavior per instance. Option B is wrong because pay-as-you-go pricing means you only pay for what you use, but the question specifically highlights that the per-hour cost per instance does not increase and AWS lowers prices over time, which is a separate concept from the billing model. Option D is wrong because high availability ensures that applications remain accessible despite failures, typically through redundancy across Availability Zones, and has no direct relation to cost per instance or price reductions.

Practice this question →
22
MCQmedium

A company runs a customer-facing web application on a single Amazon EC2 instance. To ensure the application remains accessible if the instance fails, the company launches a second EC2 instance in a different Availability Zone and configures an Application Load Balancer to distribute traffic. The application continues to serve users with minimal downtime during the failure of any single instance. This scenario best demonstrates which cloud computing concept?

A.Elasticity
B.High availability
C.Scalability
D.Fault tolerance
AnswerB

Correct. High availability is the ability to keep applications running with minimal downtime by eliminating single points of failure. Placing instances in multiple Availability Zones behind a load balancer ensures that the application remains accessible even if one instance fails.

Why this answer

High availability is the correct concept because the architecture uses redundant EC2 instances in separate Availability Zones behind an Application Load Balancer to eliminate a single point of failure. If one instance fails, the load balancer automatically routes traffic to the healthy instance, ensuring the application remains accessible with minimal downtime. This design specifically addresses fault tolerance and uptime, not the ability to handle variable load or scale resources.

Exam trap

The trap here is that candidates confuse high availability with elasticity or scalability because all three involve multiple instances, but high availability is specifically about redundancy and fault tolerance to minimize downtime, not about adjusting capacity to meet demand.

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 traffic spikes and removing them when traffic decreases; the scenario describes static redundancy, not dynamic scaling. Option C is wrong because scalability is the capacity to increase resources to handle growing workloads, typically by adding more instances or upgrading instance types; the scenario focuses on maintaining availability during a failure, not on handling increased load.

Practice this question →
23
MCQmedium

A company hosts a web application on an Amazon EC2 instance. The company installs its own application software and configures the operating system. The company also uses AWS Key Management Service (AWS KMS) to create a customer-managed key to encrypt data on the Amazon Elastic Block Store (Amazon EBS) volume attached to the instance. According to the AWS shared responsibility model, which of the following is the responsibility of AWS?

A.Encrypting the data on the Amazon EBS volume using the customer-managed key.
B.Patching the operating system of the Amazon EC2 instance.
C.Ensuring the physical security of the data center where the Amazon EC2 instance runs.
D.Configuring the security group rules to restrict traffic to the Amazon EC2 instance.
AnswerC

This is an AWS responsibility. AWS operates and controls the physical security of its data centers, including access controls, surveillance, and environmental systems. This falls under 'security of the cloud.'

Why this answer

Option C is correct because under the AWS shared responsibility model, AWS is responsible for the security of the cloud, which includes the physical security of data centers, hardware, networking, and facilities where EC2 instances run. This is a foundational layer that customers cannot manage or control.

Exam trap

The trap here is that candidates often confuse 'encryption at rest' as an AWS responsibility, but the shared responsibility model clearly assigns the management of customer-managed keys and the decision to encrypt to the customer, while AWS only provides the encryption infrastructure.

How to eliminate wrong answers

Option A is wrong because encrypting data on the EBS volume using a customer-managed key is a customer action: the customer creates the KMS key, configures the EBS volume to use it, and manages key rotation and permissions. Option B is wrong because patching the operating system of the EC2 instance is the customer's responsibility under the 'security in the cloud' model, as the customer configures and maintains the OS and installed software. Option D is wrong because configuring security group rules to restrict traffic is a customer-controlled network security task; AWS provides the security group infrastructure, but the customer defines and applies the rules.

Practice this question →
24
MCQmedium

A hospital is evaluating a move of its patient records system to the AWS Cloud. The hospital's compliance officer is concerned that the underlying physical servers in the cloud are shared with other customers, which could potentially expose sensitive patient data. The hospital wants a clear explanation of how AWS prevents one customer from accessing another customer's data even though they reside on the same physical hardware. Which essential characteristic of cloud computing best describes the mechanism that achieves this isolation?

A.On-demand self-service
B.Resource pooling
C.Rapid elasticity
D.Measured service
AnswerB

Resource pooling is the cloud characteristic where the provider's computing resources are pooled to serve multiple customers using a multi-tenant model. Virtualization provides strong logical isolation between customers, preventing data access across tenants. This directly addresses the compliance officer's concern about data security on shared hardware.

Why this answer

Resource pooling is the correct answer because it describes how AWS multi-tenancy works: physical resources like servers and storage are pooled to serve multiple customers, but strict logical isolation is enforced through hypervisor-level virtualization. The hypervisor (e.g., Xen or Nitro) ensures each customer's virtual machines operate in separate memory spaces and cannot access another customer's data, even on the same physical host. This isolation is a fundamental design of cloud computing, not a security flaw.

Exam trap

The trap here is that candidates confuse 'resource pooling' with security vulnerabilities, thinking shared hardware implies shared data, when in fact resource pooling is the very characteristic that enables secure multi-tenancy through hypervisor isolation.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to the ability to provision resources automatically without human interaction, not to data isolation mechanisms. Option C is wrong because rapid elasticity describes the ability to scale resources up or down quickly based on demand, which has nothing to do with preventing cross-customer data access. Option D is wrong because measured service involves metering and billing for resource usage (e.g., pay-per-use), not the logical separation of customer data on shared hardware.

Practice this question →
25
MCQmedium

A company is launching a new application and expects user demand to grow gradually over the next 12 months. To control upfront costs, the company plans to start with a small number of Amazon EC2 instances and manually add more instances each month as the user base increases. The operations team will monitor usage and adjust capacity based on observed trends. Which cloud computing concept does this approach BEST illustrate?

A.Elasticity
B.Scalability
C.High availability
D.Fault tolerance
AnswerB

Scalability is the ability to increase capacity to handle greater load. The company's approach of manually adding EC2 instances as user demand grows is a direct example of scaling up over time, making this the correct answer.

Why this answer

The scenario describes manually adding EC2 instances over time to match growing demand, which is a classic example of scalability—the ability to increase or decrease resources to handle changing workloads. Scalability focuses on planned capacity adjustments, whereas elasticity involves automatic, real-time scaling in response to demand fluctuations. Here, the manual, monthly additions based on observed trends align with scalability, not the automated provisioning that defines elasticity.

Exam trap

The trap here is that candidates confuse scalability with elasticity, assuming any capacity adjustment is elasticity, but the key differentiator is automation—elasticity requires automatic, real-time scaling, while manual, planned adjustments are scalability.

How to eliminate wrong answers

Option A is wrong because elasticity refers to automatically scaling resources up or down in real time based on demand, not manually adding instances on a monthly schedule. Option C is wrong because high availability ensures that applications remain accessible despite failures, typically through redundant infrastructure across multiple Availability Zones, not through capacity scaling. Option D is wrong because fault tolerance is the ability to continue operating without interruption after a component failure, often using redundant systems and failover mechanisms, which is unrelated to adding capacity for growth.

Practice this question →
26
MCQmedium

A company wants to take advantage of AWS's global infrastructure to replicate their database to a second geographic region for disaster recovery. Which benefit of cloud computing does this leverage?

A.Economies of scale
B.Trade capital expense for variable expense
C.Go global in minutes
D.Increase speed and agility for experiments
AnswerC

AWS's presence in dozens of regions worldwide means deploying in a new geographic location takes minutes via the same console and APIs — not months of hardware procurement.

Why this answer

Option C is correct because AWS's global infrastructure allows you to deploy resources, such as database replicas, across multiple geographic regions in minutes. By using services like Amazon RDS Cross-Region Read Replicas or Aurora Global Database, you can replicate data to a second region for disaster recovery, leveraging the cloud's ability to rapidly expand globally without provisioning physical data centers.

Exam trap

The trap here is that candidates confuse 'go global in minutes' with 'economies of scale' or 'speed and agility,' but the question specifically asks about leveraging global infrastructure for geographic replication, not cost savings or experimental speed.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost advantages from massive infrastructure purchasing, not the ability to replicate data across regions for disaster recovery. Option B is wrong because trading capital expense for variable expense describes the shift from upfront hardware costs to pay-as-you-go pricing, which is unrelated to geographic replication. Option D is wrong because increasing speed and agility for experiments focuses on rapid prototyping and testing, not on deploying a disaster recovery solution across regions.

Practice this question →
27
MCQmedium

A company operates its own data center with physical servers that are purchased outright every three years. The company is migrating its entire infrastructure to AWS. The CFO notes that the company will no longer need to make large upfront purchases of hardware and instead will pay monthly for the compute and storage resources used. Which cloud computing benefit does this scenario best illustrate?

A.High availability
B.Resource elasticity
C.Security compliance
D.Shifting capital expense to variable operational expense
AnswerD

Correct. AWS's pay-as-you-go pricing model eliminates the need for large upfront hardware purchases. Instead, costs become variable operational expenses based on actual usage, which is the key financial advantage illustrated in this migration scenario.

Why this answer

This scenario illustrates the shift from capital expenditure (CapEx) to variable operational expenditure (OpEx). In the on-premises model, the company makes large upfront purchases of physical servers every three years, which is a capital expense. By migrating to AWS, the company pays only for the compute and storage resources it consumes on a monthly basis, converting that fixed, upfront cost into a variable operating cost that scales with usage.

Exam trap

The trap here is that candidates often confuse the financial benefit of shifting from CapEx to OpEx with the operational benefit of resource elasticity, but the question specifically focuses on the change in how costs are incurred (upfront vs. monthly usage-based).

How to eliminate wrong answers

Option A is wrong because high availability refers to systems that are designed to remain operational with minimal downtime, typically through redundancy across multiple Availability Zones, not to the financial model of paying for resources. Option B is wrong because resource elasticity describes the ability to automatically scale compute and storage resources up or down based on demand, which is a separate benefit from the change in cost structure. Option C is wrong because security compliance involves adhering to regulatory standards and frameworks (e.g., SOC, PCI DSS) through AWS shared responsibility model, not the transformation of hardware procurement costs.

Practice this question →
28
MCQmedium

A start-up is evaluating cloud providers for its new application. The company's CTO learns that the cloud provider negotiates bulk discounts with hardware vendors and data center operators, and passes these savings on to customers through lower service prices. The CTO also notes that the provider's vast infrastructure allows customers to benefit from the provider's operational expertise in running large-scale data centers. Which benefit of cloud computing does this scenario BEST represent?

A.Pay-as-you-go pricing
B.Resource pooling
C.Economies of scale
D.High availability
AnswerC

Correct. Economies of scale allow cloud providers to reduce costs through massive infrastructure operations and volume discounts, and they pass these cost reductions on to customers.

Why this answer

Economies of scale occur when a cloud provider achieves lower per-unit costs by operating at a massive scale. The provider purchases hardware in bulk, optimizes data center operations, and leverages expertise across many customers. These savings are then reflected in lower prices for all customers.

The scenario directly describes this benefit—lower prices from bulk purchasing and operational expertise passed on to the customer.

Practice this question →
29
MCQmedium

A retail company runs a legacy application on a single on-premises server. The application experiences unpredictable traffic surges that degrade performance. The company is considering migrating to the AWS Cloud. Which cloud computing characteristic MOST directly addresses the ability to automatically adjust resources to meet changing demand without manual intervention?

A.Elasticity
B.Scalability
C.High availability
D.Durability
AnswerA

Correct. Elasticity is the ability to automatically provision and release cloud resources in response to changing demand. This directly addresses the company's need to handle traffic surges without manual intervention.

Why this answer

Elasticity is the cloud computing characteristic that enables automatic resource provisioning and de-provisioning to match demand in real time, without manual intervention. For the retail company's legacy application with unpredictable traffic surges, elasticity directly addresses the need to dynamically scale resources up during spikes and down during lulls, which is distinct from the planned, manual scaling of scalability.

Exam trap

The trap here is that candidates often confuse scalability with elasticity, but the question's emphasis on 'automatically adjust resources to meet changing demand without manual intervention' specifically tests the definition of elasticity, not the broader concept of scalability.

How to eliminate wrong answers

Option B (Scalability) is wrong because scalability refers to the ability to handle increased load by adding resources, but it often implies manual or planned scaling (e.g., adding more servers ahead of time), not the automatic, real-time adjustment that the question specifies. Option C (High availability) is wrong because high availability focuses on minimizing downtime through redundancy and failover mechanisms (e.g., multi-AZ deployments), not on automatically adjusting resources to meet changing demand. Option D (Durability) is wrong because durability pertains to data persistence and protection against loss (e.g., Amazon S3's 99.999999999% durability), which is unrelated to dynamic resource adjustment for traffic surges.

Practice this question →
30
MCQmedium

A company is designing a highly available application on AWS. The architect plans to deploy application instances across multiple Availability Zones and implement health checks to automatically route traffic away from failed instances. These design decisions primarily contribute to which pillar of the AWS Well-Architected Framework?

A.Operational Excellence
B.Security
C.Reliability
D.Performance Efficiency
AnswerC

Correct. The Reliability pillar encompasses the ability of a workload to recover from infrastructure or service failures, dynamically acquire computing resources to meet demand, and mitigate disruptions. Deploying across multiple Availability Zones and using health checks with automatic failover are fundamental reliability techniques that ensure the application continues to operate when single components fail.

Why this answer

Deploying application instances across multiple Availability Zones and using health checks to route traffic away from failed instances directly increases the system's ability to recover from failures and remain operational. This aligns with the Reliability pillar of the AWS Well-Architected Framework, which focuses on ensuring a workload performs its intended function correctly and consistently when expected, including the ability to recover from infrastructure or service disruptions.

Exam trap

The trap here is that candidates may confuse 'health checks and multi-AZ deployments' with Operational Excellence or Performance Efficiency, but the primary Well-Architected pillar addressed by these specific design decisions is Reliability, as they directly improve fault tolerance and recovery.

How to eliminate wrong answers

Option A is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value, and while health checks and multi-AZ deployments support operations, the primary goal here is fault tolerance and recovery, not operational processes. Option B is wrong because Security focuses on protecting data and systems through mechanisms like encryption, access control, and network boundaries; health checks and multi-AZ deployments do not directly address security controls. Option D is wrong because Performance Efficiency focuses on using computing resources efficiently to meet system requirements and maintain efficiency as demand changes; routing traffic away from failed instances is about availability and fault tolerance, not resource optimization.

Practice this question →
31
MCQmedium

A company is assessing their on-premises environment before migrating to AWS. Which AWS service helps discover on-premises servers, profile their utilization, and create a business case for cloud migration?

A.AWS Migration Hub
B.AWS Application Discovery Service
C.AWS Database Migration Service
D.AWS Server Migration Service
AnswerB

Application Discovery Service discovers and profiles on-premises servers (configuration, utilization, dependencies) to help plan migration waves and create a business case for cloud adoption.

Why this answer

AWS Application Discovery Service is designed to gather information about on-premises data centers, including server specifications, utilization metrics, and network dependencies. It provides this data to help build a detailed business case for migration, including cost projections and migration planning. This directly matches the requirement to discover servers, profile utilization, and create a business case.

Exam trap

The trap here is that candidates confuse AWS Migration Hub as the discovery tool, when in fact Migration Hub only aggregates and tracks data from other services like Application Discovery Service, but does not perform the discovery itself.

How to eliminate wrong answers

Option A is wrong because AWS Migration Hub is a central tracking service that monitors migration progress across multiple AWS and partner tools, but it does not perform the initial discovery or utilization profiling of on-premises servers. Option C is wrong because AWS Database Migration Service (DMS) is specifically for migrating databases to AWS, not for discovering or profiling on-premises servers or creating a general business case for cloud migration. Option D is wrong because AWS Server Migration Service (SMS) is used to replicate and migrate live on-premises virtual machines to AWS, but it does not perform discovery or utilization profiling, nor does it generate a business case.

Practice this question →
32
MCQmedium

The AWS Well-Architected Framework's Reliability pillar recommends automatically recovering from failure. Which AWS feature directly enables automated recovery when an EC2 instance status check fails?

A.EC2 Auto Scaling
B.Amazon EC2 Auto Recovery
C.Elastic Load Balancing health checks
D.AWS Systems Manager Patch Manager
AnswerB

EC2 Auto Recovery is a CloudWatch alarm action that automatically restores a failed instance with its original configuration, same instance ID, and attached volumes.

Why this answer

Amazon EC2 Auto Recovery is a feature that automatically recovers an impaired EC2 instance by restarting it on a new healthy host when a system status check fails. This directly aligns with the Reliability pillar's recommendation to automatically recover from failure without manual intervention.

Exam trap

The trap here is that candidates confuse EC2 Auto Recovery with EC2 Auto Scaling, assuming that Auto Scaling's health check replacement is the same as recovering the same instance, but Auto Recovery preserves the instance identity while Auto Scaling terminates and creates a new one.

How to eliminate wrong answers

Option A is wrong because EC2 Auto Scaling replaces instances based on scaling policies or health checks from load balancers, but it does not directly recover the same instance when a status check fails; it terminates and launches a new instance, which is a different mechanism. Option C is wrong because Elastic Load Balancing health checks monitor the health of instances behind a load balancer and route traffic away from unhealthy instances, but they do not perform automated recovery of the instance itself. Option D is wrong because AWS Systems Manager Patch Manager automates the patching of operating systems and applications, not the recovery of failed instances from status check failures.

Practice this question →
33
MCQmedium

A company is migrating its on-premises data analytics workload to AWS. Previously, the company had to purchase and maintain dedicated servers with fixed capacity to handle peak workloads, resulting in low utilization during off-peak hours. On AWS, the company can launch compute resources, run the analytics job, and terminate the resources when done. The company only pays for the compute time and storage used during the job. Which essential characteristic of cloud computing does this scenario BEST demonstrate?

A.Rapid elasticity
B.Measured service
C.Resource pooling
D.On-demand self-service
AnswerB

Measured service is the correct answer. Cloud providers meter usage (compute time, storage, etc.) and bill customers based on actual consumption. This eliminates the need to pay for idle capacity and aligns cost directly with usage, as described in the scenario.

Why this answer

Measured service is the cloud characteristic that enables pay-as-you-go pricing by metering resource usage (compute time, storage) and billing only for what is consumed. In this scenario, the company launches resources for the analytics job, runs it, and terminates them, paying solely for the compute time and storage used — a direct demonstration of metered usage and cost transparency.

Exam trap

The trap here is confusing 'pay only for what you use' (measured service) with the ability to scale resources up/down automatically (rapid elasticity), as both involve dynamic resource management but address different cloud characteristics.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down in response to demand, not to the pay-per-use billing model. Option C is wrong because resource pooling describes how a cloud provider serves multiple customers from shared physical resources using multi-tenancy, which is unrelated to the billing mechanism. Option D is wrong because on-demand self-service allows users to provision resources without human interaction, but the scenario's focus is on paying only for what is used, not the provisioning method.

Practice this question →
34
MCQmedium

A company runs an e-commerce platform on Amazon EC2 instances in a single AWS Region. The company wants to ensure that the platform remains available even if a natural disaster disrupts the entire geographic area of that Region. Which approach should the company take to meet this requirement?

A.Deploy the application across multiple Availability Zones within the same Region.
B.Deploy the application across multiple Edge Locations of Amazon CloudFront.
C.Deploy the application across multiple AWS Regions.
D.Deploy the application on a larger instance type within the same Availability Zone.
AnswerC

Deploying across multiple AWS Regions is the correct approach for geographic disaster recovery. Each Region is completely independent, with separate power, cooling, and physical infrastructure. If one Region is affected by a disaster, the application can fail over to another Region, ensuring business continuity.

Why this answer

Option C is correct because deploying the application across multiple AWS Regions ensures fault tolerance and disaster recovery even if an entire geographic area is disrupted. A natural disaster affecting a single Region would impact all Availability Zones within that Region, so multi-Region deployment is the only approach that provides geographic isolation and continuous availability.

Exam trap

The trap here is that candidates often confuse high availability within a Region (using multiple AZs) with disaster recovery across Regions, mistakenly thinking that AZ-level redundancy is sufficient to withstand a full Regional outage.

How to eliminate wrong answers

Option A is wrong because deploying across multiple Availability Zones within the same Region protects against failures of individual data centers but not against a disaster that affects the entire Region, as all AZs share the same geographic area. Option B is wrong because Amazon CloudFront Edge Locations are content delivery endpoints that cache static and dynamic content for low-latency delivery; they do not run compute workloads like EC2 instances and cannot provide active application availability in the event of a Regional disaster. Option D is wrong because using a larger instance type within the same Availability Zone does not introduce any redundancy or geographic separation; it only increases compute capacity and leaves the application vulnerable to both AZ-level and Regional failures.

Practice this question →
35
MCQmedium

A company runs an e-commerce website on Amazon EC2 instances. The website experiences unpredictable traffic spikes during flash sales and returns to normal traffic levels afterward. To handle this, the company configures an Auto Scaling group that adds EC2 instances when the average CPU utilization exceeds 70% and removes instances when it drops below 30%. Which essential characteristic of cloud computing does this configuration primarily demonstrate?

A.Elasticity
B.High availability
C.Fault tolerance
D.Durability
AnswerA

Correct. Elasticity is the ability to automatically scale resources up or down to match demand. The Auto Scaling group adjusts the number of EC2 instances based on CPU utilization, which is a clear example of elasticity.

Why this answer

This configuration demonstrates elasticity because it automatically scales EC2 instances up during flash sales (when CPU exceeds 70%) and scales them down when traffic normalizes (CPU below 30%). Elasticity is the ability to dynamically provision and de-provision resources to match demand, which is exactly what Auto Scaling groups with CPU utilization thresholds achieve.

Exam trap

The trap here is that candidates confuse elasticity with high availability or fault tolerance, but the question specifically tests the ability to match resource capacity to fluctuating demand, which is elasticity, not the ability to withstand failures or remain operational.

How to eliminate wrong answers

Option B is wrong because high availability focuses on ensuring the system remains operational despite failures (e.g., using multiple Availability Zones, load balancers, or health checks), not on scaling resources based on demand. Option C is wrong because fault tolerance is about the system's ability to continue operating without interruption when a component fails (e.g., redundant instances, automatic failover), not about adjusting capacity to match workload changes.

Practice this question →
36
MCQeasy

Which statement best describes the AWS global infrastructure concept of an Availability Zone (AZ)?

A.A geographic location where AWS hosts data centers, such as North America or Europe
B.One or more discrete data centers with redundant power, networking, and connectivity within a Region
C.A CDN edge location used to cache content close to end users
D.A logically isolated section of the AWS Cloud where customers launch resources
AnswerB

An AZ is physically isolated from other AZs in the same Region, providing fault isolation while maintaining low-latency interconnects.

Why this answer

An Availability Zone (AZ) consists of one or more discrete data centers with independent power, cooling, and physical networking, connected to each other through low-latency links within a single AWS Region. This design ensures that if one AZ fails, applications can continue operating in other AZs, providing high availability and fault tolerance. Option B correctly captures this definition, as it emphasizes the discrete, redundant infrastructure that makes an AZ distinct from a Region or a data center.

Exam trap

The trap here is that candidates often confuse an Availability Zone with a single data center or with a Region, but AWS explicitly defines an AZ as one or more discrete data centers, not just one, and it is a subset of a Region, not the Region itself.

How to eliminate wrong answers

Option A is wrong because it describes an AWS Region, not an Availability Zone; a Region is a separate geographic area containing multiple AZs, while an AZ is a specific set of data centers within that Region. Option C is wrong because it describes an Amazon CloudFront edge location, which is a CDN cache point used for content delivery, not an Availability Zone that hosts compute and storage resources. Option D is wrong because it describes a Virtual Private Cloud (VPC), which is a logically isolated section of the AWS Cloud where you launch resources, whereas an AZ is a physical location composed of data centers.

Practice this question →
37
MCQmedium

A retail company is migrating its e-commerce platform to AWS. The company's financial controller notes that AWS can offer lower pay-as-you-go prices than what it would cost the company to build and operate its own data center at the same scale. Which cloud computing concept best explains this pricing advantage?

A.Agility
B.Economies of scale
C.Elasticity
D.High availability
AnswerB

Economies of scale allow AWS to spread fixed costs over a massive customer base, reducing per-unit costs and enabling lower pay-as-you-go prices compared to a single organization building its own data center.

Why this answer

The correct answer is B, economies of scale. AWS operates at a massive global scale, allowing it to negotiate lower prices for hardware, data center power, and network bandwidth. These savings are passed on to customers as lower pay-as-you-go prices, which a single company building its own data center cannot match due to its smaller procurement volume.

Exam trap

The trap here is that candidates confuse elasticity (scaling to match demand) with the underlying cost advantage of shared infrastructure, but elasticity reduces waste, not the base price per unit of compute or storage.

How to eliminate wrong answers

Option A is wrong because agility refers to the ability to rapidly provision and deploy resources, not to cost savings from scale. Option C is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which optimizes usage but does not inherently explain lower per-unit pricing. Option D is wrong because high availability ensures systems remain operational despite failures, typically through redundancy across multiple Availability Zones, and does not directly address the cost advantage of shared infrastructure.

Practice this question →
38
MCQmedium

A company runs a web application on a fleet of Amazon EC2 instances. The application experiences unpredictable traffic patterns with sudden spikes. The company configures an Auto Scaling group with dynamic scaling policies to automatically add instances when CPU utilization exceeds 70% and remove instances when it drops below 30%. This design is an example of which key characteristic of cloud computing?

A.High availability
B.Fault tolerance
C.Elasticity
D.Durability
AnswerC

Elasticity is the ability to automatically provision and deprovision computing resources to match current demand. The dynamic scaling policy that adds and removes instances based on CPU utilization is a direct implementation of elasticity in AWS.

Why this answer

Option C is correct because the Auto Scaling group's dynamic scaling policy, which adds instances when CPU utilization exceeds 70% and removes them when it drops below 30%, directly demonstrates elasticity. Elasticity is the ability to automatically provision and de-provision resources in response to real-time demand, matching capacity to workload without manual intervention. This contrasts with static provisioning, where resources are fixed regardless of load.

Exam trap

The trap here is that candidates confuse elasticity with high availability or fault tolerance, but elasticity specifically refers to dynamic scaling of resources to match demand, not redundancy or failure recovery.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring the application remains accessible despite failures, typically achieved through multi-AZ deployments, load balancers, and health checks—not by scaling based on CPU utilization. Option B is wrong because fault tolerance is the ability to continue operating without interruption when a component fails, often via redundant systems like standby instances or failover mechanisms, whereas the described scaling policy adjusts capacity for performance, not to mask failures.

Practice this question →
39
MCQeasy

A company has migrated its customer-facing web application to AWS. The application is deployed on Amazon EC2 instances behind an Application Load Balancer. The company's customers access the application from various devices—desktop computers, laptops, tablets, and smartphones—using standard web browsers without any additional configuration or proprietary software. The ability for customers to reach the application over the internet from any device with a standard browser best demonstrates which essential characteristic of cloud computing?

A.On-demand self-service
B.Broad network access
C.Resource pooling
D.Rapid elasticity
AnswerB

Broad network access means cloud resources are accessible over the network via standard mechanisms (e.g., HTTPS) from a wide range of devices. The question describes customers using standard web browsers on various devices to reach the application, which is a direct example of broad network access.

Why this answer

Broad network access is the correct answer because the scenario describes customers accessing the application from various devices (desktops, laptops, tablets, smartphones) using standard web browsers over the internet without any proprietary software. This directly matches the NIST definition of broad network access: resources are available over the network and accessed through standard mechanisms (e.g., HTTP/HTTPS) that promote use by heterogeneous thin or thick client platforms.

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 distinction is that broad network access is about heterogeneous device reachability via standard protocols, while on-demand self-service is about automated resource 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 (e.g., launch an EC2 instance) automatically without requiring human interaction with the cloud provider, not the ability to access an application from multiple device types. Option C is wrong because resource pooling describes the provider's ability to serve multiple customers from shared physical and virtual resources dynamically assigned according to demand, which is an internal infrastructure characteristic, not a customer-facing access capability.

Practice this question →
40
MCQmedium

Which benefit of cloud computing allows a company to experiment with new ideas and quickly spin down failed experiments without financial penalty?

A.Economies of scale
B.Elasticity
C.Agility
D.Durability
AnswerC

Cloud agility means provisioning resources in minutes, experimenting at low cost, and terminating failed experiments without the financial penalty of stranded hardware.

Why this answer

Agility (Option C) is correct because cloud computing enables rapid experimentation by allowing companies to provision and de-provision resources on demand. This means a company can quickly spin up infrastructure to test a new idea and, if it fails, tear it down immediately without incurring ongoing costs. The pay-as-you-go model ensures there is no long-term financial penalty for failed experiments, directly supporting innovation and iterative development.

Exam trap

The trap here is that candidates often confuse elasticity with agility, but elasticity is about automatic scaling to meet demand, while agility is about the speed and low cost of provisioning and de-provisioning resources for experimentation.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to the cost advantages that cloud providers achieve through massive infrastructure, which are passed to customers as lower per-unit prices, but this does not specifically enable quick experimentation or cost-free teardown of failed projects. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which handles variable workloads but does not inherently address the financial penalty of failed experiments; it focuses on performance scaling rather than cost avoidance for short-lived tests. Option D is wrong because durability is a data protection concept, typically related to storage systems ensuring data remains intact and recoverable (e.g., Amazon S3's 99.999999999% durability), and has no relevance to the financial or operational aspects of experimenting with new ideas.

Practice this question →
41
MCQmedium

A company has deployed a web application on Amazon EC2 instances. The company's security team wants to ensure that the underlying host operating system is patched against a newly discovered vulnerability. According to the AWS Shared Responsibility Model, who is responsible for applying the patch to the host operating system?

A.The company, because patches for underlying infrastructure are always the customer's responsibility in EC2.
B.AWS, because the hypervisor and host OS are part of the 'Security of the Cloud'.
C.The company, because EC2 is an Infrastructure as a Service (IaaS) offering and the customer manages the OS.
D.Both the company and AWS share responsibility equally for host OS patching.
AnswerB

Correct. AWS is responsible for protecting the infrastructure that runs all AWS services, including the host OS, hypervisor, physical servers, and networking. Patching the host OS falls under this responsibility.

Why this answer

Under the AWS Shared Responsibility Model, AWS is responsible for the security of the cloud, which includes the physical infrastructure, hypervisor, and host operating system that runs EC2 instances. When a vulnerability is discovered in the host OS (the OS that runs the hypervisor and manages the physical hardware), AWS must apply the patch because the customer has no access to or control over the host OS. The customer is only responsible for patching the guest OS (the OS running inside the EC2 instance) and any applications deployed on it.

Exam trap

The trap here is that candidates mistakenly apply the IaaS model's general rule (customer manages the OS) to the host OS, forgetting that in virtualized EC2, the host OS is part of the hypervisor layer managed solely by AWS.

How to eliminate wrong answers

Option A is wrong because it incorrectly states that patches for underlying infrastructure are always the customer's responsibility in EC2; in reality, AWS patches the host OS and hypervisor, while the customer patches the guest OS. Option C is wrong because it confuses the customer's responsibility for the guest OS (which they manage in IaaS) with the host OS, which is managed by AWS as part of the virtualized infrastructure.

Practice this question →
42
MCQmedium

A financial services company is required by regulation to keep all customer transaction data on-premises. However, they want to use AWS to run analytics workloads on this data using Amazon EMR and Amazon S3 for temporary storage of intermediate results. They need a solution that connects their on-premises network to AWS securely and allows them to extend their on-premises environment into the AWS Cloud. Which cloud computing deployment model does this scenario BEST describe?

A.Public cloud
B.Private cloud
C.Hybrid cloud
D.Community cloud
AnswerC

A hybrid cloud deployment combines on-premises infrastructure (private cloud) with public cloud services, connected securely. This matches the scenario where sensitive data stays on-premises while analytics run on AWS.

Why this answer

Option C is correct because the scenario describes a hybrid cloud deployment model, where the company maintains on-premises infrastructure for regulatory compliance (keeping customer transaction data on-premises) while leveraging AWS public cloud services (Amazon EMR and Amazon S3) for analytics workloads. The requirement to connect the on-premises network to AWS securely and extend the on-premises environment into the AWS Cloud is a defining characteristic of hybrid cloud, often implemented using AWS Direct Connect or VPN connections to create a unified network.

Exam trap

The trap here is that candidates may confuse 'hybrid cloud' with 'public cloud' because the company uses AWS services, but the key differentiator is the integration with on-premises infrastructure to meet regulatory data residency requirements.

How to eliminate wrong answers

Option A is wrong because a public cloud model would involve running all workloads, including the customer transaction data, on AWS infrastructure, which violates the regulatory requirement to keep data on-premises. Option B is wrong because a private cloud model would require the company to host all resources, including the analytics workloads, within their own data center or a dedicated single-tenant environment, contradicting the use of AWS public cloud services like Amazon EMR and Amazon S3. Option D is wrong because a community cloud is designed for use by a specific group of organizations with shared concerns (e.g., compliance or security requirements), but the scenario does not involve multiple organizations sharing the infrastructure; it is a single company extending its on-premises environment into AWS.

Practice this question →
43
MCQeasy

A financial services company keeps sensitive customer data in an on-premises data center. Regulatory requirements prohibit this data from being stored in the cloud. However, the company needs to run compute-intensive analytics jobs that periodically require more processing power than its on-premises servers can provide. The company wants to use AWS for these burst capacity needs while keeping the sensitive data on premises. Which cloud deployment model best describes this approach?

A.Public cloud
B.Private cloud
C.Hybrid cloud
D.Community cloud
AnswerC

Hybrid cloud connects on-premises infrastructure with public cloud services. This enables the company to keep sensitive data on-premises for compliance while leveraging AWS for burst compute capacity, matching the described requirements.

Why this answer

The hybrid cloud model is correct because it combines on-premises infrastructure (private cloud) with public cloud resources (AWS) while keeping sensitive data on-premises. The company uses AWS for burst compute capacity via services like AWS Batch or EC2 Auto Scaling, but the data never leaves the on-premises data center, satisfying regulatory requirements.

Exam trap

The trap here is that candidates often confuse 'hybrid cloud' with 'public cloud' because they see AWS usage, but the key distinction is that sensitive data stays on-premises, making it a hybrid model, not a pure public cloud deployment.

How to eliminate wrong answers

Option A is wrong because a public cloud model would store all data and workloads in AWS, violating the regulatory prohibition against storing sensitive data in the cloud. Option B is wrong because a private cloud is entirely on-premises or hosted in a dedicated environment, which cannot provide the burst capacity from AWS that the company needs. Option D is wrong because a community cloud is shared by multiple organizations with common concerns (e.g., compliance), but it does not specifically address the hybrid burst capacity requirement between on-premises and AWS.

Practice this question →
44
MCQmedium

Which cloud deployment model involves running applications on AWS infrastructure managed entirely by AWS, where the customer does not manage any physical hardware?

A.Private cloud
B.Hybrid cloud
C.Public cloud
D.Community cloud
AnswerC

Public cloud means AWS owns and manages all hardware; customers consume services without managing physical infrastructure.

Why this answer

The public cloud deployment model is defined by infrastructure that is owned, managed, and maintained by a third-party cloud provider (in this case, AWS). The customer has no responsibility for the physical hardware, such as servers, storage, or networking equipment, and accesses resources on-demand via the internet. This matches the scenario where AWS manages everything, and the customer only interacts with virtualized services.

Exam trap

AWS often tests the misconception that a private cloud means the customer manages no hardware, but in reality, private clouds can be on-premises with the customer owning the hardware, or hosted with dedicated hardware, which still involves customer control or visibility into physical resources.

How to eliminate wrong answers

Option A is wrong because a private cloud involves dedicated infrastructure used exclusively by a single organization, which may be managed by the organization itself or a third party, but the customer often retains control over physical hardware or has dedicated hardware. Option B is wrong because a hybrid cloud combines public and private cloud models, meaning the customer still manages or controls some physical hardware (e.g., on-premises servers) that are connected to AWS. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., security, compliance), and while it may be managed by a third party, it does not imply that the customer has zero management of physical hardware; the model is about shared governance, not full provider management.

Practice this question →
45
MCQeasy

A company's employees access AWS services using the AWS Management Console from their office laptops, the AWS mobile app on their smartphones, and the AWS CLI from their home computers. Which cloud computing characteristic does this illustrate?

A.Rapid elasticity
B.Resource pooling
C.Broad network access
D.Measured service
AnswerC

Broad network access is the cloud characteristic that describes capabilities being available over the network and accessible from heterogeneous client platforms including mobile phones, laptops, and workstations — which is exactly what this scenario describes.

Why this answer

Broad network access is the correct answer because the scenario describes employees accessing AWS services from multiple types of devices (office laptops, smartphones, home computers) using different access methods (AWS Management Console, AWS mobile app, AWS CLI). This directly illustrates the cloud characteristic that resources are available over the network and can be accessed by standard protocols (e.g., HTTPS for the console and mobile app, HTTP/HTTPS for CLI API calls) from a wide range of client platforms, including mobile phones, laptops, and workstations.

Exam trap

The trap here is that candidates often confuse 'broad network access' with 'rapid elasticity' because both involve flexibility, but broad network access is about the variety of access methods and devices, not the ability to scale 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 the variety of access methods or devices. Option B is wrong because resource pooling describes how the provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned; it does not relate to how users access the services. Option D is wrong because measured service means that cloud resource usage is monitored, controlled, and reported (e.g., metering for billing), which is not illustrated by the employees using different devices and access methods.

Practice this question →
46
MCQeasy

Which of the following is NOT one of the five characteristics of cloud computing as defined by NIST?

A.On-demand self-service
B.Resource pooling
C.Dedicated hardware allocation per customer
D.Measured service
AnswerC

Dedicated hardware per customer is NOT a NIST characteristic — it's actually the opposite. Cloud computing uses shared multi-tenant resource pools (though dedicated options like Dedicated Hosts exist as a special case).

Why this answer

Option C is correct because the five essential characteristics of cloud computing as defined by NIST SP 800-145 are on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. Dedicated hardware allocation per customer is not a characteristic; instead, cloud computing relies on resource pooling where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, often with multi-tenant models.

Exam trap

AWS often tests the distinction between optional cloud deployment models (e.g., dedicated hosts, private cloud) and the mandatory NIST essential characteristics, leading candidates to mistakenly think dedicated hardware allocation is a required characteristic.

How to eliminate wrong answers

Option A is wrong because on-demand self-service is a core NIST characteristic, allowing a consumer to unilaterally provision computing capabilities (e.g., server time, network storage) without requiring human interaction with each service provider. Option B is wrong because resource pooling is a fundamental NIST characteristic, where the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. Option D is wrong because measured service is a key NIST characteristic, where cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, active user accounts).

Practice this question →
47
MCQmedium

A company is designing a highly available web application on AWS. The application must remain available and continue serving traffic even if an entire physical data center experiences a complete outage. Which AWS global infrastructure component should the solutions architect use to meet this requirement?

A.Deploy the application across multiple AWS Regions.
B.Deploy the application across multiple Availability Zones within a single AWS Region.
C.Deploy the application to an AWS Local Zone.
D.Use an AWS Edge Location to cache the application's content.
AnswerB

This is correct. Each Availability Zone is a separate data center. Distributing the application across multiple AZs ensures that if one data center fails, the application continues running in another AZ, achieving high availability and fault tolerance.

Why this answer

Option B is correct because deploying across multiple Availability Zones (AZs) within a single AWS Region protects against the failure of an entire physical data center. Each AZ is a distinct, isolated location with independent power, cooling, and networking, so if one AZ goes down, the application continues serving traffic from the other AZs. This design meets the requirement for high availability without the complexity and cost of multi-Region deployment.

Exam trap

The trap here is that candidates often confuse high availability (which requires multiple AZs) with disaster recovery (which requires multiple Regions), leading them to incorrectly choose multi-Region deployment when the question specifically asks about surviving a single data center outage.

How to eliminate wrong answers

Option A is wrong because deploying across multiple AWS Regions is designed for disaster recovery and global latency optimization, not solely for protecting against a single data center outage; it introduces higher complexity, cross-Region data transfer costs, and potential data residency issues. Option C is wrong because an AWS Local Zone is an extension of a Region that places compute and storage closer to end users for low-latency applications, but it does not provide the independent fault isolation of multiple data centers and is not designed to survive a complete data center outage.

Practice this question →
48
MCQeasy

A development team wants to deploy a Python web application to AWS without managing load balancers, auto scaling groups, or the underlying EC2 instance operating systems. They want to upload their code and have AWS handle the 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.Serverless
AnswerB

PaaS abstracts infrastructure management. Elastic Beanstalk is PaaS — the developer uploads code and AWS manages the servers, load balancers, auto scaling, and OS patches automatically.

Why this answer

Platform as a Service (PaaS) provides a managed platform where developers can upload code and AWS handles the underlying infrastructure, including load balancing, auto scaling, and OS patching. AWS Elastic Beanstalk is a PaaS service that abstracts EC2 instances, load balancers, and auto scaling groups, allowing the team to focus solely on their Python web application code.

Exam trap

The trap here is that candidates often confuse Serverless (Option D) with PaaS because both abstract infrastructure, but Serverless is specifically event-driven and stateless (e.g., AWS Lambda), whereas PaaS like Elastic Beanstalk runs a long-lived web application with traditional request-response patterns.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) requires the team to manage the underlying EC2 instances, including OS updates, security patches, and scaling configurations, which contradicts the requirement to avoid managing these components. Option C is wrong because Software as a Service (SaaS) delivers a fully managed application to end users (e.g., Salesforce, Gmail), not a platform for deploying custom code. Option D is wrong because Serverless (e.g., AWS Lambda) is a subset of PaaS that runs code in stateless compute containers with event-driven triggers, but the question explicitly mentions deploying a Python web application without managing load balancers or auto scaling groups, which is more directly aligned with PaaS (Elastic Beanstalk) rather than the function-as-a-service model of Serverless.

Practice this question →
49
MCQeasy

A company wants to run a MySQL database on AWS. They require full control over the operating system, MySQL version selection, storage layout, and network configuration. Which cloud service model provides this level of control?

A.Software as a Service (SaaS)
B.Platform as a Service (PaaS)
C.Infrastructure as a Service (IaaS)
D.Function as a Service (FaaS)
AnswerC

IaaS gives customers control over the OS, storage, and deployed applications while AWS manages the physical hardware and virtualisation. Running MySQL on an EC2 instance where the customer selects and patches the OS and controls the MySQL installation is classic IaaS.

Why this answer

C is correct because Infrastructure as a Service (IaaS) provides virtualized computing resources over the internet, giving the customer full control over the operating system, database software (including MySQL version selection), storage layout (e.g., instance store vs. EBS volumes), and network configuration (e.g., VPC, subnets, security groups). This is the only service model that allows you to manage the underlying OS and database stack directly, similar to running a physical server.

Exam trap

The trap here is that candidates often confuse Amazon RDS (a PaaS offering) with full control, but RDS does not allow OS access, custom MySQL version selection outside supported versions, or direct storage layout control, making IaaS the only correct choice for the stated requirements.

How to eliminate wrong answers

Option A is wrong because Software as a Service (SaaS) delivers a fully managed application (e.g., Amazon RDS for MySQL in a managed form) where the provider controls the OS, database version, and infrastructure, and the customer only interacts with the database via SQL, not the underlying OS or storage. Option B is wrong because Platform as a Service (PaaS) provides a managed platform (e.g., Amazon RDS) that abstracts away OS access, MySQL version selection is limited to supported versions, and storage layout and network configuration are largely predefined by the provider. Option D is wrong because Function as a Service (FaaS) (e.g., AWS Lambda) is designed for stateless, event-driven code execution with no persistent storage or OS-level control, and cannot run a MySQL database directly.

Practice this question →
50
MCQmedium

Which AWS concept describes the practice of tracking and managing costs using software engineering principles — such as tagging, automation, and real-time visibility — to enable engineers and teams to make cost-aware decisions?

A.Total Cost of Ownership (TCO)
B.Cloud Financial Management (FinOps)
C.Reserved Instance optimization
D.Cost Avoidance
AnswerB

FinOps is the practice of managing cloud costs with engineering rigor — real-time visibility, allocation, optimization, and a cultural shift where cost becomes a first-class engineering concern.

Why this answer

Cloud Financial Management (FinOps) is the correct answer because it specifically refers to the practice of applying software engineering principles—such as tagging resources, automating cost controls, and providing real-time cost visibility—to manage cloud spending. This enables engineers and teams to make cost-aware decisions during development and operations, aligning with the question's description.

Exam trap

The trap here is that candidates confuse 'Cloud Financial Management (FinOps)' with 'Total Cost of Ownership (TCO)' because both involve cost analysis, but TCO is a static comparison metric while FinOps is an active, iterative practice with automation and tagging.

How to eliminate wrong answers

Option A is wrong because Total Cost of Ownership (TCO) is a financial estimate used to compare the direct and indirect costs of a cloud solution versus on-premises infrastructure, not a practice for ongoing cost management with tagging and automation. Option C is wrong because Reserved Instance optimization is a specific cost-saving strategy that involves purchasing reserved capacity for predictable workloads, not a broad framework for applying software engineering principles to cost management. Option D is wrong because Cost Avoidance refers to actions taken to prevent future costs (e.g., right-sizing resources), but it is not a comprehensive practice that includes real-time visibility, tagging, and automation as core components.

Practice this question →
51
MCQeasy

Which statement about AWS pricing is accurate?

A.AWS prices are fixed and never change
B.AWS offers pay-as-you-go pricing with volume discounts as usage grows
C.AWS requires annual contracts for all services
D.Data transfer into AWS from the internet is the largest AWS cost component
AnswerB

AWS charges only for what you use (On-Demand), and many services offer tiered pricing where per-unit costs decrease as usage volume increases.

Why this answer

AWS pricing is accurate as pay-as-you-go with volume discounts because customers only pay for the resources they consume, and as usage increases, tiered pricing or volume-based discounts (e.g., AWS Lambda's per-request pricing or S3's storage tiers) automatically reduce the per-unit cost. This model eliminates upfront commitments and aligns cost with actual consumption, which is a core AWS pricing philosophy.

Exam trap

The trap here is that candidates often assume AWS requires long-term contracts or that inbound data transfer is a major cost, but AWS explicitly makes inbound data transfer free to encourage migration, and pay-as-you-go with volume discounts is the foundational pricing model tested in CLF-C02.

How to eliminate wrong answers

Option A is wrong because AWS prices are not fixed; they can change over time (e.g., price reductions for services like EC2 or S3) and vary by region, and AWS frequently introduces new pricing models like Savings Plans. Option C is wrong because AWS does not require annual contracts for all services; most services operate on a pay-as-you-go basis, and while Reserved Instances or Savings Plans offer discounts for 1- or 3-year commitments, they are optional, not mandatory. Option D is wrong because data transfer into AWS from the internet is typically free; the largest cost components are usually compute (e.g., EC2 instances), storage (e.g., S3), and data transfer out to the internet, not inbound transfer.

Practice this question →
52
MCQhard

According to the AWS Well-Architected Framework, which design principle is most closely associated with the recommendation to 'stop spending money on undifferentiated heavy lifting'?

A.Design for failure
B.Use managed services to reduce operational burden
C.Implement least-privilege access controls
D.Automate infrastructure provisioning
AnswerB

Using managed services (databases, message queues, ML platforms) transfers undifferentiated infrastructure management to AWS, freeing engineering resources for differentiating business features.

Why this answer

The AWS Well-Architected Framework's principle of 'stop spending money on undifferentiated heavy lifting' directly advocates for using managed services to offload operational tasks like patching, scaling, and hardware maintenance. By leveraging services such as Amazon RDS (instead of self-managed databases) or AWS Lambda (instead of managing servers), you reduce the operational burden and focus on business differentiation. This aligns with the Operational Excellence pillar's goal of minimizing manual overhead.

Exam trap

The trap here is that candidates confuse 'automation' (Option D) with 'managed services,' but automation still requires you to manage the underlying infrastructure (e.g., patching EC2 instances), whereas managed services offload that entire responsibility to AWS.

How to eliminate wrong answers

Option A is wrong because 'Design for failure' is a principle of the Reliability pillar, focusing on building resilient architectures (e.g., multi-AZ deployments, health checks), not on reducing operational overhead from undifferentiated tasks. Option C is wrong because 'Implement least-privilege access controls' is a Security pillar best practice for minimizing attack surface via IAM policies, not a cost or operational efficiency concept. Option D is wrong because 'Automate infrastructure provisioning' (e.g., using AWS CloudFormation or Terraform) reduces manual effort but still requires managing the underlying infrastructure; it does not eliminate the undifferentiated heavy lifting of patching, scaling, and hardware maintenance that managed services address.

Practice this question →
53
MCQmedium

A company traditionally operated an on-premises data center and purchased all server hardware and software licenses with upfront capital expenditure. After migrating its workloads to AWS, the company now receives a monthly invoice that reflects only the compute hours, storage, and data transfer that it actually used. The company can also stop paying for resources when they are no longer needed. Which key characteristic of cloud computing does this scenario best illustrate?

A.Elasticity
B.Pay-as-you-go pricing (variable expense)
C.Global reach
D.Security
AnswerB

This is correct. The scenario describes transitioning from a CAPEX model (buying hardware upfront) to an OPEX model where the company pays only for the resources it actually uses each month. This is the 'pay-as-you-go' characteristic of cloud computing, which avoids large upfront investments and matches costs to usage.

Why this answer

The scenario describes a shift from upfront capital expenditure (buying hardware and licenses) to a model where the company pays only for the compute hours, storage, and data transfer it actually uses, and can stop paying when resources are no longer needed. This directly illustrates the pay-as-you-go pricing characteristic of cloud computing, where costs are variable expenses based on consumption rather than fixed, upfront investments. This model is a fundamental aspect of AWS's pricing philosophy, enabling customers to align costs directly with usage.

Exam trap

The trap here is that candidates may confuse the ability to stop paying for unused resources with elasticity, but the question specifically highlights the shift from upfront capital expenditure to a variable expense model, which is the defining characteristic of pay-as-you-go pricing.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability to automatically scale resources up or down in response to demand, not to the billing model of paying only for what you use. While the scenario mentions stopping payment for unused resources, the core illustration is about the shift from capital expenditure to variable expense, not the dynamic scaling behavior. Option C is wrong because global reach describes the ability to deploy resources in multiple geographic regions around the world, which is not mentioned or implied in the scenario about billing and cost structure changes.

Practice this question →
54
MCQmedium

A company has deployed a customer relationship management (CRM) application on AWS. Sales representatives use the application from their office laptops, company-issued tablets, and personal smartphones. They access the application securely through a web browser using HTTPS from any location, including client sites and home offices. This capability is an example of which essential characteristic of cloud computing?

A.Rapid elasticity
B.Measured service
C.Broad network access
D.Resource pooling
AnswerC

Broad network access enables cloud resources to be accessed over the network via standard protocols (e.g., HTTPS) from a wide range of client devices such as laptops, tablets, and smartphones. The sales representatives accessing the CRM application from multiple device types and locations directly demonstrates this characteristic.

Why this answer

Broad network access is the correct answer because the scenario describes the ability to access the CRM application from various devices (laptops, tablets, smartphones) over the network using standard protocols (HTTPS). This aligns with the NIST definition of broad network access, which states that capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms.

Exam trap

The trap here is that candidates often confuse broad network access with rapid elasticity because both involve 'access from anywhere' or 'scalability,' but the key distinction is that broad network access is about device and protocol heterogeneity, not automatic scaling.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically and quickly scale resources up or down based on demand, such as adding more EC2 instances during peak traffic; the scenario does not mention any scaling or dynamic provisioning of resources. Option B is wrong because measured service involves monitoring, controlling, and reporting resource usage for billing and optimization (e.g., AWS CloudWatch metrics and billing reports); the scenario focuses on access from multiple devices, not on metering or pay-per-use billing.

Practice this question →
55
MCQmedium

A company runs an e-commerce website on Amazon EC2 instances behind an Application Load Balancer. The marketing team plans to run flash sales several times a year, which cause unpredictable but massive traffic spikes. The operations team wants the infrastructure to automatically add new EC2 instances when traffic increases and remove them when traffic decreases, without any manual intervention. Which cloud computing concept does this requirement MOST directly represent?

A.Elasticity
B.Scalability
C.High availability
D.Fault tolerance
AnswerA

Correct. Elasticity refers to the ability to automatically provision and de-provision resources in response to real-time demand. The described auto-scaling behavior that adds and removes EC2 instances during flash sales is the classic example of elasticity.

Why this answer

The requirement to automatically add EC2 instances during traffic spikes and remove them when traffic decreases directly represents elasticity. Elasticity is the ability to dynamically scale resources up or down based on real-time demand, which is precisely what the operations team needs for unpredictable flash sales. AWS Auto Scaling groups, integrated with the Application Load Balancer, automatically launch or terminate EC2 instances based on CloudWatch alarms (e.g., CPU utilization or request count), matching capacity to load without manual intervention.

Exam trap

The trap here is that candidates often confuse scalability (the ability to grow) with elasticity (the ability to both grow and shrink automatically), but the question explicitly requires automatic addition and removal of instances, which is the defining characteristic of elasticity.

How to eliminate wrong answers

Option B (Scalability) is wrong because scalability refers to the ability to handle increased load by adding resources, but it does not inherently include the ability to automatically remove resources when demand decreases; elasticity specifically includes both scaling up and scaling down. Option C (High availability) is wrong because high availability focuses on ensuring the system remains operational despite failures (e.g., using multiple Availability Zones), not on dynamically adjusting capacity in response to traffic changes. Option D (Fault tolerance) is wrong because fault tolerance is the ability of a system to continue functioning even when a component fails, which is unrelated to automatically adding or removing instances based on traffic spikes.

Practice this question →
56
MCQmedium

A company's leadership team wants a structured framework for planning their AWS cloud migration that addresses organisational change management, skills development, governance, platform, security, and operations. Which AWS framework provides guidance across these perspectives?

A.AWS Well-Architected Framework
B.AWS Cloud Adoption Framework (CAF)
C.AWS Migration Hub
D.AWS Trusted Advisor
AnswerB

The AWS CAF provides a structured approach to cloud adoption with six perspectives: Business (value realisation), People (culture and skills), Governance (risk and compliance), Platform (technical infrastructure), Security (protection), and Operations (running and managing cloud services).

Why this answer

The AWS Cloud Adoption Framework (CAF) is specifically designed to guide organizations through their cloud migration journey by providing structured guidance across six core perspectives: Business, People, Governance, Platform, Security, and Operations. This framework directly addresses the leadership team's requirements for organizational change management, skills development, governance, platform, security, and operations, making it the correct choice.

Exam trap

The trap here is that candidates often confuse the AWS Well-Architected Framework (which is about optimizing existing architectures) with the AWS Cloud Adoption Framework (which is about planning and executing the migration journey itself), leading them to select Option A instead of the correct Option B.

How to eliminate wrong answers

Option A is wrong because the AWS Well-Architected Framework focuses on reviewing and improving existing cloud architectures against five pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization), not on providing a structured migration planning framework that includes organizational change management and skills development. Option C is wrong because AWS Migration Hub is a service that provides a single location to track the progress of application migrations across multiple AWS and partner solutions, but it does not offer guidance on organizational change management, skills development, or governance perspectives. Option D is wrong because AWS Trusted Advisor is an automated tool that inspects your AWS environment and provides recommendations for cost optimization, performance, security, and fault tolerance, but it does not provide a strategic framework for planning cloud migration or addressing organizational change.

Practice this question →
57
MCQmedium

A company has migrated its IT infrastructure to AWS. The company's finance team receives a monthly bill that itemizes charges based on the number of Amazon EC2 instance hours consumed, the amount of Amazon S3 storage used in gigabyte-months, and the total data transferred out to the internet. The cloud provider automatically tracks and reports this usage data for billing purposes. This scenario best demonstrates which essential characteristic of cloud computing?

A.On-demand self-service
B.Broad network access
C.Measured service
D.Resource pooling
AnswerC

Measured service involves the cloud provider automatically monitoring, controlling, and reporting resource usage, providing transparency for billing. The detailed itemized bill based on actual consumption (instance hours, storage, data transfer) is a direct implementation of measured service.

Why this answer

The correct answer is C because the scenario describes a cloud provider automatically tracking and reporting usage data (EC2 instance hours, S3 storage in gigabyte-months, and data transfer) for billing purposes. This is the essence of measured service, where cloud resources are metered and usage is monitored, controlled, and reported transparently. The pay-per-use billing model relies on this characteristic to provide cost visibility and optimization.

Exam trap

The trap here is that candidates often confuse 'measured service' with 'on-demand self-service' because both involve user interaction with the cloud, but measured service specifically focuses on the automated metering and billing of resource usage, not the ability to provision resources without human 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 (e.g., launching an EC2 instance or creating an S3 bucket) without requiring human interaction with the provider, not the automated tracking and billing of usage. Option B is wrong because broad network access describes the availability of cloud services over standard network protocols (e.g., HTTPS, SSH) from a wide range of devices (e.g., laptops, smartphones), not the metering and reporting of resource consumption for billing.

Practice this question →
58
MCQmedium

A company runs its production web application on a single Amazon EC2 instance located in one Availability Zone. Recently, a power outage in that data center caused the instance to become unavailable, resulting in application downtime. The company wants to redesign the architecture so that the application automatically continues serving users even if a single data center fails, without requiring manual intervention. Which cloud computing concept does this scenario BEST illustrate?

A.Elasticity
B.High availability
C.On-demand self-service
D.Broad network access
AnswerB

High availability refers to systems that are designed to be operational and accessible for a high percentage of time by eliminating single points of failure. Deploying across multiple Availability Zones is a common practice in AWS to achieve high availability.

Why this answer

High availability (B) is the correct concept because the scenario describes designing an architecture that automatically continues serving users even if a single data center (Availability Zone) fails, without manual intervention. This is achieved by deploying the application across multiple Availability Zones, using an Elastic Load Balancer to distribute traffic, and configuring Auto Scaling groups to maintain instance health, ensuring the application remains accessible despite a zonal failure.

Exam trap

The trap here is that candidates confuse high availability with elasticity, mistakenly thinking that automatically adding more instances during a failure is the same as designing for fault tolerance across data centers, whereas elasticity handles scaling based on load, not zonal redundancy.

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 maintain service continuity during a data center failure. Option C is wrong because on-demand self-service describes the ability to provision computing resources as needed without human interaction with the provider, which is unrelated to fault tolerance or availability across Availability Zones.

Practice this question →
59
MCQmedium

A developer at a company is working on a new feature. The developer needs a test server running a specific version of Linux with certain software pre-installed. Without waiting for approval from the IT team or filling out a request form, the developer logs into the AWS Management Console, chooses an Amazon EC2 instance type, configures the security group, and launches the instance. The instance is fully operational within minutes. Which essential characteristic of cloud computing does this scenario best illustrate?

A.Rapid elasticity
B.On-demand self-service
C.Resource pooling
D.Measured service
AnswerB

Correct. On-demand self-service means a consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. The developer's ability to launch an instance without IT approval is a clear example.

Why this answer

The scenario describes a developer provisioning an EC2 instance directly through the AWS Management Console without any human interaction with the IT team. This is the defining characteristic of on-demand self-service, where a customer can provision computing resources as needed automatically without requiring human interaction with each service provider. The ability to configure the instance type, security group, and launch it in minutes without a request form or approval chain directly maps to this essential cloud characteristic.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with the speed of provisioning a single resource; rapid elasticity is about automatically scaling resources up and down based on demand, not just the speed of launching one instance, whereas on-demand self-service specifically addresses the lack of human interaction required to provision resources.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down quickly in response to demand, such as using Auto Scaling groups to add or remove EC2 instances based on CPU utilization; the scenario does not involve any scaling or dynamic adjustment of resources. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are pooled to serve multiple customers, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand; the developer's single-instance launch does not illustrate this multi-tenant pooling concept. Option D is wrong because measured service means cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth); the scenario does not mention any monitoring, metering, or billing aspects.

Practice this question →
60
MCQmedium

A company uses Amazon RDS to run their production database. Under the AWS Shared Responsibility Model, who is responsible for patching the underlying database engine software?

A.The customer, because they chose to run a relational database
B.AWS, because RDS is a managed service that abstracts OS and engine management
C.A shared responsibility where AWS and the customer each patch different components
D.A third-party DBA contracted by the customer
AnswerB

RDS is a managed database service. AWS is responsible for patching the database engine (MySQL, PostgreSQL, etc.), the underlying OS, and the hardware. This is why RDS sits on the 'AWS manages' side for engine patching, unlike a self-managed DB on EC2.

Why this answer

Amazon RDS is a fully managed database service that automates the patching of the underlying database engine software. Under the AWS Shared Responsibility Model, AWS is responsible for the security of the cloud, which includes managing the host operating system and the database engine patches. The customer is responsible for data, access management, and application-level security, not the engine software patching.

Exam trap

The trap here is that candidates often confuse the customer's responsibility for managing database configuration (e.g., parameter groups, backups) with the engine patching, leading them to incorrectly select option A or C, when in fact AWS handles all underlying infrastructure and engine software patching in RDS.

How to eliminate wrong answers

Option A is wrong because the customer's choice to run a relational database does not shift the responsibility for patching the database engine to them; AWS manages the engine as part of the RDS managed service. Option C is wrong because patching the database engine is not a shared responsibility; AWS handles it entirely, while the customer is responsible for tasks like managing database parameters and backups. Option D is wrong because a third-party DBA contracted by the customer would not be responsible for patching the RDS engine; AWS retains that responsibility as the service provider.

Practice this question →
61
MCQmedium

A financial services company maintains a legacy on-premises database for sensitive customer data that must remain in a physically controlled environment due to regulatory requirements. The company runs its customer-facing web application on AWS to benefit from scalability and global reach. A dedicated encrypted VPN connection securely links the on-premises environment with the AWS cloud. Which cloud deployment model does this scenario BEST represent?

A.Public cloud
B.Private cloud
C.Hybrid cloud
D.Community cloud
AnswerC

Correct. The company combines on-premises infrastructure with AWS public cloud, connected via a VPN. This is the definition of a hybrid cloud deployment model.

Why this answer

This scenario best represents a hybrid cloud because it combines on-premises infrastructure (the legacy database) with public cloud resources (AWS) connected via a dedicated encrypted VPN. The hybrid cloud model allows the company to keep sensitive data in a physically controlled environment while leveraging AWS's scalability for the customer-facing web application.

Exam trap

The trap here is that candidates might confuse a hybrid cloud with a public cloud because the web application runs on AWS, but the key differentiator is the integration with on-premises infrastructure for regulatory compliance.

How to eliminate wrong answers

Option A is wrong because a public cloud model would have all resources, including the sensitive database, hosted on the cloud provider's infrastructure, which does not meet the regulatory requirement for physical control. Option B is wrong because a private cloud model would have all resources dedicated to a single organization, but here the customer-facing web application runs on AWS, which is a public cloud provider, not a private cloud. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., compliance), but this scenario involves only one company using its own on-premises and AWS resources, not a multi-tenant community.

Practice this question →
62
MCQmedium

A company has employees in field offices who need to manage AWS resources (e.g., launch EC2 instances, upload files to S3) using a web browser on their company-issued laptops. The laptops connect to the internet via public Wi-Fi or cellular hotspots. The employees do not have any VPN or direct corporate network connection. They can successfully access the AWS Management Console and perform all actions over standard HTTPS ports. Which essential characteristic of cloud computing does this scenario primarily demonstrate?

A.Resource pooling
B.Broad network access
C.Measured service
D.Rapid elasticity
AnswerB

Broad network access means cloud capabilities are available over the network and accessed through standard mechanisms (e.g., web browsers, HTTPS) from a variety of client devices. This scenario directly demonstrates this characteristic: employees use laptops and public internet connectivity to reach the AWS Management Console without requiring a VPN or dedicated network.

Why this answer

This scenario demonstrates broad network access because the employees can access and manage AWS resources from anywhere using standard web browsers over HTTPS (port 443) on public Wi-Fi or cellular hotspots, without requiring a VPN or dedicated corporate network. Broad network access means that cloud resources are available over the network through standard mechanisms (e.g., web browsers, REST APIs) from heterogeneous client platforms (laptops, phones, tablets). The ability to perform all actions via the AWS Management Console over HTTPS directly illustrates this characteristic.

Exam trap

The trap here is that candidates may confuse 'broad network access' with 'resource pooling' because both involve network connectivity, but broad network access specifically addresses the ability to access services from diverse locations and devices over standard protocols, not the sharing of underlying infrastructure among multiple customers.

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 assigning them based on demand; the scenario does not describe multi-tenancy or resource sharing among customers. Option C is wrong because measured service involves metering and monitoring resource usage (e.g., CPU hours, storage GB) for billing and optimization; the scenario focuses on access methods, not usage tracking or pay-per-use billing.

Practice this question →
63
MCQmedium

Which cloud computing benefit allows a company's development team to spin up a testing environment in 5 minutes instead of waiting 6 weeks for hardware procurement and data center provisioning?

A.Economies of scale
B.High availability
C.Increase speed and agility
D.Pay-as-you-go pricing
AnswerC

Cloud agility enables developers to provision complete environments in minutes rather than weeks, reducing the cycle time for innovation and experimentation.

Why this answer

Option C is correct because one of the core benefits of cloud computing is the ability to rapidly provision and release resources with minimal management effort. Instead of waiting weeks for hardware procurement and data center provisioning, a development team can spin up a testing environment in minutes using Infrastructure as a Service (IaaS) or Platform as a Service (PaaS) offerings like Amazon EC2 or AWS Elastic Beanstalk. This agility directly reduces time-to-market and enables faster iteration cycles.

Exam trap

The trap here is that candidates often confuse the speed and agility benefit with pay-as-you-go pricing, because both are key cloud advantages, but the question explicitly asks about the time-to-provision benefit, not the billing model.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to the cost advantages that cloud providers achieve through massive infrastructure aggregation, which lowers per-unit costs for customers, not the speed of resource provisioning. Option B is wrong because high availability focuses on ensuring that applications and services remain operational and accessible despite failures, typically through redundancy across Availability Zones, not on the speed of deploying new environments. Option D is wrong because pay-as-you-go pricing is a consumption-based billing model where you pay only for the resources you use, which provides cost flexibility but does not directly address the speed of provisioning hardware or environments.

Practice this question →
64
Matchingmedium

Match each AWS storage service to its description.

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

Concepts
Matches

Object storage for any data

Block storage for EC2 instances

File storage for multiple EC2 instances

Low-cost archival storage

Hybrid cloud storage integration

Why these pairings

Each storage service addresses different storage needs.

Practice this question →
65
MCQhard

A company architect is designing a new system on AWS. They want to implement the Well-Architected Framework principle of 'loosely coupled components.' Which architecture pattern best achieves this?

A.Have all services call each other directly via synchronous API calls
B.Use Amazon SQS or Amazon SNS between services to decouple them
C.Deploy all application components on a single large EC2 instance
D.Use a single shared database for all microservices
AnswerB

Message queues and event buses create loose coupling — producers write to the queue and consumers process independently. Components can be updated, scaled, or fail without directly affecting each other.

Why this answer

Option B is correct because Amazon SQS (message queue) and Amazon SNS (pub/sub) enable asynchronous communication between services, allowing them to operate independently without direct dependencies. This decoupling aligns with the Well-Architected Framework's principle of loosely coupled components, as services can fail, scale, or be updated without impacting others.

Exam trap

The trap here is that candidates often assume synchronous API calls (Option A) are simpler and sufficient for decoupling, but the Well-Architected Framework specifically requires asynchronous messaging (SQS/SNS) to achieve true loose coupling.

How to eliminate wrong answers

Option A is wrong because synchronous API calls create tight coupling—if one service fails or slows down, all dependent services are directly impacted, violating the loose coupling principle. Option C is wrong because deploying all components on a single large EC2 instance creates a monolithic architecture with no separation of concerns, making the system tightly coupled and a single point of failure. Option D is wrong because a single shared database for all microservices introduces tight coupling at the data layer, where schema changes or contention in one service can cascade to others, undermining independence.

Practice this question →
66
MCQmedium

A company runs multiple workloads on AWS. At the end of each month, the finance team receives a detailed invoice that shows exactly how many GB-hours of Amazon EBS storage each workload used and how many hours each Amazon EC2 instance was running. This granular usage data is used to allocate costs back to the respective business units. Which essential characteristic of cloud computing does this capability best demonstrate?

A.Measured service
B.On-demand self-service
C.Resource pooling
D.Rapid elasticity
AnswerA

This is correct. Measured service means cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service. Usage is monitored, controlled, and reported, providing transparency for both the provider and consumer. The detailed billing and cost allocation precisely illustrate this characteristic.

Why this answer

The correct answer is A because the ability to track and report granular usage data—such as GB-hours of EBS storage and EC2 instance hours—directly corresponds to the measured service characteristic of cloud computing. Measured service means cloud resources are metered at an abstraction level appropriate to the service type (e.g., storage, compute), enabling usage-based billing and cost allocation. In this scenario, the detailed invoice provides precise consumption metrics that allow the finance team to allocate costs to specific business units, which is the core function of measured service.

Exam trap

The trap here is that candidates often confuse measured service with on-demand self-service because both involve user control over resources, but measured service specifically focuses on metering and billing granularity, not the ability to provision resources without human intervention.

How to eliminate wrong answers

Option B is wrong because on-demand self-service refers to a user's ability to provision and manage computing resources automatically without requiring human interaction with the service provider, not to the granular tracking or billing of those resources. Option C is wrong because resource pooling describes the provider's ability to serve multiple customers from shared physical and virtual resources, dynamically assigning and reassigning them according to demand; it does not involve the detailed usage metering or cost allocation described in the question.

Practice this question →
67
MCQmedium

A company's finance team receives a detailed monthly report from AWS that shows the exact number of Amazon EC2 instance hours used, the amount of Amazon S3 storage consumed, and the volume of data transferred out to the internet over the month. The team uses this report to analyze usage trends, allocate costs to different departments, and plan future budgets. This capability is an example of which essential characteristic of cloud computing?

A.On-demand self-service
B.Broad network access
C.Resource pooling
D.Measured service
AnswerD

Correct. Measured service is the cloud characteristic where resource usage is metered, controlled, and reported. The detailed monthly report of EC2 hours, S3 storage, and data transfer is a clear example of measured service, providing transparency for both the cloud provider and the consumer.

Why this answer

The correct answer is D, Measured service. This characteristic means cloud providers automatically meter and report resource usage (e.g., EC2 instance hours, S3 storage, data transfer) for billing, optimization, and planning. The finance team's ability to analyze exact usage data and allocate costs directly demonstrates this metering capability.

Exam trap

The trap here is that candidates confuse 'measured service' with 'resource pooling' because both involve multi-tenancy, but measured service specifically focuses on the metering and reporting of usage for billing and analysis, not the pooling of resources.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user provisioning compute resources without human interaction, not to the reporting or metering of usage after the fact. Option B is wrong because broad network access describes the ability to access cloud services over the network using standard protocols (e.g., HTTPS, SSH), not the detailed usage reporting. 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; it does not involve the metered reporting of individual resource consumption.

Practice this question →
68
MCQeasy

A company discovers they have 30 EC2 instances running 24/7 that are almost never used — CPU utilisation under 1%. Terminating these idle instances would save thousands of dollars per month. Which AWS Well-Architected Framework pillar encourages this practice?

A.Operational Excellence
B.Reliability
C.Performance Efficiency
D.Cost Optimisation
AnswerD

The Cost Optimisation pillar includes identifying and eliminating waste — resources that consume cost but deliver no business value. Terminating 30 idle instances is a cost optimisation action.

Why this answer

Option D is correct because the Cost Optimization pillar of the AWS Well-Architected Framework focuses on avoiding unnecessary costs by matching capacity with demand. Terminating idle EC2 instances (CPU utilization under 1%) directly reduces wasted spend, aligning with the pillar's principle of 'right-sizing' resources and eliminating unused components.

Exam trap

The trap here is that candidates confuse 'Performance Efficiency' (which optimizes resource usage for performance) with 'Cost Optimization' (which minimizes waste and cost), leading them to select Option C instead of D.

How to eliminate wrong answers

Option A is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value, not on cost reduction from idle resources. Option B is wrong because Reliability ensures workloads perform correctly and recover from failures, which is unrelated to terminating unused instances. Option C is wrong because Performance Efficiency deals with using IT and computing resources efficiently to meet system requirements, not with eliminating underutilized assets to save money.

Practice this question →
69
MCQmedium

A company architect uses the Well-Architected Framework to review their workload. Which pillar specifically covers the concepts of selecting the right instance types and sizes, using serverless architectures, and choosing the appropriate storage solution?

A.Cost Optimization
B.Performance Efficiency
C.Operational Excellence
D.Sustainability
AnswerB

Performance Efficiency focuses on using computing resources efficiently — selecting appropriate instance types, architectures (serverless), and storage types are core to this pillar.

Why this answer

Performance Efficiency is the correct pillar because it focuses on using computing resources efficiently to meet system requirements, which includes selecting appropriate instance types and sizes, leveraging serverless architectures to eliminate idle capacity, and choosing the right storage solution based on access patterns and performance needs. The Well-Architected Framework defines this pillar as the ability to adapt to workload changes while maintaining efficiency through resource optimization.

Exam trap

The trap here is that candidates often confuse Performance Efficiency with Cost Optimization, assuming that selecting smaller instance types or serverless is always about saving money, when the pillar's primary goal is to meet performance requirements efficiently, not just reduce spend.

How to eliminate wrong answers

Option A is wrong because Cost Optimization focuses on minimizing costs and avoiding unnecessary spending, not on selecting instance types or storage for performance reasons. Option C is wrong because Operational Excellence covers operational practices like monitoring, incident response, and automation of changes, not the technical selection of compute or storage resources. Option D is wrong because Sustainability aims to minimize environmental impacts, such as reducing energy consumption and carbon footprint, not on choosing instance sizes or serverless architectures for performance.

Practice this question →
70
MCQmedium

A company is migrating its internal email system to a cloud-based solution. After the migration, the company's IT team no longer needs to manage the email servers, apply operating system patches, or upgrade the email software. The cloud provider handles all underlying infrastructure, the platform, and the application itself. Users access their email through a web browser or a mobile app. Which cloud service model does this scenario describe?

A.Infrastructure as a Service (IaaS)
B.Platform as a Service (PaaS)
C.Software as a Service (SaaS)
D.On-premises deployment
AnswerC

SaaS delivers a complete application over the internet, fully managed by the provider. The customer only uses the software via a browser or app and has no responsibility for the underlying infrastructure, platform, or application maintenance. This matches the scenario exactly.

Why this answer

This scenario describes Software as a Service (SaaS) because the cloud provider delivers the entire email application, including the underlying infrastructure, platform, and software, to end users. The IT team has no responsibility for managing servers, applying OS patches, or upgrading the email software—users simply access the email via a web browser or mobile app. This matches the SaaS model, where the provider manages everything from the hardware to the application, and the customer only consumes the software.

Exam trap

AWS often tests the misconception that if the customer does not manage the OS, it must be PaaS, but the key differentiator is that SaaS provides a fully functional application (like email) out of the box, whereas PaaS provides a platform for building and running custom applications.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) would require the company to still manage the email software, apply OS patches, and upgrade the application—the provider only supplies virtualized compute, storage, and networking, not the email application itself. Option B is wrong because Platform as a Service (PaaS) provides a runtime environment and development tools for building and deploying custom applications, but the customer would still be responsible for managing the email application code and its configuration, not simply consuming a ready-made email service.

Practice this question →
71
MCQmedium

A company is designing a system where a failure in one component does not cause cascading failures across the entire application. Which architectural concept does this represent?

A.Tight coupling
B.Loose coupling
C.Vertical scaling
D.Monolithic architecture
AnswerB

Loose coupling minimizes dependencies between components so failures don't cascade across the system.

Why this answer

Loose coupling is the architectural concept that ensures components are independent, so a failure in one component does not cascade to others. In AWS, this is achieved through services like Amazon SQS for asynchronous messaging or Amazon SNS for event-driven decoupling, where each component can fail and recover independently without affecting the rest of the system.

Exam trap

AWS often tests the confusion between loose coupling and horizontal scaling, where candidates mistakenly think scaling out instances prevents cascading failures, but scaling alone does not decouple component dependencies.

How to eliminate wrong answers

Option A is wrong because tight coupling means components are highly dependent on each other, so a failure in one component directly causes cascading failures across the entire application, which is the opposite of the desired behavior. Option C is wrong because vertical scaling (increasing the size of a single instance, e.g., from t2.micro to t2.large) addresses capacity but does not prevent cascading failures between components. Option D is wrong because monolithic architecture packages all components into a single deployable unit, where a failure in any part typically brings down the entire application, directly causing cascading failures.

Practice this question →
72
MCQmedium

A small e-commerce company currently hosts its website on a single physical server in a colocation facility. The company pays a fixed monthly fee for the server, power, and bandwidth, regardless of actual usage. The CTO is evaluating AWS and notes that AWS operates millions of servers across multiple data centers, allowing it to negotiate lower prices for hardware and pass those savings to customers. The CTO expects that migrating to AWS will reduce the company's per-unit costs. Which benefit of cloud computing does this scenario BEST describe?

A.High availability
B.Elasticity
C.Economy of scale
D.Fault tolerance
AnswerC

Economy of scale is the correct answer. The scenario explicitly describes how AWS's massive infrastructure footprint enables lower per-unit costs that are passed to customers. This is a core benefit of cloud computing: customers benefit from the provider's ability to achieve cost efficiencies that are impossible for a single organization to match.

Why this answer

The scenario describes how AWS leverages its massive scale of operations—millions of servers across multiple data centers—to negotiate lower hardware prices from suppliers and pass those savings to customers. This is the definition of economy of scale: as the volume of production increases, the cost per unit decreases. The CTO expects that migrating to AWS will reduce the company's per-unit costs, which directly aligns with this cloud computing benefit.

Exam trap

AWS often tests the distinction between economy of scale (cost reduction from volume) and elasticity (cost reduction from right-sizing usage), so candidates may confuse the two because both can lower costs, but the mechanism is fundamentally different.

How to eliminate wrong answers

Option A is wrong because high availability refers to systems that are designed to remain operational with minimal downtime, often through redundancy across multiple Availability Zones, not cost reduction from scale. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which can reduce costs but is not the primary mechanism described here—the focus is on lower per-unit hardware costs from AWS's purchasing power. Option D 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 feature, not a cost-saving benefit from scale.

Practice this question →
73
MCQmedium

A company is currently running its IT infrastructure in an on-premises data center. The finance department wants to understand how moving to the AWS Cloud would change the company's cost structure. In particular, they want to avoid large upfront hardware purchases and instead pay only for the resources they consume on a monthly basis. Which key cloud computing concept does this shift represent?

A.Elasticity
B.Economies of scale
C.Pay-as-you-go pricing
D.High availability
AnswerC

Pay-as-you-go is a pricing model where customers pay only for the resources they consume, with no upfront commitments. This directly addresses the finance department's desire to avoid large upfront hardware purchases and shift to a variable monthly expense model.

Why this answer

Option C is correct because pay-as-you-go pricing is the cloud computing model that allows a company to avoid large upfront capital expenditures on hardware and instead pay only for the resources they consume on a monthly basis. This directly aligns with the finance department's goal of shifting from a capital expenditure (CapEx) model to an operational expenditure (OpEx) model, where costs are incurred based on actual usage rather than upfront purchases.

Exam trap

The trap here is that candidates often confuse elasticity (the ability to scale) with the pricing model, but the question specifically asks about the shift from upfront hardware purchases to monthly consumption-based billing, which is exclusively a pay-as-you-go concept.

How to eliminate wrong answers

Option A is wrong because elasticity refers to the ability of a cloud system to automatically scale resources up or down based on demand, not to the pricing model that avoids upfront costs. Option B is wrong because economies of scale describe the cost advantage that AWS gains from massive infrastructure deployments, which allows them to pass savings to customers, but this is a benefit of cloud computing in general, not the specific shift from upfront hardware purchases to consumption-based billing.

Practice this question →
74
MCQmedium

A company runs a nightly batch processing job on AWS that takes exactly 2 hours to complete. The company uses a fixed set of Amazon EC2 instances for the job. AWS automatically tracks the number of instance-hours consumed each month and bills the company precisely for that usage. The company does not need to sign a long-term contract or pay for idle resources. Which essential characteristic of cloud computing does this scenario best illustrate?

A.Resource pooling
B.Measured service
C.Rapid elasticity
D.Broad network access
AnswerB

Correct. Measured service is the characteristic where cloud resources are metered, and customers pay only for what they use. The automatic tracking of instance-hours and pay-per-use billing perfectly illustrate this concept.

Why this answer

The scenario describes AWS automatically tracking and billing precisely for the number of instance-hours consumed each month, without requiring a long-term contract or payment for idle resources. This directly illustrates the 'measured service' characteristic, where cloud resource usage is metered, monitored, and reported transparently, enabling pay-as-you-go billing. The fixed 2-hour nightly job and exact billing per instance-hour confirm that usage is measured and charged accordingly.

Exam trap

The trap here is that candidates may confuse 'measured service' with 'rapid elasticity' because both involve usage-based billing, but measured service focuses on metering and charging for actual consumption, while rapid elasticity is about automatic scaling to match demand.

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 based on demand; the scenario does not mention multi-tenancy or resource sharing. Option C is wrong because rapid elasticity involves automatically scaling resources up or down in response to workload changes, but the scenario explicitly states a fixed set of EC2 instances used for a nightly job, with no scaling or elasticity involved.

Practice this question →
75
MCQmedium

A social media startup plans to launch its application to users across North America, Europe, and Asia. The CTO wants a single deployment approach that minimizes latency for end users in all geographic regions, provides high availability, and allows the company to add new regions within minutes as the user base expands. The startup has no existing data centers outside its home country. Which fundamental benefit of cloud computing does this requirement best illustrate?

A.Pay-as-you-go pricing
B.Economies of scale
C.Global reach
D.Agility
AnswerC

Global reach (or the ability to 'go global in minutes') allows organizations to deploy applications in multiple AWS Regions around the world quickly. This directly supports the requirement to minimize latency for users across different continents and to expand to new regions with minimal effort.

Why this answer

The requirement to deploy a single application across North America, Europe, and Asia with low latency, high availability, and the ability to add new regions within minutes directly illustrates the global reach benefit of cloud computing. AWS provides a global infrastructure with Regions and Edge Locations that allow the startup to serve users from geographically distributed points without building physical data centers. This enables the company to achieve low-latency access and rapid regional expansion, which is a core advantage of cloud over on-premises architectures.

Exam trap

The trap here is that candidates often confuse agility (the ability to quickly provision resources) with global reach (the ability to deploy infrastructure across multiple geographic regions), but the scenario explicitly emphasizes geographic distribution and latency reduction, which is a hallmark of global reach.

How to eliminate wrong answers

Option A is wrong because pay-as-you-go pricing refers to the cost model where you only pay for consumed resources, not to the geographic distribution or latency reduction described in the scenario. Option B is wrong because economies of scale describe the cost advantages AWS gains from massive infrastructure purchasing power, which are passed to customers, but this does not directly address multi-region deployment or latency minimization. Option D is wrong because agility refers to the ability to quickly provision and scale resources (e.g., via AWS CloudFormation or Auto Scaling), but the specific focus of this question is on global infrastructure reach, not general speed of provisioning.

Practice this question →
Page 1 of 4 · 238 questions totalNext →

Ready to test yourself?

Try a timed practice session using only Cloud Concepts questions.

Start 20-question session