Task 1.1: Define the benefits of the AWS Cloud.

• AGo global in minutes

  Incorrect

  This advantage is about deploying in several Regions to give distant users lower latency. It does nothing about servers bought for a peak.

• BStop guessing capacity

  Correct

  A capacity decision made before deploying leaves you with idle resources or too little capacity. In the cloud you scale up and down as demand changes, so there is no peak-sized fleet to sit idle.

• CBenefit from massive economies of scale

  Incorrect

  Aggregated usage lets AWS charge lower pay-as-you-go prices, but a cheaper unit price does not stop you buying for the peak.

• DStop spending money running and maintaining data centers

  Incorrect

  This one is about no longer racking, stacking and powering servers. The problem here is how much capacity is bought, not who maintains it.

Idle capacity bought for a forecast peak is the "guessing capacity" problem. The cloud answer is to provision for today's demand and scale with it.

• AIncrease speed and agility

  Incorrect

  Agility means new resources reach developers in minutes instead of weeks. It does not bring the application any closer to distant users.

• BTrade fixed expense for variable expense

  Incorrect

  This changes how you pay — only for what you consume — not where the application runs.

• CStop guessing capacity

  Incorrect

  This is about having the right amount of capacity. The slow loads come from distance, not from too little capacity.

• DGo global in minutes

  Correct

  You can deploy the application in multiple Regions around the world with a few clicks, which gives customers lower latency and a better experience.

Latency that grows with distance is solved by running closer to users, and AWS's global infrastructure makes a second or third Region a deployment, not a construction project.

• ABenefit from massive economies of scale

  Incorrect

  Economies of scale lower the unit price AWS can charge. They do not change how fast the team gets servers for an experiment.

• BGo global in minutes

  Incorrect

  This benefit is about deploying in Regions close to users around the world. The team's problem is waiting weeks for servers, not distance.

• CIncrease speed and agility

  Correct

  New IT resources are only a click away, so the time to make them available drops from weeks to minutes, and the cost and time of an experiment fall with it.

• DStop guessing capacity

  Incorrect

  This benefit is about not having to forecast how much capacity a workload will need. The team knows what it needs; it needs it quickly.

Short-lived experiments are where agility pays: resources arrive in minutes, and the ones that do not work out are simply deleted.

• AAWS becomes responsible for patching the instances' operating systems

  Incorrect

  On Amazon EC2 the customer still manages the guest operating system, including its security patches, however many instances are running.

• BIt no longer has to forecast and buy capacity for the evening peak

  Correct

  Instead of making a capacity decision in advance, it can use as much or as little capacity as it needs and scale up and down with demand.

• CIts data is copied to every AWS Region automatically

  Incorrect

  Resources and data created in one Region do not exist in any other Region unless you copy or replicate them. Scaling does not change that.

• DIt pays for the extra instances only while they are running

  Correct

  With variable expense you pay only when you consume computing resources, and only for how much you consume, so the night-time hours cost less.

• EIt gets a lower hourly rate in exchange for committing to a fixed amount of usage

  Incorrect

  That describes a commitment discount such as a Savings Plan, which you buy separately for a one- or three-year term. Scaling with demand does not earn one.

Elasticity turns a fixed, peak-sized fleet into capacity that follows demand: no forecast to get wrong and no idle servers to pay for at night.

• ATrade fixed expense for variable expense

  Incorrect

  This advantage is about when and how you pay — only for what you consume — not about why the unit price can be lower.

• BStop guessing capacity

  Incorrect

  This advantage is about scaling with demand instead of forecasting. It does not explain the price per unit.

• CGo global in minutes

  Incorrect

  This advantage is about deploying close to users around the world.

• DBenefit from massive economies of scale

  Correct

  Because usage from hundreds of thousands of customers is aggregated, AWS achieves higher economies of scale, which translates into lower pay-as-you-go prices than a company could reach on its own.

Scale is the reason: a provider buying and running infrastructure for a vast number of customers gets a lower cost per unit and passes it on in its prices.