cert-bank

Guides

이 글을 한국어로 읽기

Seven Mistakes That Repeat Across the Azure Exams, from AZ-900 to AI-103

We have written 1,644 practice questions for seven Microsoft Azure exams: AZ-900, AZ-104, AZ-305, SC-900, DP-900, AI-901 and AI-103. Each one comes with an explanation of why every wrong option is wrong. Read side by side, the topics change from exam to exam but the mistakes do not: the same seven confusions turn up in governance, database and AI agent questions. This article describes each one, shows where it appears, and gives the clue in the stem that exposes it.

Common mistakes · Microsoft Azure certifications (AZ-900, AZ-104, AZ-305, SC-900, DP-900, AI-901, AI-103)

Seven Mistakes That Repeat Across the Azure Exams, from AZ-900 to AI-103

Mistake: trusting a name that has changed, or a feature that has ended

Microsoft renames and retires products often; the exams use current names, and every study guide says that most questions cover generally available (GA) features. In our explanations, a retirement comes up in 61 questions and preview status in 70 (44 of those in AI-103). Distractors look attractive precisely because they were the right answer a year or two ago.

Old or endedWhat the exam expects
Azure AD, Azure AI Foundry, Azure AI services, content filtersMicrosoft Entra ID, Microsoft Foundry, Foundry Tools, guardrails
Basic Load Balancer, Basic public IPRetired; Standard SKUs, which support zones
Azure BlueprintsRetiring (a preview, final retirement 31 January 2027); deployment stacks and template specs
Azure Database for MariaDBOn the retirement path; migrate to Azure Database for MySQL
Azure OpenAI On Your Data, dall-e-3Retired; classic RAG or Foundry IQ, GPT-image models

The clue: two options both work, and one of them uses a service you remember from older material. If a requirement says "production" or "new solution", the preview or retiring option is usually the wrong one.

Mistake: asking "who may do it" when the question is "what may exist"

Azure has three governance tools that answer three different questions. Azure RBAC decides who may act. Azure Policy decides what resources may look like, whoever creates them: allowed regions, allowed sizes, required tags. Resource locks stop deletion or change for everyone, Owners included. Policy and RBAC are set against each other in 21 of our explanations, 13 of them in AZ-900, and locks are a regular distractor from AZ-900 to AZ-305. Tags add a fourth trap: resources do not inherit tags from their resource group; a policy has to copy them.

The clue: if the requirement is about a property of the resource (region, SKU, tag), the answer is Policy, even when the options offer a tightly scoped role.

Going deeper: a lock protects the resource, not the data in it

Azure separates the control plane, requests to Azure Resource Manager that create, change or delete a resource, from the data plane, requests to the service itself, such as running SQL against a database or uploading a blob. Locks apply only to the control plane. A ReadOnly lock on a logical SQL server stops anyone deleting the server, but rows in its databases can still be inserted and deleted; a lock on a storage account does not stop a blob being deleted. Some calls that look like reads are control plane POST requests, so a ReadOnly lock blocks them too: listing a storage account's keys, or starting a VM. That one detail explains a well-known puzzle: with a ReadOnly lock in place, the portal cannot fetch the account key, falls back to the user's Entra identity, and an Owner without a data role suddenly cannot see the blobs. To protect data, use data features: permissions, soft delete, backups, immutability.

Mistake: one role system expected to cover everything

There are two role systems and several planes. Microsoft Entra roles (Global Administrator, User Administrator) manage the directory: users, groups, passwords, app registrations. Azure RBAC roles (Owner, Contributor, Reader) manage Azure resources. And within Azure RBAC, management roles do not grant data access: Contributor on a storage account cannot read a blob with Entra authentication; that takes a data role such as Storage Blob Data Reader. The same split appears in AI-103: the Foundry User role is what lets a developer build and call in a project, and Reader cannot call agents.

The clue: "has Contributor but gets access denied" or "is Global Administrator but cannot manage the VM" almost always means the wrong system or the wrong plane, not a missing permission inside the right one.

Beginner tip: open the Access control (IAM) blade of a storage account in the Azure portal, choose "Add role assignment", and type "Storage Blob" into the search box. Then do the same on a subscription and search for "Global Administrator": it is not there, because it is not an Azure RBAC role. Seeing which roles exist where takes two minutes and settles a whole family of questions across AZ-900, AZ-104, SC-900 and AZ-305.

Mistake: a tool that detects chosen for a job that needs enforcing

Microsoft Entra ID Protection calculates sign-in and user risk; Conditional Access is the engine that blocks or requires MFA based on that risk (SC-900 explanations draw this line in 12 questions). Defender for Cloud recommends configuration fixes; a Policy deny effect blocks the bad resource. Audit records who did what; it blocks nothing. In the AI exams the same mistake takes another form: a line in the system message such as "never reveal personal data" only steers the model, while guardrails enforce on input and output, and "only use this user's documents" is enforced by a filter in the search query, not by instructions.

The clue: words such as "must never", "block", "prevent" or "ensure" need a control that enforces. Words such as "identify", "report" or "be alerted" point to a tool that detects.

Mistake: a copy taken for a way to keep running

Azure Backup keeps recovery points so you can restore; for a VM the RPO is hours (backups at most every 4 hours). Azure Site Recovery replicates VMs so you can fail over, with an RPO of minutes. For Azure SQL, geo-restore rebuilds a database from backups (slow, new endpoint), active geo-replication keeps readable secondaries per database, and a failover group moves databases together behind listeners whose names do not change. Our AZ-104 and AZ-305 explanations contrast Backup and Site Recovery in 14 questions. The reverse mistake also appears: replication faithfully copies deletions and corruption, so it never replaces backups.

The clue: read the two numbers first. An RPO in hours with a day of downtime allowed is a backup question; minutes is a replication question; "the connection string must not change" is a failover group.

Mistake: "private" read too loosely

A service endpoint lets a subnet reach a service such as Storage or SQL over the Microsoft backbone, but the resource keeps its public endpoint and on-premises clients cannot use it. A private endpoint gives one specific resource a private IP address in your virtual network, reachable over peering, VPN and ExpressRoute, and the public endpoint can be switched off. Both appear as options in the same AZ-104 and AZ-305 questions.

The clue: "from on-premises", "disable public access" or "prevent data exfiltration to other accounts" all point to a private endpoint.

Mistake: the name you see is not the name the code uses

In Microsoft Foundry, a model in the catalog does nothing until you deploy it, and the deployment can have its own name. In code, the model parameter takes the deployment name, not the catalog name of the model. Our AI-901 and AI-103 explanations rely on this in 23 questions, usually as a "model not found" or 404 error that looks like a permissions problem. A close relative in AI-103: the resource's openai.azure.com/openai/v1 endpoint and the project endpoint under services.ai.azure.com serve different APIs, so a correct credential at the wrong endpoint still fails.

The clue: an error that names a model or a path, while authentication is known to work, is about names and endpoints, not about roles.

Going deeper: why the same confusions cross exams

These seven mistakes are not seven facts; they are four boundaries that Azure draws everywhere. Control plane against data plane (locks, RBAC data roles, Foundry roles). Detection against enforcement (ID Protection and Conditional Access, Defender for Cloud and Policy, system messages and guardrails). A copy against a running replica (Backup and Site Recovery, geo-restore and failover groups). A name or address against the thing it points to (deployment names, endpoints, private endpoints). Once you can say which side of a boundary an option sits on, you can often eliminate it even on a topic you know only loosely.

Which Azure mistake is the stem setting up?
Is the requirement a property of the resource: region, SKU or tag?
YES →
Azure Policy, not a tightly scoped role
↓ no
Does it say "must never", "block", "prevent" or "ensure"?
YES →
A control that enforces, not one that detects
↓ no
Is the RPO in minutes rather than hours?
YES →
Replication (Site Recovery), not Backup
↓ no
Must the connection string not change after failover?
YES →
A failover group
↓ no
"From on-premises" or "disable public access"?
YES →
A private endpoint, not a service endpoint
↓ no
Has Contributor or Global Administrator but gets access denied?
YES →
Wrong role system or wrong plane
↓ no
OTHERWISE →
Model or path error while authentication works: check deployment names and endpoints
Read the stem from the top: the first clue that matches names the trap and the answer it points to.

How to use this list

After each practice set, label every question you missed with one of the seven mistakes, or "new fact" if none fits. If most of your misses carry a label, more reading will help less than slowing down on the stem: find the verb, the constraint and the number before you look at the options.

Practise

Practise in the question bank: every question explains each option, right and wrong. Start with the domain you just studied, then take a timed mock exam.

Based on the explanations in our practice sets, which follow Microsoft Learn. Product names, retirement dates and exam content change; check each exam's official study guide on Microsoft Learn.