Module 1: Fundamentals of Cloud

Computing and Virtualisation

Exam Prep Notes — Step-by-Step Study Guide

1. Introduction to Cloud Computing

Definition (5-mark answer)
Cloud Computing is the availability of processing power, storage, and applications delivered on demand to customers over
the internet. Instead of owning physical hardware/software, users access computing resources as a service, paying based on
usage.

Key Points to Expand for 5 Marks

Point Detail
Provider hosts resources (servers, storage) in data centers -> user accesses via internet ->
How it works
pays per use/subscription
Services offered IaaS, PaaS, SaaS
Term symbolizes the internet/network - abstracts away physical infrastructure from the
Why "cloud"
user
Coined by Ramesh Chellappa (1997); roots in IBM/DEC timesharing (1960s), first VM by
History
IBM (1972); major growth: AWS (2002), Google App Engine (2008), Azure (2010)
No infra setup, automatic upgrades, legacy integration, reduced capex, easy maintenance,
Why businesses adopt it
easy scalability

Origins - Convergence of Technologies

Cloud computing emerged from the convergence of:
• Distributed systems - multiple systems appear as one to users
• Mainframe computing - powerful, reliable machines
• Cluster computing - networked machines, high bandwidth
• Grid computing - geographically distributed systems via internet
• Virtualization - virtual layer over hardware for multiple instances
• Web 2.0 - interactive, dynamic web pages
• Utility computing - pay-per-use service provisioning

Quick One-Liner to Memorize

"Cloud computing = renting computing services, born from the convergence of distributed computing, internet
technologies, and systems management advances."

2. Characteristics of Cloud Computing

15 total characteristics - high-yield topic, likely a full 5-mark question. If asked to "list and explain," pick 5-6 strong ones
unless asked for all 15.
# Characteristic One-line explanation Example
Provider pools CPU, RAM, storage, Google Drive - you don't know
1 Resource Pooling
bandwidth and shares among many users which server holds your files
 # Characteristic One-line explanation Example
User provisions resources automatically,
2 On-Demand Self-Service Creating a VM on AWS in minutes
without provider staff involvement
3 Easy Maintenance Provider handles updates, backups, repairs Less in-house IT staff needed
Scalability & Rapid Resources increase/decrease with demand, 10 servers -> 100 during festival sale
4
Elasticity often automatically -> back to 10
Reduces capex - no need to buy/maintain
5 Economical Startup avoids Rs.10 lakh server cost
hardware
Measured & Reporting Usage (CPU, storage, traffic) is monitored Metered service - pay for 500GB
6
Service for billing used
Shared responsibility: provider
Protects data, apps, VMs via authentication,
7 Security secures infra, user secures
encryption, firewalls
passwords/config
Tasks done with minimal human
8 Automation Auto-scaling on traffic spike
intervention
Available 24x7; recovers quickly from Server A fails -> traffic shifts to
9 Resiliency & Availability
failure Server B
10 Large Network Access Accessible from many devices over network Laptop, smartphone, tablet
Access files/apps from anywhere with
11 Work From Any Location Edit a PPT at home, reopen at college
connectivity
Multiple customers share infra, data Apartment building analogy - same
12 Multi-Tenancy
logically isolated building, separate flats
Easily change CPU, RAM, storage, OS as 2 CPU+4GB -> scale to 8
13 Flexibility
needed CPU+16GB
High performance, reliability, support -
14 Service Excellence Defined uptime commitments
backed by SLAs
Comfortable Payment
15 Pay-as-you-go or subscription models Pay only for 10 hours used
Structure

If the Question Is Exactly 5 Marks and Says "Explain Any 5"

Pick: Resource Pooling, On-Demand Self-Service, Scalability & Elasticity, Multi-Tenancy, Measured Service - these are the
most commonly asked and easiest to explain with examples.

Mnemonic-ish Grouping for Quick Recall

• Access-related: On-Demand, Large Network Access, Work From Anywhere
• Resource-related: Resource Pooling, Scalability/Elasticity, Multi-Tenancy, Flexibility
• Operational: Easy Maintenance, Automation, Measured Service
• Trust-related: Security, Resiliency/Availability, Service Excellence
• Cost-related: Economical, Comfortable Payment Structure

3. Cloud Types - NIST Model

Definition (5-mark answer)
NIST (National Institute of Standards and Technology) defines cloud computing through 14 interrelated terms, organized as:
• 1 core definition
• 5 essential characteristics
• 3 service models
• 4 deployment models
• 5 actors
5 Essential Characteristics (NIST)
• On-demand self-service
• Broad network access
• Resource pooling
• Rapid elasticity
• Measured service
Note: these overlap with the 15 characteristics studied earlier - NIST's version is the "official" condensed 5.

3 Service Models
SaaS, PaaS, IaaS (covered in detail in Topic 5)

4 Deployment Models
Public, Private, Community, Hybrid

5 Actors in Cloud Computing

Very likely a 5-mark question on its own.
Actor Definition
Person/org that maintains a business relationship with, and uses services from, Cloud
Cloud Consumer
Providers
Cloud Provider Person/org/entity responsible for making a service available to interested parties
Conducts independent assessment of cloud services - security, privacy, performance
Cloud Auditor
audits
Manages use, performance, and delivery of cloud services; negotiates between
Cloud Broker
Provider and Consumer
Intermediary providing connectivity/transport of cloud services from Provider to
Cloud Carrier
Consumer

Interactions Among Actors

Useful for diagram-based questions:
• Consumer <-> Provider <-> Carrier: SLA1 exists between Consumer-Provider, SLA2 exists between Provider-Carrier
• Consumer -> Broker -> Provider(s): Broker may combine/enhance multiple provider services; consumer only interacts
with broker, not the actual providers (broker hides them)
• Consumer <-> Provider <-> Auditor: Auditor independently assesses both sides for compliance/security

Quick Answer Structure for "Explain NIST Cloud Model" (5 marks)

• One line: NIST defines cloud via 14 terms - characteristics, service models, deployment models, actors
• List 5 characteristics
• List 5 actors with 1-line definitions
• Optionally mention the reference architecture diagram (Consumer-Provider-Broker-Auditor-Carrier)

4. Cloud Types - Cloud Cube Model

Definition (5-mark answer)
The Cloud Cube Model, proposed by the Jericho Forum, classifies cloud-based networks along four dimensional elements,
aimed primarily at providing security and protecting the cloud network/web. It helps IT managers and organizations choose
the right, secure cloud setup.
The 4 Dimensions
Dimension Meaning
1. Internal vs External Internal = Private Cloud; External = Public Cloud
Proprietary = paid/contracted services; Open = open-source, freely
2. Proprietary vs Open
shareable APIs (e.g., Google App Engine)
3. Perimeterized (Per) vs De-perimeterized Per = operations inside traditional IT security boundary (firewalls) - maps to
(D-p) IaaS/PaaS; D-p = outside boundary, not hardware-restricted - maps to SaaS
Insourced = in-house cloud development; Outsourced = handled by
4. Insourced vs Outsourced
contractors/service providers

Working of the Model - 4 Measurement Factors

Factor What it measures
Physical Location of Data Internal or external -> defines organization's boundary
Ownership Proprietary or open -> tech ownership, interoperability, data portability, vendor lock-in
Security Range Parameterized or de-parameterized -> inside/outside security boundary (firewall)
Sourcing In-sourced or out-sourced -> who provides the service (customer or provider)

Quick Answer Structure for 5 Marks

• Define Cloud Cube Model + purpose (security classification, Jericho Forum)
• List the 4 dimensions with a one-line meaning each
• Optionally mention the "working" - 4 measurement factors (can substitute if dimensions already covered)

Memory Tip
Think of it as 4 axes of a cube, each a yes/no choice about where (internal/external), who owns it (proprietary/open),
security boundary (per/d-p), and who runs it (in/out sourced).

5. Cloud Service Models - IaaS, PaaS, SaaS

High-yield, very likely a full question.

Core Definition
Cloud service models define what layer of the computing stack the provider manages vs. what the customer manages -
ranging from maximum customer control (IaaS) to minimum (SaaS).

The Three Models

Model Full Form What it provides Example
Virtual machines, servers, storage, load AWS EC2, Google
IaaS Infrastructure as a Service
balancers, network Compute Engine
Execution runtime, databases, web Google App Engine,
PaaS Platform as a Service
servers, dev tools Heroku
Gmail, Google Drive,
SaaS Software as a Service Ready-to-use applications
Zoom

Who Manages What

Classic 5-mark diagram question.
Layer On-Premises IaaS PaaS SaaS
Applications You You You Provider
 Layer On-Premises IaaS PaaS SaaS
Data You You You Provider
Runtime You You Provider Provider
Middleware You You Provider Provider
O/S You You Provider Provider
Virtualization You Provider Provider Provider
Servers You Provider Provider Provider
Storage You Provider Provider Provider
Networking You Provider Provider Provider
Control spectrum: IaaS = Maximum control (you) -> SaaS = Minimum control (you), maximum managed by vendor

The Cake Analogy (Easy to Recall & Write)

Model Analogy Managed by You Managed by Vendor
On-Premises Made at Home Everything Nothing
Dining table, water, electricity,
IaaS Buy & Bake Cake pan, flour, sugar, butter, eggs
oven
PaaS Cake Delivery Flour, sugar, butter, eggs (contents) Everything else including oven
SaaS Dine Out Nothing Everything

Why Use Each (Why / Who Table)

SaaS IaaS PaaS
Affordable, easily accessible, Minimizes cost, scalable, simple Minimizes dev time, supports
Why
ready to use deployment multiple languages, collaboration
Projects with multiple
Who Small-scale businesses Need control over hardware infra
developers/vendors

Quick Answer Structure for 5 Marks ("Explain IaaS, PaaS, SaaS with Examples")
• One line each: definition + what's provided
• One example each
• Mention control spectrum (IaaS = max control, SaaS = min control)
• Optionally: who manages what table (2-3 rows is enough for 5 marks)

6. Cloud Deployment Models - Public, Private, Hybrid

Very high-yield, detailed comparison likely asked.

Core Definition
Deployment models describe where the cloud infrastructure is hosted and who can access it.

The Bus / Car / Taxi Analogy

Easy to write, examiner-friendly.
Model Analogy Meaning
Public Bus Accessible to everyone
Private Own Car Owned by a single person/org
Hybrid Taxi Rent a private resource when needed
Definitions
Type Definition
Infrastructure located on the premises of the company offering the service; supports all users
Public Cloud
on a subscription basis. Used for app dev/testing, file-sharing, email
Infrastructure used by a single organization; managed by the org itself or a service provider
Private Cloud
(on-site/off-site)
Combines interconnected private and public infrastructure; used to scale IT rapidly (e.g.,
Hybrid Cloud
public cloud supplements private cloud capacity during peak load)

Full Comparison Table

Strong 5-mark answer on its own.
Attribute Public Cloud Private Cloud Hybrid Cloud
Owned by customers Partially by provider, partially
Ownership Owned by single org
(provider) by consumer
Performance Low to medium Excellent Good
Setup cost Low initial cost High Medium
Used by Anyone can access Limited people Medium accessibility
Security Less Highest Medium
Full (private part) + limited
User's control Limited Full
(public part)
Maintenance cost Lowest Highest Moderate
Not suitable for large
Workload Normal, short spikes Highly dynamic/changeable
workload
Reliability Medium Highest Medium

When to Use Each (Advantages / Drawbacks)

Good for scenario-based questions.
Type When to use Advantages Drawbacks
Predictable computing needs, No CapEx, technical agility, Lack of cost/security
Public
dev/test environments affordability control
Regulated industries, sensitive data, Exclusive environment, custom Price, mobile access
Private
need strong control security, scalability difficulty
Multiple compliance needs, Policy-driven, scale with security, Price, management
Hybrid
optimizing investment cost control complexity

Top Companies
• Public: AWS, Microsoft Azure, Google Cloud, IBM
• Private: VMware, Dell, Oracle, Cisco
• Hybrid: Amazon, HP, Google, Microsoft

Quick Answer Structure for 5 Marks ("Compare Public, Private, Hybrid")

Pick 5 rows from the comparison table (Ownership, Security, Cost, Control, Used by) - that alone fills a clean 5-mark table
answer.
7. Exploring the Cloud Computing Stack (6 Layers)
Core Definition
The Cloud Computing Stack shows the layered architecture of cloud resources, from the physical hardware at the bottom up
to the client-facing layer at the top. IaaS, PaaS, SaaS map onto different portions of this stack.

The 6 Layers (Top to Bottom)

Layer Description
Hardware/software that relies on the cloud for application delivery; essentially useless
1. Clients
without the cloud
Software systems supporting interoperable machine-to-machine interaction over a network
2. Services
(aka Web Services)
3. Application Leverages the cloud in software architecture - eliminates need to install/run apps locally
Delivery of a computing platform/solution stack as a service - enables app deployment
4. Platform
without managing underlying hardware/software
5. Storage Delivery of data storage as a service (often billed per GB/month)
6. Infrastructure Delivery of computer infrastructure (typically platform virtualization) as a service

Mapping to Service Models

Stack Layers Maps to
Clients, Services, Application SaaS
Platform PaaS
Storage, Infrastructure IaaS

Alternate View - Cloud Applications Diagram

Service Class Access Tool Content
SaaS Web Browser Social networks, office suites, CRM, video processing
Programming languages, frameworks, mashup editors,
PaaS Cloud Dev Environment
structured data
IaaS Virtual Infrastructure Manager Compute servers, data storage, firewall, load balancer
Full stack (bottom to top): Data Center -> Networking/Firewalls -> Servers & Storage -> Virtualization -> Operating
Systems -> Dev Tools/DB Management -> Hosted Applications

Quick Answer Structure for 5 Marks

• One-line definition of the stack concept
• List the 6 layers top to bottom with a one-line description each
• Map layers to IaaS/PaaS/SaaS (this is usually the actual "point" being tested)

8. Advantages, Disadvantages & Applications of Cloud Computing

Potential Advantages vs Disadvantages
Classic 5-mark table question.
Potential Advantages Potential Risks/Disadvantages
Reduced costs for rented IT hardware/software vs in-house
Increased costs of communications (to telecom/ISPs)
equipment (shift from CapEx to OpEx)
Reduced cost of in-house IT management Increased costs for data/service migration and integration
Enhanced elasticity of storage/processing per demand Reduced control over data and applications
 Potential Advantages Potential Risks/Disadvantages
Greater flexibility and mobility of access to data/services
Data security and privacy concerns
Unreliable services (e.g., due to inadequate ICT/power
Immediate and cost-free upgrading of software
infra)
Risk of vendor lock-in (limited interoperability & data
Enhanced reliability/security of data and services
portability)
Quick way to answer "Advantages and Disadvantages" (5 marks): Pick 5 pairs from the table above - write as two columns.

Applications of Cloud Computing

Easy list-based 5-marker.
Application Use
Online Data Storage Store files remotely (Google Drive, Dropbox)
Backup and Recovery Automated, simple, inexpensive data backup/restore
Big Data Analysis Processing large datasets using cloud compute power
Testing and Development Quick provisioning of dev/test environments without hardware setup
Antivirus Applications Cloud-based threat detection and updates
E-commerce Applications Scalable infra for online stores handling variable traffic
Cloud Computing in Education E-learning platforms, shared resources, remote access to study material
Quick answer structure for 5 marks ("List applications of cloud computing"): List all 7, with a half-line explanation each -
that alone is a clean 5-mark answer.

Module Complete - Quick Revision Map

• 1. Introduction - definition, history, why adopt
• 2. Characteristics (15) - pooling, on-demand, elasticity, multi-tenancy, etc.
• 3. NIST Model - 5 characteristics, 3 service models, 4 deployment models, 5 actors
• 4. Cloud Cube Model - 4 dimensions (Internal/External, Proprietary/Open, Per/D-p, In/Outsourced)
• 5. Service Models - IaaS/PaaS/SaaS + who manages what
• 6. Deployment Models - Public/Private/Hybrid + comparison table
• 7. Cloud Stack - 6 layers (Clients -> Services -> App -> Platform -> Storage -> Infra)
• 8. Advantages/Disadvantages/Applications