5. Cloud Service Models (IaaS, PaaS, SaaS)
Chapter 5: Cloud Service Models (IaaS, PaaS, SaaS)¶
📚 What You'll Learn in This Chapter¶
By the end of this chapter, you'll understand:
- ✓ The three main cloud service models (IaaS, PaaS, SaaS)
- ✓ What each model gives you and what you manage
- ✓ The Shared Responsibility Model
- ✓ When to use each service type
- ✓ Real-world examples of each
Time needed: 25-30 minutes
Difficulty: Moderate 🟡 (but we'll make it easy!)
Why this matters: This is one of the MOST TESTED topics on AZ-900!
The Pizza Analogy¶
Before we dive into technical details, let's understand these service models using something everyone knows: PIZZA! 🍕
Four Ways to Get Pizza:
┌──────────────────────────────────────────────────────────────┐
│ │
│ OPTION 1: MAKE PIZZA AT HOME (Traditional IT) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ YOU manage: │ │
│ │ ✓ Buy ingredients (flour, cheese, sauce, toppings) │ │
│ │ ✓ Own oven, plates, table │ │
│ │ ✓ Make the dough │ │
│ │ ✓ Cook the pizza │ │
│ │ ✓ Set the table │ │
│ │ ✓ Serve and eat │ │
│ │ ✓ Clean up everything │ │
│ │ │ │
│ │ Work: Maximum | Control: Maximum | Cost: Varies │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
│ OPTION 2: TAKE & BAKE (IaaS - Infrastructure as a Service) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ STORE provides: Premade dough, cheese, sauce │ │
│ │ YOU manage: │ │
│ │ ✓ Own oven, plates, table │ │
│ │ ✓ Bake the pizza │ │
│ │ ✓ Set the table │ │
│ │ ✓ Serve and eat │ │
│ │ ✓ Clean up │ │
│ │ │ │
│ │ Work: High | Control: High | Cost: Lower │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
│ OPTION 3: PIZZA DELIVERY (PaaS - Platform as a Service) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ STORE provides: Made and cooked pizza │ │
│ │ YOU manage: │ │
│ │ ✓ Own plates, table │ │
│ │ ✓ Set the table │ │
│ │ ✓ Serve and eat │ │
│ │ ✓ Clean up │ │
│ │ │ │
│ │ Work: Medium | Control: Medium | Cost: Higher │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
│ OPTION 4: DINE AT RESTAURANT (SaaS - Software as a Service) │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ RESTAURANT provides: Everything! │ │
│ │ YOU manage: │ │
│ │ ✓ Just eat! │ │
│ │ │ │
│ │ Work: Minimum | Control: Minimum | Cost: Highest │ │
│ └──────────────────────────────────────────────────────────┘ │
│ │
└──────────────────────────────────────────────────────────────┘
The Pattern: - More work = More control (but more responsibility) - Less work = Less control (but more convenience)
This same pattern applies to cloud services!
Understanding the Service Models¶
The Responsibility Stack¶
Every IT system has layers. Let's see who manages what in each model:
┌──────────────────────────────────────────────────────────────────────────────┐
│ WHO MANAGES WHAT? │
├──────────────────────────────────────────────────────────────────────────────┤
│ │
│ Traditional IaaS PaaS SaaS │
│ IT (Azure) (Azure) (Azure) │
│ │
│ Applications [YOU] [YOU] [YOU] [AZURE] │
│ Data [YOU] [YOU] [YOU] [YOU] │
│ Operating System [YOU] [YOU] [AZURE] [AZURE] │
│ Virtual Machine [YOU] [AZURE] [AZURE] [AZURE] │
│ Servers [YOU] [AZURE] [AZURE] [AZURE] │
│ Storage [YOU] [AZURE] [AZURE] [AZURE] │
│ Networking [YOU] [AZURE] [AZURE] [AZURE] │
│ Building/Power [YOU] [AZURE] [AZURE] [AZURE] │
│ │
│ Legend: │
│ [YOU] = You manage and are responsible │
│ [AZURE] = Microsoft manages for you │
│ │
└──────────────────────────────────────────────────────────────────────────────┘
The Trend: - Traditional IT: You manage EVERYTHING - IaaS: You manage top 3 layers - PaaS: You manage top 2 layers - SaaS: You manage almost nothing (just your data)
IaaS: Infrastructure as a Service¶
What Is IaaS?¶
Simple Definition:
Azure gives you virtual computers to use. You control everything on those computers.
Think of it like:
Renting an empty apartment. The building is there, electricity works, but YOU decide what furniture to put in, how to arrange it, and you're responsible for keeping it clean.
What Azure Provides (IaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ AZURE MANAGES: │
│ │
│ ✓ Physical servers (you never see them) │
│ ✓ Physical networking (cables, routers) │
│ ✓ Datacenter building (security, power, cooling) │
│ ✓ Virtualization software (creates virtual machines) │
│ ✓ Storage systems (hard drives, SSDs) │
│ │
│ You don't worry about: │
│ • Broken hardware │
│ • Power outages │
│ • Physical security │
│ • Network infrastructure │
│ │
└──────────────────────────────────────────────────────────────┘
What YOU Manage (IaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ YOUR RESPONSIBILITIES: │
│ │
│ ✓ Choose operating system (Windows or Linux) │
│ ✓ Install software and applications │
│ ✓ Apply security patches and updates │
│ ✓ Configure firewall rules │
│ ✓ Backup your data │
│ ✓ Monitor performance │
│ ✓ Manage user accounts │
│ │
│ You control: │
│ • What software runs │
│ • How it's configured │
│ • Who can access it │
│ • Security settings │
│ │
└──────────────────────────────────────────────────────────────┘
IaaS Examples in Azure¶
Azure Virtual Machines (VMs)
Example: Creating a Web Server
┌──────────────────────────────────────────────────────────────┐
│ Step 1: Login to Azure, click "Create Virtual Machine" │
│ ↓ │
│ Step 2: Choose your settings: │
│ • Windows Server 2022 │
│ • 4 CPU cores, 16GB RAM │
│ • 100GB disk space │
│ • Location: East US │
│ ↓ │
│ Step 3: Click "Create" (wait 5 minutes) │
│ ↓ │
│ Step 4: You now have a virtual computer! │
│ │
│ What Azure did: │
│ ✓ Allocated physical server space │
│ ✓ Created virtual machine │
│ ✓ Installed Windows Server │
│ ✓ Set up networking │
│ │
│ What YOU do next: │
│ □ Install web server software (IIS) │
│ □ Upload your website │
│ □ Configure security │
│ □ Set up backups │
│ □ Monitor performance │
│ │
│ Monthly cost: ~$150-300 (depending on size) │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use IaaS¶
✅ Good for:
┌──────────────────────────────────────────────────────────────┐
│ IDEAL IAAS SCENARIOS │
│ │
│ 1. Moving existing applications to cloud │
│ → "Lift and shift" migrations │
│ → App runs same way, just on Azure servers │
│ │
│ 2. Need full control of operating system │
│ → Custom software that requires Windows/Linux access │
│ → Legacy applications with specific requirements │
│ │
│ 3. Testing and development │
│ → Create test environments quickly │
│ → Delete when done (save money!) │
│ │
│ 4. Temporary high-power computing │
│ → Video rendering for 3 days │
│ → Data analysis for a project │
│ → Pay only for those days │
│ │
└──────────────────────────────────────────────────────────────┘
❌ Not ideal for: - Simple websites (PaaS is easier) - If you don't want to manage updates - If you're not technical
PaaS: Platform as a Service¶
What Is PaaS?¶
Simple Definition:
Azure gives you a ready-to-use platform where you just deploy your app. Azure handles the operating system and everything below it.
Think of it like:
Renting a furnished apartment. Furniture is there, utilities are set up, you just move in with your stuff. Building manager handles maintenance.
What Azure Provides (PaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ AZURE MANAGES: │
│ │
│ ✓ Physical infrastructure (servers, storage, network) │
│ ✓ Operating system (Windows/Linux) │
│ ✓ OS updates and patches (automatic!) │
│ ✓ Database software (if using database service) │
│ ✓ Scaling infrastructure │
│ ✓ Backups (automatic!) │
│ ✓ High availability setup │
│ │
│ You don't worry about: │
│ • Installing OS updates │
│ • Patching software │
│ • Server maintenance │
│ • Configuring backups │
│ • Managing underlying infrastructure │
│ │
└──────────────────────────────────────────────────────────────┘
What YOU Manage (PaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ YOUR RESPONSIBILITIES: │
│ │
│ ✓ Write your application code │
│ ✓ Upload/deploy your application │
│ ✓ Manage your data │
│ ✓ Configure application settings │
│ ✓ Control who accesses your app │
│ │
│ You focus on: │
│ • Building features │
│ • Your business logic │
│ • User experience │
│ • Your data │
│ │
│ Not on: │
│ • Managing servers │
│ • Installing updates │
│ • Infrastructure concerns │
│ │
└──────────────────────────────────────────────────────────────┘
PaaS Examples in Azure¶
Example 1: Azure App Service (Web Hosting)¶
Deploying a Website with Azure App Service:
┌──────────────────────────────────────────────────────────────┐
│ Traditional Way (IaaS): │
│ 1. Create virtual machine (10 min) │
│ 2. Install operating system updates (30 min) │
│ 3. Install web server software (20 min) │
│ 4. Configure firewall (15 min) │
│ 5. Set up SSL certificate (20 min) │
│ 6. Deploy website (10 min) │
│ 7. Configure backups (20 min) │
│ Total: 2+ hours of technical work │
│ │
│ ─────────────────────────────────────────────────────────────│
│ │
│ PaaS Way (Azure App Service): │
│ 1. Create App Service (2 min) │
│ 2. Upload your website code (5 min) │
│ Total: 7 minutes! Azure handles rest automatically! │
│ │
│ Azure automatically: │
│ ✓ Updates operating system │
│ ✓ Patches security issues │
│ ✓ Creates backups │
│ ✓ Provides SSL certificate │
│ ✓ Scales if traffic increases │
│ │
└──────────────────────────────────────────────────────────────┘
Example 2: Azure SQL Database (Managed Database)¶
Setting Up a Database:
┌──────────────────────────────────────────────────────────────┐
│ IaaS Way (VM with SQL): │
│ □ Create VM │
│ □ Install SQL Server software │
│ □ Configure SQL Server │
│ □ Set up backup system │
│ □ Configure security │
│ □ Monitor performance │
│ □ Apply SQL patches monthly │
│ Your job: Everything! │
│ │
│ ─────────────────────────────────────────────────────────────│
│ │
│ PaaS Way (Azure SQL Database): │
│ □ Click "Create SQL Database" │
│ □ Name your database │
│ □ Start using it! │
│ │
│ Azure automatically: │
│ ✓ Installs and updates SQL Server │
│ ✓ Backs up your data daily │
│ ✓ Monitors performance │
│ ✓ Applies security patches │
│ ✓ Provides 99.99% uptime guarantee │
│ │
│ Your job: Just use the database! │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use PaaS¶
✅ Good for:
┌──────────────────────────────────────────────────────────────┐
│ IDEAL PAAS SCENARIOS │
│ │
│ 1. New applications being built │
│ → Start fresh, no legacy requirements │
│ → Focus on code, not infrastructure │
│ │
│ 2. Websites and web applications │
│ → Azure App Service perfect for this │
│ → Automatic scaling, SSL, backups │
│ │
│ 3. Databases │
│ → Azure SQL, MySQL, PostgreSQL │
│ → Automatic backups, updates, security │
│ │
│ 4. Limited IT staff │
│ → Small teams, startups │
│ → Don't want to manage infrastructure │
│ │
│ 5. Rapid development │
│ → Need to build fast │
│ → Deploy frequently │
│ │
└──────────────────────────────────────────────────────────────┘
❌ Not ideal for: - Need full OS control - Legacy apps requiring specific configurations - Applications that won't run in managed environments
SaaS: Software as a Service¶
What Is SaaS?¶
Simple Definition:
Complete applications you just USE. You don't manage anything technical.
Think of it like:
Using a hotel. Everything is done for you - room service, cleaning, maintenance. You just show up and enjoy.
What Azure Provides (SaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ PROVIDER MANAGES: │
│ │
│ ✓ Everything technical! │
│ ✓ Servers, storage, network │
│ ✓ Operating system │
│ ✓ Application code │
│ ✓ Updates and new features │
│ ✓ Security patches │
│ ✓ Backups │
│ ✓ Scaling │
│ │
│ You literally don't touch ANY technology! │
│ │
└──────────────────────────────────────────────────────────────┘
What YOU Manage (SaaS)¶
┌──────────────────────────────────────────────────────────────┐
│ YOUR ONLY RESPONSIBILITIES: │
│ │
│ ✓ Use the software │
│ ✓ Manage your data │
│ ✓ Control user access (who can use it) │
│ ✓ Configure settings (what features to use) │
│ │
│ That's it! Nothing technical! │
│ │
└──────────────────────────────────────────────────────────────┘
SaaS Examples You Already Use¶
You probably use SaaS every day without knowing it!
Common SaaS Applications:
┌──────────────────────────────────────────────────────────────┐
│ │
│ EMAIL: │
│ • Gmail, Outlook.com, Yahoo Mail │
│ • You just send emails │
│ • Google/Microsoft manages servers │
│ │
│ PRODUCTIVITY: │
│ • Microsoft 365 (Word, Excel, Teams online) │
│ • Google Workspace (Docs, Sheets, Drive) │
│ • You just create documents │
│ • Providers handle infrastructure │
│ │
│ ENTERTAINMENT: │
│ • Netflix, Spotify, YouTube │
│ • You just watch/listen │
│ • They handle billions of users │
│ │
│ BUSINESS APPS: │
│ • Salesforce (customer management) │
│ • Zoom (video calls) │
│ • Slack (team chat) │
│ • QuickBooks Online (accounting) │
│ │
│ SOCIAL MEDIA: │
│ • Facebook, Instagram, TikTok, LinkedIn │
│ • You post content │
│ • They handle everything else │
│ │
└──────────────────────────────────────────────────────────────┘
Pattern: You just USE it. Provider handles EVERYTHING technical.
SaaS in Azure¶
Microsoft 365:
┌──────────────────────────────────────────────────────────────┐
│ USING MICROSOFT 365 (SaaS) │
│ │
│ What you do: │
│ 1. Pay monthly subscription ($6-20 per user) │
│ 2. Create user accounts │
│ 3. Start using: │
│ • Word, Excel, PowerPoint (online) │
│ • Outlook email │
│ • Teams for video calls │
│ • OneDrive for file storage │
│ │
│ What Microsoft does: │
│ • Maintains servers worldwide │
│ • Updates software (you always have latest version) │
│ • Provides 99.9% uptime │
│ • Backs up your data │
│ • Handles security │
│ • Manages billions of users │
│ │
│ You never think about: Servers, updates, backups, security │
│ │
└──────────────────────────────────────────────────────────────┘
When to Use SaaS¶
✅ Good for:
┌──────────────────────────────────────────────────────────────┐
│ IDEAL SAAS SCENARIOS │
│ │
│ 1. Standard business needs │
│ → Email, productivity tools, collaboration │
│ → Everyone needs the same thing │
│ │
│ 2. No IT staff │
│ → Small businesses │
│ → Non-technical teams │
│ → Just want to use software, not manage it │
│ │
│ 3. Popular, common software │
│ → CRM (Salesforce) │
│ → HR systems │
│ → Accounting │
│ → Project management │
│ │
│ 4. Want automatic updates │
│ → Always have latest features │
│ → No manual upgrade process │
│ │
└──────────────────────────────────────────────────────────────┘
❌ Not ideal for: - Unique, custom software needs - Require heavy customization - Need to control/modify source code
The Shared Responsibility Model¶
Why This Matters¶
Critical for AZ-900 exam!
Understanding WHO is responsible for WHAT is essential for: - Security - Compliance - Avoiding problems - Passing the exam!
The Responsibility Chart¶
┌───────────────────────────────────────────────────────────────────────────┐
│ SHARED RESPONSIBILITY MODEL │
├───────────────────────────────────────────────────────────────────────────┤
│ │
│ Component Traditional IT IaaS PaaS SaaS │
│ │
│ Data & Access [ALWAYS YOU] [YOU] [YOU] [YOU] │
│ Applications [YOU] [YOU] [YOU] [PROVIDER] │
│ Runtime (Java, .NET) [YOU] [YOU] [PROVIDER] [PROVIDER] │
│ Operating System [YOU] [YOU] [PROVIDER] [PROVIDER] │
│ Virtual Machines [YOU] [PROVIDER] [PROVIDER] [PROVIDER] │
│ Networking [YOU] [SHARED] [SHARED] [PROVIDER] │
│ Storage [YOU] [PROVIDER] [PROVIDER] [PROVIDER] │
│ Physical Servers [YOU] [PROVIDER] [PROVIDER] [PROVIDER] │
│ Physical Datacenter [YOU] [PROVIDER] [PROVIDER] [PROVIDER] │
│ │
│ Legend: │
│ [YOU] = You are responsible │
│ [PROVIDER] = Azure is responsible │
│ [SHARED] = Both share responsibility │
│ │
└───────────────────────────────────────────────────────────────────────────┘
What YOU Always Control (All Models)¶
┌──────────────────────────────────────────────────────────────┐
│ YOU ARE ALWAYS RESPONSIBLE FOR: │
│ │
│ 1. YOUR DATA │
│ • What data you store │
│ • How you protect it │
│ • Who can access it │
│ • Where it's stored (region) │
│ │
│ 2. USER ACCOUNTS & ACCESS │
│ • Who gets accounts │
│ • What permissions they have │
│ • Password policies │
│ • Multi-factor authentication │
│ │
│ 3. DEVICES & ENDPOINTS │
│ • Employee laptops │
│ • Mobile phones │
│ • Tablets │
│ • Security of these devices │
│ │
│ 4. COMPLIANCE │
│ • Meeting legal requirements │
│ • Following industry regulations │
│ • Data privacy laws │
│ │
│ NO CLOUD MODEL changes these! You OWN these forever! │
│ │
└──────────────────────────────────────────────────────────────┘
What Azure Always Controls (All Models)¶
┌──────────────────────────────────────────────────────────────┐
│ AZURE IS ALWAYS RESPONSIBLE FOR: │
│ │
│ 1. PHYSICAL SECURITY │
│ • Datacenter buildings │
│ • Security guards │
│ • Access controls │
│ • Surveillance cameras │
│ │
│ 2. PHYSICAL INFRASTRUCTURE │
│ • Servers and hardware │
│ • Network equipment │
│ • Power systems │
│ • Cooling systems │
│ │
│ 3. PHYSICAL NETWORK │
│ • Cables and routers │
│ • Switches │
│ • Internet connections │
│ │
│ 4. MAINTENANCE │
│ • Replace broken hardware │
│ • Fix datacenter issues │
│ • Handle power outages │
│ │
│ You NEVER worry about these! Azure owns them forever! │
│ │
└──────────────────────────────────────────────────────────────┘
Real-World Security Example¶
Example: Data Breach Scenario
┌──────────────────────────────────────────────────────────────┐
│ Scenario: Customer data was stolen from your system │
│ │
│ Question: Who's fault is it? │
│ Answer: DEPENDS on what went wrong! │
│ │
│ ─────────────────────────────────────────────────────────────│
│ │
│ AZURE'S FAULT if: │
│ • Someone broke into datacenter │
│ • Physical servers were stolen │
│ • Azure's network was hacked │
│ • Hardware failure lost your data │
│ │
│ → Azure pays you (per SLA agreement) │
│ │
│ ─────────────────────────────────────────────────────────────│
│ │
│ YOUR FAULT if: │
│ • Weak password: "password123" │
│ • Gave access to wrong person │
│ • Didn't enable encryption │
│ • Left database publicly accessible │
│ • Employee's laptop got hacked │
│ │
│ → Your responsibility, your problem │
│ │
│ KEY LESSON: │
│ Azure secures the CLOUD. │
│ You secure what's IN the cloud. │
│ │
└──────────────────────────────────────────────────────────────┘
Comparison Summary¶
┌──────────────────────────────────────────────────────────────┐
│ QUICK COMPARISON │
├──────────────────────────────────────────────────────────────┤
│ │
│ IaaS PaaS SaaS │
│ │
│ Control ⭐⭐⭐⭐⭐ ⭐⭐⭐ ⭐ │
│ Flexibility ⭐⭐⭐⭐⭐ ⭐⭐⭐ ⭐ │
│ Ease of Use ⭐⭐ ⭐⭐⭐⭐ ⭐⭐⭐⭐⭐ │
│ Speed to Deploy ⭐⭐ ⭐⭐⭐⭐ ⭐⭐⭐⭐⭐ │
│ Your Work ⭐⭐⭐⭐ ⭐⭐ ⭐ │
│ Technical Skill ⭐⭐⭐⭐⭐ ⭐⭐⭐ ⭐ │
│ │
│ Best For: │
│ │
│ IaaS: Maximum control, migration, custom needs │
│ PaaS: New apps, web dev, databases, faster deployment │
│ SaaS: Just use software, no IT staff, standard needs │
│ │
└──────────────────────────────────────────────────────────────┘
Decision Tree: Which Should I Use?¶
┌──────────────────────────────────────────────────────────────┐
│ START HERE: What do you need? │
│ │
│ Just use existing software? │
│ (Email, Office, CRM) │
│ │ │
│ └─YES→ Use SaaS (Microsoft 365, Salesforce, etc.) │
│ │ │
│ NO │
│ ↓ │
│ Building a new web app/website? │
│ │ │
│ └─YES→ Use PaaS (Azure App Service, SQL Database) │
│ │ │
│ NO │
│ ↓ │
│ Need full control of operating system? │
│ Moving existing complex app? │
│ │ │
│ └─YES→ Use IaaS (Azure Virtual Machines) │
│ │
│ Still not sure? Start with PaaS! It's the sweet spot! │
│ │
└──────────────────────────────────────────────────────────────┘
Real-World Examples by Age Group¶
For Students (16-25):
Building a Portfolio Website:
DON'T use IaaS:
• Too complex for simple website
• You'd manage servers unnecessarily
• More expensive
DO use PaaS:
• Azure App Service
• Upload your HTML/CSS
• Live in 10 minutes
• Cost: $10-20/month
OR use SaaS:
• WordPress.com, Wix, Squarespace
• Drag and drop
• No coding needed
• Cost: $5-15/month
For Career Changers (25-45):
Starting E-commerce Business:
Option 1 - IaaS:
• Create VMs
• Install e-commerce software
• You manage everything
• Time: 2 weeks setup
• Requires: Technical skills
Option 2 - PaaS:
• Use Azure App Service
• Deploy e-commerce platform
• Azure manages infrastructure
• Time: 2-3 days setup
• Requires: Some technical knowledge
Option 3 - SaaS:
• Use Shopify, BigCommerce
• Click and configure
• Everything managed for you
• Time: Start today!
• Requires: No technical skills
• BEST for most small businesses!
For Professionals (45-60):
Company Needs:
Email & Productivity:
→ SaaS (Microsoft 365)
Everyone knows how to use it
Custom Business App:
→ PaaS (Azure App Service + SQL Database)
Faster development, less maintenance
Legacy System from 1990s:
→ IaaS (Azure VMs)
Needs specific OS configuration
📝 Chapter Summary¶
Key Points to Remember:
✅ Three Service Models
IaaS (Infrastructure as a Service) - Virtual machines you control - Most control, most responsibility - Like: Take-and-bake pizza - Use for: Migrations, custom needs, full control
PaaS (Platform as a Service) - Ready-to-use platforms - Medium control, less responsibility - Like: Pizza delivery - Use for: New apps, websites, databases
SaaS (Software as a Service) - Complete applications - Least control, least responsibility - Like: Restaurant dining - Use for: Email, productivity, standard business apps
✅ Shared Responsibility Model - YOU always control: Data, accounts, access, compliance - AZURE always controls: Physical security, infrastructure, datacenter - In between: Depends on IaaS/PaaS/SaaS
✅ The Pattern - More control = More work = More flexibility - Less control = Less work = More convenience
✅ Self-Check¶
□ Can you explain IaaS, PaaS, and SaaS using the pizza analogy?
□ Can you name examples of each model?
□ Do you understand what YOU always manage?
□ Do you understand what AZURE always manages?
□ Can you decide which model to use for different scenarios?
🎯 Practice Questions¶
Question 1: Which service model gives you the MOST control?
A) SaaS
B) PaaS
C) IaaS
D) All are the same
Question 2: You want to use Microsoft Word online. Which model is this?
A) IaaS
B) PaaS
C) SaaS
D) None of these
Question 3: Which is TRUE about the Shared Responsibility Model?
A) Azure is responsible for your data security
B) You are responsible for datacenter physical security
C) You are always responsible for user access control
D) Responsibility never changes between IaaS/PaaS/SaaS
Question 4: Which is the BEST choice for a new website you're building?
A) IaaS - Maximum control
B) PaaS - Easier deployment
C) SaaS - Least work
D) Traditional IT - Own everything
Question 5: Azure is ALWAYS responsible for:
A) Your application code
B) Physical datacenter security
C) User passwords
D) Data encryption
✍️ Practice Answers¶
Question 1: C - IaaS
Explanation: IaaS gives you virtual machines where you control the operating system and everything above it. You have maximum control but also maximum responsibility.
Question 2: C - SaaS
Explanation: Microsoft Word online (part of Microsoft 365) is SaaS. You just use the software; Microsoft manages everything technical.
Question 3: C - You are always responsible for user access control
Explanation: Regardless of service model, YOU always control who has access to your resources, what permissions they have, and how accounts are managed.
Question 4: B - PaaS - Easier deployment
Explanation: For a new website, PaaS (like Azure App Service) is ideal. You get infrastructure management handled automatically but still control your application. IaaS is overkill, SaaS won't let you build custom sites.
Question 5: B - Physical datacenter security
Explanation: Azure always handles physical security (guards, building access, surveillance) regardless of service model. You handle your application and data security.
🎓 How Did You Do?¶
- 5/5: Perfect! You understand service models!
- 3-4: Good! Review what you missed
- 0-2: Re-read the chapter, try again
🔖 Quick Reference Card¶
┌──────────────────────────────────────────────────────────────┐
│ SERVICE MODELS CHEAT SHEET │
├──────────────────────────────────────────────────────────────┤
│ │
│ IaaS - Infrastructure as a Service │
│ • Virtual machines │
│ • You control: OS, apps, data │
│ • Azure controls: Servers, storage, network │
│ • Example: Azure Virtual Machines │
│ │
│ PaaS - Platform as a Service │
│ • Ready-to-use platforms │
│ • You control: Apps, data │
│ • Azure controls: OS, servers, updates │
│ • Example: Azure App Service, SQL Database │
│ │
│ SaaS - Software as a Service │
│ • Complete applications │
│ • You control: Your data, user access │
│ • Provider controls: Everything else │
│ • Example: Microsoft 365, Salesforce │
│ │
│ Shared Responsibility: │
│ • Always YOU: Data, access, accounts, compliance │
│ • Always PROVIDER: Physical security, infrastructure │
│ • Varies: Operating system, network, applications │
│ │
└──────────────────────────────────────────────────────────────┘
End of Chapter 5 ✓
Ready for Chapter 8: Azure Resource Management? Let's go! 🚀 -e