AZ-900: Microsoft Azure Fundamentals Exam Day CheatSheet 2026 All Exam-Critical & Tricky Points by Chapter

Welcome Welcome to AZ-900: Microsoft Azure Fundamentals Exam Day Cheatsheet 2026 This book was created to make Azure fundamentals easier to understand and easier to revise. The AZ-900 exam is not about configuring services or memorizing technical steps. It tests how well you understand core cloud concepts, responsibility boundaries, and basic decision making in Azure. Many learners feel overwhelmed because most resources include too much detail and not enough clarity. This guide focuses only on exam-critical points, common misunderstandings, and ideas that frequently appear in questions. You do not need to remember everything. You need to understand what each service is meant for, who is responsible for what, and how to choose the simplest correct option. That is the purpose of this cheatsheet. Use this book as a quick reference while studying, a revision guide before the exam, or a reminder of fundamentals as you learn Azure. Read it at your own pace and revisit sections when concepts feel unclear. Take it step by step. Understanding matters more than memorization. Welcome, and best wishes on your AZ-900 learning journey.

Table of Contents Chapter 1 – Cloud Concepts Chapter 2 – Azure Architecture and Core Services Chapter 3 – Azure Compute Services Chapter 4 – Azure Networking Services Chapter 5 – Azure Storage Services Chapter 6 – Identity, Access, and Security Chapter 7 – Management and Governance Chapter 8 – Monitoring and Management Tools Chapter 9 – Pricing, Cost Management, and SLAs Chapter 10 – Exam Scenarios and Decision Logic 1 4 7 10 13 16 19 22 25 28

Chapter 1 – Cloud Concepts 9. 11.Elasticity can scale down as well as up 7. Private cloud is dedicated to one organization 6. Public cloud resources are owned by Microsoft 3. Azure follows an operational expenditure model 5. Operational expenditure is usage based spending 2. Cloud does not mean free, it means pay for usage All Points 1. Cloud computing delivers services over the internet 4. Capital expenditure is upfront hardware investment 10.Elasticity means automatic scaling based on demand 8. Hybrid cloud combines on premises and public cloud Scalability means manual increase or decrease of resources 12.Cloud does not guarantee better performance automatically 1

21.Cloud services still fail 22.Cloud reduces impact, not risk 16.Fault tolerance usually costs more 17.Backup protects data, not service uptime 24.Microsoft secures the cloud infrastructure 26.Security responsibility varies by service type 27.SaaS shifts more responsibility to Microsoft 15.High availability does not mean zero downtime 20.Backup alone cannot meet uptime requirements 19.Disaster recovery usually involves another region 13.High availability focuses on minimizing downtime 18.Disaster recovery restores services after major failures 25.Customers secure data, identities, and configurations 23.Shared responsibility model applies to all cloud services 14.Fault tolerance focuses on surviving failures without interruption 2

38.Cloud pricing is not fixed 32.Cloud cost grows with usage 36.Elasticity is not load balancing 34.Cloud security is not automatic 33.Monitoring is still required in cloud 35.Cloud availability depends on design 39.Cloud SLAs depend on service choice 37.Cloud does not remove downtime risk 30.Cloud resources have quotas and limits 31.Cloud adoption requires governance planning 28.IaaS shifts more responsibility to the customer 29.Cloud does not remove compliance responsibility 40.Cloud migration does not remove IT responsibility 3

Chapter 2 – Azure Architecture and Core Services 6. Availability zones are optional 3. A region is not a single datacenter 11.Subscriptions are billing boundaries 9. Regions are isolated from each other 10.Using multiple regions increases cost 8. Region pairs support disaster recovery 2. A region contains multiple datacenters All Points 1. Azure is divided into geographic regions 5. Not all regions support availability zones 7. Region pairs are predefined by Microsoft 12.Subscriptions are access control boundaries 4. Availability zones are separate datacenters in a region 4

26.ARM enforces governance rules 15.Resource groups are not physical 14.Resource groups are logical containers 25.ARM does not control runtime behavior 13.Resource groups organize related resources 17.Resource groups cannot span subscriptions 20.Management groups sit above subscriptions 22.Management groups do not deploy resources 18.Resources can move between resource groups 24.ARM controls deployment and configuration 16.A resource belongs to only one resource group 23.Azure Resource Manager is the management layer 19.Deleting a resource group deletes all resources inside 21.Management groups help manage multiple subscriptions 27.Core Azure services fall into compute, storage, networking 5

29.Region choice affects latency 35.ARM templates are declarative 38.Resource placement affects cost 34.Azure services depend on ARM 30.Region choice affects compliance 32.More regions increase complexity 37.Resource placement affects resilience 33.Architecture decisions affect cost early 39.Azure architecture impacts availability 31.Global services are still billed per usage 40.Azure architecture impacts governance 28.Not all services are available in all regions 36.Resource organization affects management 6

Chapter 3 – Azure Compute Services 11.Azure Functions are serverless 12.Functions run code on demand 6. VM scale sets support auto scaling 9. App Service limits OS level control 4. VM scale sets manage identical VMs 2. Virtual machines require OS patching 8. App Service removes server management All Points 1. Virtual machines provide full OS control 7. Azure App Service is platform as a service 5. VM scale sets do not remove OS responsibility 10.App Service scaling is simpler than VM scaling 3. Virtual machines are infrastructure as a service 7