CCNA Cloud Concepts Questions — Page 3 of 4

151

MCQmedium

A financial services company has a core banking application that runs on-premises and stores sensitive customer data. Due to strict regulatory requirements, this application cannot be migrated to the cloud. However, the company wants to use AWS for its development and test environments to benefit from rapid provisioning and pay-per-use pricing. The company also wants to establish a dedicated private network connection between its on-premises data center and AWS to securely transfer data between the environments. Which cloud deployment model does this scenario describe?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Multi-cloud

AnswerC

Hybrid cloud is a model that combines on-premises infrastructure (private cloud) with public cloud services. This scenario perfectly fits hybrid cloud because the company runs its core application on-premises while using AWS for development and test. The dedicated private network connection (e.g., Direct Connect) bridges the two environments, enabling secure data exchange and unified operations.

Why this answer

This scenario describes a hybrid cloud deployment model because it combines on-premises infrastructure (the core banking application) with AWS public cloud resources (development and test environments) connected via a dedicated private network, such as AWS Direct Connect. The hybrid cloud model allows the company to keep sensitive data on-premises for regulatory compliance while leveraging AWS's scalability and pay-per-use pricing for non-production workloads. The key enabler is the private, low-latency connection that securely transfers data between the two environments, which is a hallmark of hybrid cloud architecture.

Exam trap

The trap here is that candidates often confuse hybrid cloud with multi-cloud, but hybrid cloud specifically refers to a mix of on-premises and public cloud (or private and public cloud), whereas multi-cloud involves using multiple public cloud providers without any on-premises component.

How to eliminate wrong answers

Option A is wrong because a public cloud model would involve running all workloads, including the core banking application, on AWS infrastructure, which contradicts the requirement that the application cannot be migrated to the cloud. Option B is wrong because a private cloud model would mean the company runs its own cloud environment, either on-premises or hosted exclusively for its use, but the scenario explicitly uses AWS public cloud services for development and test environments, not a private cloud. Option D is wrong because a multi-cloud model involves using multiple public cloud providers (e.g., AWS and Azure), but the scenario only uses AWS alongside on-premises infrastructure, not multiple public clouds.

Practice this question →

152

MCQmedium

A company's architecture team is evaluating their multi-tier application against the AWS Well-Architected Framework. They discover that their database has no backup and recovery procedure. Which pillar does this finding fall under?

A.Security

B.Operational Excellence

C.Reliability

D.Cost Optimization

AnswerC

Reliability covers recovery from failure, including data protection through backups. A database without backup violates Reliability — the system cannot recover from data loss.

Why this answer

The Reliability pillar of the AWS Well-Architected Framework focuses on ensuring that workloads can recover from infrastructure or service disruptions, acquire computing resources to meet demand, and mitigate transient or persistent failures. A database without a backup and recovery procedure directly violates the 'Backup and Restore' design principle, which is a core component of reliability because it ensures data durability and the ability to restore operations after a failure. Without backups, any data corruption or loss event would result in permanent data loss, making the system unreliable.

Exam trap

The trap here is that candidates often confuse the lack of a backup procedure with a Security issue (data protection) or an Operational Excellence issue (process gap), but the AWS Well-Architected Framework explicitly places backup and recovery under the Reliability pillar because it directly impacts the workload's ability to recover from failure.

How to eliminate wrong answers

Option A is wrong because the Security pillar focuses on protecting data, systems, and assets through access control, encryption, and threat detection, not on the ability to recover from failures. Option B is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value, and while it includes incident response, the lack of a backup procedure is a fundamental reliability concern, not an operational runbook gap. Option D is wrong because Cost Optimization focuses on avoiding unnecessary costs and matching supply with demand, and while backups incur storage costs, the absence of a backup procedure is a reliability risk, not a cost-saving measure.

Practice this question →

153

MCQmedium

A company runs a batch processing job on a single Amazon EC2 instance. The job takes 10 hours to complete. The company needs to reduce the processing time to under 1 hour to meet a new business requirement. The data can be split into independent chunks that can be processed in parallel. Which cloud computing concept would most directly enable the company to achieve this goal?

A.Elasticity

B.High availability

C.Scalability

D.Fault tolerance

AnswerC

Scalability is the ability to increase resources (scale up or out) to handle growing workloads or to reduce task completion times. By splitting the data into independent chunks and processing them in parallel across multiple EC2 instances, the company horizontally scales its compute capacity, directly reducing the job time from 10 hours to under 1 hour.

Why this answer

Scalability is the correct answer because it refers to the ability to increase resources to handle increased load. By scaling horizontally (adding more EC2 instances) and processing the independent data chunks in parallel, the batch job can be completed in under 1 hour instead of 10 hours.

Exam trap

The trap here is that candidates confuse elasticity with scalability, but elasticity is about automatic resource adjustment to match fluctuating demand, not about adding resources to meet a fixed performance goal.

How to eliminate wrong answers

Option A is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which is not the primary concept needed here; the requirement is to add enough resources to achieve a specific performance target, not to dynamically adjust. Option B is wrong because high availability focuses on ensuring the system remains operational and accessible despite failures, typically through redundancy across Availability Zones, which does not directly reduce processing time for a batch job.

Practice this question →

154

MCQeasy

Amazon CloudFront serves cached content to users from the closest possible network point, with over 400 such points globally. What are these network points called?

A.Availability Zones

B.AWS Regions

C.Edge Locations

D.Local Zones

AnswerC

Edge locations are the 400+ points of presence in CloudFront's CDN. They cache content locally so users receive it from the nearest possible server, minimising latency.

Why this answer

Amazon CloudFront uses a global network of edge locations to cache and serve content to users with low latency. These edge locations are distinct from AWS Regions and Availability Zones, as they are specifically designed for content delivery rather than compute or storage. Option C correctly identifies these network points as Edge Locations.

Exam trap

The trap here is that candidates often confuse Edge Locations with Availability Zones or Local Zones, assuming all AWS infrastructure points are similar, but CloudFront's edge locations are a separate global network optimized for content delivery, not for running general AWS services.

How to eliminate wrong answers

Option A is wrong because Availability Zones are isolated data centers within an AWS Region, used for high availability of compute and storage resources, not for content caching at the network edge. Option B is wrong because AWS Regions are geographic areas containing multiple Availability Zones, designed for resource deployment and not for serving cached content from the closest point to users. Option D is wrong because Local Zones are extensions of AWS Regions that place compute, storage, and database services closer to end users for latency-sensitive applications, but they are not the primary points for CloudFront's content caching.

Practice this question →

155

MCQmedium

A marketing company is launching a new campaign that will require a temporary increase in web server capacity. The operations team provisions an additional 10 Amazon EC2 instances through the AWS Management Console within five minutes, without needing to submit a purchase order or wait for hardware delivery. Which advantage of cloud computing does this scenario best demonstrate?

A.Benefit from massive economies of scale

B.Trade capital expense for variable expense

C.Increase speed and agility

D.Stop spending money on running and maintaining data centers

AnswerC

Increasing speed and agility means that IT resources can be provisioned in minutes, allowing organizations to respond swiftly to new requirements without the delays of traditional procurement and hardware setup. This directly matches the scenario.

Why this answer

Option C is correct because the scenario highlights how cloud computing enables rapid provisioning of resources—10 EC2 instances in five minutes—without the delays of procurement or hardware setup. This directly demonstrates increased speed and agility, a core advantage of cloud computing that allows businesses to experiment and scale quickly.

Exam trap

The trap here is that candidates may confuse 'speed and agility' with 'economies of scale' or 'variable expense,' but the key differentiator is the rapid provisioning without procurement delays, not cost structure or provider scale.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost benefits from massive provider infrastructure, not the speed of provisioning. Option B is wrong because trading capital expense for variable expense relates to paying for only what you use (e.g., per-hour billing), not the rapid deployment described. Option D is wrong because stopping spending on data centers addresses reduced operational overhead, not the temporary capacity increase or provisioning speed.

Practice this question →

156

MCQhard

A company is designing a microservices architecture on AWS. According to the AWS Well-Architected Framework's Operational Excellence pillar, which practice best supports the ability to safely make frequent, small changes to production?

A.Performing large batch deployments monthly to minimize change frequency

B.Making frequent, small, reversible changes through automated CI/CD pipelines

C.Requiring manual approval for every code change

D.Deploying all microservices simultaneously in coordinated releases

AnswerB

The Operational Excellence pillar explicitly recommends frequent, small, reversible changes via automation to reduce risk, enable faster rollback, and improve deployment confidence.

Why this answer

Option B is correct because the Operational Excellence pillar emphasizes the ability to make frequent, small, reversible changes to reduce the blast radius of failures and enable rapid recovery. Automated CI/CD pipelines enforce consistent deployment practices, allowing teams to safely iterate on production with minimal risk. This approach aligns with the principle of 'perform operations as code' and supports the 'make frequent, small, reversible changes' design principle.

Exam trap

The trap here is that candidates may confuse 'operational excellence' with 'security' or 'cost optimization' and choose manual approval (Option C) thinking it adds safety, but the Well-Architected Framework explicitly advocates for automation over manual gates to enable safe, high-velocity changes.

How to eliminate wrong answers

Option A is wrong because performing large batch deployments monthly increases the risk of complex failures and violates the principle of making small, reversible changes; it also delays feedback loops. Option C is wrong because requiring manual approval for every code change introduces bottlenecks and slows down the deployment cadence, contradicting the goal of frequent, small changes. Option D is wrong because deploying all microservices simultaneously in coordinated releases creates tight coupling and increases the blast radius of any failure, undermining the independence and resilience that microservices are meant to provide.

Practice this question →

157

MCQeasy

An e-commerce company runs its website on Amazon EC2. During normal operation, 10 instances are sufficient. During a major sale event, traffic increases 20x and the Auto Scaling group automatically adds 190 additional instances within minutes. After the sale, the instances are terminated. Which cloud computing characteristic does this behaviour demonstrate?

A.Resource pooling

B.On-demand self-service

C.Broad network access

D.Rapid elasticity

AnswerD

Rapid elasticity describes the ability to provision resources quickly to scale out during demand spikes and release them when demand drops. Auto Scaling adding hundreds of instances in minutes and terminating them after the event is the classic example.

Why this answer

D is correct because the ability to automatically scale from 10 to 200 instances within minutes and then terminate them after the sale demonstrates rapid elasticity. This characteristic allows cloud resources to be provisioned and released elastically, often automatically, to scale rapidly outward and inward commensurate with demand. AWS Auto Scaling groups achieve this by using launch configurations, scaling policies, and CloudWatch alarms to dynamically adjust the EC2 instance count based on real-time metrics like CPU utilization or request count.

Exam trap

The trap here is that candidates often confuse rapid elasticity with on-demand self-service, but the key differentiator is the speed and automatic nature of scaling in response to demand, not the ability to provision resources without human interaction.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's computing resources being pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to demand; it does not describe the rapid scaling of instances for a single customer's workload. Option B is wrong because on-demand self-service means a customer can provision computing capabilities unilaterally without requiring human interaction with each service provider, typically via a web console or API; while the scaling is automated, the key behavior here is the speed and elasticity of scaling, not the self-service provisioning model. Option C is wrong because broad network access means resources are available over the network and accessed through standard mechanisms (e.g., HTTP, HTTPS, SSH) that promote use by heterogeneous client platforms (e.g., mobile phones, laptops); this characteristic is unrelated to the dynamic scaling of compute capacity.

Practice this question →

158

MCQeasy

A company's marketing team needs a temporary compute environment to run a one-week data analysis for a campaign. The developer uses the AWS CLI to automatically provision an Amazon EC2 instance and an Amazon RDS database without any manual approval or interaction from the AWS support team. This ability to provision resources automatically without requiring human interaction from the cloud provider best demonstrates which essential characteristic of cloud computing?

A.Broad network access

B.On-demand self-service

C.Resource pooling

D.Rapid elasticity

AnswerB

Correct. On-demand self-service allows users to provision and manage computing resources as needed automatically, without requiring human interaction with the cloud provider. The developer used the AWS CLI to provision resources without contacting AWS support, matching this characteristic.

Why this answer

The scenario describes a developer using the AWS CLI to provision an EC2 instance and an RDS database without any manual approval or interaction from AWS support. This ability to automatically obtain and configure computing resources as needed, without requiring human intervention from the provider, is the defining characteristic of on-demand self-service. It allows users to provision and manage resources through a self-service interface (like the AWS Management Console, CLI, or SDKs) at any time, without needing to submit a request to AWS staff.

Exam trap

The trap here is that candidates often confuse 'rapid elasticity' with the ability to provision resources on demand, but rapid elasticity specifically refers to the speed of scaling (up/down) in response to workload changes, not the self-service provisioning mechanism itself.

How to eliminate wrong answers

Option A is wrong because broad network access refers to resources being accessible over the network via standard protocols (e.g., HTTP, SSH, RDP) from a wide range of devices (laptops, phones, etc.), not to the ability to provision resources without human interaction. Option C is wrong because resource pooling describes the provider's multi-tenant model where computing resources are pooled to serve multiple customers, with physical and virtual resources dynamically assigned and reassigned according to demand; it does not relate to the user's ability to self-provision. Option D is wrong because rapid elasticity is the ability to quickly scale resources up or down based on demand, often automatically, but the core characteristic demonstrated here is the self-service provisioning aspect, not the scaling speed or automatic adjustment.

Practice this question →

159

MCQmedium

A company runs a customer-facing web application with an Amazon RDS database. Initially, the database is deployed as a single instance in one Availability Zone (AZ). A power outage occurs in that AZ, causing the database to become unavailable for several hours. After the incident, the company modifies the database to use a Multi-AZ configuration. Shortly after the change, another power outage affects the same primary AZ. This time, the database automatically fails over to the standby instance in the other AZ without any manual intervention, and the application remains available. Which cloud computing concept does this scenario best demonstrate?

A.Elasticity

B.Fault tolerance

C.Scalability

D.Resource pooling

AnswerB

Fault tolerance is the correct concept. The Multi-AZ RDS configuration allows the database to automatically fail over to a standby instance in a different Availability Zone when the primary fails. This ensures continuous operation despite a component failure, which is the definition of fault tolerance.

Why this answer

Fault tolerance is the ability of a system to continue operating without interruption when one or more of its components fail. In this scenario, the Multi-AZ RDS deployment automatically failed over to a standby instance in a different Availability Zone when the primary AZ experienced a power outage, ensuring the application remained available without manual intervention. This demonstrates fault tolerance because the system was designed to withstand the failure of an entire AZ and continue functioning.

Exam trap

The trap here is that candidates often confuse fault tolerance with high availability or elasticity, but fault tolerance specifically implies zero downtime during a failure, whereas high availability may involve a brief interruption, and elasticity is about scaling, not failure recovery.

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; the scenario describes a failover event, not a scaling event. Option C is wrong because scalability is the ability to handle increased load by adding resources, whereas the scenario focuses on maintaining availability during a failure, not on handling more traffic. Option D is wrong because resource pooling is a multi-tenant model where computing resources are pooled to serve multiple customers, which is unrelated to the failover behavior described.

Practice this question →

160

MCQmedium

A company is deploying a web application on AWS. The application will run on multiple Amazon EC2 instances distributed across two Availability Zones. An Application Load Balancer will distribute incoming traffic across the instances. The company's primary goal is to ensure the application remains available to users even if one Availability Zone experiences a service disruption. Which cloud computing concept does this architecture primarily demonstrate?

A.Elasticity

B.Scalability

C.High availability

D.Fault tolerance

AnswerC

High availability ensures that applications remain operational with minimal downtime by using redundant components across multiple Availability Zones and a load balancer. This directly matches the company's goal of remaining available even if one zone fails. This option is correct.

Why this answer

This architecture demonstrates high availability because it uses multiple EC2 instances across two Availability Zones with an Application Load Balancer to distribute traffic. If one AZ fails, the load balancer automatically routes traffic to the healthy instances in the other AZ, ensuring the application remains accessible. High availability focuses on minimizing downtime by eliminating single points of failure through redundancy.

Exam trap

The trap here is that candidates confuse high availability with elasticity or scalability, but the key differentiator is that high availability focuses on redundancy and fault tolerance to prevent downtime, not on dynamic resource adjustment or handling increased load.

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 uptime during an AZ failure. Option B is wrong because scalability is the capacity to handle increased load by adding resources, whereas the scenario specifically addresses fault tolerance and continuous availability during a disruption.

Practice this question →

161

MCQmedium

A company runs a critical web application on a single Amazon EC2 instance in a single Availability Zone. The company wants to design the architecture so that the application continues to operate even if the physical server hosting the instance fails. Which AWS Cloud concept does this design objective primarily address?

A.Elasticity

B.Scalability

C.Fault tolerance

D.Cost optimization

AnswerC

Fault tolerance is the correct concept. The objective is to remain operational despite a hardware failure. AWS supports this by allowing resources to be deployed across multiple isolated Availability Zones, so a failure in one zone does not affect instances in another.

Why this answer

Fault tolerance is the correct concept because the design objective is to ensure continuous operation despite the failure of a physical server hosting the EC2 instance. This is achieved by deploying the application across multiple Availability Zones (AZs) using an Auto Scaling group and an Elastic Load Balancer, so that if one instance or AZ fails, traffic is automatically routed to healthy instances in another AZ. The scenario explicitly focuses on surviving infrastructure failure, which is the core definition of fault tolerance.

Exam trap

The trap here is that candidates often confuse fault tolerance with high availability (HA), but the question specifically asks for the concept that ensures operation despite a physical server failure, which is fault tolerance, not just HA.

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 a physical server failure. Option B is wrong because scalability is the capability to handle increased load by adding resources, which does not inherently ensure continued operation during a failure.

Practice this question →

162

MCQhard

According to the AWS Well-Architected Framework, which pillar focuses on the ability to run workloads effectively, gain insight into operations, and continuously improve processes?

A.Reliability

B.Performance Efficiency

C.Operational Excellence

D.Sustainability

AnswerC

Operational Excellence covers running workloads effectively and continuously improving operations.

Why this answer

Operational Excellence is the AWS Well-Architected pillar that focuses on running and monitoring workloads to deliver business value, and on continually improving processes and procedures. It includes the ability to run workloads effectively, gain operational insight through metrics and logs (e.g., Amazon CloudWatch, AWS CloudTrail), and use runbooks and automation (e.g., AWS Systems Manager) to continuously improve. This directly matches the question's description of running workloads effectively, gaining insight into operations, and continuously improving processes.

Exam trap

AWS often tests candidates by making them confuse Operational Excellence with Reliability, because both involve 'running workloads,' but Reliability is about fault tolerance and recovery, not about gaining insight or improving processes.

How to eliminate wrong answers

Option A is wrong because Reliability focuses on a workload's ability to recover from infrastructure or service disruptions, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues—not on operational insight or process improvement. Option B is wrong because Performance Efficiency focuses on using computing resources efficiently to meet system requirements, and maintaining that efficiency as demand changes and technologies evolve—it does not address gaining operational insight or continuously improving processes. Option D is wrong because Sustainability focuses on minimizing the environmental impact of running cloud workloads, including energy consumption and efficiency across compute, storage, and networking—it does not cover operational insight or process improvement.

Practice this question →

163

MCQmedium

A consulting firm has a global team of consultants who frequently travel to client sites. The firm hosts its critical business applications on AWS. The consultants need to access these applications from various locations (hotels, airports, client offices) using a variety of devices, including company laptops, personal smartphones, and tablets. They connect using standard web browsers and internet connections. This ability to access the same cloud resources from anywhere using different devices is an example of 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 that resources are available over the network and can be accessed by standard mechanisms from any heterogeneous client platform (e.g., mobile phones, tablets, laptops). This matches the scenario where multiple types of devices access the applications from various locations.

Why this answer

The scenario describes consultants accessing the same cloud-hosted applications from different locations (hotels, airports, client offices) using various devices (laptops, smartphones, tablets) over standard internet connections. This directly matches the 'broad network access' characteristic, which means resources are available over the network and can be accessed by heterogeneous client platforms (e.g., mobile phones, laptops, workstations) using standard protocols (HTTP/HTTPS, TLS).

Exam trap

The trap here is that candidates confuse 'broad network access' (access from anywhere using standard protocols) with 'on-demand self-service' (the ability to provision resources without human intervention), because both involve user-initiated actions, but the former is about network reachability and device heterogeneity, while the latter is about automated resource provisioning.

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., spin up EC2 instances) automatically without requiring human interaction with the service provider, not the ability to access applications from multiple devices. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned to serve multiple customers, not the client-side access flexibility. Option D is wrong because rapid elasticity is the ability to scale resources up or down quickly in response to demand (e.g., auto-scaling groups), not the capability to access the same application from different devices and locations.

Practice this question →

164

MCQmedium

Which AWS Well-Architected Framework pillar includes recommendations for using a mix of purchase options and rightsizing instances to optimize costs?

A.Operational Excellence

B.Performance Efficiency

C.Cost Optimization

D.Reliability

AnswerC

The Cost Optimization pillar covers right-sizing, instance purchase options (Reserved, Spot, Savings Plans), eliminating waste, and using consumption-based pricing.

Why this answer

Option C is correct because the Cost Optimization pillar of the AWS Well-Architected Framework specifically includes guidance on using a mix of purchase options (e.g., Reserved Instances, Savings Plans, Spot Instances) and rightsizing instances (e.g., selecting the correct instance family and size based on utilization metrics) to reduce overall spending while maintaining performance. This pillar focuses on avoiding unnecessary costs and aligning expenditure with business needs.

Exam trap

The trap here is that candidates often confuse the Cost Optimization pillar with the Performance Efficiency pillar, mistakenly thinking that rightsizing is about improving performance rather than reducing costs, or they associate purchase options with Operational Excellence due to the 'planning' aspect.

How to eliminate wrong answers

Option A is wrong because the Operational Excellence pillar focuses on running and monitoring systems to deliver business value, and on continually improving processes and procedures, not on cost optimization strategies like purchase options or rightsizing. Option B is wrong because the Performance Efficiency pillar deals with using computing resources efficiently to meet system requirements, and maintaining that efficiency as demand changes and technologies evolve, not on cost-saving tactics. Option D is wrong because the Reliability pillar concerns a workload's ability to perform its intended function correctly and consistently when expected, including recovery from failures and meeting demand, not on optimizing costs through purchasing or sizing decisions.

Practice this question →

165

MCQmedium

A company migrates its workloads to AWS. After the migration, the company receives a monthly invoice that shows precise charges for each service used, such as the exact number of Amazon EC2 instance hours consumed and the amount of data stored in Amazon S3. The company uses this detailed usage data to allocate costs to different departments. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.Broad network access

B.Resource pooling

C.Measured service

D.Rapid elasticity

AnswerC

Measured service is the correct answer. 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). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer. This allows the company to receive a detailed invoice and perform cost allocation.

Why this answer

The scenario describes how the cloud provider meters and reports usage (e.g., EC2 instance hours, S3 storage amounts) and then bills precisely based on that consumption. This is the definition of 'measured service' — one of the five essential characteristics of cloud computing (NIST SP 800-145), where resource usage is monitored, controlled, and reported, providing transparency for both the provider and consumer.

Exam trap

The trap here is that candidates confuse 'resource pooling' (the multi-tenant sharing of infrastructure) with the ability to see and allocate granular usage costs, but measured service is specifically about metering and billing transparency, not how resources are shared.

How to eliminate wrong answers

Option A is wrong because 'broad network access' refers to resources being available over the network via standard mechanisms (e.g., HTTP, SSH) from various devices (mobile, laptops, workstations), not to billing or usage metering. Option B is wrong because 'resource pooling' describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the ability to see detailed per-service charges for cost allocation.

Practice this question →

166

MCQmedium

A retail company runs a web application on Amazon EC2 instances behind an Application Load Balancer. During a promotional event, traffic spikes to 10 times the normal level. The company configured an Amazon EC2 Auto Scaling group with a scaling policy that adds instances when CPU utilization exceeds 70% and removes instances when it drops below 30%. The application handles the spike without any manual intervention, and after the event ends, the number of instances automatically decreases to the original count, saving costs. This scenario best demonstrates which cloud computing concept?

A.Elasticity

B.Scalability

C.High availability

D.Fault tolerance

AnswerA

Correct. Elasticity is the ability to automatically scale computing resources up and down based on demand, which is exactly what the Auto Scaling group does during the traffic spike and subsequent drop.

Why this answer

The scenario describes the system automatically scaling out to 10 times the normal capacity during a traffic spike and then scaling back down when the spike ends, which is the definition of elasticity—the ability to dynamically provision and de-provision resources to match demand. The use of an EC2 Auto Scaling group with a CPU-based scaling policy (70% threshold to add, 30% to remove) directly demonstrates this cloud computing concept, as it handles variable workloads without manual intervention and optimizes cost by reducing resources when they are no longer needed.

Exam trap

The trap here is that candidates often confuse scalability with elasticity, but scalability only implies the ability to grow (scale up/out), while elasticity explicitly includes the ability to shrink (scale down/in) to match demand and optimize costs.

How to eliminate wrong answers

Option B (Scalability) is wrong because scalability refers to the ability to increase capacity to handle growth, but it does not inherently include the ability to scale down (de-provision) 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 application remains accessible despite failures, typically through redundancy across multiple Availability Zones or health checks, not on dynamic resource adjustment based on load. Option D (Fault tolerance) is wrong because fault tolerance is the ability of a system to continue operating without interruption when one or more components fail, which is not demonstrated by the automatic scaling in response to CPU utilization changes.

Practice this question →

167

MCQmedium

A startup company is developing a new mobile application. The development team needs to quickly provision and tear down test environments to experiment with different backend configurations. They want to try new features, run performance tests for a few hours, and then delete all resources without any upfront commitment. They only pay for the compute and storage resources consumed during each test. Which benefit of cloud computing does this scenario BEST represent?

A.Agility

B.Elasticity

C.High availability

D.Fault tolerance

AnswerA

Correct. Agility in the cloud allows organizations to quickly provision and decommission resources, enabling rapid experimentation and innovation without long-term commitments.

Why this answer

The scenario describes provisioning test environments on demand, running experiments for a few hours, and then tearing everything down with no upfront commitment. This directly maps to agility—the cloud's ability to rapidly create, modify, and delete resources to adapt to changing business or technical needs. The pay-as-you-go model further reinforces agility by removing the need for long-term contracts or hardware procurement.

Exam trap

The trap here is confusing agility (the ability to rapidly provision and deprovision resources for experimentation) with elasticity (automatic scaling based on load), which is a common misconception because both involve dynamic resource management but serve fundamentally different purposes.

How to eliminate wrong answers

Option B (Elasticity) is wrong because elasticity refers to automatically scaling resources up or down in response to real-time demand (e.g., adding EC2 instances during a traffic spike), not the ability to quickly provision and tear down entire test environments for experimentation. Option C (High availability) is wrong because high availability focuses on keeping applications running continuously despite failures, typically through redundant infrastructure across multiple Availability Zones, which is unrelated to the temporary test environment lifecycle described. Option D (Fault tolerance) is wrong because fault tolerance ensures zero downtime by masking component failures (e.g., active-passive failover with synchronous replication), whereas the scenario emphasizes rapid creation and deletion of resources, not resilience to failures.

Practice this question →

168

MCQmedium

A company is migrating its customer-facing web application to AWS. The Chief Information Security Officer (CISO) is reviewing the division of security responsibilities. The CISO understands that AWS is responsible for the security of the physical data centers, hardware, and network infrastructure. The company, as the customer, is responsible for securing the application code, customer data, and operating system patches on Amazon EC2 instances. This division of security responsibilities is an example of which fundamental cloud computing concept?

A.Resource pooling

B.Shared responsibility model

C.Elasticity

D.Measured service

AnswerB

The shared responsibility model clearly delineates between AWS's responsibility for the security of the underlying cloud infrastructure and the customer's responsibility for securing their data, applications, and configurations. This is the correct concept described in the scenario.

Why this answer

The correct answer is B, the shared responsibility model. This model delineates security obligations between AWS and the customer: AWS secures the cloud infrastructure (physical data centers, hardware, network), while the customer secures what is in the cloud (application code, customer data, OS patches on EC2 instances). The scenario directly describes this division, making it a textbook example of the shared responsibility model.

Exam trap

The trap here is that candidates confuse the shared responsibility model with elasticity or resource pooling, because all three are fundamental cloud concepts, but only the shared responsibility model defines security ownership boundaries.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the multi-tenant model where AWS dynamically assigns and reassigns physical and virtual resources to serve multiple customers, not the division of security responsibilities. Option C is wrong because elasticity is the ability to automatically scale resources up or down based on demand, which is unrelated to the security responsibility split described in the question.

Practice this question →

169

MCQmedium

A global gaming company needs to deploy its application in multiple geographic locations to reduce latency for players worldwide. The application must also remain available even if an entire data center fails. The company plans to run the application on Amazon EC2 instances behind an Application Load Balancer. Which combination of AWS global infrastructure components should the company use to meet these requirements?

A.Deploy the application in a single AWS Region across multiple Availability Zones and use Amazon Route 53 with latency-based routing.

B.Deploy the application in a single AWS Region within a single Availability Zone and use Amazon CloudFront for content caching.

C.Deploy the application in multiple AWS Regions, each with at least two Availability Zones, and use Amazon Route 53 for DNS-based routing.

D.Deploy the application in multiple AWS Regions and use Amazon CloudFront with multiple origins, each pointing to an Application Load Balancer in a single Availability Zone.

AnswerC

Multiple AWS Regions provide geographic distribution to reduce latency globally. Using multiple Availability Zones within each Region ensures that the application remains available if an entire data center (one Availability Zone) fails. Amazon Route 53 can route users to the nearest healthy Region, meeting both requirements.

Why this answer

Option C is correct because deploying the application in multiple AWS Regions, each with at least two Availability Zones, ensures global low latency by placing compute resources closer to players worldwide, while the multi-AZ architecture within each Region provides high availability even if an entire data center (Availability Zone) fails. Amazon Route 53 then enables DNS-based routing (e.g., latency-based or geolocation routing) to direct player traffic to the optimal Region, meeting both latency and fault tolerance requirements.

Exam trap

The trap here is that candidates often confuse high availability within a single Region (multi-AZ) with global low latency, mistakenly thinking that multiple Availability Zones alone solve latency for global users, or that CloudFront caching alone provides application-level fault tolerance.

How to eliminate wrong answers

Option A is wrong because deploying in a single AWS Region, even across multiple Availability Zones, cannot reduce latency for players globally—players far from that Region will experience high latency. Option B is wrong because deploying in a single Availability Zone within a single Region provides no fault tolerance against an entire data center failure, and Amazon CloudFront caching alone does not ensure application availability if the origin fails. Option D is wrong because using only a single Availability Zone per Region creates a single point of failure within each Region, violating the requirement that the application remain available even if an entire data center fails.

Practice this question →

170

MCQeasy

A company has a strict data residency policy that requires all customer data to remain stored on-premises at all times. However, the company experiences unpredictable spikes in compute demand and wants to use an AWS cloud environment to handle this additional workload during peak periods. The company needs a solution that allows them to seamlessly run applications across their on-premises infrastructure and AWS, using consistent management tools and APIs. The company also needs a dedicated, private network connection between the two environments for low latency and security. Which cloud deployment model best describes this architecture?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Community cloud

AnswerC

A hybrid cloud deployment connects on-premises infrastructure (private cloud) with public cloud services (like AWS) using a secure network connection. This model enables the organization to keep sensitive data on-premises while using AWS for scalable compute capacity during peak demand, meeting both the data residency requirement and the need for burst capacity.

Why this answer

Option C is correct because the architecture described combines on-premises infrastructure with AWS cloud resources, connected via a dedicated private network (likely AWS Direct Connect or VPN), while using consistent management tools and APIs. This is the defining characteristic of a hybrid cloud model, which enables workload portability and unified operations across both environments.

Exam trap

The trap here is that candidates may confuse hybrid cloud with public cloud, overlooking the critical requirement for a dedicated private connection and on-premises data residency, which hybrid cloud uniquely satisfies.

How to eliminate wrong answers

Option A is wrong because a public cloud model would involve running all workloads on AWS infrastructure shared with other customers, which violates the strict data residency policy requiring customer data to remain on-premises at all times. Option B is wrong because a private cloud model is dedicated to a single organization but typically resides entirely within the organization's own data center or a hosted facility, failing to address the need to burst compute demand to a separate AWS environment.

Practice this question →

171

MCQmedium

A social media company hosts a web application on AWS that serves millions of users worldwide. The application delivers static content such as images, videos, and CSS files. To improve load times for users in different geographic regions, the company wants to cache this content at AWS locations that are as close to end users as possible. Which component of the AWS global infrastructure should the company use?

A.Availability Zones

B.Edge Locations

C.Regional Edge Caches

D.AWS Direct Connect Locations

AnswerB

Edge Locations are a global network of data centers used by Amazon CloudFront to cache copies of content closer to users. By serving content from the nearest edge location, the company reduces latency and improves load times for static assets. This is the correct solution for the described requirement.

Why this answer

Edge Locations are part of the AWS CloudFront content delivery network (CDN) and are specifically designed to cache static content (e.g., images, videos, CSS) at geographically dispersed points of presence (PoPs) close to end users. This reduces latency by serving content from the nearest edge location rather than the origin server, directly addressing the requirement to improve load times for a global user base.

Exam trap

The trap here is that candidates often confuse Regional Edge Caches (which are a mid-tier cache layer) with Edge Locations (the user-facing cache), leading them to select Option C instead of B, even though the question explicitly asks for the component 'closest to end users.'

How to eliminate wrong answers

Option A is wrong because Availability Zones are distinct, isolated locations within an AWS Region that provide high availability and fault tolerance for compute and storage resources, not for caching content at edge locations close to users. Option C is wrong because Regional Edge Caches are a layer of caching between origin servers and Edge Locations, used to reduce load on the origin for less-frequently accessed content, but they are not the closest to end users; Edge Locations are the primary cache layer for user-facing content. Option D is wrong because AWS Direct Connect Locations are physical co-location facilities where customers establish dedicated network connections to AWS, not for caching or content delivery.

Practice this question →

172

MCQmedium

A company wants to minimise the environmental impact of their AWS workloads by choosing the right instance sizes, maximising utilisation, using graviton processors for better performance per watt, and designing architectures that reduce total compute needed. Which AWS Well-Architected Framework pillar guides these decisions?

A.Cost Optimisation

B.Performance Efficiency

C.Sustainability

D.Reliability

AnswerC

The Sustainability pillar focuses on minimising the environmental impact of running cloud workloads. This includes maximising instance utilisation, using energy-efficient hardware (like Graviton), and eliminating unnecessary compute.

Why this answer

The Sustainability pillar of the AWS Well-Architected Framework focuses on minimizing the environmental impact of cloud workloads. Choosing right-sized instances, maximizing utilization, using Graviton processors for better performance per watt, and designing architectures to reduce total compute directly align with sustainability goals by reducing energy consumption and carbon footprint.

Exam trap

The trap here is that candidates may confuse the Sustainability pillar with Cost Optimization because both involve reducing waste, but Sustainability specifically targets environmental impact and energy efficiency, not just financial savings.

How to eliminate wrong answers

Option A is wrong because Cost Optimization focuses on reducing costs and avoiding unnecessary spending, not specifically on environmental impact or performance per watt. Option B is wrong because Performance Efficiency focuses on using computing resources efficiently to meet system requirements, but it does not explicitly address environmental sustainability or carbon footprint reduction. Option D is wrong because Reliability focuses on ensuring workloads perform their intended functions correctly and consistently, not on minimizing environmental impact through instance sizing or processor choice.

Practice this question →

173

MCQmedium

According to the AWS Shared Responsibility Model, which of the following is the customer's responsibility when using AWS Lambda?

A.Patching the Lambda execution environment and runtime

B.Managing the underlying servers that run Lambda functions

C.Writing secure function code and managing IAM permissions for the function

D.Ensuring Lambda scales automatically during traffic spikes

AnswerC

Customers are responsible for their function's code quality and security, the IAM role permissions granted to the function, and the security of data processed by the function.

Why this answer

Under the AWS Shared Responsibility Model, AWS manages the security of the cloud, including the Lambda execution environment, runtime, and underlying servers. The customer is responsible for security in the cloud, which includes writing secure function code and managing IAM permissions to control access to the function and its resources. Option C correctly identifies this customer responsibility.

Exam trap

The trap here is that candidates may confuse operational responsibilities (like patching or scaling) with customer responsibilities, assuming they must manage runtime updates or scaling configuration, when in fact AWS handles these automatically for Lambda.

How to eliminate wrong answers

Option A is wrong because AWS is responsible for patching the Lambda execution environment and runtime, not the customer. Option B is wrong because AWS manages the underlying servers that run Lambda functions as part of the infrastructure-as-a-service abstraction. Option D is wrong because AWS automatically scales Lambda functions in response to traffic spikes; the customer does not need to manage scaling.

Practice this question →

174

MCQmedium

An enterprise is planning their cloud adoption strategy. They want to understand how cloud adoption typically progresses. Which framework provides a structured approach to cloud adoption organized around business, people, governance, platform, security, and operations perspectives?

A.AWS Well-Architected Framework

B.AWS Cloud Adoption Framework (CAF)

C.AWS Migration Hub

D.AWS Trusted Advisor

AnswerB

CAF organizes cloud adoption guidance into six perspectives (Business, People, Governance, Platform, Security, Operations) for different stakeholders at different stages of adoption.

Why this answer

The AWS Cloud Adoption Framework (CAF) is specifically designed to guide organizations through their cloud adoption journey by providing structured guidance across six core perspectives: Business, People, Governance, Platform, Security, and Operations. Unlike the Well-Architected Framework, which focuses on architectural best practices for building workloads, the CAF addresses the broader organizational and process changes needed for successful cloud adoption.

Exam trap

The trap here is that candidates often confuse the AWS Well-Architected Framework (which deals with workload architecture) with the AWS Cloud Adoption Framework (which deals with organizational adoption strategy), because both use the term 'framework' and address multiple perspectives, but they serve fundamentally different purposes.

How to eliminate wrong answers

Option A is wrong because the AWS Well-Architected Framework is focused on evaluating and improving cloud workload architectures based on six pillars (Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability), not on organizing cloud adoption around business, people, governance, platform, security, and operations perspectives. 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, not a framework for structuring the overall cloud adoption strategy. 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, fault tolerance, and service limits, not a framework for guiding cloud adoption from a business and organizational perspective.

Practice this question →

175

MCQeasy

A financial institution has regulatory requirements to store sensitive customer data on-premises in its own data center. However, it wants to use AWS for compute-intensive analytics that need to access this data. The company plans to establish a dedicated, encrypted network connection between its data center and AWS. Which cloud deployment model does this scenario describe?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Multi-cloud

AnswerC

Correct. Hybrid cloud is the integration of on-premises infrastructure (private cloud) with public cloud services. The company keeps sensitive data on-premises and extends compute capabilities to AWS, connected via a dedicated encrypted link, which is a classic hybrid cloud architecture.

Why this answer

This scenario describes a hybrid cloud deployment model because it combines on-premises infrastructure (the financial institution's own data center for storing sensitive customer data) with AWS public cloud resources (for compute-intensive analytics). The dedicated, encrypted network connection (such as AWS Direct Connect with IPSec or a VPN) securely bridges the two environments, allowing data to be accessed from AWS without being stored there, which meets regulatory requirements. Hybrid cloud is defined as a mixed computing environment where on-premises and public cloud resources are orchestrated together, often via a private network link.

Exam trap

The trap here is that candidates often confuse 'hybrid cloud' with 'multi-cloud' or 'private cloud,' but hybrid cloud specifically requires a mix of on-premises and public cloud resources connected via a private network, not just any combination of cloud providers or exclusive use of a single cloud.

How to eliminate wrong answers

Option A is wrong because public cloud refers to resources owned and operated by a third-party provider (like AWS) and accessible over the public internet, without any on-premises infrastructure integration; this scenario explicitly requires on-premises data storage. Option B is wrong because private cloud involves dedicated cloud infrastructure used exclusively by a single organization, typically hosted on-premises or by a third-party provider, but it does not involve a hybrid mix of on-premises and public cloud; here, the compute is on AWS (public cloud), not a private cloud. Option D is wrong because multi-cloud refers to using multiple public cloud providers (e.g., AWS and Azure) simultaneously, not a combination of on-premises and a single public cloud; this scenario uses only AWS for compute, not multiple public clouds.

Practice this question →

176

Matchingmedium

Match each AWS pricing concept to its definition.

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

Concepts

Matches

Pay for compute capacity by the hour/second

Significant discount for 1-3 year commitment

Unused EC2 capacity at steep discount

Flexible pricing model for compute usage

Limited free usage for new customers

Why these pairings

Understanding pricing helps optimize costs.

Practice this question →

177

MCQmedium

A financial institution runs its core banking application on-premises due to regulatory requirements. It has connected its data centre to AWS using AWS Direct Connect and runs analytics workloads on AWS that access data from the on-premises systems. Which cloud deployment model does this describe?

A.Public cloud

B.Hybrid cloud

C.Private cloud

D.Multi-cloud

AnswerB

Hybrid cloud integrates on-premises or private cloud infrastructure with public cloud resources. Running core systems on-premises while using AWS for analytics, connected via Direct Connect, is textbook hybrid cloud.

Why this answer

This scenario describes a hybrid cloud deployment because the financial institution maintains its core banking application on an on-premises data center (private infrastructure) while also running analytics workloads on AWS (public cloud). The two environments are connected via AWS Direct Connect, a dedicated network link that enables secure, low-latency data transfer between the on-premises systems and AWS, allowing the analytics workloads to access on-premises data. Hybrid cloud specifically refers to the integration of on-premises private infrastructure with public cloud services, which matches this setup.

Exam trap

The trap here is that candidates may confuse hybrid cloud with multi-cloud, mistakenly thinking that using any cloud alongside on-premises is multi-cloud, but multi-cloud specifically requires the use of multiple distinct public cloud providers, not a mix of on-premises and a single public cloud.

How to eliminate wrong answers

Option A is wrong because a public cloud deployment would mean all workloads and data reside solely on AWS infrastructure, but here the core banking application remains on-premises. Option C is wrong because a private cloud deployment would involve dedicated cloud infrastructure used exclusively by the institution, either on-premises or hosted, but the analytics workloads run on AWS, which is a shared public cloud environment. Option D is wrong because multi-cloud involves using multiple public cloud providers (e.g., AWS and Azure), but this scenario uses only AWS alongside on-premises infrastructure, not multiple public clouds.

Practice this question →

178

MCQmedium

A startup is deploying a web application on Amazon EC2 instances across multiple Availability Zones (AZs). The architecture must ensure that the application remains fully operational and available to users even if one entire AZ fails. Which cloud computing concept does this requirement MOST directly represent?

A.Elasticity

B.Fault tolerance

C.Scalability

D.Resource pooling

AnswerB

Correct. Fault tolerance describes a system that continues operating without interruption despite the failure of one or more components. Distributing workloads across multiple Availability Zones is a key method to achieve fault tolerance in AWS.

Why this answer

Fault tolerance is the correct concept because the requirement specifies that the application must remain fully operational and available even if an entire Availability Zone fails. By deploying EC2 instances across multiple AZs and using an Elastic Load Balancer to distribute traffic, the architecture can withstand the failure of one AZ without any interruption in service, which is the essence of fault tolerance.

Exam trap

The trap here is that candidates often confuse fault tolerance with high availability, but fault tolerance specifically implies zero downtime and no data loss during a failure, whereas high availability may allow for brief interruptions or degraded performance.

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 operation during a failure. Option C is wrong because scalability is the ability to handle increased load by adding resources, not the ability to survive a component failure. Option D is wrong because resource pooling is a characteristic of cloud computing where computing resources are pooled to serve multiple customers, not a mechanism for ensuring availability during an AZ failure.

Practice this question →

179

MCQmedium

According to the AWS Shared Responsibility Model, which of the following is AWS responsible for?

A.Encrypting customer data stored in Amazon S3

B.Configuring security groups for EC2 instances

C.Physical security of data center facilities

D.Managing IAM user access policies

AnswerC

AWS is fully responsible for the physical security of its data centers — customers have no access or control over this layer.

Why this answer

AWS is responsible for the physical security of data center facilities, including access controls, surveillance, and environmental systems. This is a foundational component of the Shared Responsibility Model, where AWS secures the infrastructure that runs all AWS services, while the customer secures their data and configurations within those services.

Exam trap

The trap here is that candidates confuse AWS's responsibility for providing security features (like encryption or IAM) with the customer's responsibility to configure and manage those features, leading them to select options like A, B, or D instead of the correct physical security answer.

How to eliminate wrong answers

Option A is wrong because encrypting customer data stored in Amazon S3 is a customer responsibility; AWS provides server-side encryption (SSE-S3, SSE-KMS, SSE-C) as features, but the customer must enable and manage the encryption keys and policies. Option B is wrong because configuring security groups for EC2 instances is a customer responsibility; security groups act as virtual firewalls that the customer defines to control inbound and outbound traffic. Option D is wrong because managing IAM user access policies is a customer responsibility; AWS provides the IAM service, but the customer creates and manages users, groups, roles, and policies to control access to their resources.

Practice this question →

180

MCQmedium

A company wants to allow its developers to provision virtual servers in AWS without needing to submit a ticket to an IT administrator or wait for manual approval. The developers need to be able to spin up instances directly from the AWS Management Console, CLI, or SDKs, and the resources should be available immediately after the request is submitted. Which essential characteristic of cloud computing does this scenario best describe?

A.Rapid elasticity

B.On-demand self-service

C.Resource pooling

D.Measured service

AnswerB

Correct. On-demand self-service allows consumers to unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider.

Why this answer

The scenario describes developers provisioning virtual servers directly from the AWS Management Console, CLI, or SDKs without manual intervention or approval. This aligns with the on-demand self-service characteristic of cloud computing, where users can provision computing resources automatically as needed without requiring human interaction with the service provider. The key is that the resources are available immediately after the request, which is the hallmark of self-service, not elasticity.

Exam trap

The trap here is that candidates confuse 'immediate availability' with 'rapid elasticity,' but rapid elasticity is about scaling existing resources up/down automatically, not about the initial provisioning workflow without manual 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 resources without manual approval. Option C is wrong because resource pooling describes the provider's multi-tenant model where physical and virtual resources are dynamically assigned to multiple consumers, which is unrelated to the self-provisioning workflow. Option D is wrong because measured service involves metering and billing for resource usage (e.g., pay-per-use), which does not address the lack of manual approval or immediate availability.

Practice this question →

181

MCQmedium

A development team is building a web application and wants to minimize operational overhead. The team wants to focus solely on writing and deploying code without managing the underlying operating system, runtime, or middleware. The team needs the ability to simply upload their application code and have it run, with the cloud provider automatically handling capacity provisioning, load balancing, and patching of the platform. Which cloud computing service model best describes this approach?

A.Infrastructure as a Service (IaaS)

B.Platform as a Service (PaaS)

C.Software as a Service (SaaS)

D.Function as a Service (FaaS)

AnswerB

PaaS offers a managed platform where the provider handles the operating system, runtime, and middleware. Developers can upload code and let the provider manage capacity and patching, matching the team's requirement to minimize overhead.

Why this answer

Platform as a Service (PaaS) is the correct model because it abstracts the underlying infrastructure, runtime, and middleware, allowing the team to simply upload code and have it executed. The cloud provider automatically handles capacity provisioning, load balancing, and patching, which directly matches the requirement to minimize operational overhead by focusing solely on code.

Exam trap

The trap here is that candidates often confuse PaaS with FaaS, mistakenly thinking that serverless functions (FaaS) inherently include full web application hosting with load balancing and capacity provisioning, whereas FaaS is event-driven and typically requires additional services (e.g., API Gateway, auto-scaling configuration) to achieve the same level of abstraction as PaaS.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) provides virtualized compute, storage, and networking resources, but the team would still need to manage the operating system, runtime, and middleware, which contradicts the goal of minimizing operational overhead. Option C is wrong because Software as a Service (SaaS) delivers a fully managed application to end users, not a platform for the team to deploy and run their own custom code. Option D is wrong because Function as a Service (FaaS) is a subset of serverless computing that runs individual functions in response to events, but it does not inherently provide a full platform for deploying a web application with built-in load balancing and capacity provisioning; the team would need to assemble additional services for those capabilities.

Practice this question →

182

MCQeasy

A startup can now test a new application idea by provisioning cloud resources in minutes, run the experiment for a week, and tear down the resources if the idea fails — spending only a few dollars. Previously, the same experiment would have required months of procurement and significant capital expenditure. Which cloud benefit does this illustrate?

A.Economies of scale

B.Elimination of capital expense

C.Global reach

D.Increased agility

AnswerD

Agility is the cloud benefit that allows organisations to experiment quickly with minimal investment. Provisioning resources in minutes, experimenting for a week, and discarding failures cost-effectively exemplifies cloud agility.

Why this answer

Option D is correct because the scenario describes the ability to rapidly provision, experiment with, and decommission cloud resources in minutes, which directly illustrates increased agility. Agility in cloud computing refers to the speed at which resources can be deployed, scaled, and released, enabling fast experimentation without long procurement cycles.

Exam trap

The trap here is that candidates often confuse 'elimination of capital expense' (Option B) with agility, but the question explicitly highlights speed and experimentation, not cost savings from CapEx to OpEx conversion.

How to eliminate wrong answers

Option A is wrong because economies of scale refer to cost advantages from large-scale operations (e.g., AWS buying hardware in bulk), not the ability to quickly provision and tear down resources. Option B is wrong because elimination of capital expense (CapEx) is a benefit of converting upfront hardware costs to variable operational expenses (OpEx), but the question focuses on speed and flexibility, not cost structure. Option C is wrong because global reach describes deploying resources in multiple geographic regions to reduce latency, not the rapid provisioning and decommissioning of resources for experimentation.

Practice this question →

183

MCQmedium

A company operates a social media analytics platform that runs on AWS. The platform experiences unpredictable traffic spikes during major events. The company wants to ensure that compute capacity automatically increases during these spikes without any manual intervention, and decreases when traffic subsides to avoid paying for idle resources. Which characteristic of cloud computing does this business requirement directly rely on?

A.On-demand self-service

B.Broad network access

C.Rapid elasticity

D.Resource pooling

AnswerC

Rapid elasticity is the cloud characteristic that enables resources to be provisioned and released automatically, quickly scaling out during demand spikes and scaling in when demand drops. This directly satisfies the requirement for automatic capacity adjustment and cost optimization.

Why this answer

The requirement to automatically scale compute capacity up during traffic spikes and down when traffic subsides directly relies on rapid elasticity, a key characteristic of cloud computing defined by the NIST SP 800-145 standard. Rapid elasticity enables resources to be provisioned and released elastically, often automatically, to match demand at any scale, which is essential for handling unpredictable traffic on a social media analytics platform without manual intervention.

Exam trap

The trap here is that candidates often confuse on-demand self-service with automatic scaling, but on-demand self-service only covers the ability to manually request resources at any time, not the automatic, elastic adjustment of capacity based on real-time demand.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user's ability to provision computing resources (e.g., EC2 instances) unilaterally via a web console or API without requiring human interaction with the provider, but it does not inherently include automatic scaling based on load; it requires manual action or additional services like Auto Scaling to achieve elasticity. Option B is wrong because broad network access describes the ability of resources to be accessed over the network by standard protocols (e.g., HTTPS, SSH) from heterogeneous client platforms (e.g., mobile, laptops), which is unrelated to the automatic scaling of compute capacity in response to traffic spikes.

Practice this question →

184

MCQmedium

A company is migrating its on-premises application to AWS. The application currently runs on a single server and experiences occasional traffic spikes that cause performance degradation. The company wants to take advantage of cloud computing benefits to handle these spikes automatically without manual intervention. Which AWS Cloud concept would directly address this requirement?

A.Elasticity

B.High availability

C.Fault tolerance

D.Durability

AnswerA

Elasticity allows AWS resources to automatically scale in response to changing demand. This directly meets the requirement of handling traffic spikes without manual intervention.

Why this answer

Elasticity is the correct concept because it refers to the ability of an AWS infrastructure to automatically scale resources up or down based on demand. In this scenario, the company needs to handle occasional traffic spikes without manual intervention, which is directly addressed by AWS Auto Scaling groups and services like Amazon EC2 Auto Scaling or AWS Lambda's concurrency scaling. This ensures that additional compute capacity is provisioned during spikes and released when demand decreases, optimizing both performance and cost.

Exam trap

The trap here is that candidates often confuse elasticity with high availability or fault tolerance, mistakenly thinking that any redundancy or failover mechanism automatically handles traffic spikes, but elasticity specifically addresses dynamic scaling to match demand, not just maintaining uptime during failures.

How to eliminate wrong answers

Option B (High availability) is wrong because high availability focuses on ensuring that an application remains accessible and operational during failures, typically through redundancy across multiple Availability Zones, not on automatically handling traffic spikes. Option C (Fault tolerance) is wrong because fault tolerance is designed to keep an application running without interruption even when components fail, often requiring redundant systems that can take over instantly, which is a different concern than scaling to meet variable demand. Neither high availability nor fault tolerance directly addresses the need to automatically scale resources in response to traffic spikes.

Practice this question →

185

MCQeasy

A company wants to deploy their application to users in North America, Europe, and Asia Pacific to reduce latency. Using AWS, they can provision infrastructure in new geographic regions within minutes using the same tools and templates. Which cloud benefit does this illustrate?

A.Increased agility

B.Trade capital expense for variable expense

C.Go global in minutes

D.Stop guessing about capacity

AnswerC

AWS's global infrastructure lets companies deploy to any of its regions worldwide rapidly using automation. Expanding to three continents using the same CloudFormation templates is the 'go global in minutes' benefit.

Why this answer

Option C is correct because the scenario describes deploying infrastructure across multiple geographic regions (North America, Europe, Asia Pacific) using the same tools and templates, which directly illustrates the 'Go global in minutes' benefit of AWS. This benefit leverages AWS's global infrastructure—such as Regions, Availability Zones, and CloudFront edge locations—to reduce latency for users worldwide without the need to negotiate with data center providers or build physical facilities.

Exam trap

The trap here is that candidates confuse 'increased agility' (rapid provisioning of resources in general) with the specific ability to deploy globally in minutes, but the question explicitly mentions geographic regions and latency reduction, which maps directly to the 'Go global in minutes' benefit.

How to eliminate wrong answers

Option A is wrong because 'increased agility' refers to the ability to quickly experiment, iterate, and provision resources on demand (e.g., launching EC2 instances in minutes), not specifically to deploying across multiple geographic regions. Option B is wrong because 'trade capital expense for variable expense' describes the shift from upfront hardware purchases to pay-as-you-go pricing (e.g., paying per hour for compute), which is unrelated to geographic distribution. Option D is wrong because 'stop guessing about capacity' relates to auto-scaling and elasticity to match demand (e.g., using Amazon EC2 Auto Scaling), not to deploying infrastructure in new regions to reduce latency.

Practice this question →

186

MCQmedium

A company is evaluating a move to the AWS Cloud. The finance team learns that AWS can offer lower per-unit prices for compute and storage because AWS purchases hardware in very large volumes and operates at a massive scale. This cost advantage, which is then passed on to customers, is a direct benefit of which fundamental cloud computing concept?

A.Elasticity

B.Economies of scale

C.High availability

D.Resource pooling

AnswerB

Correct. Economies of scale occur when AWS purchases large volumes of hardware and negotiates better prices from suppliers, then passes these savings to customers through lower service pricing.

Why this answer

The scenario describes AWS leveraging its massive purchasing power to negotiate lower hardware costs, which are then passed to customers as lower per-unit prices. This is the direct definition of economies of scale, a fundamental cloud concept where average costs decrease as the scale of operations increases. Elasticity, high availability, and resource pooling are distinct concepts that do not inherently create the cost advantage described.

Exam trap

The trap here is that candidates confuse 'resource pooling' (multi-tenancy) with 'economies of scale,' but resource pooling is about sharing infrastructure to increase utilization, not about the direct cost reduction from bulk hardware purchasing.

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 the cost advantage gained from bulk purchasing. Option C is wrong because high availability ensures that applications remain accessible despite failures, typically through redundancy across Availability Zones, and does not address hardware procurement cost savings. Option D is wrong because resource pooling allows multiple customers to share the same physical infrastructure, which improves utilization but does not directly explain the lower per-unit hardware costs from volume purchasing.

Practice this question →

187

MCQmedium

A company runs multiple containerized applications on a single Amazon ECS cluster using AWS Fargate. The company's compliance team asks whether sharing the same underlying physical hardware with other AWS customers introduces security risks. The company explains that AWS isolates each customer's compute environment, even though resources are drawn from a shared pool. Which essential characteristic of cloud computing does this arrangement best illustrate?

A.Rapid elasticity

B.Resource pooling

C.Measured service

D.On-demand self-service

AnswerB

Resource pooling is the correct answer. AWS pools its compute resources across many customers and uses virtualization to isolate each customer's workloads. This allows AWS to serve multiple customers efficiently while maintaining security and isolation.

Why this answer

Resource pooling is the cloud characteristic where a provider's computing resources are pooled to serve multiple customers using a multi-tenant model, with physical and virtual resources dynamically assigned and reassigned according to consumer demand. AWS Fargate abstracts the underlying infrastructure, so even though containers run on shared physical hardware, each customer's compute environment is isolated at the hypervisor and kernel level. This arrangement directly illustrates resource pooling because the provider manages the shared pool while ensuring logical separation between tenants.

Exam trap

The trap here is that candidates confuse 'resource pooling' with 'rapid elasticity' because both involve shared resources, but resource pooling is about multi-tenant isolation while elasticity is about 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 to the isolation of shared infrastructure. Option C is wrong because measured service involves metering and billing for resource usage (e.g., per-second billing for Fargate tasks), not the multi-tenant sharing of physical hardware. Option D is wrong because on-demand self-service describes a customer's ability to provision resources without human interaction, not the underlying pooling and isolation of compute environments.

Practice this question →

188

MCQhard

A customer is evaluating moving to AWS and asks about the total cost of ownership (TCO) benefits. Which of the following is NOT a factor that reduces TCO when migrating to AWS?

A.Eliminating hardware refresh cycles

B.Reducing data center facility costs

C.Staff training costs for cloud technologies

D.Pay-as-you-go pricing model

AnswerC

Staff training is an upfront cost of migration that may increase TCO initially, not reduce it.

Why this answer

Option C is correct because staff training costs for cloud technologies are an additional investment required when migrating to AWS, not a factor that reduces total cost of ownership (TCO). While AWS reduces hardware and facility costs, training represents a new expense for upskilling teams on cloud services like EC2, S3, and IAM, which increases rather than decreases TCO.

Exam trap

The trap here is that candidates may mistakenly view staff training as a cost-saving measure (e.g., reducing need for specialized on-premises administrators), but the question specifically asks for factors that reduce TCO, and training is an added cost, not a reduction.

How to eliminate wrong answers

Option A is wrong because eliminating hardware refresh cycles directly reduces TCO by removing the need to purchase new servers, storage, and networking equipment every 3-5 years, which is a core benefit of moving to AWS's virtualized infrastructure. Option B is wrong because reducing data center facility costs (e.g., power, cooling, physical security, real estate) is a key TCO reduction when migrating to AWS, as the customer no longer operates their own on-premises data centers. Option D is wrong because the pay-as-you-go pricing model reduces TCO by allowing customers to pay only for consumed resources (e.g., per-hour EC2 instances, per-GB S3 storage) instead of over-provisioning for peak capacity, eliminating idle resource waste.

Practice this question →

189

MCQmedium

A solutions architect implements IAM least-privilege policies, enables encryption for all data at rest and in transit, configures VPC security groups and NACLs to limit network access, and sets up automated security incident detection. Which Well-Architected Framework pillar covers these activities?

A.Operational Excellence

B.Reliability

C.Security

D.Cost Optimisation

AnswerC

The Security pillar encompasses identity and access management, detective controls, infrastructure protection, data protection, and incident response — all of which the architect is implementing.

Why this answer

The Security pillar of the AWS Well-Architected Framework focuses on protecting data, systems, and assets through identity and access management (IAM least-privilege policies), data protection (encryption at rest and in transit), infrastructure protection (VPC security groups and NACLs), and detective controls (automated security incident detection). These activities directly map to the Security pillar's design principles and best practices.

Exam trap

The trap here is that candidates may confuse the Security pillar with Operational Excellence because both involve monitoring and automation, but Security specifically addresses data protection, identity, and network controls, not operational runbooks or deployment pipelines.

How to eliminate wrong answers

Option A is wrong because Operational Excellence focuses on running and monitoring systems to deliver business value, including operations as code and incident response, not on implementing IAM policies, encryption, or network access controls. Option B is wrong because Reliability focuses on ensuring a workload performs its intended function correctly and consistently, including recovery planning and scaling, not on security controls like encryption or least-privilege access. Option D is wrong because Cost Optimisation focuses on avoiding unnecessary costs, such as right-sizing resources and using Reserved Instances, not on security configurations like NACLs or encryption.

Practice this question →

190

MCQmedium

A company's development team frequently needs temporary test environments. A developer can log into the AWS Management Console, select an Amazon EC2 instance type, configure storage, and launch the instance within minutes without any interaction with the IT infrastructure team. This capability is an example of which essential characteristic of cloud computing?

A.Resource pooling

B.On-demand self-service

C.Measured service

D.Rapid elasticity

AnswerB

Correct. On-demand self-service means a user can provision computing capabilities automatically without requiring human interaction with the service provider. The developer using the AWS Management Console to launch an EC2 instance without contacting IT perfectly illustrates this characteristic.

Why this answer

The scenario describes a developer independently provisioning EC2 instances without requiring IT intervention. This directly matches the 'on-demand self-service' characteristic of cloud computing, where users can provision computing resources as needed automatically, without requiring human interaction with each service provider.

Exam trap

The trap here is confusing 'rapid elasticity' (the ability to scale resources quickly) with 'on-demand self-service' (the ability to provision resources without human intervention), as both involve speed but address different aspects of cloud computing.

How to eliminate wrong answers

Option A is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, not the user's ability to self-provision. Option C is wrong because measured service involves metering and reporting resource usage for billing and optimization, not the act of provisioning. Option D is wrong because rapid elasticity describes the ability to scale resources up or down quickly in response to demand, not the self-service provisioning capability.

Practice this question →

191

MCQeasy

A small startup wants to launch a new application on AWS without any upfront investment in servers. Which cloud computing deployment model allows them to use AWS infrastructure without owning any physical hardware?

A.Private cloud

B.Hybrid cloud

C.Public cloud

D.Community cloud

AnswerC

Public cloud (AWS) provides on-demand infrastructure over the internet with no upfront hardware investment — resources are shared, provisioned in minutes, and billed per use.

Why this answer

The public cloud deployment model, such as AWS, provides on-demand access to shared computing resources over the internet, allowing the startup to provision virtual servers (e.g., EC2 instances) and other services without any upfront capital expenditure or ownership of physical hardware. This model is ideal for startups because it offers a pay-as-you-go pricing structure, eliminating the need for server procurement, maintenance, and data center management.

Exam trap

The trap here is that candidates often confuse 'public cloud' with 'hybrid cloud' because they think hybrid also avoids hardware ownership, but hybrid typically requires some on-premises or dedicated infrastructure, failing the 'no physical hardware' condition.

How to eliminate wrong answers

Option A is wrong because a private cloud involves dedicated infrastructure for a single organization, often requiring upfront investment in physical hardware or leased colocation space, which contradicts the 'no upfront investment' requirement. Option B is wrong because a hybrid cloud combines public and private clouds, and while it can reduce some hardware costs, it still typically involves owning or leasing private infrastructure, failing to meet the 'no physical hardware' condition. Option D is wrong because a community cloud is shared by several organizations with common concerns (e.g., compliance), but it still usually requires participants to invest in or manage physical infrastructure, not eliminating upfront hardware costs.

Practice this question →

192

MCQeasy

Which cloud computing characteristic allows a company to pay only for the compute resources they actually use, without upfront commitments?

A.High availability

B.Elasticity

C.Pay-as-you-go pricing

D.Economies of scale

AnswerC

Pay-as-you-go eliminates upfront commitments, charging only for resources consumed — a core advantage of cloud computing.

Why this answer

Option C is correct because pay-as-you-go pricing is the cloud computing characteristic that enables a company to pay only for the compute resources they actually consume, with no upfront commitments or long-term contracts. This model aligns costs directly with usage, allowing organizations to avoid capital expenditure and scale spending based on demand. AWS implements this through services like EC2 On-Demand instances, where billing is per second (or per hour) with no minimum purchase required.

Exam trap

The trap here is that candidates often confuse elasticity (the ability to scale) with the pricing model itself, assuming that scaling automatically means pay-per-use, but elasticity is about resource adjustment while pay-as-you-go is the billing mechanism that charges only for consumed resources.

How to eliminate wrong answers

Option A is wrong because high availability refers to the ability of a system to remain operational and accessible despite failures, typically achieved through redundancy across multiple Availability Zones, not a pricing or payment model. Option B is wrong because elasticity describes the ability to automatically scale resources up or down based on demand, which affects cost efficiency but does not itself define the payment structure of paying only for what is used. Option D is wrong because economies of scale is a cost advantage that AWS passes to customers due to its massive infrastructure purchasing power, resulting in lower variable costs, but it is not a direct billing mechanism that allows pay-per-use without upfront commitments.

Practice this question →

193

MCQmedium

A company runs a critical e-commerce application on a single Amazon EC2 instance in one Availability Zone. The company wants to ensure that if the entire Availability Zone becomes unavailable, the application continues to run without manual intervention. Which AWS cloud concept best describes this requirement?

A.Scalability

B.High availability

C.Elasticity

D.Disaster recovery

AnswerB

High availability ensures that the system remains operational even when components fail, such as an entire Availability Zone, by designing with redundancy and automatic failover.

Why this answer

High availability (B) is the correct concept because it ensures that an application remains operational even when an entire Availability Zone fails. By deploying the EC2 instance across multiple Availability Zones (e.g., using an Auto Scaling group with a minimum of two instances and an Application Load Balancer), the application can automatically fail over to a healthy instance in another zone without manual intervention. This directly addresses the requirement for continuous operation during a zone outage.

Exam trap

The trap here is that candidates often confuse high availability with disaster recovery, but high availability focuses on automatic, immediate failover within a region (e.g., across Availability Zones), while disaster recovery involves restoring services after a major disruption, often with recovery time objectives (RTOs) measured in minutes or hours.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources based on demand, not to maintain uptime during a zone failure. Option C is wrong because elasticity is the ability to dynamically scale resources up or down automatically, which does not inherently provide fault tolerance across Availability Zones. Option D is wrong because disaster recovery involves restoring systems after a catastrophic event (e.g., region-wide failure) and typically requires manual steps or complex automation, not the automatic, immediate failover that high availability provides.

Practice this question →

194

MCQmedium

A company is migrating its on-premises applications to the AWS Cloud. The Chief Security Officer wants to confirm the division of security responsibilities. According to the AWS Shared Responsibility Model, which of the following tasks is the customer's responsibility?

A.Ensuring the physical security of AWS data centers

B.Patching the hypervisor layer that runs Amazon EC2 instances

C.Managing network access control lists (ACLs) for the customer's VPC

D.Replacing defective hardware components in the AWS global infrastructure

AnswerC

Network ACLs are stateless firewall rules that control inbound and outbound traffic at the subnet level within a VPC. Configuring and managing these rules is the customer's responsibility as part of managing security in the cloud.

Why this answer

Option C is correct because managing network access control lists (ACLs) for a customer's VPC is explicitly a customer responsibility under the AWS Shared Responsibility Model. Customers control inbound and outbound traffic at the subnet level by configuring NACLs, which are stateless firewall rules. AWS provides the infrastructure and the VPC service, but the customer must define and manage the ACL rules to enforce network segmentation and security.

Exam trap

The trap here is that candidates often confuse the customer's responsibility for managing network ACLs with AWS's responsibility for managing the underlying network infrastructure, such as the hypervisor or physical hardware, leading them to incorrectly select options A, B, or D.

How to eliminate wrong answers

Option A is wrong because ensuring the physical security of AWS data centers is AWS's responsibility, not the customer's; AWS implements physical controls such as biometric access, surveillance, and security guards. Option B is wrong because patching the hypervisor layer that runs Amazon EC2 instances is AWS's responsibility, as the hypervisor is part of the virtualized infrastructure managed by AWS. Option D is wrong because replacing defective hardware components in the AWS global infrastructure is AWS's responsibility, as they manage the underlying hardware, including servers, storage, and networking gear.

Practice this question →

195

MCQmedium

A company runs an e-commerce application on AWS that experiences unpredictable traffic spikes during flash sales. The application currently runs on a fixed number of Amazon EC2 instances, which leads to performance degradation during spikes and wasted capacity during low traffic. The company wants to automatically adjust the number of instances based on real-time demand, only paying for the resources it uses. This need best represents which cloud computing concept?

A.High availability

B.Elasticity

C.Fault tolerance

D.Durability

AnswerB

Correct. Elasticity refers to the ability to dynamically provision and de-provision resources to match workload changes. This scenario describes exactly that: automatically increasing instances during spikes and decreasing them during low traffic to optimize cost and performance.

Why this answer

Option B (Elasticity) is correct because the scenario describes automatically scaling EC2 instances up and down based on real-time demand, which is the definition of elasticity in cloud computing. AWS Auto Scaling and Amazon EC2 Auto Scaling groups enable this by adding or removing instances in response to CloudWatch metrics, ensuring the application only pays for resources consumed during traffic spikes and low traffic periods.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that adding more instances automatically ensures uptime, but elasticity is specifically about dynamic scaling to match demand, not about redundancy or failure recovery.

How to eliminate wrong answers

Option A (High availability) is wrong because it focuses on ensuring the application remains accessible despite failures, typically through multi-AZ deployments and load balancing, not on dynamically adjusting capacity based on demand. Option C (Fault tolerance) is wrong because it refers to the ability of a system to continue operating without interruption when a component fails, often using redundant resources, not on scaling resources to match variable load. Option D (Durability) is wrong because it concerns the long-term preservation of data, such as through replication in Amazon S3 (99.999999999% durability), and has no relation to adjusting compute capacity for traffic spikes.

Practice this question →

196

MCQmedium

A company is designing a critical web application that must remain available even if an entire data center goes offline due to a power outage. The application will run on Amazon EC2 instances in the us-east-1 Region. Which AWS infrastructure strategy should the company use to meet this high-availability requirement?

A.Launch all EC2 instances in a single Availability Zone to ensure low latency between instances.

B.Deploy the EC2 instances across two or more Availability Zones within the us-east-1 Region.

C.Deploy the EC2 instances in multiple AWS Regions, such as us-east-1 and eu-west-1.

D.Use separate AWS accounts for each EC2 instance to isolate the workload from a data center failure.

AnswerB

This is correct. Availability Zones are physically separate data centers within a Region. Running instances in multiple AZs ensures that the application remains available if one AZ goes offline, because the other AZs continue operating. This is a standard best practice for high availability.

Why this answer

Option B is correct because deploying EC2 instances across two or more Availability Zones (AZs) within a single AWS Region protects against an entire data center failure. Each AZ is physically separated, with independent power, cooling, and networking, so if one AZ goes offline, the application continues running in the other AZs. This design meets the high-availability requirement without the complexity and latency of multi-Region deployment.

Exam trap

The trap here is that candidates often confuse Availability Zones with Regions, thinking that multi-Region deployment is required for high availability, when in fact deploying across multiple AZs within a single Region is sufficient and more cost-effective for surviving a data center failure.

How to eliminate wrong answers

Option A is wrong because launching all EC2 instances in a single Availability Zone creates a single point of failure; if that data center experiences a power outage, the entire application becomes unavailable. Option C is wrong because deploying across multiple Regions (e.g., us-east-1 and eu-west-1) is overkill for this requirement—it introduces cross-Region latency, higher costs, and complexity, while the question only requires surviving a single data center failure within us-east-1. Option D is wrong because separate AWS accounts do not provide any physical infrastructure isolation; they are a billing and security boundary, not a mechanism to survive a data center outage.

Practice this question →

197

MCQeasy

A company's sales team uses a cloud-based CRM application. Sales representatives access the CRM from their laptops in the office, from tablets at customer sites, and from their smartphones while traveling, all over the internet. The application works consistently across all devices without requiring any custom client software on each device. Which essential characteristic of cloud computing does this scenario BEST demonstrate?

A.On-demand self-service

B.Resource pooling

C.Broad network access

D.Measured service

AnswerC

This is correct. Broad network access is the ability to access cloud services over the network using standard protocols (e.g., HTTP/HTTPS) from a variety of client devices such as laptops, tablets, and smartphones. The sales team accessing the CRM from different devices via the internet is a textbook example.

Why this answer

The scenario describes sales representatives accessing the CRM application from laptops, tablets, and smartphones over the internet without needing custom client software. This directly illustrates broad network access, which is the cloud computing characteristic that resources are available over the network and can be accessed by standard mechanisms (e.g., HTTPS, REST APIs) from a wide range of heterogeneous client platforms (e.g., mobile phones, tablets, laptops). The consistent experience across devices without custom software is the hallmark of broad network access.

Exam trap

The trap here is that candidates often confuse broad network access with on-demand self-service because both involve user interaction, but broad network access specifically focuses on the variety of client platforms and network-based accessibility, not the ability to self-provision resources.

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., spin up a virtual machine) automatically without requiring human interaction with the service provider, not the ability to access an application from multiple device types. Option B 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 client device diversity or network-based access. Option D is wrong because measured service involves the provider's ability to monitor, control, and report resource usage (e.g., metering CPU hours, bandwidth) for billing and optimization, not the capability to access services from various devices over the internet.

Practice this question →

198

MCQmedium

A company operates a seasonal e-commerce website. During holiday sales, traffic can increase by 500% within minutes. The company uses AWS Auto Scaling to automatically add Amazon EC2 instances when CPU utilization exceeds a threshold and remove instances during off-peak hours. The company pays only for the compute capacity it actually consumes, with no upfront commitment. This scenario best demonstrates which essential characteristics of cloud computing?

A.Rapid elasticity and measured service

B.On-demand self-service and broad network access

C.Resource pooling and high availability

D.Fault tolerance and disaster recovery

AnswerA

Correct. Rapid elasticity allows automatic scaling of resources in response to demand changes, as shown by adding and removing instances. Measured service means the provider meters usage and charges only for consumed resources – the company pays only for actual compute capacity.

Why this answer

The scenario demonstrates rapid elasticity because the Auto Scaling group can instantly add hundreds of EC2 instances to handle a 500% traffic surge, and then remove them when demand drops. It also demonstrates measured service because the company pays only for the compute capacity actually consumed, with no upfront commitment, which is metered and billed based on usage.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with 'high availability' or 'fault tolerance,' because both involve adding resources, but elasticity specifically refers to scaling up/down based on demand, not maintaining uptime during failures.

How to eliminate wrong answers

Option B is wrong because on-demand self-service refers to users provisioning resources without human interaction (e.g., via AWS Management Console or API), and broad network access refers to resources accessible over the network via standard protocols (e.g., HTTPS, SSH); neither is the primary focus of the auto-scaling and pay-per-use behavior described. Option C is wrong because resource pooling refers to multi-tenant sharing of physical infrastructure across customers, and high availability refers to systems remaining operational despite failures; the scenario does not mention multi-tenancy or fault-tolerant architecture. Option D is wrong because fault tolerance and disaster recovery involve designing systems to withstand component failures or catastrophic events (e.g., multi-AZ deployments, backups); the scenario only describes scaling based on demand and pay-per-use, not resilience or recovery.

Practice this question →

199

MCQmedium

A company uses AWS to host its web application. The company's IT manager learns that multiple AWS customers may have virtual machines running on the same physical server within an AWS data center. However, the manager is confident that each customer's data is securely isolated from others and that customers have no visibility into or control over the underlying physical infrastructure. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.Rapid elasticity

B.Resource pooling

C.On-demand self-service

D.Measured service

AnswerB

Resource pooling is the cloud characteristic 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. The customer generally has no control or knowledge over the exact location of the resources. This matches the scenario exactly.

Why this answer

Resource pooling is the correct answer because it describes the cloud characteristic where the provider's computing resources (such as physical servers) are pooled to serve multiple customers using a multi-tenant model. AWS uses hypervisor-based isolation (e.g., Xen or Nitro) to ensure that each customer's virtual machine has no visibility into or control over the underlying physical hardware or other tenants' workloads, while still sharing the same physical server. This directly matches the scenario's description of multiple customers running VMs on the same physical host with secure isolation.

Exam trap

The trap here is that candidates often confuse resource pooling with multi-tenancy or security isolation, but the exam specifically tests the definition of resource pooling as the provider's ability to serve multiple customers from the same physical infrastructure while maintaining logical 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 sharing of physical infrastructure among multiple customers. Option C is wrong because on-demand self-service describes a user's ability to provision computing capabilities without requiring human interaction with the service provider, not the multi-tenant isolation of physical resources. Option D is wrong because measured service involves the metering and billing of cloud resource usage (e.g., pay-per-use), not the pooling and isolation of physical hardware across tenants.

Practice this question →

200

MCQmedium

A startup is considering moving its infrastructure to AWS. The CTO explains that AWS can offer lower pay-as-you-go prices than what the startup would pay for equivalent on-premises hardware because AWS aggregates usage from millions of customers. Which benefit of the AWS Cloud does this scenario describe?

A.Elasticity

B.High availability

C.Economies of scale

D.Global reach

AnswerC

Economies of scale occur when the per-unit cost of delivering a service decreases as the total volume of service delivery increases. AWS's massive customer base allows it to achieve lower infrastructure costs and pass those savings to customers through lower pay-as-you-go prices.

Why this answer

The scenario describes economies of scale, a core AWS Cloud benefit where AWS aggregates compute and storage usage from millions of customers, allowing it to purchase hardware in bulk at significantly lower per-unit costs. These savings are passed on to customers as lower pay-as-you-go prices compared to what a startup would pay for equivalent on-premises hardware. This is a fundamental economic advantage of cloud computing, distinct from operational benefits like elasticity or high availability.

Exam trap

The trap here is that candidates often confuse economies of scale with elasticity, thinking that lower prices come from scaling resources dynamically, when in fact economies of scale is a separate economic benefit driven by AWS's massive customer base and bulk purchasing power.

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 advantage from aggregated purchasing. Option B is wrong because high availability ensures applications remain accessible during failures through redundancy across Availability Zones, which is a design principle, not a pricing benefit from customer aggregation. Option D is wrong because global reach describes the ability to deploy resources in multiple geographic regions worldwide, not the cost savings from AWS's bulk hardware procurement.

Practice this question →

201

MCQmedium

A company runs a retail website on AWS. During a promotional event, the website's traffic spikes from 1,000 concurrent users to 100,000 concurrent users in under 5 minutes. The AWS infrastructure automatically provisions additional Amazon EC2 instances to handle the increased load and terminates them when the event ends. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.On-demand self-service

B.Broad network access

C.Rapid elasticity

D.Resource pooling

AnswerC

Rapid elasticity is the ability to quickly and automatically scale resources up and down in response to fluctuating demand. The automatic addition and removal of EC2 instances during a traffic spike perfectly illustrates this characteristic, as the system adapts to the workload in near real-time.

Why this answer

The scenario describes the automatic scaling of EC2 instances from 1,000 to 100,000 concurrent users in under 5 minutes, and then terminating them when the event ends. This directly demonstrates rapid elasticity, which is the ability to provision and release cloud resources quickly and automatically in response to demand, a core characteristic defined by the NIST SP 800-145 standard.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with 'on-demand self-service' because both involve provisioning resources without manual intervention, but on-demand self-service is about the user's ability to provision resources on their own, while rapid elasticity is about the system automatically scaling resources up and down to meet demand.

How to eliminate wrong answers

Option A is wrong because on-demand self-service refers to a user provisioning compute resources without requiring human interaction with the service provider, not the automatic scaling of resources based on load. Option B is wrong because broad network access describes capabilities being available over the network and accessed through standard mechanisms (e.g., HTTPS, SSH), not the dynamic scaling of capacity. Option D is wrong because resource pooling refers to the provider's multi-tenant model where physical and virtual resources are dynamically assigned and reassigned according to consumer demand, but it does not specifically address the rapid scaling up and down of resources in response to traffic spikes.

Practice this question →

202

MCQmedium

A gaming company is preparing to launch a new online multiplayer game. The company expects the player traffic to be extremely high on the first few days after launch, but then stabilize at a much lower level. The IT team wants to provision sufficient server capacity to handle the launch spike without over-provisioning and wasting money during the quieter periods. Which benefit of cloud computing most directly addresses this requirement?

A.Trade capital expense for variable expense

B.Stop guessing capacity

C.Increase speed and agility

D.Benefit from massive economies of scale

AnswerB

This benefit exactly matches the scenario. Cloud computing eliminates the need to predict peak capacity requirements. You can provision just enough for current needs and automatically scale based on actual demand, preventing both under-provisioning and over-provisioning.

Why this answer

The requirement is to provision enough capacity for a launch spike without over-provisioning for lower steady-state traffic. AWS Auto Scaling with Elastic Load Balancing directly addresses this by automatically adjusting the number of EC2 instances based on real-time demand, eliminating the need to guess peak capacity. This is the core benefit of 'Stop guessing capacity' — cloud elasticity allows you to match resources to actual usage, not predictions.

Exam trap

The trap here is that candidates confuse 'Stop guessing capacity' with 'Trade capital expense for variable expense' because both involve cost optimization, but the question specifically targets the ability to handle unpredictable demand without manual capacity planning.

How to eliminate wrong answers

Option A is wrong because 'Trade capital expense for variable expense' describes the shift from upfront hardware purchases to pay-as-you-go pricing, but it does not address the specific need to handle unpredictable traffic spikes without over-provisioning. Option C is wrong because 'Increase speed and agility' refers to rapid provisioning of resources (e.g., launching instances in minutes), but it does not inherently solve the capacity planning problem of matching resources to fluctuating demand. Option D is wrong because 'Benefit from massive economies of scale' explains lower per-unit costs due to AWS’s large infrastructure, but it does not provide the dynamic scaling mechanism required to handle a launch spike and then reduce capacity.

Practice this question →

203

MCQmedium

A company is planning to migrate to AWS. Their CTO wants to understand how AWS's massive scale benefits smaller customers. Which AWS cloud economic concept explains this benefit?

A.Elasticity

B.Economies of scale

C.Capital expenditure avoidance

D.Global reach

AnswerB

AWS's massive scale enables bulk purchasing and operational efficiency that individual companies cannot match, with savings passed on as lower prices to all customers.

Why this answer

Economies of scale is the correct answer because it describes how AWS's massive infrastructure investments (data centers, hardware, networking) allow them to spread fixed costs across millions of customers, resulting in lower per-unit costs that are passed down to smaller customers. This is a core cloud economic concept where the provider's scale directly benefits all tenants, unlike elasticity which focuses on resource scaling.

Exam trap

The trap here is that candidates confuse 'economies of scale' with 'elasticity' because both involve scaling, but elasticity is about resource adjustment while economies of scale is about cost reduction from provider size.

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 benefit derived from the provider's large-scale operations. Option C is wrong because capital expenditure avoidance is about shifting from upfront hardware purchases to operational expenses, which is a financial benefit but not the specific concept explaining how AWS's massive scale benefits smaller customers. Option D is wrong because global reach describes the geographic distribution of AWS infrastructure, not the economic advantage of shared infrastructure costs.

Practice this question →

204

MCQmedium

A company is designing a highly available application that must remain operational even if a single physical data center fails. The application will be deployed in the us-east-1 Region. The company wants to distribute the application across multiple physical locations within the Region, where each location has independent power, cooling, and networking. Which AWS Global Infrastructure component should the company use to meet this requirement?

A.AWS Region

B.Availability Zone

C.Edge Location

D.Local Zone

AnswerB

Availability Zones are isolated locations within an AWS Region, each with independent power, cooling, and networking. By deploying across multiple Availability Zones, the application can survive a single data center failure, achieving high availability and fault tolerance within the same Region.

Why this answer

Availability Zones (AZs) are distinct physical locations within an AWS Region, each with independent power, cooling, and networking, and are interconnected through low-latency links. By deploying the application across multiple AZs, the company ensures high availability and fault tolerance against the failure of a single physical data center. This directly meets the requirement to remain operational even if one physical data center fails.

Exam trap

The trap here is that candidates confuse an AWS Region (a broad geographic area) with an Availability Zone (the actual isolated data center within that Region), leading them to select 'AWS Region' thinking it provides the required physical separation.

How to eliminate wrong answers

Option A is wrong because an AWS Region is a geographic area containing multiple, isolated Availability Zones; deploying within a single Region does not by itself provide fault isolation against a single data center failure. Option C is wrong because Edge Locations are used for content caching and delivery via Amazon CloudFront, not for hosting application compute or storage with the required fault tolerance. Option D is wrong because a Local Zone is an extension of an AWS Region that places compute, storage, and database services closer to end users for low-latency workloads, but it does not provide the independent power, cooling, and networking redundancy across multiple physical locations within a Region that Availability Zones offer.

Practice this question →

205

MCQmedium

A company is migrating a legacy monolithic e-commerce application to AWS. The application has three tightly integrated modules: user authentication, payment processing, and inventory management. In the current design, a failure in the payment processing module often causes the entire application to crash. The company wants to redesign the application so that each module runs independently, and a failure in one module does not cascade to other modules. Which cloud computing concept should the company apply to achieve this goal?

A.Elasticity

B.High availability

C.Loose coupling

D.Disaster recovery

AnswerC

Loose coupling is an architectural principle where components are designed to have minimal dependencies on each other. They communicate asynchronously (e.g., via queues, events, or APIs) so that a failure in one component does not cascade to others. This approach directly solves the company's problem of isolating module failures.

Why this answer

The correct answer is C, loose coupling. Loose coupling is a cloud computing concept where components are designed to have minimal dependencies on each other, communicating through well-defined interfaces or APIs. By decoupling the user authentication, payment processing, and inventory management modules, a failure in one module (e.g., payment processing) will not cascade and crash the entire application, as each module can operate independently and handle its own failures gracefully.

Exam trap

The trap here is that candidates often confuse high availability with fault isolation, thinking that making a system highly available (e.g., with multiple instances) will prevent cascading failures, but high availability does not address the tight coupling between modules that causes one failure to bring down others.

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 the architectural independence of modules. Option B is wrong because high availability focuses on ensuring that a system remains operational and accessible despite failures, typically through redundancy and failover mechanisms, but it does not inherently prevent a failure in one component from crashing another. Option D is wrong because disaster recovery involves plans and processes to restore IT infrastructure and data after a catastrophic event, not the day-to-day isolation of module failures.

Practice this question →

206

MCQmedium

A company runs a critical database on a single Amazon EC2 instance in a single Availability Zone. To increase fault tolerance and minimize downtime, the architecture team decides to deploy the database across multiple Availability Zones using a primary/standby configuration. This design pattern of distributing resources across isolated locations to ensure continuous operation even if an entire data center fails best demonstrates which fundamental concept of cloud computing?

A.Elasticity

B.High availability

C.Scalability

D.Security

AnswerB

Correct. Deploying resources across multiple Availability Zones to withstand the failure of an entire data center is the definition of high availability in cloud computing. It ensures that the application remains accessible despite infrastructure failures.

Why this answer

Deploying a critical database across multiple Availability Zones in a primary/standby configuration ensures that if one data center (AZ) fails, the standby instance can take over with minimal downtime. This design directly implements high availability (HA), which is the ability of a system to remain operational despite component failures. The scenario specifically describes fault tolerance through geographic redundancy, which is the core of HA in cloud computing.

Exam trap

AWS often tests the distinction between high availability (fault tolerance across AZs) and scalability (handling increased load), so the trap here is confusing the ability to survive failures with the ability to grow capacity.

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 distributing resources for fault tolerance. Option C is wrong because scalability is the capacity to handle increased load by adding resources (vertical or horizontal scaling), not the ability to survive infrastructure failures. Option D is wrong because security involves protecting data and systems through encryption, access controls, and compliance measures, not ensuring continuous operation during a data center outage.

Practice this question →

207

MCQmedium

A company traditionally purchases physical servers every three years to host its internal applications. The company is migrating these applications to AWS and will pay a monthly fee based on the actual compute capacity consumed. The company no longer needs to make large upfront hardware purchases and can instead budget for smaller monthly payments. Which benefit of cloud computing does this scenario BEST describe?

A.Scalability

B.Elasticity

C.Conversion of capital expense to operational expense

D.Economies of scale

AnswerC

The company is moving from purchasing servers upfront (capital expense) to paying monthly for only what they use (operational expense). This is a fundamental benefit of cloud computing, often referred to as pay-as-you-go or variable expense.

Why this answer

This scenario describes the conversion of capital expense (CapEx) to operational expense (OpEx). Traditionally, purchasing physical servers requires a large upfront capital investment, which is a capital expense. By migrating to AWS and paying a monthly fee based on actual compute capacity consumed, the company shifts to a pay-as-you-go model, which is an operational expense.

This allows the company to budget for smaller, predictable monthly payments instead of large, infrequent hardware purchases.

Exam trap

The trap here is that candidates often confuse the financial benefit of CapEx-to-OpEx conversion with the operational benefits of scalability or elasticity, but the question specifically focuses on the change in payment structure from large upfront purchases to monthly consumption-based fees.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources to meet demand, which is not the primary focus of this scenario; the company is not described as adjusting capacity based on load. Option B is wrong because elasticity specifically refers to automatically scaling resources up and down in response to real-time demand, which is not mentioned; the scenario is about changing the payment model from upfront to monthly, not about dynamic resource adjustment.

Practice this question →

208

MCQmedium

A company runs a critical e-commerce application on Amazon EC2 instances distributed across multiple Availability Zones in a single AWS Region. The application is designed so that if an entire Availability Zone experiences an outage, the application continues to serve traffic from the remaining Availability Zones without interruption. Which benefit or characteristic of cloud computing does this scenario BEST represent?

A.Elasticity

B.High availability

C.Scalability

D.Fault tolerance

AnswerB

High availability is the correct characteristic. By deploying across multiple Availability Zones, the application can withstand the failure of an entire AZ and continue serving users, which is the essence of high availability.

Why this answer

The scenario describes an application that continues to serve traffic without interruption when an entire Availability Zone fails. This is the definition of high availability, which is achieved by distributing EC2 instances across multiple Availability Zones and using an Elastic Load Balancer to route traffic away from failed instances. High availability ensures fault tolerance and minimal downtime, which is a core benefit of cloud computing.

Exam trap

The trap here is that candidates confuse high availability with elasticity or scalability, because both involve multiple instances, but high availability specifically addresses fault tolerance and uptime during failures, not dynamic scaling or load handling.

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 withstand an Availability Zone failure. Option C is wrong because scalability is the ability to handle increased load by adding resources, which is unrelated to maintaining service during an infrastructure failure.

Practice this question →

209

MCQmedium

A company wants to deliver its web application content to users across North America, Europe, and Asia with minimal latency. The application runs on Amazon EC2 instances and serves static and dynamic content. Which AWS Cloud concept is most directly supported by using AWS Regions and edge locations to meet this requirement?

A.High availability

B.Global reach

C.Elasticity

D.Fault tolerance

AnswerB

Global reach is the ability to deploy resources and serve content from multiple AWS Regions and edge locations around the world, bringing applications closer to users and minimizing latency. This directly matches the scenario's requirement.

Why this answer

AWS Regions and edge locations are geographically distributed infrastructure components that enable global reach. By deploying the application in multiple Regions (e.g., us-east-1, eu-west-1, ap-southeast-1) and using edge locations via Amazon CloudFront, the company can serve static and dynamic content from locations closer to users, reducing latency across North America, Europe, and Asia. This directly supports the concept of global reach, which is the ability to serve a worldwide user base with low latency.

Exam trap

The trap here is that candidates confuse 'global reach' with 'high availability' or 'fault tolerance,' because both involve multiple locations, but global reach specifically addresses geographic distribution for latency reduction, not redundancy for failure recovery.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring application uptime through redundancy within a single Region (e.g., Multi-AZ deployments), not on reducing latency across geographically dispersed users. Option C is wrong because elasticity refers to the ability to automatically scale resources up or down based on demand (e.g., using Auto Scaling groups), not on distributing content to multiple geographic locations. Option D is wrong because fault tolerance is the ability to continue operating without interruption despite component failures (e.g., using standby replicas or multiple Availability Zones), not on minimizing latency for a global user base.

Practice this question →

210

MCQmedium

A company's website serves static content—such as images, videos, and CSS files—to a global audience. The company wants to reduce load times for users located far from the primary AWS Region where the application is hosted. Which component of the AWS global infrastructure is specifically designed to cache and deliver this content with low latency from locations close to end users?

A.Regional Edge Caches

B.Availability Zones

C.Edge Locations

D.AWS Outposts

AnswerC

Edge locations are a key part of the AWS global infrastructure, used by services like Amazon CloudFront to cache content geographically close to end users, minimizing latency and improving performance.

Why this answer

Edge Locations are part of AWS CloudFront, a content delivery network (CDN) that caches static content (e.g., images, videos, CSS) at geographically distributed points of presence (PoPs). When a user requests content, CloudFront serves it from the nearest Edge Location, reducing latency and improving load times for global audiences. This makes Edge Locations the correct choice for caching and delivering static content with low latency.

Exam trap

The trap here is that candidates confuse Regional Edge Caches with Edge Locations, thinking that Regional Edge Caches are the primary caching layer for end users, when in fact Edge Locations are the outermost, lowest-latency layer in the CloudFront hierarchy.

How to eliminate wrong answers

Option A is wrong because Regional Edge Caches are a separate layer within CloudFront that sit between the origin and Edge Locations; they are designed to cache content with a longer time-to-live (TTL) to reduce load on the origin, but they are not the primary component for delivering content with the lowest latency to end users—Edge Locations are closer and serve that purpose. Option B is wrong because Availability Zones are distinct, isolated data centers within an AWS Region that provide high availability and fault tolerance for compute and storage resources; they do not cache or deliver content globally and are not designed for content distribution or latency reduction for end users.

Practice this question →

211

MCQeasy

Which AWS Well-Architected Framework pillar focuses on protecting information, systems, and assets while delivering business value through risk assessments and mitigation strategies?

A.Reliability

B.Security

C.Operational Excellence

D.Performance Efficiency

AnswerB

The Security pillar covers IAM, detection controls, infrastructure protection, data protection, and incident response to protect assets while enabling business value.

Why this answer

The Security pillar of the AWS Well-Architected Framework is specifically designed to protect information, systems, and assets through the implementation of risk assessments and mitigation strategies. It encompasses practices such as identity and access management (IAM), detective controls (e.g., AWS CloudTrail, Amazon GuardDuty), infrastructure protection (e.g., AWS WAF, security groups), data protection (e.g., encryption at rest and in transit), and incident response. This pillar directly aligns with the question's focus on delivering business value while managing security risks.

Exam trap

The trap here is that candidates often confuse the Security pillar with the Reliability pillar because both involve 'protection'—but Security protects against unauthorized access and data breaches, while Reliability protects against service failures and downtime.

How to eliminate wrong answers

Option A is wrong because the Reliability pillar focuses on a workload's ability to recover from infrastructure or service disruptions, dynamically acquire computing resources to meet demand, and mitigate disruptions such as misconfigurations or transient network issues—not on protecting information or risk assessments. Option C is wrong because the Operational Excellence pillar concentrates on running and monitoring systems to deliver business value, and on continually improving processes and procedures—it does not primarily address security risk assessments or asset protection. Option D is wrong because the Performance Efficiency pillar focuses on using computing resources efficiently to meet system requirements and maintain efficiency as demand changes and technologies evolve—it does not cover information protection or risk mitigation strategies.

Practice this question →

212

MCQmedium

A company runs a web application on Amazon EC2 instances. The company wants to ensure that they are billed only for the exact compute capacity they consume, down to the second, for each running instance. They also want to receive a detailed breakdown of their usage, including CPU time, storage, and data transfer, so they can analyze costs per department. Which essential characteristic of cloud computing enables this granular tracking and billing?

A.Rapid elasticity

B.Resource pooling

C.Measured service

D.On-demand self-service

AnswerC

Measured service is the essential characteristic where cloud systems automatically control and optimize resource use by metering usage. This provides transparency and granular billing, allowing customers to pay per unit consumed and receive detailed usage reports.

Why this answer

Measured service is the correct answer because it is the cloud characteristic that enables providers to monitor, control, and report on resource usage (CPU time, storage, data transfer) with granularity down to the second. This metering capability allows AWS to bill customers only for the exact compute capacity consumed and provide detailed usage breakdowns for cost analysis per department.

Exam trap

The trap here is that candidates confuse 'rapid elasticity' with the ability to scale to meet demand, but the question specifically asks about granular tracking and billing, which is a direct function of 'measured service'—a distinct pillar of cloud computing that is often overlooked in favor of more commonly discussed characteristics like elasticity or self-service.

How to eliminate wrong answers

Option A is wrong because rapid elasticity refers to the ability to automatically scale resources up or down quickly based on demand, not to the tracking or billing of consumed resources. Option B is wrong because resource pooling describes how the provider serves multiple customers from shared physical resources using multi-tenant models, which does not directly enable per-second billing or detailed usage breakdowns. Option D is wrong because on-demand self-service allows users to provision resources automatically without human interaction, but it does not provide the metering and billing granularity required for per-second consumption tracking.

Practice this question →

213

MCQeasy

Which statement best describes 'high availability' in the context of AWS cloud architecture?

A.The ability to handle any amount of traffic by adding more resources

B.A design that minimizes downtime by eliminating single points of failure and enabling automatic recovery

C.Using the largest available instance types for maximum performance

D.Storing multiple copies of data in Amazon S3

AnswerB

High availability architectures eliminate single points of failure through redundancy and enable automatic failover — ensuring the application remains accessible despite component failures.

Why this answer

High availability in AWS is achieved by designing architectures that eliminate single points of failure and enable automatic recovery, typically using services like Elastic Load Balancing (ELB) to distribute traffic across multiple Availability Zones (AZs) and Auto Scaling to replace failed instances. This ensures that if one component fails, another takes over seamlessly, minimizing downtime. Option B correctly captures this core principle of fault tolerance and automated failover.

Exam trap

The trap here is confusing 'high availability' with 'scalability' (Option A) or 'durability' (Option D), as candidates often think adding more resources or storing extra copies automatically ensures uptime, but high availability specifically requires redundant, fault-tolerant components with automatic failover mechanisms.

How to eliminate wrong answers

Option A is wrong because it describes 'elasticity' (the ability to scale resources up or down based on demand), not high availability; high availability focuses on uptime and redundancy, not just scaling. Option C is wrong because using the largest instance types does not inherently provide high availability; it may actually increase the blast radius of a single failure and ignores the need for redundancy across AZs. Option D is wrong because storing multiple copies of data in Amazon S3 is a durability feature (ensuring data is not lost), not a high availability design for compute or application services; S3's 11 nines of durability does not equate to application-level uptime.

Practice this question →

214

MCQmedium

A financial services company must keep customer financial records on-premises to comply with data residency regulations. The company wants to use AWS services such as Amazon SageMaker and Amazon Athena to run analytics on anonymized subsets of the data. The company establishes a dedicated AWS Direct Connect connection between its on-premises data center and its VPC, and uses AWS Storage Gateway to cache frequently accessed data locally while storing all data in Amazon S3. Which cloud deployment model does this architecture represent?

A.Public cloud

B.Private cloud

C.Hybrid cloud

D.Community cloud

AnswerC

Hybrid cloud is the correct model. It uses a mix of on-premises private cloud resources and public cloud services (AWS) connected via networking (like Direct Connect). This allows the company to keep sensitive data on-premises while taking advantage of AWS analytics services.

Why this answer

This architecture combines on-premises infrastructure (customer data center with AWS Storage Gateway caching) with AWS cloud services (SageMaker, Athena, S3) connected via AWS Direct Connect, which is the defining characteristic of a hybrid cloud deployment. A hybrid cloud model integrates private on-premises resources with public cloud services, allowing data to remain on-premises for compliance while leveraging cloud analytics.

Exam trap

The trap here is that candidates may confuse 'hybrid cloud' with 'private cloud' because the on-premises component is dedicated to one organization, but the use of AWS public cloud services (SageMaker, Athena, S3) over Direct Connect makes it a hybrid model, not a private cloud.

How to eliminate wrong answers

Option A is wrong because public cloud would mean all resources and data reside solely in AWS cloud, but here customer financial records remain on-premises due to data residency regulations. Option B is wrong because private cloud refers to a cloud environment dedicated to a single organization, typically hosted on-premises or in a provider's data center, but this architecture uses AWS public cloud services (SageMaker, Athena, S3) alongside on-premises infrastructure. Option D is wrong because community cloud is a shared infrastructure for several organizations with common concerns (e.g., compliance, security), but this scenario involves only one financial services company using its own on-premises and AWS resources.

Practice this question →

215

MCQmedium

A company uses AWS to run its web application. A developer needs to add additional storage capacity to an Amazon EC2 instance that hosts the application's database. The developer logs in to the AWS Management Console, navigates to the Amazon EC2 dashboard, creates a new Amazon EBS volume, attaches it to the instance, and mounts it within the operating system. The entire process takes less than 10 minutes and does not require any interaction with AWS support or approval from the IT department. Which essential characteristic of cloud computing does this scenario best demonstrate?

A.Resource pooling

B.On-demand self-service

C.Broad network access

D.Measured service

AnswerB

This is correct because on-demand self-service allows users to provision and manage computing resources automatically, without requiring human interaction with the service provider. The developer created and attached an EBS volume in minutes using only the AWS Management Console, with no support tickets or approvals needed.

Why this answer

The developer was able to provision and attach an EBS volume to an EC2 instance entirely through the AWS Management Console without requiring any human interaction with AWS support or IT approval. This ability to independently request and configure computing resources as needed is the defining characteristic of on-demand self-service, as defined by the NIST definition of cloud computing.

Exam trap

The trap here is that candidates confuse the ability to provision resources quickly (on-demand self-service) with the multi-tenant or shared infrastructure aspect of resource pooling, or with the network accessibility of the service.

How to eliminate wrong answers

Option A 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 to a single user's ability to provision resources without manual intervention. Option C is wrong because broad network access describes capabilities being available over the network via standard mechanisms (e.g., HTTPS, SSH) that promote use by heterogeneous client platforms, not the self-service provisioning action itself. Option D is wrong because measured service involves monitoring, controlling, and reporting resource usage (e.g., CloudWatch metrics, billing reports) for transparency and optimization, which is not demonstrated by the act of creating and attaching a volume.

Practice this question →

216

MCQmedium

A company runs a customer-facing web application on Amazon EC2 instances. The application experiences unpredictable traffic patterns, with occasional spikes during marketing campaigns and lulls at other times. The company configures an Auto Scaling group to automatically add EC2 instances when CPU utilization exceeds 70% and remove instances when it drops below 30%. This ability to scale computing resources up and down in response to demand best represents which essential characteristic of cloud computing?

A.Elasticity

B.High availability

C.Security

D.Cost management

AnswerA

Elasticity is the correct characteristic because the Auto Scaling group automatically adjusts the number of EC2 instances based on real-time CPU utilization, matching supply to demand without manual intervention.

Why this answer

The scenario describes an Auto Scaling group that dynamically adjusts the number of EC2 instances based on CPU utilization thresholds (70% scale-up, 30% scale-down). This ability to automatically provision and de-provision computing resources to match demand is the defining characteristic of elasticity in cloud computing, which allows resources to scale out during spikes and scale in during lulls, optimizing cost and performance.

Exam trap

The trap here is that candidates confuse elasticity with high availability, but elasticity is specifically about scaling resources up and down to match demand, while high availability is about maintaining uptime through redundancy and fault tolerance.

How to eliminate wrong answers

Option B (High availability) is wrong because high availability focuses on ensuring the application remains accessible despite failures, typically through redundant infrastructure across Availability Zones, not on dynamically adjusting capacity based on load. Option C (Security) is wrong because security encompasses measures like encryption, IAM policies, and network controls, which are unrelated to the automatic scaling of compute resources in response to demand.

Practice this question →

217

MCQmedium

A company runs a customer-facing web application on AWS. To ensure the application remains available if a fire or flood destroys one of the company's data centers, the IT team deploys the application across multiple physically separate facilities within the same AWS Region. Each facility has independent power, cooling, and physical security. Which component of the AWS global infrastructure does this deployment strategy primarily use?

A.AWS Regions

B.Availability Zones

C.Edge Locations

D.Local Zones

AnswerB

Availability Zones are physically separate and isolated data centers within an AWS Region. Each has independent power, cooling, and physical security. By deploying across multiple Availability Zones, the application can survive the failure of one data center, meeting the requirement for high availability within the same Region.

Why this answer

Availability Zones are distinct, physically separated locations within an AWS Region, each with independent power, cooling, and physical security. Deploying across multiple Availability Zones protects against data center-level failures like fires or floods, ensuring high availability for the application.

Exam trap

The trap here is confusing Availability Zones with AWS Regions, as candidates often think 'physically separate facilities' must mean different Regions, but the question explicitly states 'within the same AWS Region,' which directly points to Availability Zones.

How to eliminate wrong answers

Option A is wrong because AWS Regions are separate geographic areas (e.g., us-east-1 vs. eu-west-1) that are hundreds of miles apart, not multiple facilities within the same Region; using multiple Regions would provide disaster recovery across large distances, not the described scenario of physically separate facilities within one Region. Option C is wrong because Edge Locations are content delivery endpoints used by Amazon CloudFront to cache data closer to users for low latency, not for hosting compute or storage resources to achieve high availability against data center failures.

Practice this question →

218

MCQmedium

A company runs an e-commerce platform on AWS. The platform experiences unpredictable traffic, with occasional large spikes. The company wants to automatically adjust compute capacity to match demand exactly, ensuring consistent performance while only paying for the resources consumed. Which benefit of the AWS Cloud does this scenario primarily describe?

A.High availability

B.Elasticity

C.Disaster recovery

D.Resource pooling

AnswerB

Elasticity is the ability to automatically provision and release compute resources to match the current workload. This directly supports the described requirement for adjusting capacity in response to traffic spikes while minimizing costs.

Why this answer

Elasticity is the ability of AWS to automatically scale compute resources up or down based on demand. In this scenario, the e-commerce platform experiences unpredictable traffic spikes, and elasticity ensures that EC2 instances or Auto Scaling groups adjust capacity in real time, matching demand exactly while only charging for resources consumed. This directly aligns with the 'pay-as-you-grow' model and the operational benefit of scaling without manual intervention.

Exam trap

The trap here is that candidates often confuse elasticity with high availability, thinking that automatically adding more servers during a spike also ensures fault tolerance, but elasticity is specifically about matching capacity to demand, not about maintaining uptime during failures.

How to eliminate wrong answers

Option A is wrong because high availability focuses on ensuring applications remain accessible during failures through redundancy across Availability Zones, not on dynamically adjusting capacity to match demand. Option C is wrong because disaster recovery involves backup and restoration strategies (e.g., RPO/RTO targets) to recover from catastrophic events, not real-time scaling to handle traffic spikes. Option D is wrong because resource pooling refers to the multi-tenant model where AWS shares physical infrastructure among customers, not the ability to automatically scale compute resources based on load.

Practice this question →

219

MCQmedium

Which cloud concept describes the ability of cloud services to remain operational even when individual components fail, through techniques like redundancy, replication, and automatic failover?

A.Scalability

B.Elasticity

C.Fault tolerance

D.Agility

AnswerC

Fault tolerance ensures system continuity despite component failures through redundancy, replication, and automatic failover — a core cloud design principle.

Why this answer

Fault tolerance is the correct answer because it directly refers to a system's ability to continue operating without interruption when one or more of its components fail. This is achieved through techniques such as redundancy (e.g., deploying multiple EC2 instances across Availability Zones), replication (e.g., synchronously replicating data in Amazon RDS Multi-AZ), and automatic failover (e.g., Route 53 health checks triggering a switch to a standby resource). The core goal is to eliminate single points of failure and maintain service availability despite underlying failures.

Exam trap

AWS often tests the distinction between fault tolerance and high availability (HA), where the trap is that candidates confuse 'remaining operational during failures' (fault tolerance) with 'quickly recovering from failures' (HA), but in this question the explicit mention of redundancy, replication, and automatic failover points directly to fault tolerance.

How to eliminate wrong answers

Option A is wrong because scalability refers to the ability to increase or decrease resources (e.g., compute, storage) to handle varying load, not to remain operational during component failures. Option B is wrong because elasticity is the ability to automatically scale resources up or down based on demand, often using services like Auto Scaling, and does not inherently address fault tolerance or failure recovery. Option D is wrong because agility describes the speed and ease with which IT resources can be provisioned and deprovisioned, enabling rapid experimentation and deployment, not the resilience of services against failures.

Practice this question →

220

MCQeasy

A company needs to deploy their application in multiple geographic locations to ensure data sovereignty compliance and reduce latency for users in different continents. What is the AWS infrastructure concept that represents a distinct geographic area with multiple isolated locations?

A.Availability Zone

B.Edge Location

C.AWS Region

D.Local Zone

AnswerC

An AWS Region is a geographic area (like us-east-1 or eu-west-1) containing multiple AZs. Each region is isolated from others, making them ideal for data sovereignty and geographic distribution.

Why this answer

An AWS Region is a distinct geographic area that contains multiple, isolated Availability Zones. This design allows customers to deploy applications across separate locations within a region for high availability, while also choosing specific regions to meet data sovereignty requirements and reduce latency for users on different continents.

Exam trap

The trap here is that candidates often confuse an Availability Zone (a single data center) with a Region (a geographic area containing multiple zones), leading them to select Option A when the question explicitly asks for a 'distinct geographic area with multiple isolated locations.'

How to eliminate wrong answers

Option A is wrong because an Availability Zone is a single, isolated data center within a region, not a geographic area with multiple isolated locations. Option B is wrong because an Edge Location is a site used by AWS CloudFront for content caching and delivery, not for compute or storage deployments that ensure data sovereignty. Option D is wrong because a Local Zone is an extension of a region that places compute and storage closer to end users, but it is not a distinct geographic area with multiple isolated locations; it is a single zone within a region.

Practice this question →

221

MCQmedium

A company is migrating to AWS and wants to understand the different types of cloud service models. Which model describes a service where the provider manages everything including the application, and the customer only manages their data and user access?

A.Infrastructure as a Service (IaaS)

B.Platform as a Service (PaaS)

C.Software as a Service (SaaS)

D.Function as a Service (FaaS)

AnswerC

SaaS provides complete applications through the internet — the provider manages everything (hardware through application) and customers only manage their data and user access settings.

Why this answer

In the Software as a Service (SaaS) model, the cloud provider manages the entire application stack, including infrastructure, platform, and application software. The customer is responsible only for their data and user access, typically through a web browser or API. This aligns with the description where the provider manages everything including the application.

Exam trap

The trap here is that candidates often confuse PaaS with SaaS because both involve managed services, but PaaS still requires the customer to manage the application code and data, whereas SaaS offloads the entire application management to the provider.

How to eliminate wrong answers

Option A is wrong because Infrastructure as a Service (IaaS) provides only virtualized computing resources (e.g., EC2 instances, VPCs), and the customer must manage the operating system, middleware, and applications themselves. Option B is wrong because Platform as a Service (PaaS) provides a managed runtime environment (e.g., AWS Elastic Beanstalk) where the customer deploys their own application code, but still manages the application and data, not just data and user access. Option D is wrong because Function as a Service (FaaS) (e.g., AWS Lambda) is a serverless compute model where the customer writes and uploads function code, and the provider manages the runtime, but the customer still manages the code and data, not just data and user access.

Practice this question →

222

MCQmedium

A company runs a web application on a single Amazon EC2 instance. As the application gains popularity, the instance frequently reaches 100% CPU utilization during peak hours, causing slow response times. The operations team is evaluating two approaches: (1) migrate the application to a larger EC2 instance type with more CPU and memory, or (2) add multiple smaller EC2 instances behind a load balancer and distribute the traffic. Which cloud computing concept does approach (1) represent?

A.Elasticity

B.High availability

C.Vertical scaling

D.Horizontal scaling

AnswerC

Vertical scaling (scaling up) increases the capacity of an existing resource—in this case, upgrading the EC2 instance to a larger type with more CPU and memory. This is correct for approach (1).

Why this answer

Approach (1) involves moving the application to a larger EC2 instance type with more CPU and memory, which is the definition of vertical scaling (scaling up). This increases the capacity of a single resource rather than adding more instances.

Exam trap

The trap here is that candidates often confuse vertical scaling with elasticity, but elasticity specifically refers to the dynamic, automated adjustment of resources (both up and down) to match demand, not a manual one-time upgrade to a larger instance.

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 simply moving to a larger instance. Option B is wrong because high availability ensures the application remains accessible despite failures, typically achieved through redundancy across multiple instances and Availability Zones, not by resizing a single instance. Option D is wrong because horizontal scaling (scaling out) involves adding more instances to distribute the load, which is approach (2), not approach (1).

Practice this question →

223

MCQmedium

A startup is evaluating cloud vs. on-premises for their new product. Which cloud characteristic means they can experiment with 10 servers for a week, then scale to 1,000 servers for a product launch, and back to 10 afterward — paying only for what they use?

A.Durability

B.Elasticity and pay-as-you-go pricing

C.Multi-tenancy

D.Service Level Agreement (SLA)

AnswerB

Elasticity enables scaling from 10 to 1,000 servers on demand; pay-as-you-go ensures billing only for actual server-hours consumed — eliminating waste from idle capacity.

Why this answer

Elasticity is the cloud characteristic that allows resources to automatically scale up or down based on demand, while pay-as-you-go pricing ensures you only incur costs for resources actually consumed. In this scenario, the startup can provision 10 servers for a week, scale to 1,000 servers for a launch, and then scale back to 10 — paying only for the compute hours used during each period. This combination of rapid scaling and consumption-based billing is unique to cloud computing and directly supports the described experimental and production workloads.

Exam trap

The trap here is that candidates often confuse elasticity with durability or high availability, mistakenly thinking that data persistence or uptime guarantees enable scaling, when in fact elasticity is specifically about dynamic resource adjustment and pay-as-you-go is about cost alignment.

How to eliminate wrong answers

Option A is wrong because durability refers to the long-term protection of data against loss or corruption, typically achieved through replication (e.g., Amazon S3's 99.999999999% durability), not the ability to scale compute resources up and down or pay per use. Option C is wrong because multi-tenancy is a model where multiple customers share the same physical infrastructure while being logically isolated (e.g., AWS Nitro System), but it does not enable dynamic scaling or usage-based billing. Option D is wrong because a Service Level Agreement (SLA) is a contractual commitment for uptime and performance (e.g., Amazon EC2 99.99% monthly uptime SLA), not a mechanism for elastic resource provisioning or pay-as-you-go pricing.

Practice this question →

224

MCQmedium

A company runs a customer-facing web application on a single Amazon EC2 instance. To improve resilience, the solutions architect decides to deploy a second EC2 instance in a different Availability Zone and configure an Application Load Balancer to distribute traffic. The goal is to ensure that the application remains accessible even if one instance or one Availability Zone becomes unavailable. Which cloud computing benefit does this architecture primarily aim to achieve?

A.Elasticity

B.High availability

C.Scalability

D.Cost optimization

AnswerB

High availability ensures that a system remains operational even when components fail. Deploying EC2 instances in multiple Availability Zones behind a load balancer eliminates single points of failure and keeps the application accessible if an instance or an Availability Zone goes down. This directly addresses the requirement for resilience.

Why this answer

By deploying a second EC2 instance in a different Availability Zone and using an Application Load Balancer (ALB) to distribute traffic, the architecture ensures that if one instance or one Availability Zone fails, the ALB automatically routes traffic to the healthy instance in the other AZ. This design directly achieves high availability by eliminating a single point of failure and maintaining application uptime during infrastructure failures.

Exam trap

The trap here is that candidates confuse high availability with scalability or elasticity, mistakenly thinking adding more instances is always about handling more traffic rather than ensuring fault tolerance across Availability Zones.

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 (e.g., using Auto Scaling groups), not to maintaining uptime during failures. Option C is wrong because scalability is the ability to handle increased load by adding resources, whereas this scenario focuses on fault tolerance and redundancy, not load growth. Option D is wrong because cost optimization involves minimizing expenses while meeting requirements, but this architecture adds a second instance and an ALB, which increases cost; the primary goal is resilience, not cost savings.

Practice this question →

225

MCQmedium

A company runs a web application on a single Amazon EC2 instance. To improve the application's ability to remain operational even if an entire data center becomes unavailable, the company deploys identical application instances across three AWS Availability Zones and places them behind an Application Load Balancer. Which characteristic of cloud computing does this architecture best demonstrate?

A.Elasticity

B.High availability

C.Scalability

D.Agility

AnswerB

High availability ensures that applications remain operational by eliminating single points of failure. Deploying across multiple Availability Zones with a load balancer directly achieves this cloud computing characteristic.

Why this answer

Deploying identical application instances across three Availability Zones and placing them behind an Application Load Balancer ensures that if an entire data center (AZ) becomes unavailable, traffic is automatically rerouted to healthy instances in the remaining AZs. This architecture directly demonstrates high availability, which is the ability of a system to remain operational despite component failures, by eliminating a single point of failure at the data center level.

Exam trap

The trap here is that candidates often confuse high availability with elasticity or scalability, but high availability specifically focuses on fault tolerance and uptime through redundancy across isolated failure domains, not on dynamic resource adjustment or load handling.

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 distributing workloads across AZs for fault tolerance. Option C is wrong because scalability is the capability to handle increased load by adding resources, which is a separate concern from maintaining uptime during failures. Option D is wrong because agility refers to the speed and ease of provisioning and deploying IT resources, not to the architectural design for fault tolerance.

Practice this question →