Cloud Digital Leader Practice Question: According to the NIST definition of cloud…

Answer analysis

Option-by-option breakdown

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

• ✗

  Broad network access

  Why it's wrong here

  Broad network access means that cloud capabilities are available over the network through standard protocols and can be accessed from a variety of client platforms (e.g., mobile phones, laptops, workstations). This characteristic focuses on the ubiquity and standardization of the access path, not on how resources are provisioned. Even if a user can reach the cloud from anywhere, the ability to autonomously create and manage resources is a separate capability — broad network access is a prerequisite for remote management, not the mechanism that allows automatic provisioning without human interaction.

• ✓

  On-demand self-service

  Why this is correct

  On-demand self-service is the NIST cloud characteristic that lets a consumer unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. This is the precise capability described in the question: the user accesses a portal or API and immediately spins up resources, eliminating manual procurement or IT ticket workflows. It is the defining user-facing attribute of cloud computing that differentiates it from traditional IT, where a human administrator must manually allocate capacity — and it directly matches the scenario's requirement for automatic provisioning.

• ✗

  Resource pooling

  Why it's wrong here

  Resource pooling is a foundational NIST characteristic describing the provider's use of a multi-tenant model where compute, storage, and network resources are dynamically assigned and reassigned according to demand. This architectural approach maximizes efficiency and cost-effectiveness for the provider by sharing physical infrastructure among many customers, but it says nothing about a user's ability to request or spin up resources. The key mechanism in resource pooling is the provider's internal scheduling and isolation, not a self-service interface — so while it enables cloud economics, it does not fulfill the user-driven provisioning described in the scenario.

• ✗

  Measured service

  Why it's wrong here

  Measured service is the cloud characteristic where resource usage (CPU, storage, bandwidth, active user accounts) is automatically monitored, controlled, and reported, providing transparency for both the provider and consumer. This metering is what enables pay-per-use billing and usage optimization, but it describes the telemetry and billing loop after resources are already in operation. The scenario's requirement is about initiating resource creation without human intervention — a provisioning action — which is fundamentally different from the ongoing measurement and reporting of usage that measured service provides.

Go deeper

Related to this question