is a paradigm enabling network access to a scalable, elastic pool of shareable resources with self-service provisioning and administration on demand.

Context: ISO definition of cloud computing

In NIST’s model, means consumers can provision capabilities automatically as needed without requiring human interaction with each provider.

Context: NIST essential characteristics: on-demand self-service

NIST’s means capabilities are available over the network via standard mechanisms for heterogeneous client platforms.

Context: NIST essential characteristics: broad network access

pools provider resources for multiple consumers using a multi-tenant model with dynamic assignment based on demand.

Context: Resource pooling and multi-tenancy

lets capabilities scale outward/inward quickly (often automatically) to match demand, appearing unlimited to consumers.

Context: Rapid elasticity

meters resource usage to enable monitoring, reporting, and transparency for both provider and consumer.

Context: Measured service and metering

Cloud value can improve time-to-market and shift costs toward usage-based OpEx because enables transparency and supports elastic scaling.

Context: Cloud value proposition depends on measured service

In the shared responsibility model, the provider secures infrastructure while customers secure data, identity/access, and application-level security; responsibility shifts by .

Context: Shared responsibility model across IaaS/PaaS/SaaS

Cloud adoption depends on trade-offs involving scalability, latency, cost structure, regulatory constraints, and customization needs versus on-prem control; this is captured by .

Context: Cloud adoption and suitability

Cloud migration involves transferring workloads across environments with compatibility differences; this becomes complicated, time-consuming, and expensive, potentially causing downtime, reduced performance, or data loss.

Context: Cause→effect relationship: migration compatibility differences lead to risk

Cloud abstractions simplify resource management, which can lead to that expose underlying complexity and limitations, requiring deeper understanding to mitigate.

Context: Leaky abstractions

Customers become dependent on specific services within the same vendor; this creates which makes switching to alternative services within the same vendor difficult as needs change.

Context: Cause→effect relationship: dependency leads to service lock-in

If cloud spending is not properly governed, and cost overruns become more likely because usage can exceed expectations without accurate forecasting, proactive monitoring, and optimization.

Context: Cause→effect relationship: lack of governance leads to budget overruns

is a framework that standardizes financial operations in the cloud to manage and optimize cloud spending.

Context: FinOps

SLAs often exclude planned maintenance, external network issues, human error (such as misconfigurations), natural disasters/force majeure, and security breaches; therefore customers must monitor compliance and file claims within a timeframe because compensation is not guaranteed for every outage. This tests about SLA scope.

Context: Service Level Agreements (SLAs) and customer burdens