AZ-900 Practice Test Bank: 200+ Qs with Detailed Answers

Section 1.1: AZ-900 exam overview, audience, and certification value

AZ-900 is Microsoft’s entry-level Azure certification exam, aimed at validating foundational knowledge of cloud concepts and core Azure services. It is designed for beginners, career changers, students, sales or project roles that work around cloud technology, and technical professionals who want a structured starting point before moving into administrator, developer, security, or data certifications. Although no deep hands-on experience is required, the exam assumes that you can connect basic cloud ideas to real Azure examples.

From an exam-coach perspective, AZ-900 tests breadth more than depth. You are expected to know what categories of services exist, when they are generally used, and how core cloud principles such as scalability, elasticity, high availability, and consumption-based pricing operate. The exam is not intended to assess whether you can deploy complex infrastructure from memory. A frequent trap is overthinking the question and choosing an advanced answer because it sounds more technical. In fundamentals exams, the best answer is usually the one that cleanly matches the concept being assessed.

The certification has real value because it establishes cloud literacy. For many employers, AZ-900 signals that you understand the shared responsibility model, cloud deployment models, basic Azure architecture, and governance concepts such as policy, compliance, and cost awareness. It can also serve as a confidence-building milestone before pursuing role-based certifications.

Exam Tip: Treat AZ-900 as a concept-mapping exam. If you can explain a term in plain language and recognize the Azure service category that fits it, you are studying at the right level. If your preparation becomes too configuration-heavy, you may be going deeper than the objective requires.

Another way to think about exam value is strategic progression. Candidates who pass AZ-900 often build a stronger base for later Microsoft exams because they already understand Azure terminology, portal structure, and service families. That foundation makes future study easier and helps prevent confusion when later exams assume familiarity with cloud and Azure basics.

Section 1.2: Official exam domains and weighting strategy

A smart AZ-900 study plan begins with the official exam domains. At a high level, the exam covers three major areas: cloud concepts; Azure architecture and services; and Azure management and governance. These domains are not equally weighted, so your preparation should reflect the likely exam emphasis. Weighting can change over time, which is why you should always compare your study plan to the current Microsoft skills outline. However, the biggest takeaway remains consistent: architecture and services usually represent a large portion of the exam, while cloud concepts and governance are also essential and cannot be ignored.

Cloud concepts include public, private, and hybrid cloud models, as well as IaaS, PaaS, and SaaS. This area also includes benefits such as agility, elasticity, high availability, fault tolerance, and disaster recovery thinking at a foundational level. Azure architecture and services includes regions, availability zones, resource groups, subscriptions, and service categories such as compute, networking, and storage. Management and governance includes pricing tools, service-level ideas, policy, locks, compliance-related concepts, and monitoring tools.

Common exam traps come from domain overlap. For example, a question might mention cost, but the real objective may be identifying the correct Azure management tool. Or a scenario may mention application deployment, but the tested idea may be whether the solution aligns with IaaS or PaaS. You need to ask: what is the objective behind the wording?

Exam Tip: Weighting should guide time allocation, not allow neglect. A lower-weighted domain can still be the difference between passing and failing if you leave it underprepared.

A practical strategy is to assign study time in proportion to domain weight while mixing in daily review of weak areas. Create a simple matrix with domain, confidence level, and practice accuracy. If you consistently miss governance questions, do not keep rereading compute notes. Instead, shift attention to the tested objective where your score data shows risk. That is how high-efficiency exam prep works.

Section 1.3: Registration process, scheduling, identification, and policies

Many candidates underestimate the administrative side of certification, but logistics matter. Registering for AZ-900 typically involves creating or using a Microsoft certification profile, selecting the exam, choosing a delivery option, and scheduling through the authorized exam delivery process available in your region. You may be able to choose a test center or an online proctored format, depending on current availability and policy. This decision should not be random. Choose the environment where you are least likely to be distracted and most likely to follow requirements comfortably.

If you select a test center, plan travel time, arrival time, and acceptable identification in advance. If you choose online delivery, test your computer, internet connection, webcam, microphone, workspace conditions, and software compatibility well before exam day. Online proctored exams often have strict rules about desk setup, room privacy, behavior, and permitted items. A preventable policy issue can create unnecessary stress or delay.

Identification requirements are especially important. The name on your registration should match your identification documents. Review current policy before exam day rather than assuming past testing experiences apply. Also understand rescheduling and cancellation windows, since missing them can cost money or an exam attempt.

Exam Tip: Schedule your exam date early enough to create urgency, but not so early that you force yourself into panic review. A date on the calendar turns vague intention into a disciplined study plan.

On exam day, expect check-in procedures, security steps, and time-sensitive instructions. Read all on-screen instructions carefully. Administrative mistakes can affect your focus before the exam even begins, so remove uncertainty in advance by verifying appointment details, policy rules, and identification readiness at least a few days beforehand.

Section 1.4: Exam question styles, scoring concepts, and passing readiness

AZ-900 may include multiple-choice, best-answer, and scenario-style items. Even when a question looks simple, Microsoft often embeds clues in the wording. Terms like “best,” “most appropriate,” or “primary benefit” matter. Your task is not just to find a true statement, but the strongest answer for the objective being tested. This is where many candidates lose points: they choose an option that is factually related, but not the best fit for the scenario or domain.

You should also understand the idea of scaled scoring. Microsoft certification exams typically report a scaled score rather than a raw count of correct answers. That means you should not waste energy trying to guess your exact percentage during the exam. Focus instead on careful reading, elimination, and consistent pacing. Passing readiness is about repeated evidence in practice, not intuition alone.

A strong readiness standard is to perform consistently above your target threshold across mixed-topic practice sets, not only on topic-specific drills. If your score drops sharply when domains are blended, that often means recognition is weak and you may be relying too much on memorized patterns. The real exam rewards transfer of understanding across differently worded prompts.

Common distractors include answers that are almost correct but belong to a different service category, answers that are too advanced for a fundamentals exam, and answers that confuse general cloud concepts with Azure-specific tools. Eliminate options by asking whether the answer aligns with the exact need stated in the prompt.

Exam Tip: When stuck, remove answers that solve a different problem than the one asked. The exam often includes technically impressive distractors that do not address the actual requirement.

Your passing readiness should be based on trends: stable practice results, clear understanding of mistakes, and confidence across all domains. One lucky high score is not readiness. Reproducible performance is readiness.

Section 1.5: Beginner study plan for practice banks, notes, and revision

Beginners do best with a structured study workflow. Start by dividing your preparation into three phases: learn, practice, and refine. In the learn phase, read or watch foundational material aligned to the official domains. Keep notes short and comparative. For example, instead of copying long definitions, write contrast notes such as public vs. private cloud, IaaS vs. PaaS vs. SaaS, or Azure resource group vs. subscription. Comparison notes are more useful on exam day because many questions ask you to distinguish similar concepts.

In the practice phase, use the test bank in manageable sets. Do not begin with full exam simulations every day. Start with domain-focused practice to build confidence, then move to mixed sets that better reflect exam conditions. After each set, review every explanation, including items you answered correctly. A correct guess is still a weak area.

In the refine phase, create a revision loop. Mark missed topics, rewrite them in your own words, and revisit them after one day, three days, and one week. This spaced repetition approach improves retention far better than cramming. Build a simple tracker with columns for topic, last reviewed date, practice accuracy, and confidence level.

Exam Tip: Do not overfill your notebook. A small set of high-value notes reviewed repeatedly is far more effective than dozens of pages never revisited.

A practical weekly plan might include concept review early in the week, targeted practice midweek, and a timed mixed review session at the end. If you have limited time, consistency matters more than marathon sessions. Thirty focused minutes daily with active review usually outperforms one long but passive weekend session. The key is to connect study directly to objective areas and actual errors.

Section 1.6: How to use detailed answer explanations to improve retention

Detailed answer explanations are one of the most powerful tools in any exam-prep course, but only if you use them actively. Many candidates check whether they were right or wrong and then move on. That wastes the main learning opportunity. The explanation tells you what the exam was testing, why the correct answer fits, and why the distractors are weaker. This is how you build exam reasoning rather than memorizing isolated facts.

After each practice item, ask four questions: What objective was being tested? What clue in the prompt pointed to the correct answer? Why was my chosen answer wrong or incomplete? How can I recognize this pattern next time? Write a one-line takeaway in your notes. Over time, these takeaways become a personalized error log that is more valuable than generic summaries.

Explanations are especially helpful for identifying common traps. For example, you may notice a pattern where you confuse a cloud concept with an Azure product, or where you select an answer that is technically true but not the most direct solution. When you track these habits, you can correct them deliberately.

Exam Tip: Review correct answers with the same seriousness as incorrect ones. If your reasoning was weak but your guess was lucky, the concept is not yet secure.

Use score reports and readiness checks to guide explanation review. If your mixed-set performance shows weakness in governance or networking basics, return to those explanations first. This targeted loop turns assessment into instruction. Eventually, you will notice that questions stop feeling random. Instead, you will see recurring exam patterns: service matching, concept comparison, responsibility boundaries, pricing logic, and governance tool selection. That recognition is a major sign of AZ-900 readiness and a strong predictor of success on the real exam.

Section 2.1: Describe cloud concepts - what cloud computing is

Cloud computing is the delivery of computing services over the internet. Those services can include servers, storage, databases, networking, analytics, and software. Instead of buying and maintaining all infrastructure in a local datacenter, an organization can access resources from a cloud provider on demand. For AZ-900, the most important idea is that cloud computing provides resources when needed, at scale, and typically on a pay-as-you-go basis.

On the exam, Microsoft often tests whether you understand that cloud computing is not a single product. It is a model for consuming IT services. If a scenario describes accessing infrastructure, development platforms, or software through a provider rather than running everything yourself on-premises, it is describing cloud computing. The test may also contrast cloud with traditional datacenter ownership to assess whether you can recognize the business value.

Cloud computing usually includes several characteristics: on-demand self-service, broad network access, pooled resources, rapid provisioning, and measured usage. You do not need to recite those formally, but you should recognize their practical implications. If a company can provision resources quickly without waiting for hardware purchases, that points to cloud. If usage can grow or shrink and charges reflect consumption, that also points to cloud.

A frequent exam trap is confusing cloud computing with virtualization. Virtualization can be part of cloud computing, but running virtual machines in your own datacenter is not automatically the same as using cloud services. Another trap is assuming cloud means only web applications. In fact, cloud supports infrastructure, application development platforms, storage, AI services, and business software.

• Cloud computing emphasizes service delivery over ownership.
• Resources can often be provisioned quickly and scaled as needed.
• Customers usually pay based on usage or subscription rather than large upfront investment.
• The provider manages some or much of the underlying infrastructure, depending on the service model.

Exam Tip: If the question asks what cloud computing allows an organization to do, think in terms of flexibility, rapid provisioning, and consumption-based access to IT resources. If the wording focuses on owning servers and facilities, it is describing traditional on-premises computing, not cloud.

For exam-style reasoning, ask yourself: Is the scenario about consuming technology as a service? If yes, cloud computing is the core concept being tested.

Section 2.2: Describe cloud concepts - benefits of high availability and scalability

High availability and scalability are foundational cloud benefits, and AZ-900 frequently tests the difference between them. High availability means services remain accessible with minimal downtime, even when failures occur. Scalability means the ability to handle increasing or decreasing workload demands by adjusting resources. These concepts are related, but they are not interchangeable.

If a business requires a service to remain online despite hardware failures, maintenance events, or regional issues, the correct cloud concept is high availability. Cloud providers support this through redundancy, fault tolerance, multiple datacenters, and service design features that reduce interruption. On the exam, clue words such as uptime, minimize downtime, service interruption, or keep applications running point toward high availability.

Scalability focuses on workload growth. If a retailer expects more website traffic during promotions or a business adds users quickly, cloud resources can be adjusted to maintain performance. Azure Fundamentals may describe vertical scaling, which means increasing the capacity of an existing resource, or horizontal scaling, which means adding more resource instances. You do not need deep architecture knowledge, but you should understand that scaling addresses demand, not outage recovery.

A common trap is choosing scalability when the question is really about reliability or uptime. Another trap is reading a temporary traffic surge and selecting high availability instead of scalability. Always identify whether the scenario is about staying online during failure or handling more usage.

• High availability = service remains operational and accessible.
• Scalability = resources adjust to support workload changes.
• Vertical scaling = make one resource bigger.
• Horizontal scaling = add more resources.

Exam Tip: If a question mentions more users, increased demand, or better performance under growth, think scalability. If it mentions failures, redundancy, or reduced downtime, think high availability.

From a business-value perspective, both benefits matter because organizations want systems that remain available and can grow without major delays. Microsoft tests whether you can connect these technical ideas to outcomes such as customer satisfaction, business continuity, and operational resilience.

Section 2.3: Describe cloud concepts - elasticity, reliability, predictability, and security

This section covers several cloud characteristics that often appear together in AZ-900 questions. Elasticity is the ability to automatically or quickly scale resources up or down as demand changes. It is closely related to scalability, but the exam distinction is that elasticity usually emphasizes dynamic adjustment, especially for short-term or variable workloads. If usage spikes suddenly and then falls, elasticity is the better concept.

Reliability means a system can recover from failures and continue operating consistently. In cloud environments, this is supported through resilient design, geographic distribution, and built-in redundancy. If a scenario describes dependable service despite component failure, reliability is the tested idea. Predictability refers to consistent performance and cost. Cloud services can improve predictability because they are built on known, measurable resources and often include tools for performance monitoring and cost estimation.

Security is another major business benefit of cloud computing, but AZ-900 expects you to understand it at a high level. Cloud providers offer security tools, physical datacenter protection, identity controls, encryption options, and monitoring capabilities. However, security in the cloud is not the provider's responsibility alone. This connects to the shared responsibility model, which is introduced in the broader cloud concepts domain and appears throughout the exam. The provider secures the cloud infrastructure, while customers remain responsible for many configuration and data protection choices.

Common distractors in this area include mixing up reliability and high availability, or treating security as automatic and complete with no customer role. Reliability emphasizes dependable operation and recovery. High availability emphasizes minimizing downtime. Security emphasizes protection, but not a total transfer of all responsibility to Azure.

• Elasticity helps with changing demand patterns.
• Reliability supports consistent operation through failures.
• Predictability relates to expected performance and cost behavior.
• Security is strengthened in the cloud, but responsibilities are shared.

Exam Tip: Words like unexpected spikes and automatically adjust indicate elasticity. Words like consistent results, forecasting, or known spending indicate predictability. If an option says the cloud provider is responsible for all security, that is usually a trap.

When reviewing answer choices, always map the scenario to the exact attribute being described instead of choosing a broad “sounds good” benefit. That is the key exam skill in this topic.

Section 2.4: Describe cloud concepts - CapEx versus OpEx

AZ-900 regularly tests the financial shift from traditional on-premises investment to cloud consumption. Capital expenditure, or CapEx, is money spent upfront on physical assets such as servers, storage systems, networking gear, and datacenter facilities. Operating expenditure, or OpEx, is ongoing spending on products and services as they are consumed. Cloud computing often moves organizations away from heavy CapEx and toward OpEx.

In an on-premises model, a company may need to forecast demand, buy hardware in advance, install it, and maintain it over time. That requires large initial spending and creates a risk of overprovisioning or underprovisioning. In a cloud model, the company can often pay for what it uses, adding or reducing services as needed. This improves financial flexibility and lowers the barrier to starting new projects.

On the exam, the clue is usually in the business language. If a question mentions reducing upfront costs, avoiding large hardware purchases, or treating IT as an ongoing operating cost, the correct idea is OpEx. If a question describes purchasing datacenter equipment as a long-term asset, the concept is CapEx. Microsoft may also test whether you understand that cloud does not always eliminate all capital expenses, but the general cloud consumption model strongly aligns with OpEx.

A common exam trap is assuming that cheaper always means cloud. The exam objective is not absolute cost in every scenario; it is understanding the spending model. Another trap is choosing scalability or elasticity when the question is actually about financial planning and procurement.

• CapEx = upfront investment in owned infrastructure.
• OpEx = ongoing spending based on use or subscription.
• Cloud supports faster startup because it reduces the need for major initial purchases.
• Consumption-based pricing improves flexibility and can align spending with demand.

Exam Tip: If the requirement says “avoid upfront infrastructure costs,” eliminate any answer focused on buying hardware. If it says “pay only for resources used,” that strongly signals OpEx and cloud consumption pricing.

From a business-value standpoint, this is one reason organizations move to cloud: they can experiment, scale, and budget more dynamically. That practical reasoning appears often in Azure Fundamentals scenarios.

Section 2.5: Describe cloud concepts - IaaS, PaaS, and SaaS comparison

One of the highest-yield AZ-900 topics is the comparison among Infrastructure as a Service, Platform as a Service, and Software as a Service. Microsoft expects you to understand the management responsibilities, business use cases, and clues that identify each model. These are service models, not deployment models, and students often lose points by confusing them with public, private, and hybrid cloud.

IaaS provides basic computing resources such as virtual machines, storage, and networking. The cloud provider manages the physical infrastructure, while the customer manages more of the stack, including the operating system, applications, and much of the configuration. On the exam, if a company wants maximum control while avoiding physical hardware management, IaaS is often correct.

PaaS provides a managed platform for building, deploying, and running applications. The provider manages infrastructure and much of the runtime environment, allowing developers to focus more on code and less on server maintenance. If the scenario emphasizes application development without managing operating systems and patching, PaaS is likely the best answer.

SaaS delivers complete software applications over the internet. Users simply access the software, usually through a browser or client application, while the provider manages almost everything behind the scenes. If the scenario involves using email, productivity software, or a business application without installing and maintaining the full environment, SaaS is the match.

Common distractors include choosing IaaS because virtual machines are familiar, even when the question clearly says developers do not want to manage the platform. Another trap is choosing SaaS for any cloud software scenario, even when the company is actually building its own application. Read carefully for who manages what.

• IaaS: most control, more customer management.
• PaaS: balanced model for application development.
• SaaS: least customer management, ready-to-use software.

Exam Tip: Ask, “What does the customer still manage?” If the answer includes operating systems and runtime control, think IaaS. If the customer mainly manages the application and data, think PaaS. If the customer mainly just uses the software, think SaaS.

This comparison is central to shared responsibility and appears repeatedly across the exam. The less you manage, the more responsibility shifts to the provider.

Section 2.6: Describe cloud concepts - public, private, and hybrid cloud models

Deployment models describe where cloud resources are hosted and how they are used. For AZ-900, you must compare public cloud, private cloud, and hybrid cloud. This is a different classification from IaaS, PaaS, and SaaS. Service model questions are about what is delivered; deployment model questions are about where and how the environment is deployed.

Public cloud means resources are owned and operated by a third-party cloud provider and delivered over the internet. Multiple customers share the provider's overall infrastructure, even though data and workloads are logically separated. Public cloud is often associated with speed, scalability, and reduced capital cost. If the scenario describes consuming services from a provider like Microsoft without owning the underlying datacenter, public cloud is usually correct.

Private cloud refers to cloud resources used exclusively by one organization. It can be hosted in the organization's own datacenter or by a third party, but it is dedicated to that single organization. On the exam, private cloud is often linked to greater control, customization, or specific compliance needs, though it may involve higher cost and management overhead than public cloud.

Hybrid cloud combines public and private environments, allowing data and applications to move between them as needed. This model is common when organizations must keep some workloads on-premises while taking advantage of public cloud scalability or services. If the scenario mentions regulatory requirements, gradual migration, disaster recovery integration, or connecting existing systems to cloud resources, hybrid cloud is a strong answer.

A common trap is assuming hybrid means “using more than one cloud service.” That wording more often describes multi-cloud, which is different from the core public/private/hybrid model set emphasized in AZ-900. Another trap is equating private cloud with simply having a local datacenter. A private cloud still uses cloud principles such as self-service and pooled resources, but in a dedicated environment.

• Public cloud: provider-owned, shared model, broad scalability.
• Private cloud: dedicated to one organization, more control.
• Hybrid cloud: combines both to meet mixed requirements.

Exam Tip: If a company must keep certain data on-premises but wants cloud benefits for other workloads, hybrid cloud is the likely best answer. If the scenario emphasizes rapid deployment and minimal infrastructure ownership, public cloud is usually favored.

For exam success, first identify whether the question is asking about control, compliance, migration flexibility, or cost. Then match that requirement to the deployment model that best satisfies it. That disciplined approach helps you avoid distractors and choose the answer Microsoft expects.

Section 3.1: Describe cloud concepts - shared responsibility model

The shared responsibility model is one of the highest-value AZ-900 concepts because it appears in direct questions and also hides inside service questions. The core idea is simple: security and operational responsibilities are divided between the cloud provider and the customer. In Azure, Microsoft is always responsible for the security of the cloud, meaning the physical datacenters, physical hosts, networking infrastructure, and foundational platform components. The customer is always responsible for security in the cloud to some degree, but the amount depends on the service model being used.

For Infrastructure as a Service, the customer manages more. If you deploy virtual machines, you are typically responsible for the guest operating system, patches inside the VM, installed applications, identity configuration, and much of the network access configuration. For Platform as a Service, Microsoft manages more of the underlying platform, but the customer still manages data, account access, and application configuration. For Software as a Service, Microsoft manages most of the stack, while the customer usually remains responsible for data, user access, and endpoint usage. AZ-900 does not require low-level security operations knowledge, but it absolutely tests whether you understand this sliding scale of responsibility.

A common exam trap is selecting answers that say Microsoft is responsible for everything in the cloud. That is incorrect. Another trap is assuming the customer always patches every system. That may be true in IaaS, but it is not broadly true in PaaS or SaaS. Read the service model first, then assign responsibility. If a prompt mentions physical servers, physical networking, or datacenter facilities, think Microsoft. If it mentions user identities, data classification, or access permissions, think customer.

Exam Tip: The exam often uses wording such as “depending on the service type” or “varies by cloud model.” That is a signal that the correct answer is not absolute. Be cautious with answers containing words like “always” and “never” unless the topic is something firmly fixed, such as Microsoft managing physical infrastructure.

To identify the correct answer, separate infrastructure responsibilities from workload responsibilities. If the scenario mentions Azure SQL Database or another managed service, do not automatically bring IaaS assumptions into the question. Microsoft handles more in managed services than in raw virtual machine deployments. This is where cloud principles connect directly to Azure architecture basics: the exam wants you to understand not only what Azure offers, but how responsibility changes depending on the architecture chosen.

Section 3.2: Describe Azure architecture and services - Azure regions and region pairs

An Azure region is a set of one or more datacenters deployed within a specific geographic area. Regions are foundational because many Azure services are deployed into them, and exam questions often test whether you understand that a region is the place where resources are hosted. Students sometimes confuse a region with a country or a datacenter. A region is broader than a single datacenter and narrower than the entire global Azure network. Examples include East US, West Europe, and Southeast Asia.

Region pairs are also testable. Microsoft pairs many regions within the same geography, such as one region being linked to another for certain disaster recovery and platform update priorities. You do not need to memorize every pair for AZ-900, but you should understand why region pairs exist. They support resiliency planning, help with platform recovery priorities in rare large-scale outages, and can be relevant for data residency and business continuity discussions. If the exam asks which architectural concept supports broad regional resiliency, region pairs are a strong candidate.

A major trap is mixing up availability zones with region pairs. Region pairs involve two separate regions. Availability zones are separate physical locations within a single region. The exam may place both in the same answer set, so read closely. If the prompt says “within the same region,” think zones. If it says “another region in the same geography,” think region pair.

Exam Tip: On AZ-900, region questions often test purpose rather than memorization. Focus on what a region provides: geographic deployment choice, proximity, compliance support, and service availability location. Focus on what a region pair adds: broader resilience and structured pairing for continuity considerations.

When evaluating answers, ask what problem the architecture is trying to solve. If the goal is reduced latency for users in a given area, choose an answer related to selecting an appropriate region. If the goal is large-scale recovery planning across regional boundaries, choose region pairs. This “problem-to-component” matching approach is a reliable exam strategy and reinforces the lesson of connecting cloud principles to Azure foundational architecture.

Section 3.3: Describe Azure architecture and services - availability zones and datacenters

Availability zones are physically separate locations within a single Azure region. Each zone has independent power, cooling, and networking, which allows supported services to achieve higher resilience against datacenter-level failures. This is an important distinction: a zone is not another region, and it is not merely a logical partition. It represents physical separation inside a region. Microsoft uses this concept to help organizations build high availability while remaining in the same geographic region.

Datacenters, by contrast, are the actual physical facilities that house servers, storage, and networking equipment. In exam wording, remember the hierarchy: datacenters make up the physical infrastructure; availability zones are separate physical locations within a region; regions are larger geographic deployment areas that may contain one or more datacenters. If you confuse these layers, distractor answers become very tempting.

One common trap is assuming every Azure region supports availability zones. Not all services and not all regions have the same capabilities. AZ-900 will not expect a detailed availability matrix, but it may test whether you know that service availability can differ by region. Another trap is believing that using multiple availability zones means using multiple regions. It does not. Zone-based resilience stays inside one region.

Exam Tip: If an answer mentions protection from a datacenter outage while keeping resources in the same region, availability zones are usually the best match. If it mentions wider geographic separation, then look at regions or region pairs instead.

To identify the correct answer, map the outage scope. For a localized facility failure, zones are relevant. For larger regional events, region-level design choices are more relevant. AZ-900 is testing whether you can classify resilience options by physical scope. This is practical exam reasoning, not just memorization. In architecture-focused fundamentals questions, the best answer is often the one that matches the right level of failure isolation.

Section 3.4: Describe Azure architecture and services - subscriptions and management groups

Subscriptions are logical containers used to provision and manage Azure services. They are central to billing, access control boundaries, and organizational separation. If a company wants to separate production from development, separate departments, or track costs independently, multiple subscriptions may be used. On AZ-900, subscriptions are often tested as an administrative and billing boundary rather than a technical hosting mechanism.

Management groups sit above subscriptions in the Azure hierarchy. They allow organizations to organize multiple subscriptions and apply governance at scale. For example, policies and access controls can be assigned at the management group level and inherited by subscriptions underneath. This is especially relevant for large enterprises with many subscriptions. On the exam, if the scenario is about centrally governing many subscriptions, management groups are usually the correct answer.

A frequent trap is choosing resource groups when the prompt is really about organizing multiple subscriptions. Resource groups exist inside a subscription; they do not contain subscriptions. Another trap is thinking subscriptions are only for billing. Billing is a major purpose, but subscriptions also form a scope for governance and access management. The exam may present several true statements, and your task is to select the one that best fits the specific requirement in the scenario.

Exam Tip: Remember the hierarchy: management groups can contain subscriptions, subscriptions can contain resource groups, and resource groups contain resources. If the question asks for organization across many subscriptions, resource groups are too low in the hierarchy.

To eliminate distractors, focus on scope. If the requirement is enterprise-wide policy across several business units, think management groups. If the requirement is one billing boundary or one administrative unit for Azure services, think subscription. This section also supports mixed-domain answer analysis because governance concepts later in the exam depend heavily on understanding this hierarchy correctly.

Section 3.5: Describe Azure architecture and services - resource groups and resources

A resource group is a logical container within an Azure subscription that holds related resources for a solution. Resources are the individual Azure service instances you create, such as virtual machines, storage accounts, virtual networks, or databases. The exam expects you to know that resource groups help organize, manage, and apply lifecycle thinking to related components. For example, resources used by the same application may be placed in one resource group for easier administration.

One point the exam often checks is that a resource group is not a physical boundary and not a billing mechanism in the same way a subscription is. Resources in a resource group can sometimes exist in different regions, even though the resource group itself is a management construct. This surprises many beginners and creates exam confusion. Be careful not to assume “same group” means “same region.”

Another common trap is believing a resource can belong to multiple resource groups. A resource belongs to one resource group at a time. Similarly, a resource group belongs to one subscription. If a question asks about moving resources or organizing them, keep those boundaries in mind. AZ-900 typically stays conceptual, but these structural facts matter for selecting the right answer.

Exam Tip: If the prompt emphasizes grouping related services for management, permissions, automation, or lifecycle operations, resource groups are often the right answer. If it emphasizes cost tracking or separation at a higher organizational level, a subscription may be the better fit.

When choosing between resource groups and subscriptions, ask whether the requirement is “manage related components together” or “create a higher-level administrative and billing boundary.” That distinction appears repeatedly in Azure Fundamentals. Knowing it also improves your performance on scenario-based questions because many distractors rely on students picking the largest familiar term rather than the most precise one.

Section 3.6: Describe Azure architecture and services - Azure Resource Manager basics

Azure Resource Manager, commonly abbreviated as ARM, is the deployment and management service for Azure. It provides a consistent management layer that allows you to create, update, and delete resources in an Azure subscription. For AZ-900, you do not need deep template authoring skills, but you do need to understand ARM as the control plane that organizes and manages Azure resources. When you deploy through the Azure portal, Azure PowerShell, Azure CLI, or templates, Azure Resource Manager is the underlying management framework.

ARM supports infrastructure as code concepts through declarative templates, allowing resources to be deployed consistently and repeatedly. Even though AZ-900 is introductory, Microsoft may test whether you know that templates improve consistency and reduce manual configuration errors. This fits the foundational architecture theme because ARM provides standardization across deployments. It also supports governance through policy, role-based access, and tagging at management scopes.

A common trap is confusing Azure Resource Manager with a specific resource type or with the Azure portal itself. The portal is a user interface; ARM is the management layer behind resource deployment and administration. Another trap is mixing ARM with resource groups. Resource groups are containers for resources. ARM is the service that manages deployment and operations across those resources and scopes.

Exam Tip: If the question refers to deploying Azure resources in a repeatable, consistent way, ARM templates or Azure Resource Manager are likely involved. If it refers to simply grouping resources, that points to resource groups instead.

To identify the correct answer, look for verbs such as deploy, manage, update, delete, or automate. Those words usually indicate Azure Resource Manager. This is a classic AZ-900 “what does the service do?” objective. Strong candidates strengthen recall by pairing each architectural term with its main action: subscriptions organize and bill, resource groups group, regions host, zones provide in-region resilience, and Azure Resource Manager deploys and manages. That mental map is exactly the kind of practical reasoning that improves your final review strategy and reduces mistakes under time pressure.

Section 4.1: Describe Azure architecture and services - compute services and use cases

Azure compute services provide processing power for applications, websites, APIs, background jobs, and enterprise workloads. The AZ-900 exam expects you to recognize the major compute categories and choose among them based on operational control, scalability, and workload design. At a high level, Azure compute ranges from infrastructure-based options such as Virtual Machines to managed application hosting such as Azure App Service, and event-driven execution such as Azure Functions.

Azure Virtual Machines are best for scenarios where an organization needs maximum control over the operating system and software stack. These are commonly used for lift-and-shift migrations, legacy applications, custom server setups, and workloads that require administrator access. Azure App Service is designed for hosting web apps, REST APIs, and mobile app back ends without managing the operating system. Azure Functions supports serverless execution, meaning code runs in response to triggers and the organization pays primarily for execution time rather than reserving full servers.

The exam often tests whether you understand the difference between IaaS and PaaS through service selection. If the company wants to patch the OS, install special software, or keep a familiar server environment, that points toward Virtual Machines. If the business wants to deploy a web app quickly with minimal infrastructure management, App Service is usually correct. If the requirement is to process events, automate short tasks, or respond to timers or messages, Functions is commonly the intended answer.

• Choose Virtual Machines for control and compatibility.
• Choose App Service for managed web hosting.
• Choose Functions for event-driven serverless code.
• Choose containers when portability and packaging are central requirements.

Exam Tip: When the question says the organization wants to reduce administrative effort, eliminate answers that require managing operating systems unless the scenario explicitly requires OS-level control.

A common trap is confusing what is technically possible with what is best aligned to Azure fundamentals design goals. Yes, a website can run on a virtual machine, but if the exam says the company wants a managed web hosting platform, App Service is the better answer. The exam rewards the most suitable service, not merely a service that could work.

Section 4.2: Describe Azure architecture and services - virtual machines, containers, and serverless

This topic appears often because it tests service comparison skills. Virtual machines, containers, and serverless all support application execution, but they differ significantly in management model and ideal use case. On AZ-900, you do not need deep implementation knowledge, but you must understand the purpose of each model.

Virtual machines emulate physical computers in Azure. You choose the operating system, size, and installed software. They are useful for traditional enterprise applications, development and test environments, and workloads migrated from on-premises data centers. Because they offer the greatest control, they also require the most management. The customer is responsible for guest operating system maintenance, patching, and many security tasks.

Containers package an application and its dependencies so it runs consistently across environments. Azure Container Instances is a good option when you want to run containers without managing virtual machines or a full orchestration platform. Azure Kubernetes Service is intended for managing large-scale containerized applications that require orchestration, scaling, and resilience. At the AZ-900 level, the key distinction is simple: ACI is for simpler container execution; AKS is for orchestrated container environments.

Serverless services such as Azure Functions remove most infrastructure management. Developers focus on code, and Azure handles much of the scaling and runtime allocation. This model is ideal for event-driven processes, scheduled tasks, integrations, and lightweight APIs. The exam may present requirements such as automatic scaling, execution on demand, or minimizing infrastructure administration; these are strong clues for serverless.

Exam Tip: If the requirement mentions microservices or container orchestration, think AKS. If it only mentions running a container quickly and simply, ACI is usually the better fit. If it mentions event triggers or paying only when code runs, think Azure Functions.

A common trap is selecting Kubernetes whenever containers appear in the scenario. That is not always correct. The exam often checks whether orchestration is actually needed. Another trap is assuming serverless means “no servers exist.” In reality, Azure still uses infrastructure, but the customer does not manage it directly. Be precise with that language when reasoning through answer choices.

Section 4.3: Describe Azure architecture and services - networking fundamentals, VNets, and connectivity

Azure networking questions usually focus on foundational concepts: how resources communicate, how Azure connects to on-premises environments, and how organizations control traffic. The most important term is the Virtual Network, or VNet. A VNet is the basic private network boundary in Azure. It enables Azure resources such as virtual machines to communicate securely with one another, with the internet if allowed, and with on-premises environments through supported connectivity options.

Subnets divide a VNet into smaller segments, which helps organize and secure resources. Network Security Groups are used to allow or deny network traffic to and from resources. Although AZ-900 does not go deep into rule design, you should know that NSGs help control traffic at the subnet or network interface level. Public IP addresses enable internet-facing connectivity, while private IP communication stays within private networking scopes.

The exam also expects you to distinguish internet-based and private connectivity options. A VPN gateway can connect an on-premises network to Azure over the public internet using encryption. Azure ExpressRoute provides private, dedicated connectivity between on-premises infrastructure and Azure, bypassing the public internet. If the scenario emphasizes higher reliability, private connectivity, or consistent enterprise networking, ExpressRoute is often the expected answer.

Load balancing concepts may also appear. Azure Load Balancer distributes traffic at the network layer, while Azure Application Gateway operates at the web traffic level and includes web-focused features. For AZ-900, focus on recognizing broad purpose rather than deep protocol details.

Exam Tip: When a question asks for private connectivity from on-premises to Azure without traversing the public internet, ExpressRoute is the key phrase to recognize. If the question says encrypted connection over the internet, VPN is more likely correct.

A common trap is confusing a VNet with a subscription or resource group. A VNet is specifically a networking construct. Another trap is selecting ExpressRoute simply because it sounds more advanced. The exam usually wants the service that matches the exact requirement, not the premium enterprise option by default.

Section 4.4: Describe Azure architecture and services - storage services, redundancy, and migration basics

Storage is a high-value AZ-900 topic because Azure provides multiple storage types for different data patterns. You should know the main services and when to use them. Azure Blob Storage is optimized for massive amounts of unstructured object data such as images, video, backups, logs, and documents. Azure Files provides managed file shares using familiar file-sharing protocols. Azure Disk Storage supplies persistent disks for Azure virtual machines. Each one serves a different purpose, and exam questions often test whether you can map the business need to the correct storage model.

Blob Storage is often the best choice when the scenario involves storing large volumes of data accessible through object storage methods. Azure Files is more suitable when applications need shared file storage that resembles traditional file servers. Disk Storage is closely tied to virtual machines and should be selected when the requirement is storage for VM operating systems or application data disks.

Redundancy is another key exam area. Locally redundant storage replicates data within a single datacenter. Zone-redundant storage replicates across availability zones in a region. Geo-redundant storage adds replication to a secondary region. The exam may ask which option provides the highest resilience or supports regional disaster recovery. Your answer should depend on the stated business need, especially around availability and geographic resilience.

Migration basics can appear through services such as Azure Migrate, which helps assess and migrate on-premises workloads to Azure. At the fundamentals level, remember its purpose rather than technical migration steps. If the business wants to discover, assess, and plan migration of servers or workloads, Azure Migrate is a likely answer.

Exam Tip: Watch for the phrase “unstructured data.” That usually points to Blob Storage. If the scenario says “shared file access” or “file shares,” Azure Files is usually the intended service.

A common trap is choosing the most resilient storage redundancy option even when the requirement does not justify it. The exam tests fit-for-purpose thinking. Another trap is mixing up disks with file shares. VM disks are not the same as Azure Files, even though both store data.

Section 4.5: Describe Azure architecture and services - identity, access, and Microsoft Entra ID fundamentals

Identity is central to Azure architecture because access to resources depends on authentication and authorization. For AZ-900, the most important service to know is Microsoft Entra ID, formerly Azure Active Directory. Microsoft Entra ID is Azure’s cloud-based identity and access management service. It supports user sign-in, application access, and identity-based security capabilities across cloud and hybrid environments.

The exam commonly distinguishes authentication from authorization. Authentication verifies who a user is. Authorization determines what that user is allowed to do. This distinction matters when evaluating answer choices involving identities, permissions, and access control. Role-Based Access Control, or RBAC, is the primary Azure mechanism for assigning permissions to users, groups, and identities at different scopes such as subscription, resource group, or resource level.

You should also recognize single sign-on and multifactor authentication. Single sign-on allows users to sign in once and access multiple applications. Multifactor authentication improves security by requiring more than one verification method. These capabilities are frequent exam targets because they represent core security benefits of cloud identity platforms.

Managed identities may also appear in service-related scenarios. They allow Azure resources to authenticate to other Azure services without storing credentials in code. At the AZ-900 level, remember the business value: reducing secret management and improving security.

Exam Tip: If a question asks how to control what a user can do in Azure, think RBAC. If it asks how to verify a user’s identity at sign-in, think authentication features such as Microsoft Entra ID and MFA.

A common trap is confusing Microsoft Entra ID with Windows Server Active Directory. They are related in identity purpose but not the same product or deployment model. Another trap is assuming authentication automatically grants permissions. It does not. A user can be successfully authenticated and still not be authorized to access a resource. That distinction is tested regularly.

Section 4.6: Describe Azure architecture and services - Azure solutions for databases, analytics, and AI overview

Although the core of this chapter is compute, networking, and storage, AZ-900 also expects broad familiarity with Azure solutions for data and AI. These questions are usually high level and test whether you can identify the type of service being described. Azure SQL Database is a fully managed relational database service. It is the right fit when the scenario involves structured relational data, SQL compatibility, and reduced database administration compared with self-managed database servers.

Azure Cosmos DB is a globally distributed database service designed for modern applications requiring low latency, flexible scale, and support for different data models. On the exam, phrases such as globally distributed, high throughput, or planet-scale often indicate Cosmos DB. For analytics, services such as Azure Synapse Analytics may appear as integrated analytics solutions for large-scale data processing, reporting, and insight generation.

AI-related fundamentals may reference Azure AI services, which provide prebuilt capabilities such as vision, speech, language, and document intelligence. The exam generally does not expect deep model-building knowledge. Instead, it tests whether you understand when to choose prebuilt AI capabilities versus general-purpose infrastructure. If a business wants to add speech recognition or image analysis without creating a custom machine learning platform, Azure AI services are usually the intended direction.

This area is especially prone to distractors because many Azure services overlap conceptually. Your goal is to identify the dominant requirement: relational database, globally distributed NoSQL-style data, analytics at scale, or prebuilt AI capability. Once you classify the workload, the correct answer becomes much easier to spot.

Exam Tip: If the scenario emphasizes structured tables and SQL, think Azure SQL Database. If it emphasizes global distribution and massive scale, think Azure Cosmos DB. If it emphasizes built-in AI APIs rather than building models from scratch, think Azure AI services.

A common trap is overcomplicating the scenario and choosing a more specialized service than necessary. AZ-900 rewards broad service recognition and business alignment. Focus on what the service is for, not on advanced implementation details beyond the exam scope.

Section 5.1: Describe Azure management and governance - cost management and pricing factors

Cost management is a core AZ-900 topic because cloud value depends on understanding what drives spending. Azure pricing is influenced by several factors, including resource type, usage or consumption, region, performance tier, storage amount, outbound data transfer, redundancy options, and licensing model. Some services are billed per second or per hour, some by transactions, and some by allocated capacity. The exam may present a scenario that sounds technical, but the real objective is to determine what would change the bill.

You should know the difference between Azure Pricing Calculator and Azure Cost Management. The Pricing Calculator is used before deployment to estimate expected costs. Azure Cost Management is used after or during deployment to analyze actual spending, set budgets, identify trends, and help optimize costs. This distinction is a favorite exam trap. If the question asks to forecast a planned migration, think calculator. If it asks to review current monthly charges by subscription or resource group, think Cost Management.

Reservations and savings options can also appear. If a company has predictable long-term workloads, reserving capacity can reduce costs compared with pure pay-as-you-go pricing. Spot pricing may reduce costs for interruptible workloads, but it is not suited to stable production needs. Free services, trial credits, and spending limits may show up as distractors as well. Read carefully for whether the organization wants lower cost, predictable billing, or protection against overuse.

• Pricing factors include compute time, storage consumed, network egress, service tier, and region.
• Resource tags can help organize cost reporting and chargeback.
• Budgets in Cost Management help track spending against thresholds.
• Total cost can change based on scaling choices and redundancy selections.

Exam Tip: If a question asks how to “analyze current spending” or “identify cost trends,” the answer is usually Azure Cost Management. If it asks how to “estimate the cost before creating resources,” the answer is Azure Pricing Calculator.

A common trap is confusing cost control with governance enforcement. Cost Management helps you understand and optimize spend, but it does not itself enforce naming standards or location restrictions. Another trap is forgetting that deploying the same resource in different regions may result in different pricing. For exam success, translate the scenario into a billing driver: usage, tier, region, or commitment term. Once you identify the driver, the right answer becomes much easier to spot.

Section 5.2: Describe Azure management and governance - Service Level Agreements and service lifecycle

Service Level Agreements, or SLAs, define Microsoft’s commitment for uptime and connectivity for many Azure services. On AZ-900, you are not expected to memorize every percentage for every service, but you should understand the concept of uptime guarantees, how composite SLAs work, and why architecture choices affect availability. If multiple Azure components are used together in a solution, the overall availability can be lower than the SLA of the best individual service. This is because each dependency can affect total service availability.

The exam may ask about designing for higher availability. The key principle is that adding redundancy across availability zones or regions can improve resiliency, whereas relying on a single instance may provide a lower SLA or no SLA at all in some cases. You should also know that financially backed SLAs provide service credits if Microsoft does not meet the stated commitment, but they do not eliminate the need for customers to design appropriately.

Another important topic is the service lifecycle: generally available (GA), public preview, and private preview. GA services are production-ready and fully supported under standard support terms. Preview services are offered for evaluation and may have limited support, changing features, and weaker production guarantees. This is a classic exam trap. If the question asks which option is suitable for production workloads requiring full support and commitments, GA is the correct choice, not preview.

• SLA refers to expected uptime and service commitments.
• Architectural design affects actual solution availability.
• Preview features may be useful for testing but are not the default best answer for critical production systems.
• GA indicates general availability and broader production readiness.

Exam Tip: If the question includes words like “mission-critical,” “production,” or “fully supported,” avoid preview unless the scenario explicitly accepts experimental or limited-support features.

Students often miss questions here by overthinking. AZ-900 is testing fundamentals, not advanced architecture mathematics. If a prompt compares a single virtual machine with a distributed design, the exam is usually testing your understanding that redundancy improves reliability. Likewise, if a service is in preview, the safest fundamentals answer is that it is not the preferred option for workloads that require full production support. Keep your reasoning simple and aligned to service commitment language.

Section 5.3: Describe Azure management and governance - governance tools, Azure Policy, and resource locks

Governance in Azure is about making sure resources are deployed and managed according to organizational standards. For AZ-900, the most important governance tools include management groups, subscriptions, resource groups, tags, Azure Policy, and resource locks. You should know what each one does and, just as important, what it does not do. The exam often presents two plausible answers that differ only in whether they organize, authorize, enforce, or protect.

Azure Policy evaluates resources for compliance with defined rules. It can deny deployments, audit existing resources, apply settings in some cases, or enforce conditions such as allowed locations, required tags, or approved SKU sizes. This is different from role-based access control (RBAC), which determines who is allowed to do what. Policy is about the rules resources must follow; RBAC is about user permissions. This distinction is one of the most common exam traps in the governance domain.

Resource locks protect resources from accidental deletion or modification. A CanNotDelete lock prevents deletion, while a ReadOnly lock prevents changes and may also block actions that require write access. If a question asks how to stop administrators from accidentally deleting a production database, a resource lock is a strong answer. If it asks how to ensure all storage accounts are created only in approved regions, Azure Policy is the better answer.

• Management groups organize multiple subscriptions for governance at scale.
• Resource groups organize related resources for lifecycle management.
• Tags support organization, reporting, and cost tracking.
• Azure Policy enforces and evaluates standards.
• Resource locks prevent accidental deletion or modification.

Exam Tip: If the scenario says “require,” “enforce,” or “deny,” think Azure Policy. If it says “prevent accidental deletion,” think resource locks. If it says “control who can create,” think RBAC rather than Policy.

Another exam pattern is scope inheritance. Policies can be assigned at higher scopes such as management group or subscription so that they apply broadly. Candidates sometimes choose a narrower scope than necessary because they focus on one resource example in the scenario. Always ask yourself whether the requirement applies to one resource, one resource group, one subscription, or the whole organization. That scope clue often reveals the correct answer immediately.

Section 5.4: Describe Azure management and governance - compliance, privacy, and trust offerings

Compliance, privacy, and trust offerings help organizations evaluate whether Azure meets regulatory, legal, and internal governance needs. On the AZ-900 exam, you should understand the purpose of the Microsoft trust resources rather than memorize every certification. Microsoft provides documentation and reporting related to compliance standards, data protection commitments, and privacy practices. A key exam objective is knowing where customers can review this information and what these offerings are intended to communicate.

The Microsoft Service Trust Portal is a central resource for compliance documentation, audit reports, privacy details, and related trust materials. If the exam asks where an organization can access information about Microsoft compliance offerings or downloadable audit documents, the Service Trust Portal is the best match. Questions may also reference concepts such as data residency, privacy commitments, or industry standards. The important point is that Azure provides transparency and documentation to help customers assess suitability.

Another concept that appears is shared responsibility. Microsoft is responsible for the security and compliance of the cloud platform itself, while customers are responsible for compliance related to how they configure and use their services, manage identities, classify data, and control access. This links back to earlier course outcomes about shared responsibility and can be integrated into management and governance scenarios.

• Service Trust Portal provides access to compliance and trust documentation.
• Compliance offerings help organizations evaluate Azure against standards and regulations.
• Privacy information explains Microsoft commitments around handling customer data.
• Shared responsibility remains important even when Azure meets many certifications.

Exam Tip: If the prompt asks where to review Microsoft compliance reports or trust documentation, do not choose Azure Policy or Azure Monitor. The correct answer is usually the Service Trust Portal.

A common trap is assuming that Microsoft compliance certifications automatically make the customer compliant. They do not. Azure provides a compliant platform foundation and supporting documentation, but the customer must still configure services correctly and meet its own regulatory obligations. In exam terms, be careful with absolute statements such as “Azure makes the customer fully compliant.” Those options are usually wrong because they ignore the customer side of shared responsibility.

Section 5.5: Describe Azure management and governance - monitoring tools, Azure Monitor, and Service Health

Monitoring tools help administrators observe resource performance, collect telemetry, investigate issues, and respond to incidents. In AZ-900, the most important distinction is between Azure Monitor and Azure Service Health. Azure Monitor collects and analyzes metrics, logs, and alerts from Azure resources and applications. It is used for operational visibility: CPU usage, response times, diagnostic logs, alert rules, dashboards, and trends. If the question is about performance data or resource behavior, Azure Monitor is usually the right answer.

Azure Service Health is different. It communicates information about Azure service incidents, planned maintenance, and advisories that may affect your subscribed services and regions. It tells you about platform-level issues impacting your environment. A related service, Azure Status, gives broad public information about Azure outages, but Service Health is personalized to your tenant and resources. This difference appears often in fundamentals questions.

The exam may also reference log analysis and alerts. You should recognize that monitoring includes collecting data and notifying administrators when conditions are met. But do not confuse monitoring with governance. Azure Monitor does not enforce location restrictions or required tags. It observes and reports. Service Health does not measure your VM CPU usage. It reports Microsoft-side service events that may impact your resources.

• Azure Monitor tracks metrics, logs, alerts, and operational performance.
• Service Health shows incidents, maintenance, and advisories affecting your Azure services.
• Azure Status provides broad public service status information.
• Monitoring helps detect problems; governance helps prevent noncompliant deployment.

Exam Tip: If the question says “receive alerts when a VM exceeds CPU thresholds,” think Azure Monitor. If it says “find out whether a regional Azure outage is affecting your subscription,” think Service Health.

One common trap is choosing Service Health whenever the scenario mentions an issue. Ask whether the issue is inside your resource performance data or due to the Azure platform itself. Another trap is confusing Azure Advisor with Azure Monitor. Advisor makes recommendations; Monitor observes telemetry. Keep those roles separate and you will handle most exam questions in this area confidently.

Section 5.6: Describe Azure management and governance - management interfaces, portal, CLI, PowerShell, and Advisor

AZ-900 also tests the ways administrators interact with Azure. The main management interfaces are Azure Portal, Azure CLI, Azure PowerShell, and infrastructure deployment guidance such as ARM templates. Azure Portal is the browser-based graphical interface and is ideal for learning, ad hoc management, and visual administration. Azure CLI is a command-line tool suited for cross-platform scripting and automation. Azure PowerShell is task automation through PowerShell cmdlets, often favored in Windows-heavy administration environments or by users already comfortable with PowerShell workflows.

From an exam perspective, the goal is not to decide which tool is universally best, but which one best fits the scenario. If the prompt emphasizes graphical access through a web browser, choose Portal. If it emphasizes repeatable scripted administration from Linux, macOS, or Windows, Azure CLI is a strong fit. If the scenario specifically mentions PowerShell scripting or cmdlets, Azure PowerShell is the expected answer. For consistent deployments, templates and automation are usually preferred over manual portal steps.

Azure Advisor is another management service you must recognize. Advisor analyzes your deployed resources and provides recommendations related to reliability, security, performance, operational excellence, and cost. It does not directly enforce policy and does not replace monitoring. It is a recommendation engine that helps improve Azure environments based on best practices.

• Azure Portal is web-based and user-friendly for interactive management.
• Azure CLI supports command-line administration and automation across platforms.
• Azure PowerShell uses cmdlets for scripting and management tasks.
• Azure Advisor provides personalized best-practice recommendations.
• Templates support repeatable, consistent deployments.

Exam Tip: Advisor recommends; Policy enforces; Monitor observes; Portal manages visually. This one-line comparison is extremely useful for eliminating distractors quickly.

As you consolidate all domain knowledge with mixed review drills, practice identifying the action word in each scenario: estimate, analyze, enforce, monitor, protect, review compliance, recommend, or automate. Those verbs map directly to the Azure service name. That exam-style reasoning is exactly what turns memorized definitions into correct answers under time pressure. If you can separate interfaces from governance services and recommendation tools from monitoring tools, you will be well prepared for this chapter’s objective and for the AZ-900 exam overall.

Section 6.1: Full mock exam blueprint mapped to all AZ-900 domains

A full mock exam is most useful when it mirrors the structure and thinking style of the real AZ-900 exam. Do not treat it as a random bundle of Azure facts. Instead, map your performance to the three official domains tested in Azure Fundamentals. The first domain, Describe cloud concepts, covers core ideas such as cloud computing benefits, shared responsibility, cloud models, and consumption-based pricing logic. The second domain, Describe Azure architecture and services, includes core architectural components like regions, availability zones, resources, subscriptions, and resource groups, as well as major service families across compute, networking, and storage. The third domain, Describe Azure management and governance, includes cost management, compliance, identity support concepts at the fundamentals level, monitoring, and governance tools.

When using Mock Exam Part 1 and Mock Exam Part 2, create a simple tracking grid. Label each question by domain and by subtopic. This allows you to identify whether your errors are concentrated in one area or spread across the blueprint. If your misses are scattered, your issue may be pacing or reading discipline. If most misses cluster in management and governance, your content review should focus on tools like Microsoft Cost Management, Azure Policy, Service Level Agreements, and monitoring-related concepts.

Exam Tip: AZ-900 often tests whether you can distinguish categories. For example, a question may not require deep technical deployment knowledge; it may simply require recognizing whether something is a compute service, a governance tool, or a networking feature. Blueprint mapping helps you train that categorization skill.

A good blueprint-based review also highlights exam weighting in a practical way. Even if exact percentages shift over time, Azure architecture and services usually feel broad because they include many named services and structural concepts. Candidates often underprepare for cloud concepts because the content looks simple, but those questions can be deceptively easy to miss when wording is subtle. Likewise, governance items may seem straightforward, yet they contain many near-neighbor terms that invite confusion.

As you review your mock performance, ask what the exam was testing beneath the surface. Was the item really about knowing a service name, or about understanding why a managed service reduces operational overhead? Was it testing geography concepts, or understanding that regions and availability zones solve different availability concerns? This blueprint mindset turns each practice session into targeted exam preparation rather than generic repetition.

Section 6.2: Timed practice strategy for mixed difficulty question sets

The AZ-900 exam is not just a knowledge check; it is a decision-making exercise under time pressure. A smart timed practice strategy helps you avoid spending too long on tricky wording while protecting easy points. In mixed difficulty sets, the first rule is to maintain forward momentum. If a question is clearly within your knowledge base, answer it decisively. If it feels ambiguous after a careful first read, mark it mentally for review and move on. Fundamentals exams reward broad consistency more than heroic effort on a few uncertain items.

During timed practice, divide your work into three passes. On the first pass, answer all straightforward items. These are questions where you immediately recognize the concept and can eliminate distractors confidently. On the second pass, revisit medium-difficulty items and compare the remaining options using category logic: managed versus unmanaged, IaaS versus PaaS versus SaaS, governance versus monitoring, or storage versus compute. On the third pass, handle only the most uncertain items and choose the best answer based on exact wording rather than instinct.

Exam Tip: If two options both seem technically plausible, the correct AZ-900 answer is often the one that best matches the specific business need in the prompt, such as minimizing administration, improving scalability, or enforcing governance consistently.

Mixed difficulty practice matters because the exam jumps rapidly between simple recall and reasoning-based interpretation. One item may ask about the benefit of elasticity, while the next may require distinguishing Azure Advisor from Azure Monitor or identifying the function of a resource group. Candidates who rely only on untimed study often know the content but hesitate too long when the format changes. Timed practice trains cognitive switching, which is a real exam skill.

Avoid two common pacing traps. First, do not reread every question excessively. Overreading often creates doubt rather than clarity. Second, do not assume a longer question is harder. Some scenario-based items are actually easier because they contain clues about cost, management burden, or availability needs. Your timed strategy should therefore focus on identifying signal words quickly and using elimination logic with discipline. The goal is controlled efficiency, not rushed guessing.

Section 6.3: Review framework for incorrect answers and distractor patterns

Your score improves after the mock exam, not during it. The review process is where weak spot analysis becomes meaningful. For every incorrect answer, avoid the shallow habit of simply reading the explanation and moving on. Instead, classify the error. Useful categories include: concept misunderstanding, service confusion, terminology confusion, missed keyword, overthinking, and weak elimination. This framework helps you determine whether the problem is lack of knowledge or poor exam technique.

Distractor patterns in AZ-900 are usually predictable. A common trap is pairing a correct-sounding Azure term with the wrong responsibility or use case. Another is presenting multiple real services where only one fits the exact requirement, such as low administration effort, compliance enforcement, or monitoring. Some distractors are broad tools placed against narrower services, tempting candidates who recognize the name but not the purpose. Others reverse related concepts, such as mixing up availability zones with regions or cost estimation tools with governance tools.

Exam Tip: When reviewing a miss, ask two questions: “Why is the correct option right?” and “Why was my chosen option tempting?” The second question is what reveals your distractor vulnerability.

An effective review note should include four parts: the tested domain, the precise concept, the keyword that should have guided you, and the rule you will use next time. For example, your note may say that a question belonged to governance, tested policy enforcement, used the clue “ensure compliance,” and should lead you toward governance tooling rather than monitoring. This level of specificity makes review reusable.

Also look for recurring distractor behavior in your own choices. If you often choose the most technical-looking answer, you may be overcomplicating a fundamentals exam. If you repeatedly miss questions that ask for the “best” or “most cost-effective” option, you may be ignoring the business requirement and focusing too narrowly on function. Your weak spot analysis should uncover these habits. Once identified, they become easier to correct before exam day.

Section 6.4: Final revision by domain - Describe cloud concepts

In the final review stage, the cloud concepts domain deserves more attention than many candidates expect. Because the ideas seem familiar, people often review them casually and then lose points on wording. You should be able to explain public, private, and hybrid cloud models; compare IaaS, PaaS, and SaaS; describe the shared responsibility model; and distinguish CapEx from OpEx. These are foundational topics, and the exam expects clean conceptual separation.

Pay special attention to benefits and tradeoffs. High availability, scalability, elasticity, agility, fault tolerance, and disaster recovery are related but not interchangeable. AZ-900 may test whether you can identify which concept best fits a described situation. Scalability refers to the ability to handle increased workload; elasticity emphasizes automatic or rapid adjustment to demand; high availability focuses on service uptime; fault tolerance addresses continued operation despite failures. The exam often rewards precise vocabulary rather than broad familiarity.

Exam Tip: If a question describes reducing upfront hardware spending and paying for resources as needed, think OpEx and cloud consumption model. If it emphasizes control over infrastructure and operating systems, think IaaS. If it emphasizes managed application hosting with reduced administration, think PaaS.

The shared responsibility model is another frequent trap. Microsoft does not assume every security and management responsibility simply because a workload is in Azure. Responsibilities vary by service model. In SaaS, Microsoft handles more of the stack; in IaaS, the customer still manages more elements such as the guest operating system and some configuration responsibilities. Review this carefully, because exam items may frame it indirectly through maintenance, patching, or infrastructure control.

Finally, remember that cloud concepts questions often appear simple but are designed to verify whether you understand why organizations adopt cloud services. Cost flexibility, speed of deployment, reduced hardware management, and global reach are all core business drivers. When choosing the best answer, match the business goal to the cloud concept rather than selecting the most advanced-sounding technology term.

Section 6.5: Final revision by domain - Describe Azure architecture and services

This is typically the broadest review domain because it spans both structural Azure concepts and major service families. Start with core architectural components: regions, region pairs at a basic awareness level, availability zones, subscriptions, management groups at a fundamentals recognition level, resource groups, and resources. The exam often checks whether you understand the relationship among these. A resource belongs to a resource group, and subscriptions are used for billing and management boundaries. Resource groups are not the same as regions, and availability zones are not the same as geographies.

Then move through services by category. For compute, know the positioning of virtual machines, containers, Azure Kubernetes Service at a basic level, virtual desktops, and serverless options such as Azure Functions. For networking, review virtual networks, VPN Gateway, ExpressRoute at a high level, load balancing basics, and content delivery concepts. For storage, know the purpose of Blob storage, file storage, disk storage, archive versus hot access ideas, and redundancy concepts at an introductory level.

Exam Tip: Many wrong answers in this domain come from choosing a real Azure service that works technically, but not in the simplest or most appropriate way for the stated requirement. AZ-900 usually favors the best-fit foundational answer, especially when the requirement mentions managed service, scale, or minimal administration.

Another common trap is confusing identity-related Azure features with general infrastructure services. Even when a term sounds familiar, pause and ask what category it belongs to. Is it compute, storage, networking, organization, or identity support? This category-first method reduces errors quickly.

Your final revision here should be comparative, not isolated. Do not memorize services as separate flashcards only. Compare them. Ask how VMs differ from serverless compute, how Blob storage differs from managed disks, and how availability zones differ from load balancing. The exam often tests these distinctions more than deep implementation details. If you can classify the service, identify its primary purpose, and reject neighboring distractors, you are prepared for this domain.

Section 6.6: Final revision by domain - Describe Azure management and governance

The final domain combines practical business control with Azure-specific management awareness. Candidates sometimes underestimate it because it appears less technical, but that is exactly why wording matters. Your review should cover cost management concepts, governance tools, compliance awareness, and monitoring basics. You should recognize tools and concepts such as Azure Policy, resource locks, tags, Microsoft Cost Management, the pricing calculator, the Total Cost of Ownership calculator, Service Level Agreements, and Azure Monitor at a fundamentals level.

A major exam distinction is between planning cost, controlling cost, and observing operations. Pricing calculators help estimate expected cost before deployment. Total Cost of Ownership comparison tools help evaluate migration economics. Cost Management supports ongoing visibility and control. Azure Monitor is about collecting and analyzing telemetry, not enforcing governance policy. Azure Policy helps apply or evaluate compliance rules. If you blur these functions together, distractors become very effective.

Exam Tip: Watch for verbs in the question stem. “Estimate” points toward pricing tools. “Analyze ongoing spend” suggests cost management. “Enforce compliance” suggests policy. “Track metrics and logs” suggests monitoring.

Another common review point is governance scope. Tags help with organization and reporting, but they do not replace policy enforcement. Resource locks help prevent accidental deletion or modification, but they are not compliance engines. Service Level Agreements describe expected service uptime commitments, but they do not guarantee that your architecture is automatically resilient. These distinctions matter because AZ-900 frequently tests the purpose of a tool rather than its internal mechanics.

As part of your exam day checklist, do a final rapid review of verbs and tool roles in this domain. Many last-minute score gains come from sharpening these associations. If you can quickly map a requirement to estimate, monitor, govern, organize, or protect, you will eliminate distractors more confidently and finish the exam with fewer second guesses.