AZ-104 Manage Azure Identities and Governance Practice Question
This AZ-104 practice question tests your understanding of manage azure identities and governance. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Bicep snippet:
resource vm 'Microsoft.Compute/virtualMachines@2023-09-01' = {
name: 'appvm01'
location: resourceGroup().location
identity: {
type: 'SystemAssigned'
}
properties: {
hardwareProfile: {
vmSize: 'Standard_D2s_v5'
}
osProfile: {
computerName: 'appvm01'
}
}
}
Operational note:
- The VM is rebuilt every month from source control.
- The workload must read secrets from Key Vault and upload logs to Blob Storage.
- Recreating the VM must not require new role assignments for the workload identity.
Based on the exhibit, which change should the administrator make so the application identity remains stable across VM redeployments without reapplying RBAC assignments?
Exhibit
Bicep snippet:
resource vm 'Microsoft.Compute/virtualMachines@2023-09-01' = {
name: 'appvm01'
location: resourceGroup().location
identity: {
type: 'SystemAssigned'
}
properties: {
hardwareProfile: {
vmSize: 'Standard_D2s_v5'
}
osProfile: {
computerName: 'appvm01'
}
}
}
Operational note:
- The VM is rebuilt every month from source control.
- The workload must read secrets from Key Vault and upload logs to Blob Storage.
- Recreating the VM must not require new role assignments for the workload identity.
A
Keep the system-assigned identity and reapply the same RBAC roles after each rebuild.
Why wrong: A system-assigned identity is recreated with the VM, so its object ID changes after redeployment. That forces RBAC updates every time.
B
Create a user-assigned managed identity and attach it to the VM template.
A user-assigned managed identity is an independent Azure resource. It survives VM deletion and redeployment, so RBAC assignments remain valid.
C
Store a local administrator password in Key Vault and use it for Azure resource access.
Why wrong: A local administrator password helps sign in to the VM, but it does not provide Azure authorization for Key Vault or Storage access.
D
Replace the identity with a shared access signature so the VM can authenticate to Azure services.
Why wrong: A SAS token is scoped to a storage resource and is not a general-purpose identity for Azure resource authorization or RBAC.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a user-assigned managed identity and attach it to the VM template.
A user-assigned managed identity is decoupled from the VM lifecycle, so it persists independently of VM redeployments. By attaching the same user-assigned identity to the new VM instance, the application retains its Azure AD object ID and all existing RBAC role assignments remain valid without requiring reapplication.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Keep the system-assigned identity and reapply the same RBAC roles after each rebuild.
Why it's wrong here
A system-assigned identity is recreated with the VM, so its object ID changes after redeployment. That forces RBAC updates every time.
When this WOULD be correct
If the question asked for a solution that automatically reapplies RBAC roles after each rebuild (e.g., via automation scripts), keeping the system-assigned identity and reapplying roles could be acceptable, though not ideal.
✓
Create a user-assigned managed identity and attach it to the VM template.
Why this is correct
A user-assigned managed identity is an independent Azure resource. It survives VM deletion and redeployment, so RBAC assignments remain valid.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store a local administrator password in Key Vault and use it for Azure resource access.
Why it's wrong here
A local administrator password helps sign in to the VM, but it does not provide Azure authorization for Key Vault or Storage access.
✗
Replace the identity with a shared access signature so the VM can authenticate to Azure services.
Why it's wrong here
A SAS token is scoped to a storage resource and is not a general-purpose identity for Azure resource authorization or RBAC.
When this WOULD be correct
When the question asks for a method to grant a client application time-limited access to a specific Azure Storage blob or container without exposing the storage account key, and the access does not need to persist across VM redeployments or involve RBAC.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.
✓Create a user-assigned managed identity and attach it to the VM template.Correct answer▾
Why this is correct
A user-assigned managed identity is an independent Azure resource. It survives VM deletion and redeployment, so RBAC assignments remain valid.
✗Keep the system-assigned identity and reapply the same RBAC roles after each rebuild.Wrong answer — click to see why▾
Why this is wrong here
System-assigned identity is tied to the VM lifecycle; redeploying the VM creates a new identity, requiring RBAC reassignment. This does not keep the identity stable.
★ When this WOULD be the correct answer
If the question asked for a solution that automatically reapplies RBAC roles after each rebuild (e.g., via automation scripts), keeping the system-assigned identity and reapplying roles could be acceptable, though not ideal.
Why candidates choose this
Candidates may think system-assigned identity is simpler and that reapplying roles is a minor overhead, overlooking that the identity itself changes on redeployment.
✗Replace the identity with a shared access signature so the VM can authenticate to Azure services.Wrong answer — click to see why▾
Why this is wrong here
A shared access signature (SAS) is used for delegated access to specific Azure storage resources, not for VM identity. It cannot provide a stable application identity across VM redeployments and does not support RBAC assignments.
★ When this WOULD be the correct answer
When the question asks for a method to grant a client application time-limited access to a specific Azure Storage blob or container without exposing the storage account key, and the access does not need to persist across VM redeployments or involve RBAC.
Why candidates choose this
Candidates may confuse SAS with managed identities because both provide authentication without storing credentials, but SAS is for storage access only and lacks the identity stability and RBAC integration required for this scenario.
Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse system-assigned and user-assigned managed identities, assuming both persist across VM redeployments, but only user-assigned identities survive VM deletion because they are separate Azure resources.
Detailed technical explanation
How to think about this question
User-assigned managed identities are created as standalone Azure resources in Azure AD, with their own service principal and object ID. When attached to a VM, the Azure Instance Metadata Service (IMDS) endpoint provides tokens for that identity, and because the identity resource exists independently, it can be attached to a new VM after redeployment, preserving all pre-configured RBAC assignments. This decoupling is critical in scenarios like Azure Virtual Machine Scale Sets or autoscaling where instances are frequently replaced.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Quick reference
Access Control Model Comparison
Model
Acronym
Who Controls Access?
Best For
Discretionary Access Control
DAC
Resource owner
Small teams, file shares
Mandatory Access Control
MAC
System / security labels
Classified govt / military
Role-Based Access Control
RBAC
Administrator (via roles)
Enterprise environments
Attribute-Based Access Control
ABAC
Policy engine (user + resource attributes)
Fine-grained, dynamic policies
Rule-Based Access Control
RuBAC
System rules / ACLs
Firewall rules, network ACLs
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Manage Azure Identities and Governance — This question tests Manage Azure Identities and Governance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a user-assigned managed identity and attach it to the VM template. — A user-assigned managed identity is decoupled from the VM lifecycle, so it persists independently of VM redeployments. By attaching the same user-assigned identity to the new VM instance, the application retains its Azure AD object ID and all existing RBAC role assignments remain valid without requiring reapplication.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.