AZ-900: Cloud Computing Fundamentals Curriculum Overview
Describe cloud computing
Curriculum Overview: Describe Cloud Computing
This curriculum provides a foundational understanding of cloud computing concepts as defined in the Microsoft Azure Fundamentals (AZ-900) exam. It explores the transition from traditional on-premises infrastructure to flexible, provider-managed cloud services.
[!IMPORTANT] Cloud computing is not just "someone else's computer." It is a delivery model that shifts responsibility and financial risk from the consumer to the provider.
Prerequisites
Before beginning this curriculum, learners should have a basic understanding of the following:
- Basic Networking: Knowledge of what the internet is and how devices connect to networks.
- Server Concepts: Understanding that applications (like websites) run on physical hardware called servers.
- Business Basics: Familiarity with the difference between buying an asset (Capital Expenditure) and paying a monthly service bill (Operational Expenditure).
Module Breakdown
| Module | Focus | Estimated Time |
|---|---|---|
| 1. The Definition of Cloud | Core characteristics and the role of the Cloud Provider (e.g., Microsoft). | 20 Mins |
| 2. Shared Responsibility | Determining who manages the OS, Network, and Hardware. | 30 Mins |
| 3. Cloud Models | Comparing Public, Private, and Hybrid implementations. | 25 Mins |
| 4. The Economics of Cloud | Consumption-based pricing vs. traditional hardware investment. | 20 Mins |
| 5. Modern Architectures | Introduction to Serverless computing and high availability. | 25 Mins |
Learning Objectives per Module
Module 1: Defining Cloud Computing
- Define cloud computing as the delivery of computing services over the internet.
- Identify the role of the Cloud Provider in managing infrastructure.
Module 2: The Shared Responsibility Model
- Differentiate between responsibilities held by the customer and the provider.
- Understand how responsibility shifts based on the service model used.
Module 3: Cloud Models & Use Cases
- Public Cloud: Resources owned and operated by a third-party provider.
- Private Cloud: Resources used exclusively by one business or organization.
- Hybrid Cloud: A combination that allows data and apps to be shared between them.
Module 4: Consumption-Based Models
- Describe the shift from CapEx (Capital Expenditure) to OpEx (Operational Expenditure).
- Explain why paying only for what you use increases financial agility.
Success Metrics
To demonstrate mastery of this curriculum, learners should be able to successfully complete the following tasks:
- Scenario Analysis: Given a business case (e.g., a startup with fluctuating traffic), identify if a Public or Private cloud model is more appropriate.
- Responsibility Mapping: Correctly identify whether the Provider or Customer is responsible for patching a Virtual Machine's Operating System.
- Cost Calculation: Explain how a consumption-based model prevents "wasted capacity" compared to on-premises hardware.
- Term Identification: Define "Serverless" and its benefit in removing infrastructure management overhead.
Real-World Application
In a professional environment, understanding these concepts allows for:
- Business Agility: Deploying resources in minutes rather than waiting weeks for hardware procurement.
- Disaster Recovery: Utilizing the provider's global infrastructure to ensure applications survive regional outages.
- Cost Optimization: Scaling down resources during off-peak hours to save thousands of dollars in operational costs.
Visualizing the Economic Shift
The following diagram illustrates how Cloud Computing (OpEx) aligns capacity with actual demand, unlike traditional On-Premises (CapEx) which often results in wasted resources or insufficient capacity.
\begin{tikzpicture} % Axes \draw[->] (0,0) -- (6,0) node[right] {Time}; \draw[->] (0,0) -- (0,4) node[above] {Capacity};
% Traditional On-Prem (Step function - CapEx)
\draw[thick, blue] (0,1.5) -- (2,1.5) -- (2,3.5) -- (5.5,3.5);
\node[blue, scale=0.8] at (4,3.8) {On-Prem Fixed Capacity};
% Actual Demand (Wavy line)
\draw[thick, red, dashed] (0,0.5) .. controls (1,2.5) and (2,0.5) .. (3,3) .. controls (4,2) and (5,4) .. (5.5,3.5);
\node[red, scale=0.8] at (5.5,3.2) {Actual Demand};
% Cloud (Matches demand - OpEx)
\draw[thick, green!60!black] (0,0.6) .. controls (1,2.6) and (2,0.6) .. (3,3.1) .. controls (4,2.1) and (5,4.1) .. (5.5,3.6);
\node[green!60!black, scale=0.8] at (2,0.3) {Cloud Elastic Supply};\end{tikzpicture}
[!TIP] Remember: In the cloud, you don't pay for the potential to use a server; you pay for the actual usage of its resources.