Why You Keep Choosing Wrong Between Similar Azure Services—And How to Stop
You’ve studied for the Microsoft Azure Administrator certification (AZ-104), yet when you encounter answer choices like “Azure App Service” vs. “Azure Container Instances” or “Role-Based Access Control (RBAC)” vs. “Azure AD groups,” your confidence collapses. The answers aren’t obviously wrong—they just feel close. This is the single largest confidence killer for candidates stuck between 65-75% on practice exams, and it stems from one core problem: you’re not yet distinguishing services by their architectural intent.
Direct Answer
The AZ-104 exam deliberately includes near-identical answer options that test whether you understand why you’d choose one Azure service over another in a specific operational context. The differences aren’t semantic—they’re functional: Role-Based Access Control (RBAC) assigns permissions to principals at resource scope, while Azure AD is the identity provider managing who those principals are. Virtual Networks (VNet) provide network isolation, while Network Security Groups (NSG) control traffic within that isolation. Storage Accounts provide scalable data persistence, while Key Vault manages secrets and encryption keys. The Microsoft Azure Administrator exam measures whether you can apply each service to its intended use case, not just name it. This is why similar-looking answers trap candidates who’ve memorized features without understanding operational purpose.
Why This Happens to Microsoft Azure Administrator Candidates
Most candidates approach Azure services as isolated features to memorize: “App Service runs web apps.” “Container Instances runs containers.” But the AZ-104 exam asks: “Where do you deploy this workload and why?” That’s a different question entirely.
When you see two answers that both technically could work, your brain freezes. You’re missing the operational constraint that makes one answer correct. Consider these real patterns from the exam:
RBAC vs. Azure AD confusion — Both control access. RBAC is the permission model (what can you do?), Azure AD is the identity system (who are you?). Candidates often reverse these. A scenario asking “Where do you assign role definitions to users?” is RBAC. A scenario asking “Where do you configure multi-factor authentication?” is Azure AD.
VNet vs. NSG confusion — Both relate to networking. VNet is the container (the isolated network address space). NSG is the filter (what traffic enters/exits). You need a VNet first, then add NSGs. A scenario asking “How do you create an isolated network for your VMs?” is VNet. A scenario asking “How do you block inbound port 3389?” is NSG.
Storage Account vs. Key Vault confusion — Both are secure containers. Storage Accounts hold data at scale (blobs, queues, tables, file shares). Key Vault holds secrets and encryption keys in HSM-backed vaults. A scenario asking “Where do you store application logs?” is Storage. A scenario asking “Where do you store database connection strings?” is Key Vault.
App Service vs. Container Instances confusion — Both run applications. App Service is a managed platform with scaling, deployment slots, and monitoring built in. Container Instances is a serverless container runtime with no scaling or orchestration. A scenario asking “How do you deploy a web app with staging slots?” is App Service. A scenario asking “How do you run a Docker container once?” is Container Instances.
The pattern: You’re seeing feature overlap instead of operational purpose. The exam tests purpose.
The Root Cause: Lack of Precision in Understanding Service Differentiators
Azure services aren’t designed in isolation. Microsoft built them to solve specific operational problems at different scales and management levels. When you skip the “why” and jump to “what,” you can’t distinguish them under pressure.
Here’s the cognitive trap: You’ve read that RBAC “controls access” and Azure AD “manages identities.” Both sentences are true. But they answer different questions:
- RBAC answers: “Given that this person exists, what can they do?”
- Azure AD answers: “How does this person prove who they are in the system?”
Without that distinction, both feel equally right when you’re scanning quickly under exam time pressure.
The same happens with VNet and NSG. You know:
- VNet = network isolation
- NSG = traffic filtering
But you haven’t internalized that VNets are the foundational layer and NSGs are the enforcement layer. If a scenario asks “You need to create an isolated network environment for HIPAA compliance,” a candidate who only memorized “NSG = security” might choose NSG. But the actual answer is VNet—because compliance isolation requires network segmentation first. NSG filtering is secondary.
This precision gap shows up in Storage Accounts vs. Key Vault too. A candidate who knows “both are secure” but hasn’t internalized the operational boundary—“Storage Accounts scale for data volume, Key Vault scales for secret rotation”—will guess randomly when a scenario asks which service supports automatic rotation of database credentials.
The root cause isn’t stupidity. It’s incomplete translation from feature knowledge to operational context. You need to know not just what each service does, but when you’d choose it over something similar.
How the Microsoft Azure Administrator Exam Actually Tests This
The AZ-104 exam uses scenario-driven questions that hide the service name and force you to identify the right tool based on operational constraints. The test vendor—Pearson VUE on behalf of Microsoft—is measuring whether you can translate a business requirement into an Azure architecture decision.
Notice the pattern in these real-world scenarios:
- You’re given a constraint (e.g., “HIPAA compliance,” “secret rotation,” “traffic filtering”)
- You’re given similar answer options (each one solves part of the problem)
- You must choose the option that solves the complete problem
The exam is deliberately testing your ability to disambiguate.
Here’s why Microsoft does this: An Azure Administrator job involves recommending and implementing services. If you recommend Key Vault for bulk data storage or App Service for a one-time container job, you’ve made a costly architectural error. The exam gatekeeps that mistake.
The testing logic is: “Can you see beyond feature overlap to operational purpose?” Candidates who can’t fail. Candidates who can pass.
Example scenario:
Your organization needs to ensure that database connection strings and API keys are never stored in application code. The strings must be rotatable without redeploying the application. Where should you store these values?
A) Azure Storage Account with blob encryption
B) Azure Key Vault with automatic rotation policy
C) Azure App Service configuration settings
D) Azure SQL Database Transparent Data Encryption
Why candidates get this wrong:
- Option A seems right because Storage Accounts are “secure.” They are—for data. But they don’t support automatic rotation or secret versioning. Wrong.
- Option C seems right because App Service manages configuration. It does—but it doesn’t support automatic rotation independent of deployment. Wrong.
- Option D seems right if you misread “database connection strings” as “database encryption.” TDE encrypts data at rest in SQL, not connection strings. Wrong.
- Option B is correct. Key Vault is purpose-built for secret rotation, versioning, and access policy enforcement. This is the operational boundary that separates it from Storage and App Service.
A candidate who memorized “Key Vault = secrets” would get this right. A candidate who knows “both Storage and Key Vault are secure” would guess. That’s the test.
How to Fix This Before Your Next Attempt
This is fixable in 2-3 weeks of targeted study. Here’s how:
1. Build a service differentiation matrix
Create a table with these services down the left (RBAC, Azure AD, VNet, NSG, Storage Accounts, App Service, Key Vault, Container Instances). Across the top, add columns: “Primary Use Case,” “Operational Boundary,” “What It Doesn’t Do.” Fill it out. Example:
| Service | Primary Use Case | Operational Boundary | What It Doesn’t Do |
|---|---|---|---|
| RBAC | Grant permissions to existing identities | Role definitions + resource scope | Authenticate users (Azure AD does that) |
| Azure AD | Manage identities + authentication | Identity provider + credential enforcement | Assign permissions (RBAC does that) |
| VNet | Create isolated network address space | Network segmentation layer | Filter traffic (NSG does that) |
| NSG | Filter traffic in/out of subnets | Rule-based traffic control | Isolate networks (VNet does that) |
| Key Vault | Rotate and version |