- A
Use Azure RBAC for Key Vault with role assignments scoped per team: Key Vault Secrets Officer for DevOps, Key Vault Secrets User for the app team, and Key Vault Reader for auditing
RBAC assignments are integrated with Azure's identity and access management plane. All access decisions are logged in Azure Activity Log, fulfilling the audit requirement. Roles can be assigned at vault scope or narrower scopes. RBAC policies are managed centrally in Azure IAM, consistent with how all other Azure resources are governed.
- B
Create separate access policies for each team with the minimum required permissions
Why wrong: Access policies are a flat list at the vault level. They cannot be scoped to individual secrets. All policy assignments apply to the entire vault. Access policies are not integrated into Azure Activity Log as a unified RBAC audit trail — they have their own, separate logging mechanism.
- C
Create a separate Key Vault per team to enforce isolation between access levels
Why wrong: Using separate vaults for access isolation multiplies management overhead (key rotation, backup, monitoring, cost) without providing the per-operation granularity that RBAC roles offer within a single vault.
- D
Issue shared access signatures for each team scoped to the operations they need
Why wrong: Key Vault does not support SAS tokens. SAS is a feature of Azure Storage. Key Vault access is controlled exclusively through Azure AD identity-based permissions — access policies or RBAC.
AZ-204 Practice Question: Key Vault RBAC vs access policies for multi-team…
This AZ-204 practice question tests your understanding of implement azure security. 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. A key principle to apply: key Vault RBAC. 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.
Multiple teams need different levels of access to the same Azure Key Vault: the DevOps team needs to create and rotate secrets, the application team needs read-only secret access, and the auditing team needs list-only access. The security team wants audit logs of all access decisions and the ability to manage permissions through a single system. What access model should the developer recommend?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Use Azure RBAC for Key Vault with role assignments scoped per team: Key Vault Secrets Officer for DevOps, Key Vault Secrets User for the app team, and Key Vault Reader for auditing
Option A is correct because Azure RBAC for Key Vault provides a unified, centralized access management system that meets all requirements. The Key Vault Secrets Officer role allows DevOps to create and rotate secrets, the Key Vault Secrets User role grants read-only access to the application team, and the Key Vault Reader role provides list-only access for auditing. Additionally, RBAC integrates with Azure Monitor to deliver audit logs of all access decisions, satisfying the security team's need for a single management plane.
Key principle: Key Vault RBAC
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Azure RBAC for Key Vault with role assignments scoped per team: Key Vault Secrets Officer for DevOps, Key Vault Secrets User for the app team, and Key Vault Reader for auditing
Why this is correct
RBAC assignments are integrated with Azure's identity and access management plane. All access decisions are logged in Azure Activity Log, fulfilling the audit requirement. Roles can be assigned at vault scope or narrower scopes. RBAC policies are managed centrally in Azure IAM, consistent with how all other Azure resources are governed.
Related concept
Key Vault RBAC
- ✗
Create separate access policies for each team with the minimum required permissions
Why it's wrong here
Access policies are a flat list at the vault level. They cannot be scoped to individual secrets. All policy assignments apply to the entire vault. Access policies are not integrated into Azure Activity Log as a unified RBAC audit trail — they have their own, separate logging mechanism.
- ✗
Create a separate Key Vault per team to enforce isolation between access levels
Why it's wrong here
Using separate vaults for access isolation multiplies management overhead (key rotation, backup, monitoring, cost) without providing the per-operation granularity that RBAC roles offer within a single vault.
- ✗
Issue shared access signatures for each team scoped to the operations they need
Why it's wrong here
Key Vault does not support SAS tokens. SAS is a feature of Azure Storage. Key Vault access is controlled exclusively through Azure AD identity-based permissions — access policies or RBAC.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse the older Key Vault access policies (which are vault-specific and lack centralized audit integration) with Azure RBAC, or incorrectly assume that SAS tokens can be applied to Key Vault, when in fact SAS is exclusive to Azure Storage services.
Detailed technical explanation
How to think about this question
Azure RBAC for Key Vault uses Azure Active Directory (Azure AD) to authenticate and authorize principals, with built-in roles like Key Vault Secrets Officer (which includes write, delete, and rotate permissions) and Key Vault Secrets User (which includes get and list permissions). Under the hood, RBAC decisions are logged via Azure Monitor's activity logs and diagnostic settings, enabling the security team to audit all access attempts. In a real-world scenario, this model simplifies compliance by allowing the security team to assign roles at the subscription or resource group level, ensuring consistent permissions across multiple Key Vaults without per-vault policy management.
KKey Concepts to Remember
- Key Vault RBAC
- Key Vault access policies
- least privilege
- centralized access management
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
Key Vault RBAC
Real-world example
How this comes up in practice
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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 |
What to study next
Got this wrong? Here's your next step.
Review key Vault RBAC, then practise related AZ-204 questions on the same topic to reinforce the concept.
- →
Implement Azure security — study guide chapter
Learn the concepts, then practise the questions
- →
Implement Azure security practice questions
Targeted practice on this topic area only
- →
All AZ-204 questions
997 questions across all exam domains
- →
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
- →
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-204 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Develop Azure compute solutions practice questions
Practise AZ-204 questions linked to Develop Azure compute solutions.
Develop for Azure storage practice questions
Practise AZ-204 questions linked to Develop for Azure storage.
Implement Azure security practice questions
Practise AZ-204 questions linked to Implement Azure security.
Connect to and consume Azure services and third-party services practice questions
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Monitor, troubleshoot, and optimize Azure solutions practice questions
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
AZ-204 fundamentals practice questions
Practise AZ-204 questions linked to AZ-204 fundamentals.
AZ-204 scenario practice questions
Practise AZ-204 questions linked to AZ-204 scenario.
AZ-204 troubleshooting practice questions
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Start a free AZ-204 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-204 question test?
Implement Azure security — This question tests Implement Azure security — Key Vault RBAC.
What is the correct answer to this question?
The correct answer is: Use Azure RBAC for Key Vault with role assignments scoped per team: Key Vault Secrets Officer for DevOps, Key Vault Secrets User for the app team, and Key Vault Reader for auditing — Option A is correct because Azure RBAC for Key Vault provides a unified, centralized access management system that meets all requirements. The Key Vault Secrets Officer role allows DevOps to create and rotate secrets, the Key Vault Secrets User role grants read-only access to the application team, and the Key Vault Reader role provides list-only access for auditing. Additionally, RBAC integrates with Azure Monitor to deliver audit logs of all access decisions, satisfying the security team's need for a single management plane.
What should I do if I get this AZ-204 question wrong?
Review key Vault RBAC, then practise related AZ-204 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
Key Vault RBAC
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 →
Keep practising
More AZ-204 practice questions
- An app must store relational state and perform transactions across multiple tables with T-SQL support. Which Azure data…
- You are monitoring an Azure App Service using Application Insights. You notice that the server response time is high for…
- Which TWO services can be used to implement a publish-subscribe messaging pattern in Azure?
- You need to monitor the CPU utilization of an Azure VM in real-time and set up an alert when it exceeds 90%. Which Azure…
- You are monitoring an Azure web application with Application Insights. You notice a sudden increase in the number of fai…
- You are monitoring an Azure web app using Application Insights. You need to create a query that returns the average dura…
Last reviewed: Jun 11, 2026
This AZ-204 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-204 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.