Practice Cloud Concepts questions for the AWS Certified Cloud Practitioner. Every question includes a full explanation of why the correct answer is right and why the tempting distractors are wrong.
20 questions available · easy difficulty · AWS CLF · Free, no registration required
10 example questions with full explanations. Use the interactive practice above to work through the complete set.
Question 1medium
A retail company experiences large traffic spikes during holiday seasons and wants to expand its customer base into multiple international markets while avoiding large upfront infrastructure investments. Which of the following AWS Cloud benefits would directly address these business needs? Select all that apply.
- A.Elasticity — automatically scale compute resources up during peak traffic periods and down afterward to avoid over-provisioning✓
- B.Global reach — deploy applications in AWS Regions close to international customers to reduce latency✓
- C.Trade capital expense for operational expense — pay only for resources consumed rather than purchasing hardware upfront✓
- D.Dedicated physical hardware — AWS reserves exclusive physical servers for each customer to ensure performance
- E.Guaranteed fixed monthly pricing — AWS locks in a flat rate regardless of actual usage levels
Correct answer: A, B, C
Elasticity (A) directly addresses the holiday spike challenge by automatically scaling resources to match demand, preventing both under-provisioning and waste. Global reach (B) allows the company to deploy in multiple AWS Regions worldwide, placing infrastructure closer to international customers. Trading CapEx for OpEx (C) eliminates the need for large upfront hardware purchases, replacing them with variable, pay-as-you-go costs. Option D is incorrect because AWS operates a shared infrastructure model — dedicated physical servers are not the default, and multi-tenancy is how AWS achieves economies of scale. Option E is incorrect because AWS pricing is consumption-based, not a flat fixed rate.
Question 2medium
A company is deploying a web application on Amazon EC2 instances and storing user data in Amazon RDS. A security audit requires the team to clearly document which security responsibilities belong to the customer under the AWS Shared Responsibility Model. Which of the following are customer responsibilities? Select all that apply.
- A.Patching and updating the operating system installed on EC2 instances✓
- B.Managing physical access controls to the AWS data centers hosting the EC2 instances
- C.Configuring security groups and network ACLs to control inbound and outbound traffic✓
- D.Maintaining the underlying hypervisor and virtualization layer that runs EC2
- E.Enabling and managing encryption for data stored in Amazon RDS✓
Correct answer: A, C, E
Under the Shared Responsibility Model, customers are responsible for security 'in' the cloud, which includes: managing the OS on EC2 instances (A), since AWS only provides the virtualized compute; configuring network controls like security groups and ACLs (C), which govern what traffic reaches their resources; and enabling encryption for their data at rest (E), such as RDS encryption settings. Option B is incorrect because physical data center security is entirely AWS's responsibility — customers have no access to or control over AWS facilities. Option D is incorrect because the hypervisor and virtualization infrastructure are part of AWS's managed layer, which sits below the customer's visibility.
Question 3medium
A company is reviewing 50 on-premises applications as part of a cloud migration program. After the assessment, the team decides to: move their CRM system to a cloud-based SaaS vendor, decommission several redundant internal tools that are no longer used, lift-and-shift a billing application to EC2 with no code changes, and completely re-architect a customer-facing API to use serverless and managed cloud-native services. Which of the following migration strategies from the 6 R's are being applied in this scenario? Select all that apply.
- A.Repurchase — replacing the CRM with a SaaS-based product such as Salesforce✓
- B.Retire — shutting down the redundant internal tools that no longer provide business value✓
- C.Rehost — migrating the billing application to EC2 without any code modifications✓
- D.Refactor/Re-architect — redesigning the customer-facing API to use cloud-native, serverless services✓
- E.Revert — rolling back cloud-migrated applications to their original on-premises state
Correct answer: A, B, C, D
All four scenarios described in the question map directly to established 6 R's strategies. Repurchase (A) involves dropping an existing application in favor of a SaaS alternative. Retire (B) means decommissioning applications that no longer serve a business purpose, reducing the migration scope and cost. Rehost (C), commonly called lift-and-shift, moves applications to the cloud with no code changes — the fastest migration path. Refactor (D) involves re-architecting an application to take advantage of cloud-native features like serverless computing, typically yielding the highest long-term benefits but also the highest effort. Option E (Revert) is not one of the 6 R's migration strategies; it is a fabricated option designed to test familiarity with the actual framework.
Question 4medium
A company's CFO is building a business case to migrate from an on-premises data center to AWS. She wants to identify which current costs are capital expenditures (CapEx) that would be eliminated after a full cloud migration. Which of the following represent CapEx costs that are typically eliminated when moving entirely to AWS? Select all that apply.
- A.Purchasing physical servers, storage arrays, and networking hardware✓
- B.Constructing and expanding the physical data center facility✓
- C.Paying monthly AWS usage fees for compute, storage, and data transfer
- D.Buying perpetual software licenses tied to specific on-premises hardware✓
- E.Ongoing salaries for cloud engineers hired to manage AWS infrastructure
Correct answer: A, B, D
Capital expenditures are large, upfront investments in physical assets. Purchasing servers and hardware (A), building or expanding data center facilities (B), and buying perpetual on-premises software licenses (D) are all CapEx items that disappear after a full cloud migration, because AWS owns and manages all of that infrastructure. Option C is incorrect — monthly AWS usage fees are operational expenditures (OpEx), not CapEx; this is actually the new cost model the company adopts in the cloud. Option E is also OpEx (recurring labor costs) and does not represent a CapEx item, nor is it necessarily eliminated — cloud migrations often shift headcount from hardware maintenance to cloud operations roles.
Question 5medium
A solutions architect is reviewing a company's cloud architecture using the AWS Well-Architected Framework to identify areas for improvement before a production launch. Which of the following are official pillars of the AWS Well-Architected Framework that the architect would evaluate? Select all that apply.
- A.Operational Excellence — the ability to run and monitor systems to deliver business value and continually improve processes✓
- B.Vendor Diversification — ensuring workloads are distributed across multiple cloud providers to avoid lock-in
- C.Reliability — the ability of a system to recover from failures and meet demand consistently✓
- D.Cost Optimization — avoiding unnecessary costs and achieving the best value for money spent✓
- E.Security — protecting data, systems, and assets through risk assessments and mitigation strategies✓
Correct answer: A, C, D, E
The AWS Well-Architected Framework consists of six official pillars: Operational Excellence (A), Security (E), Reliability (C), Performance Efficiency, Cost Optimization (D), and Sustainability. All four of the correct answers map directly to named pillars in the framework. Option B, Vendor Diversification, is not a pillar of the AWS Well-Architected Framework — it is a fabricated distractor. While multi-cloud strategies are a valid architectural discussion, AWS's framework focuses on building well on AWS, not distributing across competitors. Candidates who confuse the Well-Architected Framework with general cloud design principles may select B incorrectly.
Question 6hard
A financial analyst is preparing a business case to justify migrating the company's on-premises data center to AWS. She notes that AWS has reduced its service pricing more than 100 times since 2006, even without any changes in the company's usage patterns. Which cloud economics principle BEST explains why AWS is able to continually lower its prices over time?
- A.Economies of scale, because as AWS aggregates usage from hundreds of thousands of customers, it achieves greater purchasing power and operational efficiencies that are reflected in lower prices✓
- B.Elasticity, because AWS automatically right-sizes infrastructure to reduce waste and passes the savings to customers
- C.Capital expenditure reduction, because AWS eliminates the need for hardware refresh cycles, reducing overall infrastructure costs
- D.Pay-as-you-go pricing, because customers only pay for what they consume, which inherently lowers the average cost per unit over time
Correct answer: A
Economies of scale is the principle at work here. As AWS serves an enormous and growing customer base, it can negotiate better prices for hardware, energy, and facilities, and spread fixed operational costs across more customers — savings that AWS passes on through periodic price reductions. Elasticity (B) refers to scaling resources up or down with demand, not to AWS's own purchasing efficiency. CapEx reduction (C) describes a benefit customers realize, not the mechanism by which AWS lowers its own costs. Pay-as-you-go pricing (D) is a billing model and does not itself cause per-unit cost to decrease over time.
Question 7hard
A startup's development team deploys their web application on Amazon EC2 instances, manages their own operating system patching, installs their own web server software, and configures their own network security groups. A second team at the same company uses AWS Elastic Beanstalk, where they simply upload their application code and AWS automatically handles the underlying capacity provisioning, load balancing, and runtime environment. Which cloud service model does each team's approach BEST represent, respectively?
- A.The first team uses PaaS; the second team uses SaaS
- B.The first team uses IaaS; the second team uses PaaS✓
- C.The first team uses IaaS; the second team uses SaaS
- D.The first team uses PaaS; the second team uses IaaS
Correct answer: B
The first team's approach — managing EC2 instances, OS patching, web server software, and network configuration — is Infrastructure as a Service (IaaS), where the customer controls everything above the physical hardware layer. The second team using Elastic Beanstalk is a Platform as a Service (PaaS) model, because AWS manages the underlying runtime environment and infrastructure while the team only provides application code. SaaS (C) would mean the team consumes a fully managed software product (like Amazon WorkMail or Salesforce) without any deployment responsibility at all — that does not apply here. Swapping the models (A or D) contradicts the level of control and responsibility described for each team.
Question 8hard
A global media company streams video content to users worldwide. To reduce buffering and improve load times, the company wants to cache video files as close to end users as possible without deploying full AWS infrastructure in every geographic location. Which component of AWS Global Infrastructure is specifically designed to serve this need?
- A.AWS Availability Zones, because each AZ is an independent data center that can cache content locally for users in its geographic area
- B.AWS Regions, because selecting a Region nearest to the majority of users minimizes latency for global content delivery
- C.AWS Edge Locations, because they are endpoints used by services like Amazon CloudFront to cache and deliver content to users with low latency✓
- D.AWS Local Zones, because they extend AWS compute capacity into metropolitan areas to provide single-digit millisecond latency for all applications
Correct answer: C
Edge Locations are the correct answer. They are geographically distributed nodes used by Amazon CloudFront (AWS's CDN) to cache content close to end users, reducing latency without requiring the company to launch full AWS infrastructure globally. Availability Zones (A) are isolated data centers within a Region used for deploying resilient applications, not for content caching close to users. Regions (B) are large geographic areas containing multiple AZs; choosing a Region helps proximity for users in that geography but does not provide global edge caching. Local Zones (D) extend compute, storage, and database services into metro areas for latency-sensitive applications — they are not primarily a caching layer for content delivery and are a different, more expensive solution than Edge Locations for this use case.
Question 9hard
An e-commerce company's architecture team is debating resilience strategies. Engineer A proposes that all critical order-processing servers should be deployed across multiple Availability Zones with an auto scaling group, so that if one AZ fails, traffic automatically shifts to the remaining AZs with no manual intervention, though a brief degradation in capacity may occur. Engineer B argues the system should be designed so that even if an entire AZ fails, there is zero impact on performance or transactions — requiring fully redundant, active-active capacity in every AZ at all times. Which resilience concepts do Engineer A and Engineer B RESPECTIVELY describe?
- A.Engineer A describes fault tolerance; Engineer B describes high availability
- B.Engineer A describes disaster recovery; Engineer B describes fault tolerance
- C.Engineer A describes high availability; Engineer B describes disaster recovery
- D.Engineer A describes high availability; Engineer B describes fault tolerance✓
Correct answer: D
High availability (Engineer A) ensures a system remains operational with minimal downtime by automatically recovering from failures — but it tolerates brief capacity reductions or brief failover periods during a disruption. Fault tolerance (Engineer B) is a stricter standard: the system continues to operate at full capacity with zero disruption even when a component fails, requiring fully redundant active-active infrastructure. The key distinction is that HA allows for *some* degradation during recovery, while fault tolerance requires *no* degradation at any point. Disaster recovery (B, D) refers to restoring systems after a catastrophic event — often involving data backup, RPO/RTO targets, and planned recovery procedures — which is a separate concept from either HA or fault tolerance described in this scenario.
Question 10easy
A company is evaluating whether to move its IT infrastructure to the AWS Cloud. Which of the following are characteristics of cloud deployment that differ from a traditional on-premises deployment? Select all that apply.
- A.The company pays only for the resources it consumes, with no upfront hardware purchases✓
- B.The company is responsible for purchasing and maintaining all physical servers
- C.The company can provision new resources within minutes rather than weeks✓
- D.The company can access resources globally through the internet✓
Correct answer: A, C, D
Cloud deployments eliminate upfront hardware purchases (pay-as-you-go model), allow near-instant provisioning of resources, and enable global access through the internet — all of which contrast sharply with on-premises environments. Option B describes on-premises infrastructure, where the company is responsible for buying and maintaining physical servers. In the cloud, AWS owns and manages the underlying physical hardware.