AI Certification Exam Prep — Beginner
Pass AZ-900 with realistic practice and clear answer breakdowns.
This course blueprint is designed for learners preparing for the Microsoft AZ-900 Azure Fundamentals certification exam. It is built specifically for beginners who may have no prior certification experience but want a clear, efficient way to study the official exam objectives. The course uses a structured 6-chapter format and focuses on realistic exam-style practice, domain coverage, and detailed answer reasoning so learners can understand not only what the correct answer is, but why it is correct.
The AZ-900 exam is one of Microsoft’s most popular entry-level certifications because it validates foundational cloud knowledge, Azure service awareness, and an understanding of management and governance concepts in Azure. This course supports that goal by aligning directly to the official domains: Describe cloud concepts; Describe Azure architecture and services; and Describe Azure management and governance.
The first chapter introduces the exam itself. Learners review the registration process, scheduling options, question formats, scoring expectations, and practical study strategies. This early orientation helps reduce anxiety and ensures that students know how to approach the test before diving into technical content.
Chapters 2 through 5 map directly to the official AZ-900 objectives. The course begins with cloud fundamentals, including cloud models, service types, shared responsibility, and pricing basics. It then moves into Azure architecture and services, covering core architectural components, compute, networking, storage, databases, and identity. Finally, it addresses management and governance topics such as Azure tools, monitoring, policy, compliance, pricing calculators, service level agreements, and cost control concepts.
Many AZ-900 candidates understand basic definitions but still struggle with how Microsoft frames questions on the real exam. That is where a well-designed practice test bank becomes valuable. This course focuses on helping learners identify keywords, distinguish between similar Azure services, eliminate distractors, and connect each question back to a specific exam objective. That process improves both recall and exam judgment.
Because the AZ-900 exam is broad rather than deeply technical, success often depends on recognizing the best answer in context. This course helps learners build that skill through repeated exposure to scenario-based questions and explanation-driven review. Instead of memorizing isolated facts, students learn how to think in the style of the exam.
The 6-chapter structure is ideal for step-by-step preparation. Chapters are organized so that each one has milestones and internal sections that can be followed in sequence. This makes it easier for learners to study in short sessions, revisit weaker domains, and measure progress as they move through the course.
The final chapter includes a full mock exam and final review strategy. This is where learners bring everything together, test readiness across all domains, analyze weak spots, and prepare for exam day with a clear checklist. By the end of the course, students should feel more comfortable with Microsoft’s terminology, Azure service positioning, and the overall pacing required for the AZ-900 exam.
If you are starting your Azure certification journey, this course provides a practical and approachable path forward. You can Register free to begin learning or browse all courses to explore more certification prep options on Edu AI.
This course is intended for individuals preparing for the Microsoft Azure Fundamentals exam, including students, career changers, entry-level IT professionals, business stakeholders, and technical learners who want a solid cloud foundation. If your goal is to pass AZ-900 while building a clear understanding of Azure basics, this exam-prep blueprint is designed for you.
Microsoft Certified Trainer and Azure Solutions Architect
Daniel Mercer is a Microsoft Certified Trainer with extensive experience teaching Azure Fundamentals and role-based Microsoft certification courses. He has helped beginner learners prepare for Microsoft exams through structured objective mapping, realistic question practice, and practical exam strategies.
Welcome to your starting point for Azure Fundamentals success. The AZ-900 exam is Microsoft’s entry-level certification for candidates who need to understand cloud principles and the basics of Microsoft Azure services, pricing, governance, and support concepts. This chapter is designed to help you get oriented before you begin drilling practice questions. Strong candidates do not simply memorize facts; they understand the exam blueprint, recognize how Microsoft frames beginner-level scenarios, and follow a study plan that matches the tested objective areas.
The AZ-900 exam does not expect deep hands-on engineering expertise, but it does expect clean conceptual judgment. You should be able to distinguish cloud models, identify major Azure service categories, and understand governance tools such as policies, locks, and cost controls. Microsoft often tests whether you can match a need to the correct service category, not whether you can deploy it from memory. That means your preparation should focus on definitions, use cases, comparison skills, and elimination strategy.
This chapter covers the practical orientation topics that many beginners skip: the official exam blueprint, registration and delivery choices, scoring and question styles, and a realistic study plan. These topics matter because candidates who understand the test mechanics usually perform better under time pressure. If you know what the exam is really measuring, you are less likely to overstudy low-value details and more likely to recognize traps built into answer choices.
Across this chapter, keep one core principle in mind: AZ-900 rewards broad understanding over technical depth. The exam objective areas align to three major domains you will revisit throughout the course: cloud concepts; Azure architecture and services; and Azure management and governance. The best study approach is to build a simple framework for each domain, then reinforce it with repeated exposure to exam-style wording. That is exactly how this course and practice bank should be used.
Exam Tip: Early success on AZ-900 comes from clarity, not complexity. If an answer choice sounds highly technical but the question asks about a basic business or cloud concept, that choice is often a distractor. Microsoft wants you to know the right category, purpose, or principle.
By the end of this chapter, you should know what the AZ-900 exam covers, how it is delivered, how to plan your preparation, and how to approach the test with a structured beginner-friendly mindset. Treat this chapter as your roadmap. The students who pass efficiently are usually the ones who begin with orientation, then study in alignment with the official objectives instead of studying Azure randomly.
Practice note for Understand the AZ-900 exam blueprint: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Learn registration, scheduling, and delivery options: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Review scoring, question types, and passing strategy: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Build a beginner-friendly study plan: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
The AZ-900 exam validates foundational knowledge of cloud services and how those services are provided with Microsoft Azure. It is intended for beginners, career changers, students, sales professionals, project stakeholders, and technical learners who need a broad understanding of Azure without performing advanced administration or development tasks. This audience point matters because it explains the exam’s style: Microsoft is not testing command-line syntax or architectural specialization. Instead, it tests whether you can identify the right concept, service family, pricing idea, or governance tool for a basic scenario.
The official Microsoft objective areas are typically grouped into three broad domains. First, you must describe cloud concepts. This includes cloud computing models such as public, private, and hybrid cloud; service models such as IaaS, PaaS, and SaaS; shared responsibility concepts; and benefits like scalability, elasticity, reliability, high availability, and consumption-based pricing. Second, you must describe Azure architecture and services. That includes core architectural components, compute, networking, storage, databases, analytics awareness at a high level, and identity services. Third, you must describe Azure management and governance. This domain includes cost management, service-level agreements, monitoring, compliance, trust, security features, policy tools, and resource organization concepts.
What the exam tests in practice is your ability to classify information correctly. For example, if a question describes controlling access to resources, think identity and access management. If it describes enforcing organizational rules, think governance tools such as Azure Policy. If it describes paying only for what is used, think consumption-based pricing. This is why domain awareness is so important.
Common exam traps include confusing service categories, mixing governance with security, or assuming every Azure feature is fully managed. Another frequent mistake is choosing a technically powerful service when the question asks for the simplest conceptual fit. The correct answer is usually the one that best matches the stated requirement, not the one that seems most advanced.
Exam Tip: Memorize the objective domains in plain English. When you read a question, first ask yourself which domain it belongs to. That single step narrows the answer space and makes elimination far easier.
As you continue through this course, map every new topic back to one of these three domains. That habit mirrors the exam blueprint and builds a mental structure that helps you recall facts under pressure.
Before you worry about passing, make sure you understand the registration process and delivery options. AZ-900 is typically scheduled through Microsoft’s certification portal with an authorized exam delivery provider. You sign in with a Microsoft account, locate the AZ-900 exam, select your country or region, review pricing, and choose either a test center appointment or an online proctored exam if available in your location. This process sounds simple, but many candidates create unnecessary stress by waiting too long to schedule or by overlooking identification and environment requirements.
When choosing between a test center and online delivery, think practically. A test center may offer a more controlled environment and fewer technical uncertainties. Online testing offers convenience, but it usually requires strict room setup, webcam monitoring, reliable internet, system checks, and compliance with workspace rules. If your home environment is noisy or unpredictable, an in-person center may be the safer option.
Exam policies matter because policy mistakes can prevent you from testing even if you are academically prepared. Candidates should review check-in timing, required identification, rescheduling windows, cancellation rules, prohibited items, and conduct expectations. Online candidates should also verify software compatibility and complete any required system test ahead of time. Last-minute technical issues are not a study problem, but they can still ruin an exam attempt.
A common trap is assuming scheduling details never change. Certification vendors may update policies, appointment availability, and regional delivery options. Always confirm the current rules from the official Microsoft certification page and the delivery provider before exam day. Another trap is scheduling too early based on enthusiasm rather than readiness. It is better to book with a plan than to gamble on rushed preparation.
Exam Tip: Schedule your exam with a target date that creates urgency but still allows two full review cycles. For most beginners, that means enough time to learn the domains once, then revisit weak areas with practice tests before the appointment.
Good exam preparation includes logistical readiness. Know where you are testing, what time to arrive or check in, what identification to bring, and what behaviors are not allowed. Reducing uncertainty outside the content helps preserve mental energy for the actual questions.
AZ-900 is a fundamentals exam, but you should not mistake “fundamentals” for “easy.” The exam measures breadth across several domains and often uses short business-oriented scenarios. Candidates typically encounter a set of mixed question formats rather than one single style. These may include standard multiple-choice items, multiple-select items, matching or drag-and-drop style interactions, and statement-based formats where you evaluate whether listed claims are correct. Microsoft can adjust exam presentation over time, so treat any exact number of questions or precise timing details as subject to change. What stays consistent is the need for careful reading and efficient pacing.
The scoring model is scaled, and the commonly cited passing mark is 700 on a scale of 100 to 1000. Do not overinterpret the scale as a simple percentage. Not every question carries the same weight in the way candidates imagine, and the exam may include different forms. Your goal is not to calculate scoring mechanics during the exam. Your goal is to answer consistently well across all domains. A stronger performance in one area may help offset weaker performance elsewhere, but relying on that is risky because objective balance can vary.
Common question styles in AZ-900 test recognition, differentiation, and mapping. You may need to identify which cloud model fits a description, which Azure service category meets a basic need, or which governance feature enforces a policy. The trap answers are often plausible because they belong to the same broad family. For example, two services may both relate to storage, or two tools may both relate to security, but only one fits the stated requirement precisely.
The best answering strategy is to underline the keyword mentally: identify, describe, minimize cost, enforce rules, authenticate users, monitor performance, or guarantee uptime. Those verbs point to the correct category. Then eliminate answers that are too narrow, too advanced, or unrelated to the domain being tested.
Exam Tip: If two answers both sound correct, compare them against the exact scope of the requirement. AZ-900 often rewards the more general foundational answer over the specialized implementation detail.
Finally, pacing matters. Do not get stuck on one item. Mark difficult questions mentally, answer your best current option, and move forward. Fundamentals exams reward steady, disciplined progress more than perfectionism.
A practice test bank is one of the most effective tools in AZ-900 preparation, but only if you use it correctly. Many beginners misuse practice questions as a memorization shortcut. That approach creates false confidence because the real exam does not reward recognition of repeated wording alone. Instead, you should use the test bank as a diagnostic and reinforcement system. Each wrong answer should teach you something about the domain, the service category, or the wording pattern that misled you.
Begin with untimed domain-focused sets rather than full random exams. If you are learning cloud concepts, answer a block of questions only from that domain and review each explanation immediately. This helps you build your mental map. Once you are more comfortable, shift to mixed sets to simulate the real exam experience where topics are interleaved. In the final stage, complete full-length timed practice sessions and analyze the results by domain, not just by total score.
Your review process should be structured. For every missed item, determine whether the problem was one of knowledge, vocabulary, attention, or overthinking. Did you confuse IaaS with PaaS? Did you mix up Azure Policy with a security service? Did you miss a keyword such as “govern,” “monitor,” or “pay only for what you use”? This kind of error logging turns practice into progress.
Common traps in practice bank usage include repeating only favorite questions, ignoring explanations for correct guesses, and chasing a score target without mastering weak topics. Another major trap is studying answer patterns instead of learning why alternatives are wrong. On the real exam, distractors are designed to be tempting, so learning elimination is as important as learning definitions.
Exam Tip: Review correct answers too. If you guessed correctly, treat it as unstable knowledge until you can explain why the other options were wrong. That is exam-level understanding.
The strongest preparation rhythm is simple: learn a topic, answer practice items on that topic, review explanations deeply, summarize errors, and retest later. Used this way, a 200-plus question bank becomes a full readiness system rather than just a score generator.
Your study plan should mirror the official domains because that is how the exam is designed. Start with cloud concepts. This domain builds the foundation for everything else. Learn the cloud deployment models, the service models, the meaning of shared responsibility, and the business benefits of cloud computing such as agility, elasticity, scalability, reliability, disaster recovery support, and consumption-based pricing. These topics appear simple, but the exam often tests precise distinctions. For example, elasticity and scalability are related but not identical in meaning.
Next, move into Azure architecture and services. This is usually the largest content area for beginners because it introduces the major building blocks of Azure. Focus on core architectural components such as regions, region pairs, availability zones, subscriptions, resource groups, and management groups. Then learn the high-level purpose of compute services, networking components, storage options, databases, and identity services like Microsoft Entra ID. At AZ-900 level, you are not expected to master deployment steps. You are expected to know what a service is generally used for and how it differs from nearby alternatives.
Then study Azure management and governance. This domain includes cost management, SLAs, monitoring, compliance, privacy and trust ideas, security capabilities, and governance tools such as Azure Policy, resource locks, and tagging. This area often trips up beginners because several tools seem similar. Remember the exam usually tests purpose: monitoring observes, policy enforces rules, locks prevent certain changes, and cost tools help control spending.
A beginner-friendly schedule usually works best in phases. In week one, learn cloud concepts and complete small practice sets. In week two, cover Azure architecture and services in chunks. In week three, learn management and governance. In week four, perform mixed review, take a mock exam, and revisit weak domains. If you have more time, slow the pace and add repetition rather than extra complexity.
Exam Tip: Do not try to memorize Azure by product list alone. Organize services by function: compute, network, storage, database, identity, governance, monitoring, and cost. Functional grouping matches how exam questions are written.
Domain-based planning gives you coverage, confidence, and better recall. It also prevents a common beginner error: spending too much time on interesting services while neglecting governance and pricing concepts that appear regularly on the exam.
Success on AZ-900 is not only about what you know. It is also about how calmly and efficiently you apply that knowledge under exam conditions. Your mindset should be steady and businesslike. This is a fundamentals exam, so trust the core concepts you studied. Many candidates lose points by second-guessing a basic correct answer because a more technical option looks impressive. If the requirement is foundational, the correct answer is usually foundational too.
Pacing starts before exam day. During practice, build the habit of answering in passes. On the first pass, answer questions you know with confidence. On the second, work through the ones that require comparison or elimination. Avoid letting one difficult item consume disproportionate time. If you can eliminate two options, choose the best remaining answer and move on. Time pressure creates mistakes, and fundamentals questions are often easier to solve when you stay relaxed.
Your review habits should be active, not passive. In the final days before the exam, avoid cramming random facts. Instead, review your error log, your domain summaries, and the distinctions you tend to confuse. Revisit high-yield categories such as cloud models, Azure service types, identity basics, governance tools, SLAs, pricing concepts, and monitoring terminology. Short repeated sessions are more effective than a single overloaded marathon.
If your exam attempt does not go as planned, use the result professionally. Review the score report by domain, identify weak areas, and rebuild with targeted practice. A retake plan should not be emotional or random. It should be domain-led: strengthen the lowest objective area first, then retest with mixed sets and another mock exam. Many candidates pass on a later attempt because they finally shift from broad rereading to focused correction.
Exam Tip: Confidence on test day comes from pattern recognition. If you have practiced enough to recognize the difference between pricing, governance, monitoring, identity, and service-category questions, you will make faster and cleaner decisions.
Approach the AZ-900 as a structured milestone, not a mystery. With sound pacing, disciplined review, and a clear retake plan if needed, you can turn this exam into an achievable first certification win.
1. A candidate is beginning AZ-900 preparation and wants to study efficiently. Which action should the candidate take FIRST to align preparation with what Microsoft actually measures on the exam?
2. A student asks what kind of knowledge the AZ-900 exam is most likely to reward. Which response is MOST accurate?
3. A company employee plans to take AZ-900 from home. Before exam day, which preparation step is MOST appropriate based on standard exam logistics and delivery expectations?
4. During a practice exam, a question asks for the BEST answer to a basic business need, but one option contains highly technical implementation detail. Based on AZ-900 test strategy, how should the candidate approach this?
5. A beginner has two weeks to prepare for AZ-900 and wants a realistic study plan. Which approach is MOST appropriate?
This chapter maps directly to one of the most testable AZ-900 domains: cloud concepts. Microsoft expects candidates to recognize the language of cloud computing, distinguish service types and deployment models, and apply foundational ideas such as shared responsibility and consumption-based pricing. These questions are usually not mathematically difficult, but they do test whether you can separate similar-looking terms under exam pressure. That is why this chapter emphasizes both concept mastery and exam pattern recognition.
At this stage of the course, your goal is not to become an architect. Your goal is to think like an AZ-900 candidate who can identify the best answer from several plausible choices. The exam often presents short business scenarios and asks which cloud model, service type, or benefit best fits the situation. A beginner trap is to answer based on general tech intuition instead of the exact Microsoft definition. In AZ-900, definitions matter. For example, scalability and elasticity are related, but they are not identical. Reliability and availability also overlap, yet they test different ideas.
The lessons in this chapter develop in a sequence that mirrors how Microsoft frames the objective. First, you will master core cloud computing ideas. Next, you will differentiate cloud service types: IaaS, PaaS, and SaaS. Then you will compare deployment models: public, private, and hybrid cloud. Finally, you will translate all of that into exam-readiness through practical reasoning and answer selection patterns.
As you read, focus on three recurring exam tasks. First, identify what part of the stack the customer still manages. This quickly separates IaaS from PaaS and SaaS. Second, identify whether the question is asking about technical capability or business outcome. For instance, elasticity is a technical response to changing demand, while predictability often refers to expected performance and cost. Third, watch for keywords such as shared, on-demand, pay-as-you-go, hybrid, and fully managed. These often point directly to the correct concept.
Exam Tip: On AZ-900, many wrong answers are not absurd; they are partially true. Your job is to choose the most precise answer for the exact wording of the prompt. If two answers seem correct, look for the one that matches Microsoft terminology most closely.
By the end of this chapter, you should be able to explain why organizations adopt cloud services, compare cloud benefits, classify common service models, evaluate deployment scenarios, and avoid common traps around responsibility and pricing. Those are essential skills not only for passing this chapter’s practice items, but also for building confidence across the broader Azure Fundamentals exam.
Practice note for Master core cloud computing ideas: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Differentiate cloud service types: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Compare cloud deployment models: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Practice cloud concepts questions: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Master core cloud computing ideas: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Differentiate cloud service types: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Cloud computing is the delivery of computing services over the internet. These services can include servers, storage, databases, networking, analytics, and software. Instead of buying, installing, and maintaining all infrastructure in a local datacenter, an organization can access resources on demand from a cloud provider such as Microsoft Azure. For AZ-900, this definition is foundational. The exam is not asking for deep engineering detail here; it is testing whether you understand cloud as a service delivery model rather than merely a location where servers sit.
Organizations use cloud computing for several practical reasons. They may want to reduce upfront capital expense, deploy services faster, scale resources when demand changes, improve business continuity, or expand globally without building datacenters in every region. Cloud computing also helps teams move from long procurement cycles to rapid provisioning. In exam wording, this often appears as the ability to provision resources in minutes rather than weeks or months.
A frequent exam trap is confusing cloud computing with virtualization. Virtualization is a technology that can be used in cloud environments, but it is not the same thing as cloud computing. Cloud computing includes characteristics such as on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. If a question emphasizes internet-based access, provider-managed infrastructure, and usage-based billing, think cloud computing.
Another trap is assuming cloud always means eliminating all local infrastructure. That is not true. Many organizations adopt cloud gradually or use hybrid models. The exam may describe a company keeping some systems on-premises for regulatory or legacy reasons while using Azure for other workloads. That is still cloud adoption.
Exam Tip: When a scenario emphasizes speed of deployment, avoiding hardware purchases, and accessing IT resources as needed, the underlying concept being tested is usually cloud computing itself, not a specific Azure service.
What the exam tests most often in this area:
When identifying the correct answer, ask yourself: is the question describing a flexible service model delivered over the internet, with provider-managed infrastructure and customer-selected resources? If yes, cloud computing is the target concept.
This AZ-900 objective is heavily definition-driven. Microsoft expects you to know the major benefits of cloud services and tell them apart. High availability refers to designing services so they remain accessible even when failures occur. Reliability means a system can recover from failures and continue to function. These terms are related, but on the exam, availability emphasizes uptime, while reliability emphasizes resilience and recovery.
Scalability means increasing or decreasing resources to meet demand. This can be vertical, such as adding CPU or memory to a server, or horizontal, such as adding more server instances. Elasticity goes a step further: the system can automatically or dynamically adjust resources as demand rises or falls. In simple exam language, scalability is the capability to grow; elasticity is the ability to grow and shrink more fluidly with usage patterns.
Predictability refers to being able to forecast performance and cost. Cloud platforms provide tools and standardized service behaviors that make planning more consistent than in many traditional environments. If a question mentions budgeting, expected performance, or known deployment patterns, predictability may be the intended answer. Security in the cloud includes provider-side protections as well as customer-side configuration responsibilities. Azure offers physical security, infrastructure protections, and many security services, but customers still secure identities, data, configurations, and access controls depending on the service model.
A common trap is choosing security as the answer every time a question asks for a cloud benefit. Security is important, but not every scenario is about security. If the wording focuses on uptime, select high availability. If it focuses on quick response to demand spikes, think elasticity. If it focuses on the ability to add capacity, think scalability.
Exam Tip: Memorize paired distinctions: availability versus reliability, and scalability versus elasticity. These pairs are among the easiest places to lose points due to vague reading.
What the exam tests for this topic:
To identify the correct answer, locate the dominant keyword in the scenario: uptime, recovery, growth, automatic adjustment, forecasting, or protection. Then map that keyword to the cloud benefit that best fits.
One of the most important beginner skills for AZ-900 is differentiating IaaS, PaaS, and SaaS. These service types are tested repeatedly because they reveal whether you understand who manages what. Infrastructure as a Service, or IaaS, gives the customer the most control among the three. The provider manages the physical datacenter, networking foundation, and hardware, while the customer typically manages the operating system, applications, data, and many configurations. Virtual machines are the classic IaaS example.
Platform as a Service, or PaaS, reduces management overhead. The provider manages the underlying infrastructure, operating system, and runtime environment, while the customer focuses mainly on the application and data. This is ideal when developers want to build and deploy applications without managing servers. Many web app hosting and managed database offerings fit PaaS-style thinking.
Software as a Service, or SaaS, is the most fully managed model. The provider delivers a complete application over the internet, and the customer simply uses it. Microsoft 365 is a familiar example. In SaaS, customers still manage some things, such as user access, data handling, and configuration options, but they do not manage the application platform or infrastructure itself.
The exam often compares these models by asking which one requires the least administration, which offers the most control, or which best suits a company that wants to develop apps without managing operating systems. A common trap is assuming PaaS means no responsibility at all. That is false. Customers still manage their apps and data. Another trap is treating every hosted application as SaaS; if customers deploy their own code to a managed platform, that is usually PaaS, not SaaS.
Exam Tip: Use the “who manages the OS?” shortcut. If the customer manages the operating system, think IaaS. If the provider manages the OS but the customer deploys applications, think PaaS. If the customer mainly consumes a finished application, think SaaS.
AZ-900 style comparison logic:
If two options look similar, identify the highest layer the customer still controls. That usually reveals the correct service model quickly and accurately.
AZ-900 also expects you to compare where cloud resources are deployed and how they are operated. Public cloud refers to services offered over the internet and available to multiple customers, with the cloud provider owning and managing the infrastructure. Azure is a public cloud platform. Customers consume shared provider resources logically separated from other tenants. For exam purposes, public cloud is associated with rapid deployment, broad scalability, and minimal infrastructure ownership by the customer.
Private cloud refers to cloud resources used exclusively by a single organization. The infrastructure may be located on-premises or hosted by a third party, but it is dedicated to one organization. Private cloud can provide greater control and may be chosen for regulatory, security, or customization reasons. However, it generally requires more cost and management effort than public cloud.
Hybrid cloud combines public cloud and private or on-premises environments, allowing data and applications to move between them as needed. This is a very common exam scenario. Organizations may keep sensitive systems locally while bursting other workloads to Azure, or they may migrate in phases rather than all at once. If a question mentions connecting existing datacenter assets to cloud services, extending resources, or supporting regulatory constraints while still using Azure, hybrid cloud is often the correct answer.
A common trap is thinking hybrid means using multiple public cloud providers. That concept is more accurately called multicloud, not hybrid cloud. Another trap is assuming public cloud is always less secure. AZ-900 does not frame the models as good versus bad. Instead, it focuses on tradeoffs such as control, flexibility, cost, and management responsibility.
Exam Tip: If the scenario mentions retaining some on-premises systems while integrating with Azure, choose hybrid cloud unless the wording clearly points somewhere else.
What the exam tests here:
To identify the correct answer, first ask whether resources are shared provider services, dedicated to one organization, or split across cloud and on-premises environments. That one question usually narrows the answer immediately.
The shared responsibility model is central to cloud literacy and appears throughout AZ-900, even outside the cloud concepts objective. The basic idea is that security and management responsibilities are divided between the cloud provider and the customer. What changes is how much responsibility shifts depending on the service model. In all models, the provider is responsible for the physical datacenter, physical network, and physical hosts. Customers are always responsible for things like their data and access management to some degree. As you move from IaaS to PaaS to SaaS, more responsibility shifts to the provider.
In IaaS, customers manage operating systems, applications, data, identities, and many network controls. In PaaS, customers typically focus on applications, data, and access, while the provider also manages the operating system and runtime. In SaaS, the provider manages almost everything related to the application stack, but the customer still manages data usage, user access, device considerations, and configuration choices. The exam frequently tests this by asking who is responsible for patching, identity control, or data classification.
Consumption-based pricing means customers pay for what they use. Instead of large upfront hardware purchases, they pay based on resource consumption such as compute time, storage volume, network usage, or service transactions. This supports operational expenditure rather than purely capital expenditure. However, a subtle exam trap is assuming cloud is always cheaper. Cloud can reduce upfront cost and improve flexibility, but total cost depends on usage patterns and governance.
Another key idea is that cloud resources can often be scaled up and down, which affects cost. If resources are overprovisioned, spending rises unnecessarily. If they are right-sized, organizations can align cost more closely with demand. Questions may also point to reserved capacity or fixed licensing in contrast with pay-as-you-go, but the fundamental tested concept remains measured service and variable billing based on consumption.
Exam Tip: If a question asks who is responsible for the physical servers, the answer is the cloud provider. If it asks who is responsible for data, account management, or access configuration, the customer almost always retains at least part of that responsibility.
To answer well, separate two themes: responsibility and billing. Responsibility asks who secures or manages a layer. Billing asks how the customer is charged for resource use. Do not let those ideas blur together in scenario-based questions.
This section is about how to think through cloud concepts questions in an AZ-900 style, not about memorizing isolated facts. Microsoft often writes foundational questions using short scenarios, keyword-driven statements, or compare-and-contrast wording. To score well, train yourself to classify the prompt before you evaluate the options. Ask: is this question about a cloud benefit, a service type, a deployment model, shared responsibility, or pricing? Once you know the category, many distractors become easier to eliminate.
Start with keyword analysis. Words such as automatic adjustment suggest elasticity. Dedicated to one organization points to private cloud. Complete software application delivered over the internet indicates SaaS. Customer manages the operating system strongly suggests IaaS. Retains on-premises systems while using Azure indicates hybrid cloud. These clues are usually more valuable than surface-level business wording.
Next, use elimination. Remove answers that are true statements but do not match the exact requirement. For example, if a scenario focuses on uptime during component failure, reliability may sound close, but high availability is usually more precise if the question is about remaining accessible. If a company wants developers to deploy code without managing servers, IaaS is too low-level and SaaS is too finished; PaaS becomes the strongest fit.
Common traps in this domain include confusing scalability with elasticity, hybrid with multicloud, and security with every other cloud benefit. Another trap is choosing the most familiar term rather than the most accurate one. Many beginners overselect SaaS because it sounds simple and recognizable. On the exam, however, the deciding factor is what the customer still manages.
Exam Tip: In cloud concept questions, the best answer is often the one that exactly matches Microsoft’s textbook definition, even if another option seems broadly reasonable in real life.
Your practical review strategy should be:
If you can consistently classify prompts, spot keywords, and eliminate near-miss distractors, you will be well prepared for this objective. That skill also carries into later chapters on Azure architecture and governance, where the exam continues to reward precise interpretation over guesswork.
1. A company wants to move an internal web application to Azure. The company wants Azure to provide the operating system, runtime, and scaling platform so developers can focus only on the application code. Which cloud service type should the company choose?
2. A retail company experiences large spikes in website traffic during holiday sales and much lower usage during the rest of the year. Which cloud benefit best describes the ability to automatically add or remove resources to match demand?
3. A company must keep some workloads in its own datacenter because of regulatory requirements, but it also wants to use Azure for other applications and to extend capacity when needed. Which deployment model best fits this requirement?
4. A startup chooses Azure because it wants to avoid buying servers upfront and instead pay only for the resources it uses each month. Which cloud concept does this describe?
5. A company deploys virtual machines in Azure. According to the shared responsibility model, which task remains the customer's responsibility?
This chapter maps directly to one of the highest-value AZ-900 objective areas: describing Azure architecture and services. On the exam, Microsoft is not testing whether you can deploy a production environment by memory. Instead, it tests whether you can recognize the purpose of core Azure components, distinguish between similar services, and select the best fit based on scenario language. That means this chapter focuses on the terms, relationships, and decision clues that repeatedly appear in entry-level Azure questions.
You should think about this chapter in four layers. First, understand the physical and logical Azure architecture: regions, availability zones, region pairs, edge locations, subscriptions, resource groups, and resources. Second, learn the major compute choices: virtual machines, containers, Azure App Service, and serverless options such as Azure Functions. Third, review networking basics including virtual networks, subnets, connectivity methods, DNS, and load balancing. Fourth, practice reading the wording of exam questions so you can eliminate tempting but incorrect choices.
For AZ-900, the exam often uses short business requirements rather than deep technical detail. A question may describe a company that wants high availability within a region, global presence, private connectivity to Azure, or rapid web app deployment without managing operating systems. Your task is to identify the Azure service category being tested. Exam Tip: If a question sounds operationally complex but the exam objective is fundamentals, the correct answer is usually the broad service that best matches the requirement, not an advanced engineering feature.
Another important pattern is scope. Many test-takers confuse architectural scope levels such as management groups, subscriptions, resource groups, and resources. They also mix up physical resilience concepts such as regions and availability zones. Microsoft expects you to know what belongs inside what, what can be organized or governed together, and what is meant by redundancy across datacenters versus across geographies. This chapter helps you build that hierarchy in a clean way so you can answer with confidence.
As you read, keep linking each service to the exam objective wording. If the prompt is about organizing, billing, or applying policy across environments, think governance structure. If the prompt is about running code or hosting an application, think compute. If the prompt is about communication paths or name resolution, think networking. If the prompt uses words such as resilient, isolated, nearby, global, private, or automatic, those are signal words that help narrow the answer.
Finally, remember the AZ-900 exam rewards conceptual precision. A virtual machine is not the same as a container. A region is not the same as an availability zone. A resource group is not the same as a subscription. A load balancer is not DNS. Many wrong options are included because they sound related. Your advantage comes from understanding what each service is designed to do and noticing when an answer goes one layer too high or one layer too low.
Use this chapter as both a learning guide and an elimination guide. When you know what a service does, also learn what it does not do. That is often the fastest route to the correct answer on AZ-900.
Practice note for Learn core Azure architectural components: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Understand Azure compute options: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Review Azure networking basics: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Azure’s global infrastructure is a favorite AZ-900 test area because it introduces the idea that cloud architecture spans both geography and resiliency design. An Azure region is a geographic area containing one or more datacenters. On the exam, when you see a requirement tied to geographic presence, data residency, or placing services closer to users, a region is often part of the answer. Regions help organizations deploy resources near customers, support compliance needs, and improve performance by reducing latency.
Availability zones are separate physical locations within an Azure region. Each zone has independent power, cooling, and networking. The exam tests whether you understand that zones are about resilience within a region. If a scenario says an application must continue running even if one datacenter in the region fails, availability zones are the clue. Exam Tip: If the question asks for protection from a single datacenter failure inside one region, choose availability zones rather than region pairs.
Region pairs are another common concept. Azure pairs many regions within the same geography for disaster recovery and platform update prioritization. If a question mentions broad geographic resiliency, disaster recovery between regions, or one region recovering from another regional outage, region pairs are the likely concept. A common trap is confusing region pairs with availability zones. Region pairs protect across regions; availability zones protect within a region.
Edge locations are associated with delivering content closer to end users, often in the context of services like Azure Content Delivery Network. These locations reduce latency by caching or delivering content from points nearer to users. On AZ-900, edge locations are less about deep configuration and more about recognizing their purpose in improving global content performance. If the wording emphasizes end-user proximity for content delivery rather than resource deployment, think edge locations instead of regions.
What the exam really tests here is your ability to separate physical distribution concepts by scope. Regions equal broad deployment geography. Availability zones equal fault isolation within a region. Region pairs equal cross-region resiliency alignment. Edge locations equal content delivery proximity. Common distractors include resource groups and subscriptions, which are organizational constructs, not physical infrastructure concepts. When you read a scenario, ask: is the requirement about location, fault tolerance, disaster recovery, or faster content delivery? That question usually identifies the correct architecture term.
This section covers the logical hierarchy of Azure, which appears frequently because it connects architecture, billing, and governance. At the lowest level are resources, such as a virtual machine, storage account, or virtual network. Resources are the actual services you create and use. A resource group is a container that holds related resources for an Azure solution. A subscription provides a unit for billing and access control. Above subscriptions, management groups allow administrators to organize multiple subscriptions for governance at scale.
The most common exam trap is mixing up resource groups and subscriptions. Resource groups are used to logically group related resources, often for lifecycle management. For example, resources that belong to one application may be placed in the same resource group so they can be managed together. A subscription, by contrast, is tied to billing, quotas, and broader access boundaries. Exam Tip: If the scenario focuses on cost tracking, account structure, or limits, think subscription. If it focuses on organizing components of a solution, think resource group.
Management groups sit above subscriptions and are useful when an organization has many subscriptions and wants to apply governance consistently. On the AZ-900 exam, you are usually not asked for advanced policy inheritance details, but you should know that management groups help standardize administration across subscriptions. If a question mentions a large enterprise needing consistent governance over several subscriptions, management groups are a strong clue.
Another important point is that resources in a resource group can work together, but a resource group is not the same as a network boundary or a physical location. Some learners wrongly assume a resource group means all resources must serve the same technical purpose or exist in the same place. For exam purposes, think of resource groups as management containers, not physical constructs. Likewise, management groups do not contain individual resources directly in the way a resource group does; they organize subscriptions.
The exam often tests hierarchy recognition. A quick mental model helps: management groups at the top, subscriptions under them, resource groups inside subscriptions, and resources inside resource groups. If answer choices all sound plausible, pick the option that matches the scope stated in the scenario. Large-scale organization across subscriptions means management groups. Billing or access boundary means subscription. Application component organization means resource group. Actual service instance means resource.
Compute is one of the easiest areas to score points on if you can match requirements to the correct service model. Azure Virtual Machines are the classic infrastructure as a service option. They provide full control over the operating system and environment, making them a fit when a company needs to run custom software, manage the OS, or migrate traditional workloads with minimal redesign. On AZ-900, if the scenario mentions administrative control, custom OS configuration, or lift-and-shift migration, virtual machines are the likely answer.
Containers package an application and its dependencies in a lightweight, portable format. They are faster to start and more efficient than full virtual machines for many workloads. The fundamentals exam does not expect deep orchestration knowledge, but you should know the high-level value: consistency, portability, and microservice-friendly deployment. A common trap is choosing a VM when the question actually emphasizes packaging and rapid deployment consistency rather than OS-level control.
Azure App Service is a platform as a service offering for hosting web apps, APIs, and mobile back ends without managing the underlying infrastructure. This is a frequent exam favorite because it illustrates the cloud benefit of reducing operational overhead. If the requirement is to deploy a web application quickly and avoid server management, App Service is usually the best answer. Exam Tip: Watch for wording such as “without managing infrastructure” or “focus on application code.” Those phrases strongly indicate App Service or another PaaS choice rather than virtual machines.
Serverless basics usually appear through Azure Functions. Serverless means developers can run code in response to events without provisioning and managing servers in the traditional sense. Billing commonly aligns to execution or consumption, making it appealing for intermittent workloads. On AZ-900, if a scenario describes code triggered by an event, task automation, or paying only when code runs, Azure Functions is the concept being tested.
What the exam is really asking in compute questions is: how much infrastructure management is required, and how custom is the workload? More control means VMs. Application hosting without server management means App Service. Lightweight portable packaging means containers. Event-driven execution means serverless. The distractors are often close, so use elimination. If a requirement demands OS access, App Service is wrong. If the requirement says run code only on demand, a continuously running VM is probably wrong. Match the service to the operational model, not just to the word “compute.”
Azure networking questions in AZ-900 are typically scenario based and test whether you understand the role of each service. An Azure virtual network, or VNet, is the foundational private network space for Azure resources. If the exam describes communication between Azure resources in an isolated network, a virtual network is central to the answer. Subnets divide a virtual network into smaller segments, helping organize and control traffic. If the question focuses on segmenting resources within a network, subnets are the clue rather than separate VNets.
VPN and ExpressRoute are often compared. A VPN connection uses the public internet to connect on-premises networks to Azure securely. ExpressRoute provides a dedicated private connection and is typically chosen for higher reliability, privacy, and predictable performance. Exam Tip: If the wording says “private dedicated connection” or emphasizes avoiding the public internet, choose ExpressRoute. If the requirement is simply secure connectivity from on-premises over the internet, VPN is usually correct.
Azure DNS provides name resolution. It is not a traffic distribution tool, and this distinction matters on the exam. If a scenario is about resolving a domain name to an IP address, DNS is relevant. If the scenario is about distributing incoming traffic across multiple servers or instances, that points to a load balancing service instead. Many beginners incorrectly select DNS because web access is involved, but the tested concept may actually be balancing traffic or routing users.
Load balancing itself appears in fundamentals as the broad idea of distributing traffic to improve availability and performance. You do not usually need an architect-level comparison of every Azure load balancing product for AZ-900, but you should recognize the function: spreading requests across multiple instances. If the scenario mentions preventing one server from becoming overloaded or improving application availability by using multiple instances, think load balancing.
The key to networking questions is to identify the network problem type. Need private Azure network space? VNet. Need internal segmentation? Subnet. Need secure site-to-site internet-based connectivity? VPN. Need private dedicated connectivity? ExpressRoute. Need name resolution? DNS. Need traffic distribution? Load balancing. Common distractors exploit related but different ideas, so always ask what exact problem the service solves rather than what general technology category it belongs to.
AZ-900 rarely rewards memorizing isolated definitions without context. Instead, it rewards your ability to notice clues in the wording. Certain terms almost automatically map to specific Azure services. “Single datacenter failure” suggests availability zones. “Disaster recovery across regions” suggests region pairs. “No server management” suggests App Service or another PaaS option. “Run code on demand” suggests serverless. “Dedicated private connection” suggests ExpressRoute. “Billing boundary” suggests subscription. “Organize related components” suggests resource group.
One of the biggest distractor patterns is the “related but wrong layer” answer. For example, a scenario about organizing resources for an application may offer subscription, resource group, and management group. All are real Azure constructs, but only one matches the required scope. Another pattern is the “technically possible but not best fit” option. A company can host a website on virtual machines, but if the requirement emphasizes minimizing infrastructure management, App Service is the better answer. The exam typically expects the most appropriate cloud-native choice, not just any workable choice.
Another trap is overthinking. Because Azure includes many advanced services, beginners sometimes assume the hardest-sounding answer must be correct. In fundamentals, the best answer is usually the simplest service that directly satisfies the requirement. Exam Tip: If an answer choice introduces unnecessary complexity that the scenario did not ask for, eliminate it. Fundamentals questions favor broad service recognition over expert tuning.
Watch for words indicating whether the requirement is physical, logical, operational, or financial. Physical clues include region and availability zone. Logical clues include resource group and virtual network. Operational clues include VM, containers, App Service, and Functions. Financial or organizational clues include subscription and management group. If you classify the scenario first, you narrow the answer pool before reading every choice in depth.
Finally, remember that distractors often reuse familiar Azure words to create uncertainty. Your defense is precision. Ask what the service is primarily for. If the answer choice does not match the primary purpose, it is probably wrong for an AZ-900 fundamentals question, even if it sounds adjacent to the scenario.
When practicing AZ-900 questions on architecture and services, do more than check whether your answer is right or wrong. Train yourself to identify the objective domain being tested before you evaluate choices. Ask: is this a geography and resiliency question, a hierarchy and governance question, a compute model question, or a networking question? This first step prevents you from being pulled toward attractive distractors.
For architecture items, practice separating within-region resilience from cross-region resilience. If your brain can instantly distinguish availability zones from region pairs, you will avoid one of the most common mistakes in this domain. For hierarchy items, repeatedly visualize the structure from management groups down to resources. Many test-takers lose easy points because they reverse resource groups and subscriptions under exam pressure.
For compute practice, compare the management responsibility in each option. VMs require the most control and management. Containers focus on packaging and portability. App Service abstracts infrastructure for application hosting. Serverless runs code in response to events and usually aligns with consumption-based execution. If you read each scenario through the lens of “who manages what,” the correct answer becomes much clearer.
For networking practice, classify the requirement as connectivity, segmentation, name resolution, or traffic distribution. This method quickly separates VPN and ExpressRoute from DNS and load balancing. It also helps with VNets and subnets. Many learners miss networking questions because they focus on product names instead of the network problem being solved.
Exam Tip: During your final review, create a one-line trigger phrase for each service. Example mental cues include “zones = datacenter fault isolation,” “region pairs = regional disaster recovery alignment,” “resource group = manage related resources,” “App Service = host web apps without server management,” and “ExpressRoute = private dedicated connection.” Fast recall of these trigger phrases is extremely effective on fundamentals exams.
As you continue into later chapters and full mock exams, revisit this chapter’s concepts often. Azure architecture, compute, and networking are foundational domains that connect to governance, pricing, security, and reliability topics across the AZ-900 blueprint. The more quickly you can identify the service category being tested, the more confidently you can answer under time pressure.
1. A company wants to deploy two virtual machines in the same Azure region and ensure they are protected from a single datacenter failure. Which Azure architectural component should the company use?
2. A startup wants to host a web application in Azure with minimal management overhead. The developers want Microsoft to manage the underlying operating system and platform components. Which Azure compute option is the best fit?
3. A company needs private connectivity from its on-premises datacenter to Azure without using the public internet. Which Azure service should you recommend?
4. A company wants to organize related Azure resources for a single application so they can be managed, monitored, and deleted together. Which Azure scope should the company use?
5. A development team needs to run code in response to events and wants to pay only when the code executes. Which Azure compute service best matches this requirement?
This chapter continues the AZ-900 objective domain on Azure architecture and services, with a strong focus on the storage, data, identity, integration, and service-selection topics that frequently appear in beginner-friendly but carefully worded exam items. Microsoft often tests whether you can recognize the purpose of a service, distinguish it from a similar service, and match a simple business requirement to the correct Azure offering. That means memorizing names is not enough. You must understand what each service is for, what problem it solves, and what keywords in a question point to the best answer.
In this chapter, you will explore storage and data services, understand identity and access fundamentals, recognize analytics and integration services, and practice how to choose among Azure services in realistic exam scenarios. On the AZ-900 exam, many questions are not deeply technical, but they do reward precision. For example, the exam may present several valid Azure services and ask for the best option based on requirements such as structured data, event routing, file sharing, or identity management. Your job is to identify the defining requirement and eliminate the distractors.
A common trap in this objective area is mixing up categories. Storage services are not databases. Identity services are not governance tools. Event-based messaging is not the same as enterprise message queuing. The exam expects you to know the boundary lines. When you study, organize services by function: object storage, file shares, messages, NoSQL data, identity, integration, and analytics. This mental grouping makes it easier to answer quickly.
Exam Tip: When two answer choices seem correct, look for the keyword that narrows the requirement. Words such as files, objects, globally distributed, single sign-on, events, relational, and hybrid identity are usually the deciding clues.
Another exam pattern is service recognition through short descriptions. You may be asked which service stores unstructured data, which provides directory and identity capabilities, which supports enterprise integration through reliable message delivery, or which helps move and transform data between sources. These are foundational Azure concepts. If you can clearly explain each service in one sentence, you are in a strong position for the test.
As you read the sections in this chapter, keep returning to the exam objective wording: describe Azure architecture and services. The AZ-900 exam is not asking you to design advanced solutions. It is asking whether you can describe what major Azure services do and recognize when they should be used. That is exactly the skill this chapter develops.
Practice note for Explore storage and data services: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Understand identity and access fundamentals: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Recognize analytics and integration services: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Practice Azure services questions: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Explore storage and data services: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Understand identity and access fundamentals: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Azure Storage is a core AZ-900 topic because it introduces several services under one broad platform. The exam commonly starts with the storage account, which is the top-level Azure resource that provides access to storage services such as Blob Storage, Azure Files, Queue Storage, and Table Storage. If a question asks where these services live or how Azure organizes them, the storage account is the key concept.
Blob Storage is used for massive amounts of unstructured object data, such as images, video, backups, logs, and documents. The exam often uses words like unstructured, objects, or media files to signal Blob Storage. Azure Files, by contrast, provides managed file shares that can be accessed using the SMB protocol and is commonly associated with lift-and-shift scenarios or shared access by multiple systems. If a scenario mentions a traditional file share or shared folders, Azure Files is usually the right match.
Queue Storage is used to store messages for asynchronous processing between application components. On the exam, this appears in basic application-decoupling scenarios. The key idea is that Queue Storage helps services communicate reliably without needing to process everything immediately. Table Storage is a NoSQL key-value store for structured but non-relational data. It is highly scalable and simple, but many learners confuse it with relational databases. It does not support SQL-style relational features in the way Azure SQL Database does.
Exam Tip: Do not confuse Queue Storage with Service Bus. Queue Storage is simpler and is often tested as basic message queuing, while Service Bus is associated with more advanced enterprise messaging and integration scenarios.
A classic exam trap is choosing Azure Files for backups or media simply because the word “files” appears in the requirement. Read carefully. If the need is object storage at scale, Blob Storage is the stronger answer. Another trap is treating Table Storage like a full database engine. For AZ-900, remember that it is a simple non-relational storage option, not a replacement for relational querying. Questions in this area test whether you can classify data correctly and connect a storage need to the right Azure service.
AZ-900 expects you to recognize the difference between relational and non-relational databases. Relational databases store structured data in tables with rows, columns, and relationships, and they are commonly queried with SQL. In Azure, the most important beginner-level relational service to know is Azure SQL Database. When the exam mentions structured business data, transactions, SQL compatibility, or traditional relational design, Azure SQL Database should be near the top of your answer choices.
Non-relational databases, often described as NoSQL databases, are designed for flexible schema models, very large scale, and specific performance patterns. Azure Cosmos DB is the flagship non-relational database service that appears regularly on the exam. The words globally distributed, low latency, planet-scale, or multi-model NoSQL strongly suggest Azure Cosmos DB. It is designed for applications that need fast response times and broad geographic distribution.
The exam usually does not require deep implementation knowledge, but it does require correct service identification. Azure SQL Database is a managed relational database service. Cosmos DB is a managed NoSQL database service. That distinction is basic but heavily tested. Another related point is that not every non-relational need must point to Cosmos DB; however, on AZ-900, Cosmos DB is the best-known answer when Microsoft wants you to identify Azure’s globally distributed NoSQL option.
Exam Tip: If a question emphasizes fixed schema, transactions, and SQL-based relationships, think Azure SQL Database. If it emphasizes flexible schema, huge scale, or global distribution, think Azure Cosmos DB.
A common trap is confusing Table Storage with Cosmos DB simply because both are non-relational in a broad sense. For the exam, Cosmos DB is the more feature-rich Azure database service associated with modern globally distributed applications. Table Storage is simpler and usually appears in storage discussions rather than core database-service comparisons. Another trap is assuming that “database” automatically means relational. The exam often checks whether you notice the business requirement before selecting the service category.
As an exam coach, I recommend building a quick decision rule: structured business application data points to Azure SQL Database; highly scalable, globally distributed, low-latency app data points to Azure Cosmos DB. This rule will solve many beginner-level database questions efficiently and accurately.
Identity is one of the highest-value AZ-900 domains because it connects directly to security, access control, and user experience. The primary identity service to know is Microsoft Entra ID, formerly Azure Active Directory. On the exam, Microsoft Entra ID is the cloud-based identity and access management service used for user identities, application registration, conditional access support, and single sign-on across cloud resources and many third-party applications.
You must clearly distinguish authentication from authorization. Authentication answers the question, “Who are you?” It verifies identity, often through usernames, passwords, multifactor authentication, or other sign-in methods. Authorization answers the question, “What are you allowed to do?” It controls permissions after identity has been verified. AZ-900 questions often test these two terms directly because they are easy to confuse under exam pressure.
Single sign-on, or SSO, allows a user to sign in once and access multiple applications without re-entering credentials repeatedly. If the requirement is improving user sign-in convenience while centralizing identity, SSO is the likely concept being tested. Microsoft Entra ID supports SSO and integrates with many Microsoft and non-Microsoft services. The exam also expects broad awareness that identity can extend across cloud and hybrid environments.
Exam Tip: When a question asks which service provides identity, user sign-in, and access management for Azure resources, the answer is usually Microsoft Entra ID, not Azure Policy, not Defender for Cloud, and not a subscription feature.
One common trap is mixing identity tools with access-control outcomes. Microsoft Entra ID manages identities and authentication. Azure role-based access control, often paired conceptually with authorization, helps determine what a user can do on Azure resources. Another trap is choosing Active Directory Domain Services concepts when the question is clearly about cloud identity and Azure sign-in. For AZ-900, keep the focus on Microsoft Entra ID as the default cloud identity platform.
What is the exam really measuring here? It is testing whether you understand that cloud security begins with identity. If a scenario mentions employee sign-in, user accounts, app access, directory services, or SSO, move quickly toward Microsoft Entra ID and evaluate whether the wording is about authentication, authorization, or both.
The AZ-900 exam introduces integration and analytics at a recognition level. You are not expected to architect advanced pipelines, but you are expected to identify what these services do. Azure Event Grid is an event-routing service. If the question mentions reacting to events, triggering actions when something happens, or event-based architectures, Event Grid is a strong candidate. Think of it as event notification and routing.
Azure Service Bus is a messaging service used for more advanced enterprise integration scenarios. It supports reliable message delivery between distributed applications and services. When the exam points to enterprise messaging, decoupled systems, or durable communication patterns, Service Bus is often the best choice. This is where many learners stumble because Queue Storage also handles messages. The difference is that Service Bus is the more robust enterprise messaging service, while Queue Storage is simpler.
Azure Data Factory is used to move and transform data across different sources. If a scenario refers to data pipelines, ingestion, orchestration, or moving data from one system to another for processing or reporting, Data Factory should stand out. It is one of the most testable service-recognition items in this chapter because its purpose is distinct and practical.
For analytics, AZ-900 may refer broadly to services that help process, query, or visualize large datasets. At this level, focus on the idea rather than deep product configuration. You should recognize that Azure offers analytics services for large-scale data processing and business insight generation.
Exam Tip: If the keyword is event, think Event Grid first. If the keyword is message queueing between business systems, think Service Bus. If the keyword is pipeline or data movement, think Data Factory.
A classic exam trap is selecting Event Grid for any integration question. Not all integration is event routing. Likewise, not all messaging is Queue Storage. Microsoft often tests whether you can separate event-driven responses from enterprise messaging and from data orchestration. Read for the business pattern, not just the technical buzzword.
This section brings together the chapter’s major lesson: matching a workload to the right Azure service. On AZ-900, this is less about implementation and more about categorization. You will see short scenarios describing business needs, and you must identify the most appropriate service. The fastest path to the correct answer is to isolate the workload type first: storage, database, identity, integration, or analytics.
Start by asking what the requirement is really about. Is the scenario about storing files, objects, messages, or application records? Is it about sign-in and access? Is it about moving data, reacting to events, or supporting global low-latency application data? This first classification step eliminates many distractors immediately. For example, if the problem is user sign-in across apps, do not waste time comparing storage services. If the problem is media object storage, do not compare relational databases.
A good beginner-level decision map looks like this: use Blob Storage for unstructured objects; Azure Files for shared file access; Queue Storage for simple queued messages; Azure SQL Database for relational data; Azure Cosmos DB for globally distributed NoSQL data; Microsoft Entra ID for identity and SSO; Event Grid for event routing; Service Bus for enterprise messaging; and Data Factory for data pipelines.
Exam Tip: Watch for answer choices that are technically possible but not the best fit. AZ-900 often rewards the most direct service match, not a creative workaround.
Another important exam skill is keyword analysis. Words such as shared drive, transactional SQL, directory, sign-on, event notification, and ETL-like pipeline usually point to one service category. Be careful with broad phrases like “store data” because many Azure services store data. The surrounding details matter more than the broad requirement.
One final trap: some candidates overthink the scenario and imagine constraints not present in the question. The AZ-900 exam is fundamentals-level. If the wording is simple, the intended answer is usually simple too. Choose the service that most directly satisfies the stated need, and avoid bringing in advanced architecture assumptions that are not mentioned.
As you prepare for exam-style questions in this domain, focus on how Microsoft frames answer choices. The test often places related services together to see whether you understand the differences. You may need to distinguish Blob Storage from Azure Files, Azure SQL Database from Azure Cosmos DB, or Event Grid from Service Bus. The strongest strategy is elimination based on service purpose. If a choice belongs to the wrong category, remove it immediately.
For storage questions, look for clues about the data form. Objects and unstructured content suggest Blob Storage. Shared file access suggests Azure Files. Simple asynchronous messaging points to Queue Storage. Basic key-value NoSQL storage suggests Table Storage. For database questions, identify whether the app needs a relational model or a globally distributed NoSQL model. This quickly narrows the choices to Azure SQL Database or Azure Cosmos DB.
For identity questions, separate sign-in from permissions in your mind. If the issue is proving user identity, that is authentication. If it is controlling what the user can do, that is authorization. If the requirement is one login for many apps, that is single sign-on, typically supported through Microsoft Entra ID. Many incorrect answers on this topic come from rushing and blending these concepts together.
Integration questions are often solved by identifying the pattern: event reaction, message brokering, or data movement. Event Grid handles events. Service Bus handles enterprise messaging. Data Factory handles data pipelines. This pattern-based approach is more reliable than memorizing product descriptions word for word.
Exam Tip: Before selecting an answer, say the requirement in your own words in one short phrase, such as “shared files,” “cloud identity,” or “global NoSQL.” Then pick the Azure service that most directly matches that phrase.
When reviewing mistakes, do not just memorize the correct answer. Record why the wrong answers were wrong. That is how you build exam confidence. AZ-900 success comes from recognizing the defining feature of each service and resisting distractors that sound familiar but do not fully match the requirement. If you can classify the service correctly and identify the key keyword in the scenario, you are well prepared for this portion of the exam.
1. A company needs to store large amounts of unstructured data such as images, video files, and backups in Azure. Which Azure service should they use?
2. A company wants employees to use one username and password to access Microsoft 365, the Azure portal, and thousands of SaaS applications. Which Azure service provides this functionality?
3. A business needs a fully managed relational database service in Azure for an application that stores customer orders in tables with defined schemas. Which service should be selected?
4. A company wants to build workflows that move and transform data from multiple sources into a central data store for reporting and analytics. Which Azure service is most appropriate?
5. An application must respond whenever a new file is uploaded to Azure storage by triggering serverless processing. Which Azure service should be used to route the event to subscribers?
This chapter maps directly to one of the highest-value AZ-900 objective areas: Azure management and governance. On the exam, Microsoft is not asking you to configure enterprise-scale production environments from memory. Instead, it tests whether you can recognize the correct Azure tool for a given administrative, governance, monitoring, compliance, pricing, or lifecycle scenario. That means your success depends less on memorizing deep technical commands and more on distinguishing between similar-sounding services such as Azure Monitor versus Azure Service Health, Azure Policy versus resource locks, or Pricing Calculator versus Total Cost of Ownership (TCO) Calculator.
From an exam-prep perspective, think of this chapter as the “decision framework” chapter. You need to know which tool helps you manage Azure resources, which one helps you monitor them, which one helps you control or standardize deployments, and which one helps you estimate or reduce cost. The exam frequently presents short business scenarios and asks which service best meets the requirement. If you can identify the keywords in the prompt, you can often eliminate two or three wrong answers immediately.
The first lesson in this chapter focuses on management and monitoring tools. Azure gives administrators several interfaces for working with resources: the graphical Azure portal, browser-based Azure Cloud Shell, and command-line tools such as PowerShell and Azure CLI. The exam commonly checks whether you understand when a graphical interface is sufficient and when a command-based or automated approach is better. Remember that all of these tools can be used to manage Azure; the key distinction is how you interact with the platform.
The second lesson covers governance and compliance controls. Governance is about enforcing standards, organizing subscriptions and resources, and reducing risk from accidental or noncompliant changes. Here the exam targets foundational distinctions: Azure Policy evaluates and enforces standards, tags help organize and report, resource locks prevent deletion or modification, management groups provide hierarchy above subscriptions, and Azure Blueprints is historically associated with packaging governance artifacts. Even when a service is less central in the newest real-world deployment patterns, it may still appear conceptually in fundamentals-level questions.
The third lesson addresses pricing, service-level agreements, and lifecycle tools. Microsoft expects AZ-900 candidates to understand consumption-based pricing, how to estimate Azure costs before deployment, and what factors influence cost after deployment. It also expects you to know basic SLA ideas such as uptime commitments and how combining services may affect overall availability. These questions are usually vocabulary-driven, so precise definitions matter.
Finally, this chapter closes with exam-focused answer analysis. The goal is not just to know the content, but to develop the habit of reading carefully for clues such as “prevent deletion,” “estimate future monthly cost,” “review Azure outages affecting my region,” “recommend best practices,” or “enforce allowed SKUs.” Those phrases map strongly to specific services.
Exam Tip: In AZ-900, the wrong answers are often not random. They are usually real Azure services that solve a different problem. Your job is to match the requirement to the service’s primary purpose, not to the service that merely sounds familiar.
As you study, keep connecting each service to a core verb. Portal manages. Monitor observes. Policy enforces. Locks protect. Tags classify. Advisor recommends. Service Health informs. Pricing Calculator estimates. TCO compares. Defender for Cloud strengthens security posture. If you can say the service name and immediately state its main purpose in one short phrase, you are on track for the exam.
Practice note for Learn management and monitoring tools: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
AZ-900 expects you to recognize the main ways administrators interact with Azure. The Azure portal is the web-based graphical user interface for creating, configuring, and reviewing resources. It is the easiest starting point for beginners and is ideal for tasks such as creating a virtual machine, reviewing subscription information, or checking resource settings. On the exam, if the scenario emphasizes a browser-based graphical experience, manual configuration, dashboards, or visual navigation, Azure portal is often the correct answer.
Azure Cloud Shell is a browser-accessible shell environment available directly from the Azure portal. It provides both Bash and PowerShell environments and is useful when you want command-line access without installing tools locally. This distinction matters on the exam. If a question says an administrator wants to run commands from a browser or avoid installing Azure tools on a local workstation, Cloud Shell is a strong match. Cloud Shell also integrates with authenticated Azure sessions, making it convenient for fast administration.
PowerShell and Azure CLI are both command-line management options, but they differ in style. Azure PowerShell uses PowerShell cmdlets and is especially familiar to administrators with Microsoft ecosystem experience. Azure CLI is cross-platform and uses text-based commands that work well in Linux, macOS, and Windows environments. In AZ-900, you usually do not need to know specific commands. You do need to know that both support automation, scripting, and repeatable management tasks.
From a governance perspective, these tools are not governance services by themselves. They are interfaces for managing Azure resources. That is a common trap. If the exam asks how to enforce rules or prevent changes, the answer is not portal, CLI, or PowerShell. Those tools can apply governance settings, but the actual governance service would be Azure Policy, resource locks, or another governance feature.
Exam Tip: Watch for wording such as “graphical interface” versus “command-line interface” versus “browser-based shell.” Those phrases map cleanly to Azure portal, PowerShell/Azure CLI, and Azure Cloud Shell.
Another common trap is assuming Cloud Shell is the same as Azure CLI. Cloud Shell is the hosted environment; Azure CLI is one of the command tools you can run in that environment. Likewise, PowerShell can be run locally or inside Cloud Shell. Think of Cloud Shell as the place, and CLI or PowerShell as the tools.
What the exam is really testing here is whether you understand administrative access methods at a fundamentals level: visual management, browser-based command access, and automated scripting. If two answers both seem possible, choose the one that best fits the interaction style described in the scenario.
Monitoring questions on AZ-900 often depend on your ability to separate operational telemetry from platform status updates and best-practice recommendations. Azure Monitor is the core service for collecting, analyzing, and acting on telemetry from Azure resources and sometimes on-premises or hybrid environments. It can track metrics, logs, application behavior, and performance data. If a question asks how to observe resource performance, analyze activity, or trigger notifications based on measured conditions, Azure Monitor is typically the best answer.
Azure Service Health is different. It provides personalized information about Azure service issues, planned maintenance, and advisories that may affect your specific subscriptions, regions, or resources. This is not the tool for CPU metrics or memory trends. It is the tool for understanding whether Azure itself is experiencing incidents that affect you. On the exam, phrases like “service outage,” “planned maintenance,” “issues in a region,” or “health of Azure services affecting my subscription” point to Service Health.
Azure Advisor provides recommendations to improve reliability, security, performance, operational excellence, and cost. It is a recommendation engine, not a real-time monitoring engine. If the requirement is to identify unused resources, improve cost efficiency, or receive configuration recommendations, Advisor is a strong choice. Candidates often confuse Advisor with Azure Monitor because both can help administrators make decisions, but Advisor focuses on guidance and optimization.
Alerts are also testable. Alerts are triggered when specified conditions are met, such as when a metric exceeds a threshold, when a log query returns certain results, or when activity occurs. Alerts often work with Azure Monitor data. The exam may ask which feature notifies administrators automatically when a monitored condition is met; that is an alert, not Advisor or Service Health.
Exam Tip: Use this memory aid: Monitor measures, Service Health informs, Advisor recommends, Alerts notify.
A common exam trap is choosing Service Health when the scenario is actually about a workload issue inside your own resource, such as high CPU on a VM. That is Azure Monitor territory. Another trap is choosing Advisor when the question asks for immediate notification of an event. Advisor may recommend improvements, but it does not replace alerting.
The exam tests whether you can match the tool to the purpose: telemetry and analysis, Azure platform incident visibility, optimization guidance, or automated notification. Read the scenario carefully and identify whether the issue is about your workload, Microsoft’s platform status, recommendations, or event-driven awareness.
Governance is one of the most important AZ-900 domains because it reflects how organizations keep Azure environments controlled, organized, and compliant. Azure Policy is used to create, assign, and enforce rules over resources. For example, a policy can restrict allowed resource locations, require tags, or deny creation of nonapproved resource types. The exam often describes a need to enforce standards across resources or subscriptions. When you see words like “require,” “audit,” “deny,” or “enforce compliance,” Azure Policy should come to mind immediately.
Resource locks help prevent accidental changes. There are two main lock behaviors commonly discussed at a fundamentals level: delete locks, which prevent deletion, and read-only locks, which prevent modification. The key here is that locks protect existing resources from accidental administrative actions; they do not evaluate compliance rules like Azure Policy does. This distinction is tested often. If the requirement is “stop users from deleting a storage account,” the answer is resource lock, not Azure Policy.
Tags are metadata labels applied to resources. They are useful for categorization, reporting, cost tracking, ownership identification, and organization. Tags do not directly prevent actions, and they are not security boundaries. That is a frequent exam trap. If the goal is to group resources by department, project, or environment, tags are a good fit. If the goal is to restrict deployment or block deletion, tags are not enough.
Management groups provide a hierarchy above subscriptions. They allow organizations to apply governance conditions such as policies and access controls across multiple subscriptions. If a scenario involves many subscriptions and asks for centralized governance or policy inheritance, management groups are likely correct. For AZ-900, you should understand the hierarchy broadly: resources exist in resource groups, resource groups are inside subscriptions, and subscriptions can be organized under management groups.
Azure Blueprints concepts may also appear. Historically, Blueprints provided a way to package artifacts such as policies, role assignments, templates, and resource groups for repeatable, governed deployments. Even if your real-world experience emphasizes newer approaches, the exam may still test the concept of repeatable governance-aligned deployment packages.
Exam Tip: If the question asks to organize, think tags or management groups. If it asks to enforce, think Azure Policy. If it asks to prevent accidental deletion or modification, think resource locks.
What the exam tests most here is not implementation detail, but conceptual separation. Policy governs standards. Locks protect resources. Tags label resources. Management groups structure subscriptions. Blueprints package governance intent. Learn these differences clearly and you will answer many scenario questions correctly.
Cost management is a core Azure fundamentals skill because cloud spending is consumption-based. On AZ-900, Microsoft expects you to know the difference between estimating future cloud costs, comparing cloud costs to on-premises costs, and analyzing or controlling current Azure spending. The Azure Pricing Calculator is used before or during planning to estimate the expected cost of Azure services. If a company wants to model monthly expenses for virtual machines, storage, or networking before deployment, the Pricing Calculator is usually the right tool.
The Total Cost of Ownership, or TCO, Calculator serves a different purpose. It helps estimate potential savings when comparing on-premises infrastructure costs with Azure. This includes considering hardware, power, maintenance, and other ownership-related expenses. If the scenario mentions moving from a datacenter to Azure and wants a business case comparison, the TCO Calculator is the better answer. Candidates commonly confuse it with the Pricing Calculator, so focus on the keyword compare.
Cost Management in Azure helps monitor, allocate, analyze, and optimize actual spending. It supports budgeting, visibility into cost trends, and identifying areas to reduce waste. If the question is about tracking current cloud costs, reviewing spending by subscription or tag, or creating budgets, Cost Management is more appropriate than the calculators.
You also need to know what affects Azure cost. Typical factors include resource type, service tier, region, usage amount, data transfer, storage capacity, redundancy options, licensing, and duration of use. For example, running more powerful virtual machines costs more than smaller ones, and storing data with higher redundancy can increase price. Outbound data transfer may also affect billing. The exam does not usually require exact pricing numbers, but it absolutely expects you to understand the variables that influence cost.
Exam Tip: Pricing Calculator estimates Azure service cost. TCO Calculator compares on-premises cost to Azure. Cost Management tracks and optimizes actual spend after or during deployment.
A common trap is selecting the Pricing Calculator when the requirement is to justify migration from an existing datacenter. Another is selecting Cost Management when the scenario clearly asks for a pre-deployment estimate. Read whether the question is about planning, comparison, or active spend control.
The exam also tests awareness that cloud cost is flexible because it is tied to consumption. This supports scaling up and down, but it also means unmanaged resources can increase spending unexpectedly. Cost governance is therefore part financial and part operational discipline.
AZ-900 does not expect legal-level expertise in trust and compliance, but it does expect you to understand the key assurances Microsoft provides around privacy, regulatory standards, and service reliability. Trust in Azure includes Microsoft commitments related to data handling, transparency, and platform reliability. Privacy refers to how customer data is collected, processed, and protected. Compliance refers to Azure support for recognized standards, certifications, and regulatory frameworks that help organizations meet industry or regional requirements.
On the exam, trust and compliance questions are usually conceptual. You may need to recognize that Microsoft publishes compliance documentation, provides information through trust-focused resources, and supports many global, industry, and regional standards. The test is typically checking whether you know Azure is designed to help customers address compliance obligations, not that Azure automatically makes every workload compliant by default. That last point is a classic trap. Compliance is a shared effort.
Service-level agreements, or SLAs, are formal commitments about service uptime and availability. You should understand that SLAs are expressed as percentages over time and that different services can have different SLA levels. The exam may ask what an SLA represents or how composite solutions can affect overall availability. At this level, the key idea is that higher availability often requires architectural choices such as redundancy or multi-instance deployment, not just trust in a single service.
Microsoft Defender for Cloud is a security posture management and workload protection service. It helps identify security recommendations, improve secure configuration, and protect Azure, hybrid, and multi-cloud resources. For AZ-900, think of it as the service that helps strengthen security posture and surface security recommendations. It is not the same as Azure Policy, though both can influence secure configurations. Defender for Cloud is security-focused guidance and protection; Azure Policy is broader governance enforcement.
Exam Tip: If the scenario is about security posture, recommendations, and protection across resources, think Microsoft Defender for Cloud. If it is about compliance rules or enforcing allowed settings, think governance tools such as Azure Policy.
A common mistake is to assume SLA equals guaranteed zero downtime. That is not what an SLA means. It is a contractual commitment to a certain level of uptime. Another trap is to confuse privacy and compliance with security tooling. Security features help protect systems, but compliance also involves process, governance, and regulatory alignment.
The exam tests broad understanding: Azure supports trust through transparency and commitments, supports compliance through standards and certifications, uses SLAs to define service availability targets, and offers Defender for Cloud to improve security posture and protections.
This final section is about how to think like a high-scoring AZ-900 candidate when facing governance questions. Even without listing practice questions here, you should train yourself to identify scenario keywords and map them to the correct Azure service. The governance objective is one of the easiest places to gain points if your mental categories are clear. Many questions are really testing one distinction at a time.
Start with verb matching. If the scenario says create or manage resources visually, look toward Azure portal. If it says use commands in a browser without local installation, think Azure Cloud Shell. If it mentions automation or scripting, consider PowerShell or Azure CLI. If it asks to collect metrics, analyze logs, or generate notifications from telemetry, choose Azure Monitor and alerts. If it says platform outage, maintenance, or service issue affecting a region or subscription, choose Service Health. If it asks for best-practice recommendations on cost, reliability, or security, choose Advisor.
For governance controls, focus sharply on intent. “Require a tag,” “restrict locations,” or “allow only certain SKUs” are Azure Policy patterns. “Prevent deletion” or “make changes impossible” indicates a lock. “Group resources by cost center” indicates tags. “Apply governance across many subscriptions” indicates management groups. “Package governance artifacts for repeatable deployment” points to Blueprints concepts.
For cost questions, identify the timeline. If it is before deployment and asks for a monthly estimate, use Pricing Calculator. If it compares current datacenter ownership to Azure migration costs, use TCO Calculator. If it is about existing spend, budgets, and optimization, use Cost Management. For trust and security, if the prompt is about uptime commitments, that is SLA language. If it is about security posture and recommendations, that is Microsoft Defender for Cloud.
Exam Tip: Eliminate answers that solve a neighboring problem. For example, Azure Advisor may recommend improvements, but it does not provide outage details for your region. Azure Policy can enforce standards, but it does not stop a specific resource from being deleted the same way a lock does.
Common traps in this domain include confusing Advisor with Monitor, Policy with locks, Pricing Calculator with TCO Calculator, and Service Health with resource performance monitoring. Another trap is overthinking. AZ-900 is foundational. Usually, the simplest service-purpose match is the right one.
In your final review, create a one-line definition for every service in this chapter and recite it until the distinction feels automatic. That skill alone can turn uncertain scenario questions into fast, confident points on exam day.
1. A company wants to estimate the expected monthly cost of deploying several Azure virtual machines, storage accounts, and outbound bandwidth before creating any resources. Which Azure tool should they use?
2. An administrator needs to prevent a critical Azure resource from being accidentally deleted, while still allowing authorized users to view it. Which Azure feature should be used?
3. A company wants to ensure that users can create virtual machines only in specific Azure regions and only with approved VM SKU sizes. Which Azure service should be used to enforce this requirement?
4. A subscription owner wants to know whether an Azure outage or planned maintenance event is affecting resources in the company's specific region. Which service should they use?
5. A company has multiple Azure subscriptions for different departments and wants to apply governance at a level above the subscriptions so policies and access can be organized centrally. What should the company use?
This chapter brings together everything you have studied so far and converts it into exam readiness. The AZ-900 exam is designed for beginners, but that does not mean it is random or easy. Microsoft tests whether you can recognize core cloud principles, identify the correct Azure service for a simple business need, and distinguish between governance, cost, security, and management features. In a final review chapter, the goal is not to memorize isolated facts. The goal is to think the way the exam expects you to think.
The full mock exam process in this chapter is organized around the official AZ-900 domains. That matters because many candidates make the mistake of reviewing Azure as a product catalog instead of reviewing it as an exam blueprint. The real test is domain-based. Some items focus on cloud concepts such as public, private, and hybrid cloud, while others test Azure architecture and services, including compute, storage, networking, databases, and identity. A third major area checks Azure management and governance, including costs, monitoring, compliance, policy, and service levels. Your final review should mirror that structure so your practice is aligned to the objective statements.
The two mock exam parts represented in this chapter are meant to simulate the mixed and sometimes abrupt transitions found on the actual test. One item may ask about the shared responsibility model, and the next may ask about Azure regions or role-based access control. This shift is intentional. AZ-900 rewards candidates who can quickly identify the domain being tested and eliminate distractors that belong to a different domain. If you read a scenario and immediately ask yourself, "Is this a pricing question, a security question, or a service selection question?" you are already improving your odds of selecting the correct answer.
Exam Tip: On AZ-900, many wrong answers are not completely false. They are often real Azure concepts placed in the wrong context. Your task is not just to spot a true statement. Your task is to match the best Azure concept to the specific requirement in the question.
This chapter also emphasizes weak spot analysis, which is where most final score improvement happens. A mock exam only helps if you review the results intelligently. Instead of saying, "I got storage questions wrong," dig deeper. Did you confuse Azure Files with Blob Storage? Did you mix up Azure Policy and Azure Blueprints? Did you misread wording around capital expenditure versus operational expenditure? Score improvement usually comes from fixing patterns of confusion, not from rereading everything equally.
Finally, you will use the exam-day checklist approach to reduce avoidable errors. Beginner candidates often lose points because of poor pacing, second-guessing, and last-minute cramming of low-value details. The AZ-900 exam is broad, but its level is foundational. Success comes from clarity on definitions, practical service recognition, and disciplined elimination techniques. As you move through the sections below, treat each one as part of a final coaching session: what the exam is testing, where candidates get trapped, how to recognize the best answer, and how to turn practice performance into confident exam execution.
Practice note for Mock Exam Part 1: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Mock Exam Part 2: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Weak Spot Analysis: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Practice note for Exam Day Checklist: document your objective, define a measurable success check, and run a small experiment before scaling. Capture what changed, why it changed, and what you would test next. This discipline improves reliability and makes your learning transferable to future projects.
Your full mock exam should be mapped directly to the AZ-900 objective areas, because the real exam measures broad foundational understanding rather than deep technical administration. A strong blueprint includes balanced coverage of cloud concepts, Azure architecture and services, and Azure management and governance. That structure trains you to recognize domain shifts quickly. When candidates perform poorly, it is often because they study in isolated lesson order but face mixed-domain questions on test day and struggle to switch mental context.
The first domain, cloud concepts, typically checks whether you understand cloud computing models, public versus private versus hybrid cloud, the shared responsibility model, and consumption-based pricing. These are high-value fundamentals because Microsoft expects you to identify why cloud services are useful, not just what Azure offers. The second domain, Azure architecture and services, includes regions, availability zones, resource groups, subscriptions, virtual machines, containers, serverless computing, storage services, networking options, databases, and Microsoft Entra ID. The third domain, management and governance, focuses on cost management, SLAs, monitoring tools, security capabilities, compliance concepts, and governance tools such as Azure Policy and resource locks.
Exam Tip: Build your mock review sheet in three columns: domain, missed concept, and reason missed. This helps you identify whether the problem was knowledge, vocabulary, or misreading.
A realistic blueprint should also include item variety. Some exam items are straightforward definition checks, while others are short scenarios that require matching a business need to the right Azure feature. The exam often tests whether you can distinguish similar concepts. For example, a service may sound related to security, but the question may really be about governance. Or a scenario may mention high availability, but the best answer depends on region design rather than backup. Common traps include choosing an answer because it sounds advanced or because it contains familiar Azure branding. The correct answer is usually the one that directly satisfies the stated requirement with the least extra assumption.
When using a full mock exam, do not just score it once and move on. Use it as a blueprint validation tool. Ask whether your mistakes cluster around architecture vocabulary, pricing language, or governance tools. That pattern is far more important than raw score alone during final revision.
In the cloud concepts domain, the exam tests whether you understand the logic behind cloud adoption. This includes cloud models, deployment models, elasticity, scalability, high availability, fault tolerance, disaster recovery, and the financial model of cloud computing. The questions are foundational, but they are not trivial. Microsoft often checks whether you can apply a definition to a simple business situation rather than recite the definition in isolation.
One major exam target is the difference between CapEx and OpEx. If an organization buys and owns physical hardware, that is capital expenditure. If it pays for cloud services as they are used, that is operational expenditure. Candidates often miss these items because they focus on technical wording and ignore the finance clue. Another frequent topic is the shared responsibility model. The exam may ask who is responsible for what in IaaS, PaaS, or SaaS. The trap is assuming Azure handles everything. In reality, responsibility shifts depending on the service model. The more managed the service, the more Microsoft handles.
Exam Tip: When you see wording about reducing upfront cost, improving flexibility, or paying only for usage, immediately think consumption-based pricing and OpEx.
The exam also tests public, private, and hybrid cloud. The common trap is to assume hybrid means multiple public clouds. For AZ-900, hybrid usually means combining on-premises infrastructure with cloud services. You should also be able to distinguish scalability from elasticity. Scalability means increasing or decreasing resources to meet demand. Elasticity emphasizes automatic or dynamic adjustment in response to changes. These terms are related, but the exam may reward the more precise one based on wording.
Read carefully for clues about availability and recovery. High availability is about keeping services accessible. Fault tolerance is about continuing to operate despite component failures. Disaster recovery is about restoring operations after a significant outage. If a question mentions accidental regional outage or restoring business operations, disaster recovery is likely the tested concept. If it emphasizes uninterrupted service during a component failure, think high availability or fault tolerance instead. Strong performance in this domain comes from linking business language to the correct cloud principle.
This domain is usually the broadest and often feels the most intimidating to beginners because it includes many service names. The key is not to memorize every Azure offering. The exam focuses on major categories and whether you can match needs to services. You should know the role of regions, region pairs, availability zones, subscriptions, management groups, and resource groups. You should also recognize common compute choices such as virtual machines, containers, and serverless functions, along with core storage, networking, database, and identity services.
A common exam pattern is service selection. If the requirement is full control over an operating system, virtual machines are likely relevant. If the requirement is to run packaged applications consistently, containers fit better. If the requirement is event-driven code without managing infrastructure, Azure Functions is a strong candidate. The trap is selecting the most familiar service instead of the most appropriate level of abstraction. Similar confusion appears in storage. Blob Storage is for unstructured object data, Azure Files supports shared file access, and managed disks are tied to Azure virtual machines. Candidates often miss these because all three are storage, but each serves a different use case.
Exam Tip: For architecture questions, ask: Is the exam testing where resources are organized, how workloads run, how data is stored, how networks connect, or how identities are authenticated? That single question narrows the answer set quickly.
Networking items often include virtual networks, VPN Gateway, ExpressRoute, DNS, and load balancing concepts. The exam may describe a need for private communication between Azure resources and on-premises systems. You must identify whether internet-based encrypted connectivity or private dedicated connectivity is being tested. Database questions usually stay high-level: relational versus non-relational, managed database services, and analytics-oriented services. Identity questions often point toward Microsoft Entra ID for authentication and access management.
Another trap is confusing organizational components. A resource group is a logical container for related resources. A subscription is tied to billing and access boundaries. A management group helps organize multiple subscriptions. These distinctions appear repeatedly because they represent core Azure architecture. If you can classify these components cleanly and identify the purpose of major service families, you are in strong shape for this domain.
This domain checks whether you understand how Azure environments are controlled, monitored, secured, and optimized. Many candidates lose points here because the terminology overlaps. Cost Management, Azure Policy, resource locks, Service Trust Portal, Defender for Cloud, and Azure Monitor all sound administrative, but they solve different problems. The exam expects you to connect each tool to its primary purpose.
Cost-focused items often test pricing calculators, total cost of ownership comparisons, tagging, budgeting, and reservation concepts at a high level. If a question asks how to estimate future cloud spend before deployment, think of pricing estimation tools rather than monitoring tools. If it asks how to track spending by department or project, tags and cost analysis are stronger concepts. Governance questions frequently center on consistency and compliance. Azure Policy evaluates and enforces rules on resources. Resource locks prevent accidental deletion or modification. These are classic trap pairs because both protect resources, but one governs configuration standards while the other protects against change operations.
Exam Tip: If the wording is about enforcing standards, think policy. If the wording is about preventing accidental changes, think locks. If the wording is about permissions, think RBAC.
Monitoring and health concepts are also important. Azure Monitor collects and analyzes telemetry. Service Health communicates issues affecting Azure services and subscriptions. Advisors provide recommendations. A frequent trap is choosing a tool that sounds analytical when the question is really about platform incidents or planned maintenance. Security and compliance items may reference Microsoft Defender for Cloud, compliance offerings, or the Service Trust Portal. The exam is usually checking whether you know where to find compliance documentation versus where to improve security posture.
SLAs appear as well. You do not need deep contract law knowledge, but you should understand that SLAs define expected uptime commitments and that combining services can affect overall solution availability. Read these items carefully, because the trap is often mathematical distraction. Focus on the tested principle: higher availability percentages mean less allowed downtime, and architecture decisions influence availability outcomes. In final review, prioritize clean distinctions among governance, monitoring, cost, and security tools because this domain rewards precise categorization.
After completing a full mock exam, many learners look only at the percentage score. That is useful, but not sufficient. Your real goal is diagnosis. A score tells you your current level; a pattern tells you how to improve. Break your results down by the official domains and then by subtopics. For example, a low cloud concepts score may actually come from only two recurring errors: mixing up OpEx and CapEx, and misunderstanding shared responsibility. That is a much easier problem to fix than trying to restudy the entire domain.
Start by reviewing every missed item and placing it into one of three categories: knowledge gap, vocabulary confusion, or reading mistake. A knowledge gap means you truly did not know the concept. Vocabulary confusion means you know the idea but mixed up close terms such as availability zone and region, or Azure Policy and RBAC. A reading mistake means you ignored a keyword such as "estimate cost," "prevent deletion," or "dedicated private connection." This classification is powerful because each problem type has a different fix.
Exam Tip: If two answer choices both seem correct, look for the one that matches the exact verb in the question: estimate, monitor, enforce, authenticate, migrate, store, or analyze.
Your final revision priorities should be weighted, not equal. Focus first on high-frequency fundamentals that produce multiple points across the exam: cloud models, pricing concepts, shared responsibility, resource organization, compute choices, storage types, identity basics, policy versus locks versus RBAC, and monitoring versus health versus recommendations. Next, review any service families where you consistently choose answers that are technically related but not best fit. Finally, do a light scan of lower-frequency details.
Avoid the common trap of spending your final hours on obscure facts because they feel advanced. AZ-900 is a fundamentals exam. Strong candidates win by being consistently correct on broad essentials. If your mock score is already near your target, shift from memorization to decision discipline: slow down, identify the domain, underline keywords mentally, eliminate mismatched options, and trust the cleanest fit.
On exam day, your objective is to convert prepared knowledge into calm execution. AZ-900 is not won by last-minute cramming. It is won by clear thinking, careful reading, and steady pacing. Before the exam, make sure you know the logistics: registration details, identification requirements, testing environment rules, and whether you are testing online or at a center. Administrative stress can damage performance more than one missed study topic.
Your time management strategy should be simple. Move through the exam at a steady pace, answer what you can confidently, and avoid getting stuck on one item. Because AZ-900 questions are generally short, overthinking is a real danger. If a question seems confusing, identify the domain first. Is it cloud concepts, architecture and services, or governance? That framing often clarifies what Microsoft is really asking. Then look for keywords that point to the function being tested, such as cost estimation, authentication, private connectivity, compliance documentation, or automatic scaling.
Exam Tip: Read the last line of the question carefully before reviewing the answer choices. It helps you focus on the requirement instead of being distracted by familiar Azure terms in the options.
For confidence building, remember that you do not need expert-level administrator knowledge. You need foundational judgment. The exam expects recognition of core Azure services and concepts, not complex deployment steps. If you have completed full mock practice and reviewed your weak spots, you are already aligned with what the exam measures. During the test, avoid changing answers unless you spot a clear misread or a specific concept you initially overlooked. Second-guessing based on anxiety often lowers scores.
Your last-minute review should be light and structured. Skim a one-page sheet covering cloud models, service models, pricing concepts, resource hierarchy, core compute and storage options, identity basics, governance tools, monitoring tools, and security/compliance resources. Do not attempt to learn new material in the final hour. Instead, reinforce the distinctions that commonly create traps. Walk into the exam with a short mental checklist: identify the domain, find the keyword, eliminate mismatches, choose the best fit, and move on with confidence.
1. You are reviewing results from a full AZ-900 mock exam. A candidate repeatedly chooses Azure Policy when a question asks for assigning permissions to users so they can manage virtual machines. Which Azure concept should the candidate review to correct this weak spot?
2. A company wants to reduce exam-day mistakes by practicing how to identify the domain of each question before selecting an answer. During a mock exam, a question asks which pricing model avoids large upfront hardware purchases and instead uses ongoing service-based spending. Which concept should the candidate recognize?
3. A practice exam question states: 'A company needs to store unstructured data such as images, backups, and log files in Azure.' Which service is the best answer?
4. A company plans to move some applications to Azure but must keep other systems on-premises due to regulatory requirements. On the exam, which cloud model best matches this scenario?
5. During final review, a candidate notices they miss questions because they pick answers that are true Azure concepts but do not match the requirement. A new practice item asks: 'A company wants to enforce that resources can be created only in approved Azure regions.' Which Azure service should be selected?
- Learning Evolved.
- Intelligence Amplified.
