Cloud Digital Leader Fundamental Cloud Concepts Practice Question

A small marketing agency currently runs its customer relationship management (CRM) application on a physical server in its office closet. The server is five years old, and the agency's IT consultant has warned that a disk failure could take the CRM offline for days. The agency wants to move the CRM to Google Cloud so that it can scale capacity up or down as campaign volumes change, without buying new hardware. Which cloud computing benefit does this scenario primarily illustrate?

⚠ Common exam trap

The trap here is assuming that any cloud benefit involving reliability or scaling automatically maps to high availability, when the scenario is really about matching capacity to fluctuating demand.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Elasticity, allowing resources to scale automatically with demand

The agency's core problem is fixed on-premises capacity that cannot flex with campaign demand and depends on aging hardware. Elasticity lets compute and storage resources expand during peak periods and contract afterward, with consumption-based billing. This removes the need to purchase new servers and directly addresses the scaling requirement described in the scenario.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
Vendor lock-in, allowing the agency to depend on a single provider for all services
Why it's wrong here
Vendor lock-in is generally considered a risk or drawback of cloud adoption, not a benefit. It describes difficulty in moving workloads between providers, which is unrelated to the agency's need to scale capacity with campaign demand and retire an aging on-premises server.
✓
Elasticity, allowing resources to scale automatically with demand
Why this is correct
Elasticity means the agency can provision more compute or storage during busy campaign periods and release it afterward, paying only for what it uses. This directly solves the problem of fixed physical hardware that cannot grow or shrink, and it eliminates the multi-day downtime risk tied to a single aging server in an office closet.
✗
Colocation, allowing the server to be housed in a third-party data center
Why it's wrong here
Colocation only moves the agency's own physical server into someone else's facility; it does not provide on-demand scaling or eliminate hardware ownership. The agency would still need to buy, maintain, and eventually replace the server, so the campaign-driven capacity flexibility and the hardware-refresh problem described in the scenario would remain unresolved.
✗
High availability, guaranteeing the CRM will never experience an outage
Why it's wrong here
High availability reduces the likelihood and duration of outages through redundancy, but no cloud provider guarantees that an application will never go down. The scenario's central requirement is flexible capacity that tracks campaign volumes, not an absolute uptime guarantee, so high availability alone does not capture the benefit being described.

Go deeper

Cloud Digital Leader Fundamental Cloud Concepts Practice Question

Why each option matters

Option-by-option breakdown

Related to this question