Cloud Digital Leader Why Cloud Technology Can Transform Business Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Global Reach

  Why it's wrong here

  Global Reach in cloud computing means distributing applications across multiple geographic regions (e.g., Google Cloud's global network of regions and edge points of presence) to reduce latency and comply with data residency laws. While essential for launching a mobile app worldwide, it describes the infrastructure footprint, not the commercial billing model. The requirement to pay only for resources used is a financial attribute tied to pricing, which Global Reach does not address. Thus, although valuable, it is not the correct answer for the stated cost-efficiency need.

• ✗

  Agility

  Why it's wrong here

  Agility in cloud platforms refers to the speed and ease with which you can provision, modify, and redeploy infrastructure and application code, often via automation, CI/CD, and managed services. For a startup launching a new app, agility reduces time-to-market and lets you iterate quickly, but it does not inherently change how you are billed; you can still be charged on a fixed or committed basis regardless of how fast you deploy. The startup's core requirement is a billing model that aligns costs with actual usage, which is a separate dimension from operational agility. Therefore, agility is not the key driver of paying only for consumed resources.

• ✓

  Pay-as-you-go pricing

  Why this is correct

  Pay-as-you-go pricing is a usage-based billing model where cloud customers pay per unit of measured consumption (e.g., vCPU-hours, GB-months, or network requests) with no upfront capital expenditures or minimum commitments. For a startup with limited budget and uncertain initial user volume, this model directly matches the requirement of paying only for resources actually used, because the bill scales with demand and can be near-zero when the app has no traffic. It avoids the waste of idle capacity that is inherent in fixed-cost models like reserved instances or on-premises hardware. This is the precise reason it is the correct choice for the described cost-efficiency need.

• ✗

  Scalability

  Why it's wrong here

  Scalability is the architectural capability to automatically or manually adjust resources in response to traffic changes, such as using managed instance groups or serverless autoscaling to handle global mobile app spikes. While autoscaling can reduce wasted resources during low-demand periods, the actual charging mechanism that ensures you pay only for what you use is the pricing contract itself. In fact, a system can be highly scalable yet still be billed at a flat monthly rate if the cloud contract is set up that way. Thus scalability alone does not guarantee usage-based billing; the pay-as-you-go model is the fundamental enabler of that financial outcome.

Go deeper

Related to this question