LFCA 71 🐧 What Cloud Computing Is - KandZ

Cloud computing is the delivery of computing resources — servers, storage, databases, networking, software — over the internet as a service. Instead of buying and maintaining physical hardware, you rent what you need from a provider and pay for what you use. The LFCA exam places this topic under Cloud Computing Fundamentals, which carries 18–20% of the total weight . The competency list includes “Cloud Computing,” “Performance/Availability,” and “Budgeting” . This chapter covers the definition, the essential characteristics, the service models, the deployment models, and the benefits that make cloud computing the dominant model for modern IT.

Key point: The most widely accepted definition comes from the National Institute of Standards and Technology (NIST): “Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction” . This definition contains five essential characteristics, three service models, and four deployment models. The exam tests all three categories.

Why cloud computing exists

Before cloud computing, organizations owned and operated their own IT infrastructure. They bought servers, installed them in data centers, hired administrators to maintain them, and paid for power and cooling to keep them running. This model worked, but it had structural inefficiencies that became more painful as technology advanced.

The capital cost problem. Buying servers, storage, and networking equipment requires significant upfront investment. A single rack of enterprise servers can cost hundreds of thousands of dollars. The organization commits that capital before knowing whether the workload will succeed. If the project fails or scales down, the hardware remains — depreciating, consuming power, and taking up space. Cloud computing converts this capital expense into an operating expense. You pay for what you use, when you use it, with no upfront commitment .

The utilization problem. On-premises infrastructure is sized for peak demand. A retail company might provision servers for the holiday shopping season, but for the other ten months of the year, those servers sit mostly idle. The utilization rate for typical enterprise IT systems is low — often below 20% . Cloud providers pool resources across many customers, so the same physical hardware serves multiple workloads. When one customer’s demand drops, another’s rises. The provider achieves high utilization, and the customer pays only for their share.

The scaling problem. When an on-premises application needs more capacity, someone must order hardware, wait for delivery, install it, configure it, and deploy it. This process takes weeks. When demand drops, the hardware cannot be returned. Cloud resources are provisioned in minutes. A virtual machine can be created on demand. Storage can be expanded with a command. When demand falls, the resources are released, and the billing stops . This elasticity — the ability to scale up and down rapidly — is one of cloud computing’s defining characteristics.

The maintenance problem. On-premises infrastructure requires ongoing maintenance: hardware repairs, firmware updates, operating system patches, security fixes, backup management, and capacity planning. Each of these tasks consumes staff time and requires specialized skills. Cloud providers handle the underlying infrastructure. The customer focuses on their application, not on the data center .

The trade-off. Cloud computing introduces new problems. Security and privacy concerns are significant — data stored on someone else’s hardware must be protected. Vendor lock-in is a real risk: an application built for one cloud provider’s services may require substantial modification to run elsewhere . Compliance with regulations governing data location and handling adds complexity. And the pay-as-you-go model can become expensive if usage is not monitored. The LFCA exam tests both the benefits and the trade-offs.

a. The Five Essential Characteristics

The NIST definition specifies five characteristics that distinguish cloud computing from traditional hosting. These are the criteria that make a service “cloud” rather than merely “remote” .

On-demand self-service. The consumer can provision computing capabilities — server time, storage, network bandwidth — automatically, without requiring human interaction with the service provider. A developer can spin up a virtual machine through a web console or API call and have it running in minutes. No support ticket, no sales call, no waiting for someone to rack a server .

Broad network access. The capabilities are available over the network through standard mechanisms. This means the services are accessible from heterogeneous client platforms — laptops, phones, tablets, workstations — using standard protocols like HTTP, SSH, and APIs. The cloud is not tied to a specific device or location .

Resource pooling. The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model. Physical and virtual resources are dynamically assigned and reassigned according to demand. The consumer generally has no knowledge or control over the exact location of the provided resources, though they may be able to specify location at a higher level of abstraction (country, state, or data center) . This pooling is what enables the provider to achieve high utilization and pass the cost savings to the customer.

Rapid elasticity. Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time . This is the characteristic that makes cloud computing suitable for workloads with unpredictable or seasonal demand.

Measured service. Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (storage, processing, bandwidth, active user accounts). Resource usage is monitored, controlled, and reported, providing transparency for both the provider and consumer. The consumer pays for exactly what they use, and the bill reflects the actual consumption .

b. The Three Service Models

Cloud services are categorized by how much of the technology stack the provider manages and how much the consumer manages. The NIST definition identifies three service models: Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS) .

Infrastructure as a Service (IaaS) provides the fundamental computing resources: processing, storage, networks, and other fundamental computing resources. The consumer can deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications . Examples include Amazon EC2, Microsoft Azure Virtual Machines, and Google Compute Engine . The consumer is responsible for the guest operating system, patches, runtime, middleware, and applications. The provider is responsible for the physical hardware, network, and virtualization layer.

Platform as a Service (PaaS) provides a platform for developing, testing, and deploying applications. The consumer does not manage the underlying infrastructure — network, servers, operating systems, or storage — but has control over the deployed applications and possibly configuration settings for the application-hosting environment . Examples include Heroku, Google App Engine, and AWS Elastic Beanstalk . PaaS provides the runtime, middleware, and development tools. The consumer writes code; the provider handles the rest. This model is efficient for developers who want to focus on application logic without managing servers.

Software as a Service (SaaS) provides applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser, or a program interface. The consumer does not manage or control the underlying cloud infrastructure — network, servers, operating systems, storage, or even individual application capabilities — with the possible exception of limited user-specific application configuration settings . Examples include Gmail, Salesforce, and Office 365 . The consumer simply uses the software. No installation, no maintenance, no patches.

The responsibility split is the key distinction. In IaaS, the consumer manages everything above the virtualization layer. In PaaS, the consumer manages only the application and its data. In SaaS, the consumer manages only their own data and user settings .

c. The Four Deployment Models

Deployment models describe how the cloud infrastructure is provisioned and who has access to it. The NIST definition identifies four: public, private, hybrid, and community .

Public cloud infrastructure is provisioned for open use by the general public. It is owned, managed, and operated by a business, academic, or government organization, or some combination of them. It exists on the premises of the cloud provider. The resources are shared among multiple tenants, and the consumer has limited visibility into the underlying infrastructure . AWS, Azure, and Google Cloud are public clouds. The advantages are low upfront cost, high elasticity, and no maintenance. The risks include multi-tenancy — workloads may be co-resident with competitors or adversaries — and limited control over the physical environment .

Private cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (business units, for example). It may be owned, managed, and operated by the organization, a third party, or some combination, and it may exist on or off premises . The organization has high visibility and control. Security perimeters can be implemented to the same standard as non-cloud resources . The trade-offs are significant upfront investment and fixed capacity — the organization pays for the hardware whether it is used or not. Private clouds are common in government, finance, and healthcare, where data sovereignty and regulatory compliance matter .

Hybrid cloud infrastructure is a composition of two or more distinct cloud infrastructures (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability . A common pattern is hosting mission-critical workloads on-premises and using the public cloud for elastic capacity or less sensitive workloads . This allows the organization to keep sensitive data under its own control while benefiting from the public cloud’s scalability for non-sensitive workloads.

Community cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination, and it may exist on or off premises . Community clouds mitigate some multi-tenancy risks by restricting the set of potential attackers to members of the community, though the security depends on the security of all participant organizations . Examples include cloud services for government agencies or research institutions with shared compliance requirements.

Complete Example Session

This session explores the three service models with a practical scenario: deploying a web application.

# ============================================
# PART 1: THE ON-PREMISES APPROACH
# ============================================

# Buy a physical server
# Install the operating system
# Install the web server (nginx, Apache)
# Install the runtime (Node.js, Python, Ruby)
# Install the database (PostgreSQL, MySQL)
# Configure networking, firewall, backups
# Monitor hardware health
# Replace failed components
# Pay for power and cooling

# You manage everything.

# ============================================
# PART 2: THE IaaS APPROACH
# ============================================

# Provision a virtual machine from a cloud provider
aws ec2 run-instances --image-id ami-12345 --instance-type t3.medium

# SSH into the VM
ssh ec2-user@<public-ip>

# You still install and configure everything above the OS:
sudo yum install nginx
sudo yum install nodejs
sudo yum install postgresql-server
# Configure the application
# Configure backups
# Monitor the VM

# The provider manages the physical hardware.
# You manage the OS, runtime, middleware, and application.

# ============================================
# PART 3: THE PaaS APPROACH
# ============================================

# Deploy the application to a platform
# The platform provides the runtime, web server, and database
git push heroku main

# The platform handles:
# - Operating system
# - Runtime (Node.js, Python, etc.)
# - Web server
# - Database provisioning
# - Scaling
# - Logging
# - Monitoring

# You manage only the application code and its configuration.

# ============================================
# PART 4: THE SaaS APPROACH
# ============================================

# Use a hosted application
# Open a browser
# Navigate to https://mail.google.com
# Log in with credentials

# The application is fully managed.
# You use it, you don't administer it.
# No installation, no patches, no servers.

# ============================================
# PART 5: THE DEPLOYMENT MODEL COMPARISON
# ============================================

# Public cloud:
#   - Multi-tenant
#   - Pay-as-you-go
#   - Low upfront cost
#   - High elasticity
#   - Limited control

# Private cloud:
#   - Single-tenant
#   - High upfront cost
#   - Fixed capacity
#   - High control
#   - Strong security perimeter

# Hybrid cloud:
#   - Combination of public and private
#   - Sensitive workloads on-premises
#   - Elastic workloads in public cloud

# Community cloud:
#   - Shared by organizations with common requirements
#   - Restricted multi-tenancy
#   - Shared compliance and security controls

# ============================================
# PART 6: THE BILLING MODEL
# ============================================

# IaaS: Pay per hour/second for VM, storage, network
# PaaS: Pay per dyno/container instance, plus database
# SaaS: Pay per user per month, or per feature tier

# The pricing model reflects what the provider manages.
# More provider management = more predictable cost per user.
# More consumer management = more variable cost.

# ============================================
# PART 7: THE SERVERLESS EXTENSION
# ============================================

# Function as a Service (FaaS) is a further abstraction.
# You provide the function. The provider handles everything else.
# The function runs when triggered, and you pay per invocation.

# Example: AWS Lambda
# Upload the function code
# Configure the trigger (HTTP request, file upload, timer)
# The provider runs the function when the trigger fires
# You pay for execution time, not idle time

# ============================================
# PART 8: THE VIRTUALIZATION BASIS
# ============================================

# Cloud computing is built on virtualization.
# A hypervisor creates virtual machines on physical hardware.
# Each VM has its own operating system, isolated from others.
# The provider manages the hypervisor and physical hardware.
# The consumer manages the VM's operating system and above.

# Containers are a lighter form of virtualization.
# They share the host operating system kernel.
# They are faster to start and more portable.
# But they provide less isolation than VMs.

# ============================================
# PART 9: THE LFCA EXAM CONTEXT
# ============================================

# The LFCA Cloud Computing domain (18-20%) tests:
# - Cloud computing fundamentals (definition, characteristics)
# - Performance and availability
# - Serverless
# - Cost and budgeting

# The exam expects you to know:
# - The NIST definition and its five characteristics
# - The three service models (IaaS, PaaS, SaaS)
# - The four deployment models (public, private, hybrid, community)
# - The benefits and trade-offs of cloud adoption

# ============================================
# PART 10: THE SUMMARY
# ============================================

# Cloud computing = computing as a utility
# Pay for what you use, when you use it
# Scale up and down on demand
# The provider manages the data center
# You manage what you choose to manage
# The service model determines the boundary

The ten parts cover the on-premises approach, IaaS, PaaS, SaaS, deployment models, billing, serverless, virtualization, LFCA context, and summary.

Quick Reference

The NIST Definition

Element	Description
Definition	On-demand network access to a shared pool of configurable computing resources
Provisioning	Rapid, with minimal management effort
Five characteristics	On-demand self-service, broad network access, resource pooling, rapid elasticity, measured service
Three service models	IaaS, PaaS, SaaS
Four deployment models	Public, private, hybrid, community

The Service Models

Model	Provider Manages	Consumer Manages	Examples
IaaS	Hardware, network, virtualization	OS, runtime, middleware, app, data	EC2, Azure VMs, GCE
PaaS	Hardware, network, virtualization, OS, runtime, middleware	App, data	Heroku, App Engine, Elastic Beanstalk
SaaS	Everything	Data, user settings	Gmail, Salesforce, Office 365

The Deployment Models

Model	Access	Control	Cost	Use Case
Public	General public	Limited	Low upfront	Web apps, startups
Private	Single organization	High	High upfront	Government, finance
Hybrid	Combination	High for on-prem	Mixed	Sensitive + elastic
Community	Shared organizations	Shared	Shared	Compliance communities

The Benefits and Trade-offs

Benefit	Trade-off
Low upfront cost	Ongoing operational cost
Rapid provisioning	Vendor lock-in
Elastic scaling	Security and privacy concerns
No maintenance	Limited control
High utilization	Multi-tenancy risks

Best Practices

✅ Do This:

# Start with the service model that matches your team's skills
# SaaS if you want zero maintenance
# PaaS if you want to focus on code
# IaaS if you need full control           # ✅

# Monitor cloud spending from day one
# Set budget alerts in the provider console # ✅

# Use the deployment model that matches your compliance requirements
# Private or hybrid for regulated data      # ✅

# Understand the shared responsibility model
# Know what the provider manages and what you manage # ✅

❌ Don’t Do This:

# Don't assume the cloud is automatically secure
# Security is a shared responsibility          # ❌

# Don't provision resources without monitoring usage
# Unused resources still cost money            # ❌

# Don't ignore vendor lock-in when designing
# Migration between providers can be expensive # ❌

# Don't treat the cloud as just "someone else's computer"
# The service models and deployment models matter # ❌

Common Pitfalls

Pitfall	Why It Happens	Fix
Unexpected bill	Resources left running	Set budget alerts, review usage
Security breach	Misconfigured access	Follow shared responsibility model
Vendor lock-in	Using provider-specific services	Abstract where possible
Performance issues	Wrong service model	Match model to workload
Compliance violation	Data stored in wrong region	Configure location restrictions

Real-World Examples

1. NIST Definition

# "Cloud computing is a model for enabling ubiquitous,
# convenient, on-demand network access to a shared pool
# of configurable computing resources."

2. IaaS Example

aws ec2 run-instances --image-id ami-12345 --instance-type t3.medium

3. PaaS Example

git push heroku main

4. SaaS Example

# Navigate to https://mail.google.com

5. Public Cloud

# AWS, Azure, Google Cloud

6. Private Cloud

# On-premises OpenStack or VMware

7. Hybrid Cloud

# On-premises database + public cloud web tier

8. Community Cloud

# Government shared services cloud

9. Serverless

# AWS Lambda, Azure Functions, Google Cloud Functions

10. Virtualization

# Hypervisor creates VMs on physical hardware

Visual

The Cloud Computing Stack

┌──────────────────────────────────────────────┐
│  CLOUD COMPUTING STACK                       │
│                                              │
│  SaaS:   Application (Gmail, Salesforce)     │
│  ─────────────────────────────────────────   │
│  PaaS:   Runtime, Middleware, Database       │
│  ─────────────────────────────────────────   │
│  IaaS:   Virtual Machines, Storage, Network  │
│  ─────────────────────────────────────────── │
│  Physical: Servers, Disks, Switches          │
│                                              │
│  Provider manages from the bottom up.        │
│  Consumer manages from the top down.         │
│  The boundary depends on the service model.  │
│                                              │
└──────────────────────────────────────────────┘

The Five Characteristics

┌──────────────────────────────────────────────┐
│  NIST CHARACTERISTICS                        │
│                                              │
│  1. On-demand self-service                   │
│     └─ Provision without human interaction   │
│                                              │
│  2. Broad network access                     │
│     └─ Available over the network            │
│                                              │
│  3. Resource pooling                         │
│     └─ Multi-tenant, dynamically assigned    │
│                                              │
│  4. Rapid elasticity                         │
│     └─ Scale up and down quickly             │
│                                              │
│  5. Measured service                         │
│     └─ Pay for what you use                  │
│                                              │
└──────────────────────────────────────────────┘

The Deployment Models

┌──────────────────────────────────────────────┐
│  DEPLOYMENT MODELS                           │
│                                              │
│  PUBLIC:                                     │
│  Shared infrastructure, multi-tenant         │
│                                              │
│  PRIVATE:                                    │
│  Dedicated infrastructure, single-tenant     │
│                                              │
│  HYBRID:                                     │
│  Public + private, workload placement        │
│                                              │
│  COMMUNITY:                                  │
│  Shared by organizations with common needs   │
│                                              │
└──────────────────────────────────────────────┘

The Shared Responsibility Model

┌──────────────────────────────────────────────┐
│  SHARED RESPONSIBILITY                       │
│                                              │
│  IaaS:                                       │
│    Provider: Hardware, network, hypervisor   │
│    Consumer: OS, runtime, app, data          │
│                                              │
│  PaaS:                                       │
│    Provider: Hardware, network, OS, runtime  │
│    Consumer: App, data                       │
│                                              │
│  SaaS:                                       │
│    Provider: Everything                      │
│    Consumer: Data, user settings             │
│                                              │
└──────────────────────────────────────────────┘

Summary

Item	Value
NIST definition	On-demand network access to shared configurable resources
Five characteristics	Self-service, network access, pooling, elasticity, measured
Three service models	IaaS, PaaS, SaaS
Four deployment models	Public, private, hybrid, community
IaaS	Infrastructure (VMs, storage, network)
PaaS	Platform (runtime, middleware, database)
SaaS	Software (fully managed application)
Public cloud	Shared, multi-tenant, pay-as-you-go
Private cloud	Dedicated, single-tenant, high control
Hybrid cloud	Combination of public and private
LFCA weight	Cloud Computing Fundamentals, 18–20%

Key takeaways:

Cloud computing is the delivery of computing resources as a utility over a network. You pay for what you use, when you use it, and the provider manages the underlying infrastructure. The NIST definition is the standard reference .
The five essential characteristics are the criteria for “cloud.” On-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. A service that does not have all five is not cloud computing in the NIST sense .
The three service models describe the responsibility boundary. IaaS gives the consumer control over the OS and above. PaaS gives the consumer control over the application only. SaaS gives the consumer control over nothing but their data and settings .
The four deployment models describe who has access. Public clouds are open to everyone. Private clouds are for one organization. Hybrid clouds combine both. Community clouds serve organizations with shared requirements .
The benefits are cost, speed, scalability, and maintenance. The trade-offs are security, control, vendor lock-in, and ongoing cost management. The LFCA exam tests both sides .
Virtualization is the foundation. Virtual machines and containers are the mechanisms that allow cloud providers to pool physical resources and allocate them on demand. The consumer’s experience of the cloud is built on this abstraction .
The LFCA Cloud Computing domain carries 18–20% of the exam weight. The competencies include cloud computing fundamentals, performance/availability, serverless, and cost/budgeting .

Remember: Cloud computing is not a single technology. It is a delivery model for computing resources, defined by five characteristics, organized into three service models and four deployment models. The provider owns the infrastructure. The consumer rents what they need. The boundary of responsibility shifts with the service model. The LFCA exam expects you to know the definition, the characteristics, the models, and the trade-offs. Cloud computing is computing as a utility — the same way electricity is a utility. You do not build a power plant to use a light bulb, and you do not buy a data center to run a web application.

Stop using slow, ad-bloated tool sites! 🤮

🔎 Search “KandZ Tools” on Google to use many professional utilities for free.

KandZ.me is the ultimate minimalist hub for:
✅ Finance (Mortgage, Interest, Inflation)
✅ Tech (Base64, JSON, Dev Suite, IP)
✅ Health (BMI, BMR, TDEE)
✅ Productivity (Timer, Workspace, QR)

⚡️ Fast & Private
🔒 No data leaves your device
💎 100% Free

🔗 Use it now: https://tools.kandz.me
🔖 Bookmark it—you’ll need it later!