AZ-900 study guide for beginners

Begin with the difference between public, private, and hybrid cloud; IaaS, PaaS, and SaaS; shared responsibility; consumption-based pricing; and the reasons organizations use cloud platforms.

A real-world example is a company moving an internal application from an on-premises server to Azure. If it uses virtual machines, it still manages the operating system and much of the runtime. If it uses a managed app platform, Azure takes on more of the infrastructure burden. If it uses SaaS, the customer mostly configures and consumes the application.

Practice questions should make you identify the model from the responsibilities in the scenario. Who patches the operating system? Who manages the application? Who controls identity and data? Those questions are more useful than simply memorizing IaaS, PaaS, and SaaS definitions.

Group services into compute, storage, networking, identity, monitoring, and database categories. This makes it easier to choose between services when a question describes a business need.

For compute, compare virtual machines, App Service, containers, and serverless functions. For storage, understand account types, blobs, files, queues, and disks at a high level. For networking, recognize virtual networks, load balancers, VPN gateways, private connectivity, and DNS concepts.

In real work, service selection starts from a requirement. A static website, a line-of-business web app, a batch job, and a relational database all point to different service categories. The exam expects you to understand that matching process at a foundational level.

Azure Fundamentals learners often underestimate identity, access, subscriptions, resource groups, policy, locks, and management groups. These topics help explain how Azure environments are organized and controlled.

In a real organization, cloud resources are not managed one server at a time. Teams need subscriptions for billing and isolation, resource groups for lifecycle management, role-based access control for permissions, and policies to enforce standards such as allowed regions or required tags.

If a question asks how to prevent accidental deletion, a lock may be relevant. If it asks how to enforce a rule across many resources, policy may be stronger. If it asks how to group resources for a single application lifecycle, resource groups matter. The scenario should drive the answer.

Review cost tools, service-level agreements, support options, and the Azure pricing calculator. Practice questions should ask you to choose the correct tool or concept for a scenario, not simply define a term.

A project manager estimating a future deployment needs a different tool than an operations team investigating last month’s spend. A business asking about uptime commitments is thinking about service-level agreements, while a team seeking technical help may need to understand support plan options.

The mistake to avoid is treating pricing as a side topic. Cloud fundamentals exams include cost because cloud decisions are operational and financial. Practice identifying whether a scenario is about estimation, monitoring, optimization, governance, or support.

For each study week, pick one domain, answer a short drill, review missed rationales, then finish with saved questions. Add timed practice only after the main service categories are familiar.

A beginner-friendly rhythm is cloud concepts first, core services second, identity and governance third, then pricing and support. Each week, keep a short list of confused services and revisit them through scenarios rather than rereading a glossary.

When a missed question appears, explain the wrong answer in plain language. For example, App Service can host web apps, but it is not the same thing as a virtual network. That kind of contrast builds durable understanding.