Unit 1 Curriculum Overview: Cloud Concepts (AZ-900)

This document provides a comprehensive roadmap for Unit 1: Describe Cloud Concepts, part of the Microsoft Azure Fundamentals (AZ-900) curriculum. This unit serves as the foundational layer for all cloud-related knowledge, moving from abstract definitions to concrete operational models.

## Prerequisites

To succeed in this unit, learners should possess the following background:

General IT Literacy: A basic understanding of what a server is and how the internet functions.
Internet Connectivity: Awareness of how web-based applications are accessed by end-users.
Business Awareness: A high-level understanding of basic business concepts like "budget" and "hardware maintenance" is helpful, though not strictly required.
No Prior Cloud Experience Required: This is an entry-level unit designed for beginners.

## Module Breakdown

The following table outlines the progression of topics within Unit 1, categorized by their conceptual difficulty.

Module Segment	Primary Focus	Difficulty Level
1.1 Cloud Fundamentals	Definition, Shared Responsibility, and Consumption-based models	Beginner
1.2 Cloud Deployment Models	Public, Private, and Hybrid environments	Intermediate
1.3 The Benefits of Cloud	High Availability, Scalability, and Reliability	Beginner
1.4 Cloud Service Types	IaaS, PaaS, and SaaS definitions and use cases	Intermediate

## Learning Objectives per Module

1.1 Describe Cloud Computing

Define Cloud Computing: Understand the delivery of computing services over the internet.
Shared Responsibility Model: Distinguish between the tasks the cloud provider performs and the tasks the customer remains responsible for.
Pricing Models: Contrast the consumption-based model (Pay-as-you-go) with traditional fixed-cost models.

1.2 Describe Cloud Deployment Models

Public Cloud: Identify use cases for multi-tenant environments owned by providers like Microsoft.
Private Cloud: Understand dedicated environments for single organizations.
Hybrid Cloud: Analyze how organizations combine on-premises resources with public cloud flexibility.

1.3 Describe the Benefits of Cloud Services

Operational Excellence: Define High Availability (HA) and Scalability (Vertical vs. Horizontal).
Security & Governance: Explain how the cloud enhances data protection and regulatory compliance.

1.4 Describe Cloud Service Types

IaaS (Infrastructure): Renting servers and storage.
PaaS (Platform): Development and deployment environments without managing underlying VMs.
SaaS (Software): Ready-to-use applications (e.g., Microsoft 365).

## Visual Anchors

The Shared Responsibility Model

Loading Diagram...

Cloud Service Model Comparison

\begin{tikzpicture}[scale=0.8] \draw[thick,->] (0,0) -- (10,0) node[right] {User Management}; \draw[thick,->] (0,0) -- (0,6) node[above] {Abstraction Level};

code

% IaaS
\draw[fill=blue!20] (0.5,0.5) rectangle (3,2);
\node at (1.75,1.25) {\textbf{IaaS}};
\node[below, scale=0.7] at (1.75,0.5) {Virtual Machines};

% PaaS
\draw[fill=green!20] (3.5,0.5) rectangle (6,3.5);
\node at (4.75,2) {\textbf{PaaS}};
\node[below, scale=0.7] at (4.75,0.5) {App Services};

% SaaS
\draw[fill=orange!20] (6.5,0.5) rectangle (9,5);
\node at (7.75,2.75) {\textbf{SaaS}};
\node[below, scale=0.7] at (7.75,0.5) {Office 365};

\node[rotate=90] at (-0.5,3) {Provider Managed};

\end{tikzpicture}

## Success Metrics

To verify mastery of Unit 1, a learner should be able to:

Identify Responsibilities: Correcty state who is responsible for OS patching in an IaaS vs. a PaaS scenario.
Model Selection: Choose the correct cloud model (Public, Private, or Hybrid) based on a specific business constraint (e.g., "Must keep data on-site for legal reasons").
Financial Contrast: Explain the shift from CapEx (Capital Expenditure) to OpEx (Operational Expenditure).
Service Type Matching: Differentiate between a developer using Azure SQL (PaaS) and a business user using Microsoft Teams (SaaS).

## Real-World Application

Understanding these concepts is critical for modern IT roles for several reasons:

Cost Efficiency: Organizations no longer need to buy expensive hardware upfront. Instead, they scale resources based on demand (e.g., a retailer scaling up for Black Friday).
Global Reach: Cloud concepts like "Regions" allow a startup in one country to deploy applications globally in minutes, something impossible with traditional data centers.
Agility: Developers can spin up "Serverless" functions to test ideas without waiting weeks for hardware procurement.

[!TIP] Think of Cloud Service Types like housing:

IaaS is like renting an empty apartment (you bring the furniture/OS).

PaaS is like staying in a furnished rental (the basics are there, you just bring your clothes/code).

SaaS is like staying in a hotel (everything is provided, you just use the service).

[!IMPORTANT] The Shared Responsibility Model is the most frequent area of confusion on the AZ-900 exam. Always remember: Regardless of the model, the customer is ALWAYS responsible for their data and identities.