Use AZ-900 to build an accurate mental model
AZ-900 is the Azure Fundamentals examination. Its current study guide groups the material into cloud concepts, Azure architecture and services, and management and governance. You should be able to explain the differences between concepts and choose an appropriate example, rather than administer every service in depth.
Start with a business scenario: a team needs an application, a database and controlled access for employees. Explain which responsibilities remain with the organisation under different cloud service models. This is a stronger foundation than memorising definitions without understanding what changes for the customer.
Separate service models and cloud benefits
With infrastructure as a service, the customer retains more operating-system and application responsibilities than with a managed platform. Software as a service supplies an application experience, but the customer still makes decisions about users, data and permitted use. Shared responsibility is therefore not a single fixed division for every service.
Also distinguish elasticity, scalability, reliability and availability. An application can scale but still have a single point of failure. A highly available design can still have poor access controls. Use a short example for each concept so that similar words do not collapse into the vague idea that “cloud is better.”
Understand the Azure hierarchy
A resource is an individual service instance or component. Resource groups organise related resources; subscriptions provide an important management and billing boundary; management groups organise subscriptions for governance at a higher level. Microsoft Entra ID provides identity capabilities and should not be confused with a resource group.
Draw an illustrative organisation with a development subscription and a production subscription. Place an application’s resources in suitable groups and explain where a governance rule would be applied. The drawing is a learning aid, not a universal enterprise architecture. Its purpose is to make the hierarchy and scope understandable.
Compare the services by workload
Contrast a virtual machine with a container-based application and an event-triggered function. Ask who manages the runtime, what starts execution and what operating tasks remain. For storage, distinguish object-like content from files and disks rather than treating every storage option as identical.
For identity and security, separate authenticating a user from authorising an action. Multifactor authentication strengthens a sign-in process; a role assignment controls permitted actions at an applicable scope. Neither should be described as a replacement for the other.
Make governance concrete
Imagine a team repeatedly creates resources without useful ownership information. Tags help classify resources, while a governance policy can evaluate or enforce defined conditions. A resource lock addresses particular deletion or modification scenarios; it is not a complete substitute for access control.
Add a cost exercise: identify the likely cost drivers, use the pricing calculator with explicit assumptions and decide how you would notice unexpected spend. Avoid assuming that a budget alert is itself a universal hard spending cap. The examination’s governance topics are easier to remember when tied to an actual management problem.
Use a small review loop
Read an official learning module, explain the concept without the page open, then answer an authorised practice question or complete a relevant demonstration. Record the distinction behind each error. If you confused identity scope with resource scope, return to the hierarchy rather than repeating the same question immediately.
Use Microsoft’s sandbox to learn the interface separately from the subject. Practice assessments do not reproduce the complete live examination. Confirm the current study-guide version, booking identity and delivery rules before payment. Fundamentals credentials do not require the annual renewal process used for eligible role-based credentials.
Practical questions answered
How technical should my notes become? Match the depth to the published fundamentals objective. Explain the purpose, appropriate use and responsibility of a capability before drilling into deployment options. If a detailed configuration does not help distinguish the concepts being assessed, return to the objective rather than expanding the notes indefinitely.
What is a useful first exercise? Sketch an application’s resource hierarchy and identify who needs access, what consumes money and which operating tasks remain with the team. You can do this without deploying a billable service. Validate the terminology using a learning module, then explain the diagram to someone else.
Official references
Certification requirements and programme terms can change. Use the issuer’s current page and your account to confirm details before applying or paying.