Summary of "Exam AZ-900: Microsoft Azure Fundamentals | Tutorial on Module 1: Describe Cloud Computing"
Overview / Exam roadmap (how to start)
- Go to Microsoft Learn (learn.microsoft.com) → Discover → Credentials → Browse certifications → Filter: Azure → (optionally filter Administrator) → click “Microsoft Certified: Azure Fundamentals (AZ-900)”.
- Follow the three-step flow on the certification page: Prepare for the exam → Practice for the exam → Take the exam.
Exam logistics:
- Common name: AZ-900 (Azure Fundamentals)
- Duration: 45 minutes
- Cost: USD 99 (varies by country — local currency shown when scheduling)
- End-to-end flow: prepare (study topics) → practice (assessment on MS Learn) → schedule/take exam (provide personal details when scheduling)
Exam topics and weightings (what to study, focus areas)
Three main topic areas and approximate question distribution:
- Describe cloud concepts — ~25–30%
- Describe Azure architecture and services — ~35–40% (highest weight)
- Describe Azure management and governance — ~30–35%
Advice: study all three areas — they are interrelated — but prioritize Azure architecture and services because it usually has the most exam questions.
Detailed module breakdown (what MS Learn expects you to study)
Describe Cloud Concepts (3 modules):
- Describe cloud computing
- Benefits of using cloud services
- Cloud service types
Describe Azure architecture and services:
- Core architectural components of Azure
- Azure compute and networking services
- Azure storage services
- Identity, access, and security (identity services)
Describe Azure management and governance:
- Describe cost management
- Features and tools in Azure governance and compliance
- Managing and deploying Azure resources
- Monitoring and tools
What is Microsoft Azure and cloud computing (core definitions)
- Microsoft Azure: a cloud computing platform — a large set of services and products delivered over the internet.
- Cloud computing: delivery of computing services over the internet (compute/VMs, storage, databases, networking, AI, IoT, etc.).
- Example: an Azure virtual machine is a VM you access over the internet — you do not need to know or maintain its physical location.
On-premises data center example — problems & hidden costs
Example scenario: a tours-and-travels website requiring servers, databases, networking, cooling, power backup, physical security, engineers, etc. — all of which add cost and operational overhead.
Problems with owning on-prem servers:
- High upfront capital expense (servers, power/cooling, space)
- Ongoing maintenance and staffing
- Inefficient utilization when demand fluctuates (over-provisioning wastes money; under-provisioning causes outages)
- Slow procurement and setup for additional capacity
Benefits of cloud (illustrated)
- Elastic scaling: scale up resources (CPU, RAM, storage, VMs) during peaks and scale down afterward — pay only for what you use.
- Lower operational overhead: provider handles hardware, power, cooling, physical security.
- Faster provisioning: add resources in minutes through the portal instead of long procurement cycles.
- Consumption-based pricing: pay-as-you-go model (pay for what you use).
Shared Responsibility Model
Responsibilities are shared between the cloud provider (e.g., Microsoft Azure) and the customer:
- On-premises (traditional): customer is responsible for everything (physical host, networking, cooling, security, OS, application, data, identity).
- Cloud provider: assumes responsibility for many physical/infrastructure concerns (physical host, data center facilities, network). Customer retains responsibility for data, accounts/identities, application access, and some configuration.
Which service model places most responsibility on the customer?
- IaaS (Infrastructure as a Service) — most customer responsibility (manage OS, apps, data, network configuration)
- PaaS (Platform as a Service) — shared responsibilities (provider manages OS/platform; customer manages apps/data)
- SaaS (Software as a Service) — least customer responsibility (provider manages most of the stack; customer manages users/data access)
Cloud service models (short)
- IaaS: provider supplies infrastructure (VMs, storage, network); customer installs and maintains OS and apps.
- PaaS: provider supplies runtime/platform; customer deploys apps and data.
- SaaS: provider supplies complete application; customer uses the app and manages user access/data as needed.
Cloud deployment models
- Private cloud: dedicated to a single organization — more control, potentially higher cost; can be on-site or hosted.
- Public cloud: services provided by a third-party cloud provider, shared infrastructure, pay-for-use, rapid provisioning.
- Hybrid cloud: combination of private and public — allows workload bursting to public cloud; choose which services remain private vs public.
- Multicloud: using multiple public cloud providers concurrently — manage resources and security across providers.
Comparison highlights:
- Private: capital expenditure, full control, higher cost
- Public: no capital expenditure to scale up, pay only for used resources, less control over infrastructure
- Hybrid: flexible, control over where apps/data run; good for compliance and security choices
Management across environments
- Azure Arc: Microsoft tool/platform that simplifies governance and management across multicloud and on-premises environments, providing consistent management across them.
Cost models: CapEx vs OpEx and cloud consumption model
- CapEx (capital expenditure): one-time upfront purchases (buy servers, buildings, vehicles)
- OpEx (operational expenditure): ongoing expenses for services/products (rent, pay-as-you-use)
- Cloud computing is primarily OpEx / consumption-based: pay-as-you-go / pay-for-what-you-use
Quote for exam emphasis:
Cloud computing follows an operational, consumption-based model (OpEx).
Problems with traditional data centers and cloud advantages
Traditional issues:
- Over-provisioning (wasted capital)
- Under-provisioning (performance problems)
- Procurement delays
- Maintenance overhead
Cloud advantages:
- On-demand provisioning
- Elastic scaling
- Faster response to demand
- Reduced capital investment
Cloud pricing / billing model
- Pay-as-you-go: you pay for resources used in a billing period (scale up → pay more; scale down → pay less)
- Analogy: renting a car vs buying — rent compute/storage instead of buying hardware
Quick knowledge-check questions (examples and answers)
-
Q: What is cloud computing? A: Delivery of computing services over the internet.
-
Q: Which cloud model uses data centers focused on providing cloud services to anyone who wants them? A: Public cloud.
-
Q: Which model has data centers focused on a single customer? A: Private cloud.
-
Q: Combining private + public is? A: Hybrid cloud.
-
Q: According to the shared responsibility model, which service type places the most responsibility on the customer? A: IaaS (Infrastructure as a Service).
Practical steps / methodology for preparing AZ-900 (actionable workflow)
- On Microsoft Learn: open the AZ-900 certification page and follow the three tabs: Prepare → Practice → Take exam.
- Prepare:
- Study the three main topic areas and their associated modules (see module lists above).
- Prioritize Azure architecture & services (highest exam weight).
- Practice:
- Use the practice assessment on Microsoft Learn to assess readiness.
- Take exam:
- Schedule through the certification page, complete personal details, pay (local currency shown), and sit the 45-minute exam.
Speakers / sources featured
- Rakesh — presenter / instructor (video narrator)
- Microsoft Learn / learn.microsoft.com — official MS Learn certification pages and practice assessment
- Microsoft / Azure — the cloud provider discussed (context/source for services, Azure Arc, and shared responsibility)
Category
Educational
Share this summary
Is the summary off?
If you think the summary is inaccurate, you can reprocess it with the latest model.