■■ Cloud Computing
Complete Study Notes
SPPU In-Semester Exam Preparation
Previous Year Questions – Explained Simply
Topics Covered
Q1a: Cloud Deployment Models (Public, Private, Hybrid, Community)
Q1b: Cloud Service Models Architecture (IaaS, PaaS, SaaS)
Q2a: Challenges of Cloud Computing
Q2b: Federated Cloud – Concept & Benefits
Benefits of Cloud Hosting
Cloud Federation – Detailed
Benefits of Cloud Computing
Cloud Computing Definition + Challenges
Q1a) Cloud Deployment Models [8 Marks]
Significance of various cloud deployment models with their benefits and applicability.
1. ■ Public Cloud
• Resources owned & managed by third-party providers (AWS, Azure, GCP), shared over the internet
• No upfront cost – pay-as-you-go
• Highly scalable & elastic | Zero maintenance for the user | Global availability
• Applicability: Startups, e-commerce, web apps, email services, online storage (Google Drive)
2. ■ Private Cloud
• Cloud infrastructure used exclusively by one organization, hosted on-premise or by a third party
• High security & data privacy | Full control over resources | Customizable as per org needs
• Meets compliance requirements
• Applicability: Banks, hospitals, government agencies, organizations with sensitive data
3. ■ Hybrid Cloud
• Combination of Public + Private cloud, connected together
• Best of both worlds (flexibility + security)
• Burst to public cloud during peak load | Cost-effective – keep sensitive data private, rest on public
• Applicability: Large enterprises, healthcare, retail, disaster recovery systems
4. ■ Community Cloud
• Shared infrastructure among organizations with common goals/interests (e.g., same industry or
compliance needs)
• Cost shared among members | Better security than public cloud | Meets sector-specific compliance
• Applicability: Government agencies, universities, healthcare networks, research groups
Model Cost Security Control Best For
Public Low Low Low Startups, general use
Private High High High Banks, Govt
Hybrid Medium Medium-High Medium Enterprises
Community Shared Medium Medium Same-sector orgs
■ Exam Tip: For 8 marks – cover all 4 models, each with definition + 2-3 benefits + applicability.
Q1b) Cloud Service Models – Architecture & Examples [7 Marks]
1. IaaS – Infrastructure as a Service
• You get: Virtual machines, storage, networking — raw hardware over internet
• User manages: OS, Middleware, Runtime, Data, Applications
• Provider manages: Servers, Storage, Networking, Virtualization
• Examples: AWS EC2, Google Compute Engine, Microsoft Azure VMs
• Who uses it: IT admins, developers needing full control
2. PaaS – Platform as a Service
• You get: A ready platform to build & deploy apps (no OS management)
• User manages: Data and Applications ONLY
• Provider manages: OS, Runtime, Middleware, Servers, Storage, Networking
• Examples: Google App Engine, Heroku, AWS Elastic Beanstalk
• Who uses it: Developers who just want to write & deploy code
3. SaaS – Software as a Service
• You get: Ready-to-use software via browser, nothing to manage
• User manages: Just uses the application
• Provider manages: App, Data, OS, Runtime, Middleware, Servers, Network — EVERYTHING
• Examples: Gmail, Google Docs, Zoom, Dropbox, Netflix
• Who uses it: End users, businesses, everyone
Feature IaaS PaaS SaaS
Control Maximum Medium Minimum
Manages Hardware only Hardware+OS+Runtime Everything
Flexibility High Medium Low
Target User Sysadmins Developers End Users
Example AWS EC2 Heroku Gmail
Architecture Pyramid (Draw this in exam!):
SaaS (Just use the app) → PaaS (Build your app here) → IaaS (Get raw
infrastructure) → Data Center (Physical hardware)
The higher you go → Less control, Less complexity, More convenience
■ Exam Tip: For 7 marks — draw the pyramid, explain all 3 models with diagram + 2 examples each.
Q2a) Challenges of Cloud Computing [8 Marks]
1. ■ Security & Privacy
• Challenge: Data stored on remote servers = risk of unauthorized access, hacking, data breaches.
Multi-tenant environment → one user's vulnerability affects others. Data ownership becomes unclear.
• Significance: Sensitive data (banking, medical) can be exposed. Critical for organizations with
compliance requirements.
2. ■ Internet Dependency / Availability
• Challenge: Cloud needs constant, reliable internet — no internet = no access.
• Significance: Businesses can halt completely during outages. Remote areas with poor connectivity
can't use cloud effectively.
3. ■ Vendor Lock-in
• Challenge: Once you adopt one provider (AWS/Azure), switching is very difficult. Proprietary formats
make migration hard.
• Significance: Huge switching costs (time, money, compatibility). Provider can increase prices and
you're stuck.
4. ■ Performance & Latency
• Challenge: Data travels over internet → delays compared to local systems.
• Significance: Real-time applications (gaming, trading) get affected. Performance depends on
provider's infrastructure.
5. ■ Cost Management
• Challenge: Pay-as-you-go sounds cheap but costs can spiral unexpectedly. Unused resources still
billed if not monitored.
• Significance: Hard to predict monthly bills. Long-term costs may exceed on-premise setup.
6. ■ Compliance & Legal Issues
• Challenge: Data stored in different countries = different laws apply. GDPR, IT Act, HIPAA compliance
required.
• Significance: Legal penalties for non-compliance. Healthcare & finance industries face strictest
regulations.
7. ■■ Limited Control & Flexibility
• Challenge: User has no control over underlying infrastructure. Dependent on provider for updates,
maintenance windows.
• Significance: Can't customize hardware/network as per need. Provider downtime = your downtime.
8. ■ Data Transfer & Bandwidth Costs
• Challenge: Moving large amounts of data in/out of cloud is expensive & slow. Egress (outgoing) data
charges are high.
• Significance: Big Data workloads face serious bottlenecks. Backup & recovery over internet is
time-consuming.
Challenge Core Impact
Security Data breach risk
Internet Dependency No access without connectivity
Vendor Lock-in Difficult to switch providers
Latency Slow real-time performance
Cost Management Unexpected billing
Compliance Legal penalties
Limited Control Can't customize infrastructure
Bandwidth Cost Expensive data movement
■ Exam Tip: For 8 marks — write any 6-8 challenges, each with a 2-line explanation + significance.
Q2b) Federated Cloud – Complete Concept [7 Marks]
What is Federated Cloud?
Federated Cloud is the interconnection of multiple independent cloud providers to work together as a
single unified system, allowing sharing of resources, services, and data across different clouds
seamlessly.
Analogy: Like UPI payment system — different banks (SBI, HDFC, Axis) are separate, but UPI connects
them so you can transact across any bank instantly.
Key Components
Component Role
Federation Broker Middleman that manages all clouds
Trust Management Establishes trust between providers
SLA Manager Handles agreements across providers
Resource Scheduler Decides which cloud handles which task
Identity Manager Single login across all clouds
Benefits of Federated Cloud
■ No Vendor Lock-in
• Not dependent on a single cloud provider. Freely switch or distribute workloads across AWS, Azure,
GCP. Gives organizations negotiating power over pricing.
■ Greater Scalability
• When one cloud reaches its limit → automatically burst to another cloud. Nearly unlimited resource
pool available.
■ Cost Optimization
• Choose the cheapest provider for each specific task. Use AWS for compute, GCP for ML, Azure for
storage.
■ High Availability
• If one cloud provider goes down → other clouds continue working. Eliminates single point of failure.
■ Geographic Reach
• Use cloud providers in different countries/regions. Data served from location closest to end user = low
latency.
■ Improved Security
• Sensitive data kept on private/trusted cloud. Less sensitive workloads moved to public cloud.
■ Better Performance
• Workloads assigned to the most suitable cloud for that task. Parallel processing across multiple
clouds.
■■ Resource Optimization
• Idle resources of one cloud shared with others. No resource wastage.
Feature Single Cloud Multi Cloud Federated Cloud
Providers 1 Many (isolated) Many (interconnected)
Resource Sharing No No Yes
Unified Management Yes No Yes
Vendor Lock-in High Medium Low
Cost Optimization Low Medium High
■ Exam Tip: For 7 marks — define → draw architecture → explain Federation Broker → list 4
benefits + 2 challenges.
Benefits of Cloud Hosting [8 Marks]
1. ■ Cost Efficiency
• No need to buy physical servers or hardware
• Pay-as-you-go model → pay only for what you use
• Eliminates costs of maintenance, electricity, cooling
• Converts CapEx (Capital Expenditure) to OpEx (Operational Expenditure)
• Example: A startup doesn't need to spend lakhs on servers — just pay AWS monthly as per usage.
2. ■ Scalability & Elasticity
• Scale resources up or down instantly based on demand
• No need to predict future requirements
• Vertical scaling = increase CPU/RAM of existing server
• Horizontal scaling = add more servers automatically
• Example: Flipkart scales up servers during Big Billion Days sale, scales down after.
3. ■ High Availability & Reliability
• Data stored across multiple servers & locations (redundancy)
• If one server fails → another takes over automatically
• Providers guarantee 99.9% uptime SLA
• Built-in disaster recovery & automatic backups
• Example: Even if AWS's one data center goes down, your website stays live.
4. ■ Accessibility & Mobility
• Access your data/applications from anywhere in the world
• Works on any device — laptop, mobile, tablet
• Enables remote work & collaboration across teams
• No dependency on being physically present at office
• Example: Google Drive lets you access your files from anywhere with just internet.
Benefit Core Advantage Real Example
Cost Efficiency No hardware, pay-as-you-go Startups save infra cost
Scalability Grow/shrink as needed Flipkart during sales
High Availability 99.9% uptime, auto failover Auto failover across regions
Accessibility Anywhere, any device Google Drive, Gmail
■ Exam Tip: For 8 marks with 4 benefits → spend 2 marks per benefit = definition + explanation +
example.
Cloud Computing – Definition & Challenges [7 Marks]
■■ What is Cloud Computing?
Cloud Computing is the delivery of computing services — servers, storage, databases, networking,
software, analytics — over the internet on a pay-as-you-go basis, without owning physical infrastructure.
NIST 5 Key Characteristics
Characteristic Meaning
On-demand Self Service Get resources instantly, no human interaction needed
Broad Network Access Access from anywhere via internet
Resource Pooling Resources shared among multiple users
Rapid Elasticity Scale up/down instantly
Measured Service Pay only for what you use
Challenges of Cloud Computing
■ Security & Privacy
• Hacking, data breaches, multi-tenancy risks. Sensitive data of banks, hospitals can be exposed.
■ Downtime & Internet Dependency
• Requires constant internet. AWS outages have halted businesses globally.
■ Vendor Lock-in
• Switching from AWS/Azure is costly and complex due to proprietary formats.
■ Unexpected Cost
• Pay-as-you-go bills can spiral. Unused resources still get billed.
■ Compliance & Legal Issues
• GDPR, IT Act, HIPAA compliance. Data in different countries has different laws.
■ Performance & Latency
• Internet delays affect real-time apps like stock trading, online gaming.
■■ Limited Control
• Zero access to underlying hardware. Dependent on provider for maintenance.
Challenge Core Problem Impact
Security Data breach risk Sensitive data exposed
Downtime Internet dependency Business halts
Vendor Lock-in Hard to switch Stuck with one provider
Cost Management Unexpected billing Budget overruns
Compliance Different country laws Legal penalties
Latency Slow data travel Real-time apps affected
Limited Control No hardware access Can't customize
■ Exam Tip: For 7 marks → Definition = 2 marks (include NIST 5 characteristics) + Challenges = 5
marks (any 5 with explanation).
SaaS Architecture – Detailed Explanation [7 Marks]
What is SaaS?
Software delivered over the internet as a ready-to-use service. No installation, no maintenance — just
open browser and use!
5-Layer SaaS Architecture
Layer Description
■ User Layer Users access via web browser or mobile app. No installation. Works on any de
■■ Presentation Layer The UI/frontend the user sees. Built with HTML, CSS, JS. Handles user interac
■■ Application Layer Core business logic. Handles requests, processes data. Exposes APIs for integ
■■ Data Layer Stores all user data, files, settings. Multi-tenant DB. Includes backups & recove
■ Infrastructure Layer Physical/virtual servers, networking, storage. Fully managed by provider. User
Key Characteristics of SaaS
Feature Detail
Multi-tenancy Multiple users share same app instance
Subscription Model Monthly/yearly billing
Auto Updates Provider updates app, user gets it instantly
Scalability Provider scales as users grow
Accessibility Available 24/7 from anywhere
Real-World Examples
SaaS Product Purpose
Gmail / Outlook Email
Google Docs Document editing
Zoom / Meet Video conferencing
Salesforce CRM
Dropbox File storage
Netflix Video streaming
■ Exam Tip: For 7 marks — draw the 5-layer architecture → explain each layer → add examples.
Multi-tenancy is a bonus point!