Skip to content

CLF-C02 Exam Notes — Task Statement 1.1

Define the benefits of the AWS Cloud

Focus areas: Value proposition of the AWS Cloud · Global infrastructure benefits (speed of deployment, global reach) · High availability · Elasticity · Agility

Question 1

A company is evaluating whether to migrate its on-premises data center to AWS. Which statement best describes Amazon Web Services (AWS)?

  • A. A private cloud platform that provides only compute and storage services inside a customer’s own data center
  • B. The world’s most comprehensive and broadly adopted cloud, offering over 200 fully featured services from data centers globally
  • C. A content delivery network that is limited to serving static websites
  • D. An open-source virtualization platform that customers must install and manage themselves
Click to reveal answer **Correct Answer:** B **Explanation:** AWS describes itself as the world’s most comprehensive and broadly adopted cloud, offering over 200 fully featured services from data centers globally. Millions of customers use AWS to lower costs, become more agile, and innovate faster. - **A** is incorrect because AWS is a public cloud (with options for hybrid/private via services such as Outposts), not a platform you run only inside your own data center. - **C** describes a CDN (for example Amazon CloudFront), which is only one part of AWS. - **D** describes software such as KVM or Xen, not AWS. **Exam tip / trap:** Do not confuse AWS (a managed public cloud) with on-premises virtualization products. Keywords: *comprehensive*, *broadly adopted*, *200+ services*, *global data centers*.

Question 2

Which of the following is a required characteristic of cloud computing that AWS must meet?

  • A. Customers must submit a ticket and wait for AWS staff to provision every resource
  • B. Resources can be provisioned on demand by the customer without human intervention from the cloud provider
  • C. Customers must purchase hardware in advance and ship it to an AWS Region
  • D. All resources must be dedicated to a single customer and never shared
Click to reveal answer **Correct Answer:** B **Explanation:** One of the five cloud computing criteria is **on-demand self-service**: the ability to provision compute, storage, databases, networking, and more when needed, without human interaction from the provider. AWS supports this through the Management Console, CLI, and APIs. - **A** is the opposite of on-demand self-service. - **C** describes traditional hardware procurement, not cloud. - **D** contradicts **resource pooling** (multi-tenant shared capacity). Dedicated Hosts exist, but they are optional, not a cloud requirement. **Exam tip / trap:** Memorize the five cloud characteristics: (1) on-demand self-service, (2) broad network access, (3) resource pooling, (4) rapid elasticity, (5) measured service. “Without human intervention” is a high-yield keyword for on-demand self-service.

Question 3

Which FIVE characteristics must a service meet to be considered cloud computing? (Choose five.)

  • A. On-demand self-service
  • B. Broad network access
  • C. Resource pooling
  • D. Rapid elasticity
  • E. Measured service
  • F. Dedicated hardware for every customer
  • G. Mandatory multi-year hardware contracts
Click to reveal answer **Correct Answer:** A, B, C, D, E **Explanation:** These are the five NIST / industry characteristics of cloud computing, which the lesson maps directly to AWS: | Characteristic | AWS meaning | |---|---| | On-demand self-service | Provision via console, CLI, or API with no AWS staff involvement | | Broad network access | Access over the network (HTTPS, VPN, SSH, etc.) | | Resource pooling | Shared, multi-tenant capacity; you pick a Region (and optionally an AZ), not a specific rack | | Rapid elasticity | Scale out/in as demand changes | | Measured service | Usage is monitored and billed; you pay for what you use | - **F** and **G** describe traditional data-center buying, not cloud. **Exam tip / trap:** If an option mentions *pre-purchasing hardware*, *human ticket queues*, or *always-dedicated servers*, it is not a cloud characteristic. “Pay only for what you use” = measured service.

Question 4

A startup wants to launch a new application without estimating peak capacity months in advance. Which benefit of the AWS Cloud does this describe?

  • A. Stop guessing capacity
  • B. Mandatory reserved capacity for every workload
  • C. Capital expense (CapEx) for all new servers
  • D. Fixed capacity that cannot change after launch
Click to reveal answer **Correct Answer:** A **Explanation:** A core value proposition of AWS is **stop guessing capacity**. You no longer pre-provision servers based on a guess. You provision what you need and scale with demand, avoiding both over-provisioning (wasted money) and under-provisioning (outages). - **B**, **C**, and **D** describe on-premises constraints, not cloud benefits. **Exam tip / trap:** Pair this with elasticity and pay-as-you-go. Exam wording often includes *estimate demand*, *over-provisioned*, *under-provisioned*, or *no longer pre-provisioning*.

Question 5

How does AWS pass cost savings to customers through economies of scale?

  • A. AWS charges every customer the same high fixed fee regardless of usage
  • B. Because AWS procures a massive volume of resources, it can offer lower prices and pass those savings to customers
  • C. Customers must buy hardware in bulk from AWS and install it themselves
  • D. Economies of scale apply only to government customers
Click to reveal answer **Correct Answer:** B **Explanation:** Resource pooling at AWS scale (thousands of servers, storage systems, and more) creates **economies of scale**. AWS’s purchasing power lowers unit costs, and those savings are passed to customers. - **A** is the opposite of usage-based pricing. - **C** is traditional procurement. - **D** is false; economies of scale apply to all customers. **Exam tip / trap:** Link *economies of scale* with *resource pooling* and *lower costs*. Do not confuse it with Reserved Instances (a pricing model) or with elasticity (a scaling behavior).

Question 6

A company currently buys servers every three years (a capital expense). After moving to AWS, it pays a monthly bill based on usage. Which cloud benefit is this?

  • A. Trade capital expense (CapEx) for variable/operating expense (OpEx)
  • B. Increase capital expense by purchasing more hardware
  • C. Eliminate all costs related to IT
  • D. Require a three-year hardware refresh cycle in every Region
Click to reveal answer **Correct Answer:** A **Explanation:** One of the six advantages of cloud computing is **trade capital expense for variable expense**. Instead of large upfront hardware purchases (CapEx), you pay as you go (OpEx) only for the resources you consume. - **B** is the on-premises model. - **C** is a trap — cloud is not free; it is usage-based. - **D** is an on-premises refresh cycle. **Exam tip / trap:** Keywords: *CapEx → OpEx*, *pay as you go*, *no upfront hardware*. If a question says “eliminate all IT costs,” that is always wrong.

Question 7

Which AWS Cloud benefit allows a company to deploy an application in multiple geographic locations in a short amount of time?

  • A. Go global in minutes
  • B. Mandatory single-Region architecture
  • C. Physical shipment of servers to each country
  • D. Manual cabling of a new data center for every launch
Click to reveal answer **Correct Answer:** A **Explanation:** AWS global infrastructure (Regions, Availability Zones, and edge locations connected by a high-speed network) lets you **go global in minutes**. You can deploy closer to users worldwide without building data centers. This maps to the skill: *benefits of global infrastructure (speed of deployment, global reach)*. - **B**, **C**, and **D** describe traditional, slow, physical expansion. **Exam tip / trap:** “Go global in minutes,” “speed of deployment,” and “global reach” are the exact phrases used in the exam guide. Regions = geographic areas; AZs = isolated data centers inside a Region; edge locations = CloudFront/CDN points of presence.

Question 8

A company wants its application to remain available as often as possible. If a component fails, the design should replace or recover that component quickly. Some brief downtime may occur. Which concept does this describe?

  • A. High availability
  • B. Fault tolerance with zero interruption
  • C. Disaster recovery planning only, with no running standby
  • D. Vertical scaling of a single instance with no redundancy
Click to reveal answer **Correct Answer:** A **Explanation:** **High availability (HA)** designs systems to stay up and serving as often as possible. Failures are expected; the goal is fast recovery so the system returns to service quickly. HA does **not** mean zero failures or zero downtime. Brief downtime can occur (for example, failing over to a standby server where users may need to log in again). - **B** describes **fault tolerance**, which continues operating through a failure with no downtime. - **C** is DR — planning what to do *after* a disaster, not day-to-day uptime design. - **D** is a single point of failure. **Exam tip / trap:** HA vs FT is a classic trap: - **HA** = maximize uptime, recover fast, *some brief downtime OK* - **FT** = keep operating *through* the failure, *no downtime* - FT designs are usually **more expensive** than HA.

Question 9

An application runs on two active Amazon EC2 instances behind a load balancer. If one instance fails, the second instance already serving traffic continues with no downtime. Which design is this?

  • A. Fault tolerance
  • B. High availability with an expected outage during failover
  • C. Disaster recovery only (restore from backup after the event)
  • D. Vertical scaling of a single instance
Click to reveal answer **Correct Answer:** A **Explanation:** **Fault tolerance** is the ability of a system to **keep operating when a component fails**. Two active servers (or equivalent redundant components) mean users experience no interruption if one fails. The lesson’s HA example used active/standby (possible brief downtime). The FT example used two active servers (no downtime). - **B** is HA with failover delay. - **C** is DR — recover *after* a disaster, not continue through a component failure. - **D** still has a single point of failure. **Exam tip / trap:** Keywords for FT: *continue operating*, *no downtime*, *through the failure*. Keywords for HA: *recover as quickly as possible*, *some downtime possible*. Do not treat HA, FT, and DR as the same thing.

Question 10

Which statement best describes disaster recovery (DR) compared with high availability and fault tolerance?

  • A. DR is the pre-planned process of restoring systems after a disaster; HA and FT are about designing systems to operate through failures
  • B. DR, HA, and FT all mean the same thing: zero downtime forever
  • C. DR replaces the need for backups and is only used for vertical scaling
  • D. DR is only about choosing a larger EC2 instance type
Click to reveal answer **Correct Answer:** A **Explanation:** **Disaster recovery** is about *what you plan and do when a disaster occurs*. The worst time to invent a recovery plan is during the disaster. HA and FT are architectural properties of a running system (stay up / keep running through faults). DR is the plan, runbooks, backups, and failover steps used after a major event. - **B** is false — they are related but distinct. - **C** and **D** mix unrelated concepts. **Exam tip / trap:** If the scenario is “a Region fails” or “we need a documented plan to restore,” think **DR**. If the scenario is “one server dies and users should keep working,” think **HA or FT**.

Question 11

What is elasticity in AWS?

  • A. Manually resizing one server once per year
  • B. Using automation with horizontal scaling so capacity increases and decreases to match changing demand
  • C. Buying the largest instance type available and leaving it running 24/7
  • D. Locking capacity so it can never change after deployment
Click to reveal answer **Correct Answer:** B **Explanation:** **Elasticity** = automation + horizontal scaling to match supply with demand. Demand is rarely linear. Auto Scaling (with launch templates/configurations) adds instances when demand rises and removes them when demand falls — even down to zero — which supports performance, operational excellence, and cost optimization. - **A** is a one-time manual change, not elasticity. - **C** is over-provisioning (the opposite of elasticity). - **D** is fixed capacity. **Exam tip / trap:** Lesson exam tip: *Vertical = larger size; horizontal = more instances of the same size; elasticity = automation + horizontal scaling to match demand.* “Auto Scaling” on the exam almost always points to elasticity.

Question 12

An application on a t3.micro Amazon EC2 instance is CPU-bound. The team resizes it to a t3.large (more CPU and memory). The instance must reboot. Which type of scaling is this?

  • A. Vertical scaling (scale up)
  • B. Horizontal scaling (scale out)
  • C. Elasticity with Auto Scaling groups
  • D. Geographic scaling across Regions
Click to reveal answer **Correct Answer:** A **Explanation:** **Vertical scaling** means making a *single* resource bigger (or smaller): more vCPU and RAM on the same instance. Typical traits from the lesson: - Often requires a **reboot** (brief disruption) - Usually **no application code changes** - Works for many applications - **Cost increases** with larger instance sizes — right-size using the Cost Optimization pillar - **B** would add *more* instances of the same size. - **C** is automated horizontal scaling. - **D** is multi-Region deployment, not instance resizing. **Exam tip / trap:** *Bigger box = vertical. More boxes = horizontal.* Disruption/reboot is a common vertical-scaling distractor clue.

Question 13

A company wants to handle more traffic by adding more Amazon EC2 instances of the same size and distributing requests with a load balancer, instead of making one instance larger. Which approach is this?

  • A. Horizontal scaling (scale out)
  • B. Vertical scaling (scale up)
  • C. Replacing elasticity with a single large server
  • D. Resource pooling inside one instance
Click to reveal answer **Correct Answer:** A **Explanation:** **Horizontal scaling** adds (scale out) or removes (scale in) instances of the same size. A load balancer distributes traffic. Benefits vs vertical: - Avoids the reboot of resizing one large instance - Often **less expensive** (many small instances vs one huge instance) - Enables elasticity with Auto Scaling Consideration: user **sessions**. With multiple servers, use sticky sessions (or store session state externally) so users are not dropped when the load balancer shifts them. - **B** is resizing one instance. - **C** and **D** misuse terms. **Exam tip / trap:** Keywords: *add more instances*, *same size*, *load balancer* → horizontal. *Sticky sessions* may appear as a related detail, not as the definition of scaling itself.

Question 14

Which statement correctly compares vertical and horizontal scaling?

  • A. Vertical scaling increases instance size; horizontal scaling adds more instances of the same size
  • B. Vertical scaling always has zero downtime; horizontal scaling always requires a reboot
  • C. Horizontal scaling only works in a single Availability Zone
  • D. Vertical scaling is the same as elasticity
Click to reveal answer **Correct Answer:** A **Explanation:** Direct lesson exam tip: - **Vertical** = larger (or smaller) instance size - **Horizontal** = more (or fewer) instances of the same size - **Elasticity** = automation + horizontal scaling to match demand Vertical scaling often has a small disruption (reboot) and higher cost at large sizes. Horizontal scaling typically needs a load balancer and attention to sessions, but is usually cheaper and is what Auto Scaling uses. - **B** reverses the disruption characteristics. - **C** is false — you can (and often should) scale across AZs. - **D** — elasticity is not the same as vertical scaling. **Exam tip / trap:** If you see “Auto Scaling group,” think **horizontal + elasticity**, not vertical.

Question 15

A development team can provision a test environment in minutes from the AWS Management Console instead of waiting weeks for hardware. Which cloud benefit is this?

  • A. Increase speed and agility
  • B. Increase capital expense
  • C. Reduce network connectivity so resources cannot be reached
  • D. Require AWS Support to click every button for the team
Click to reveal answer **Correct Answer:** A **Explanation:** **Agility** (increase speed and agility) is a primary AWS value proposition. On-demand self-service plus global infrastructure means teams experiment, deploy, and iterate faster — minutes instead of weeks. This also maps to *speed of deployment* under global infrastructure benefits. - **B** is CapEx, the opposite direction. - **C** contradicts broad network access. - **D** contradicts on-demand self-service. **Exam tip / trap:** Agility on the exam = *faster experimentation, faster provisioning, less time to market*. Do not confuse agility (speed of change) with elasticity (matching capacity to demand) or HA (uptime).

Question 16

A company no longer wants to spend money on power, cooling, racking, and staffing its own data centers. It will use AWS instead. Which advantage of cloud computing is this?

  • A. Stop spending money running and maintaining data centers
  • B. Increase spending on physical data center real estate
  • C. Require the company to build a new data center in every AWS Region
  • D. Move all costs to a one-time hardware purchase
Click to reveal answer **Correct Answer:** A **Explanation:** One of the six AWS advantages of cloud is **stop spending money running and maintaining data centers**. AWS operates the facilities; you consume services. Related advantages you should also know: 1. Trade CapEx for variable expense 2. Benefit from massive economies of scale 3. Stop guessing capacity 4. Increase speed and agility 5. Stop spending money running and maintaining data centers 6. Go global in minutes **Exam tip / trap:** “We still have to manage the underlying hardware in AWS Regions” is a common wrong answer. In the shared responsibility model, AWS manages the infrastructure of the cloud.

Question 17

A company is designing for the AWS Cloud. Which combination of benefits does the AWS global infrastructure provide? (Choose TWO.)

  • A. Speed of deployment (launch resources in minutes)
  • B. Global reach (serve users from Regions around the world)
  • C. A guarantee that every workload runs in a single physical rack that the customer chooses
  • D. Elimination of the need for IAM permissions
  • E. Automatic exemption from all compliance requirements
Click to reveal answer **Correct Answer:** A, B **Explanation:** The exam guide explicitly lists **speed of deployment** and **global reach** as benefits of global infrastructure. Regions, AZs, and edge locations connected by a high-speed network let you design resilient, highly available systems and deploy close to users quickly. - **C** contradicts resource pooling (you choose a Region/AZ, not a specific rack; AWS places the hardware). - **D** — you still need IAM. - **E** — you still share compliance responsibility. **Exam tip / trap:** Resource pooling means you typically **do not know the exact physical location** of the host (beyond Region/AZ). That is a feature of cloud, not a problem.

Question 18

When you launch an Amazon EC2 instance, you select an AWS Region (and optionally an Availability Zone), but you do not choose the exact data center rack. Which cloud computing characteristic does this illustrate?

  • A. Resource pooling
  • B. Dedicated on-premises hardware ownership
  • C. Measured service only
  • D. Vertical scaling
Click to reveal answer **Correct Answer:** A **Explanation:** **Resource pooling** means AWS serves many customers from a shared pool of resources. You do not control (or even know) the exact physical host. You pick a **Region**; AWS may place the instance in any data center in that Region unless you specify an **Availability Zone**. This multi-tenant pooling is also what enables economies of scale. - **B** is the opposite of pooling. - **C** is billing/metering, not location abstraction. - **D** is changing instance size. **Exam tip / trap:** “You cannot choose the exact physical server” = resource pooling. You *can* choose Region and AZ. Do not say “AWS randomly places instances in any Region in the world” — Region is always your choice.

Question 19

Which statements about AWS Cloud billing and usage are correct? (Choose TWO.)

  • A. Resource usage can be monitored and billed
  • B. Customers pay only for what they use instead of pre-provisioning unused capacity
  • C. AWS requires customers to buy three years of capacity before any resource can start
  • D. Monitoring usage is optional and AWS never generates a bill
  • E. Over-provisioning on premises is always cheaper than AWS
Click to reveal answer **Correct Answer:** A, B **Explanation:** The fifth cloud characteristic is **measured service**. Usage is monitored and billed. Combined with elasticity, you scale to demand instead of being over- or under-provisioned. The biggest cost-optimization benefit called out in the lesson: **pay only for what you use**. - **C** describes Reserved Instances / Savings Plans as *optional* discounts, not a requirement to start. - **D** is false. - **E** is not generally true; over-provisioning is a common on-premises cost problem. **Exam tip / trap:** “Pay for what you use” is both a cloud characteristic (measured service) and a cost-optimization benefit. Do not confuse it with “AWS is always free” or “you must reserve everything.”

Question 20

A retailer expects traffic to spike during a holiday sale and drop afterward. They want capacity to grow automatically during the sale and shrink afterward to save money, while remaining able to deploy new features quickly and keep the site up if a single server fails. Which AWS Cloud advantages are they using? (Choose THREE.)

  • A. Elasticity
  • B. High availability
  • C. Agility
  • D. Buying a single oversized server that stays at peak size all year (no scaling)
  • E. Requiring a change ticket to AWS staff before every scale event
Click to reveal answer **Correct Answer:** A, B, C **Explanation:** This scenario hits the three advantages called out in the task statement: | Need in the story | Concept | |---|---| | Grow/shrink automatically with demand, save money off-peak | **Elasticity** (Auto Scaling + horizontal scaling) | | Stay up if one server fails | **High availability** (redundancy, fast recovery) | | Deploy new features quickly | **Agility** (on-demand provisioning, speed) | - **D** is over-provisioning — the opposite of elasticity and cost optimization. - **E** violates on-demand self-service. Together with global infrastructure (deploy fast, go global), these are the core “benefits of the AWS Cloud” for Task 1.1. **Exam tip / trap:** On scenario questions, map phrases: - *scale with demand / pay less when idle* → elasticity - *stay online / recover from failure* → HA (or FT if *zero* downtime) - *launch faster / experiment / innovate* → agility - *users worldwide / another Region* → global reach Do not pick “AWS staff must provision for you” — that is never a cloud benefit.

Quick revision card — Task 1.1

Concept One-line exam meaning
On-demand self-service You provision via console/CLI/API; no AWS human in the loop
Broad network access Reach resources over the network (HTTPS, VPN, SSH, etc.)
Resource pooling Shared multi-tenant capacity; Region/AZ, not a specific rack
Rapid elasticity Capacity grows and shrinks with demand
Measured service Usage metered; pay for what you use
Economies of scale AWS’s huge footprint → lower prices passed to you
CapEx → OpEx Stop buying servers; pay a variable bill
Stop guessing capacity No more over/under-provisioning in advance
Agility Provision and experiment in minutes
Go global in minutes Regions/AZs/edge locations = speed + global reach
High availability Maximize uptime; recover fast; brief downtime possible
Fault tolerance Keep running through a failure; typically no downtime; usually costs more
Disaster recovery The plan to restore after a disaster
Vertical scaling Bigger instance; often reboot; simple for apps
Horizontal scaling More instances + load balancer; cheaper; session-aware
Elasticity Automation + horizontal scaling to match demand