The answer is Azure Resource Locks, which are the correct feature to prevent accidental deletion or modification of critical resources, even for users with Contributor or Owner permissions. Resource Locks work by applying a setting at the resource, resource group, or subscription level that overrides any role-based access control (RBAC) permissions, with two lock types: CanNotDelete prevents deletion but allows changes, while ReadOnly blocks both deletion and modification entirely. On the AZ-900 exam, this concept tests your understanding of how governance tools complement RBAC—a common trap is confusing locks with Azure Policy or role assignments, but remember that locks are a simple on/off safety switch, not a rule or permission. A useful memory tip is to think of a padlock icon: once locked, even the owner needs to remove the lock first before making changes, making it the ultimate safeguard for production environments.
AZ-900 Describe Azure management and governance Practice Question
This AZ-900 practice question tests your understanding of describe azure management 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.
A company has a critical Azure resource group that contains production resources. They want to ensure that no one can accidentally delete or modify the resources in this group, even if they have Contributor permissions. Which Azure feature should they use?
Why wrong: Azure Policy enforces compliance rules but does not prevent deletion or modification when a user has Contributor role; it audits or denies based on conditions.
B
Role-Based Access Control (RBAC)
Why wrong: RBAC manages who can perform actions, but a Contributor can delete resources. RBAC alone cannot prevent a user with that role from deleting.
C
Resource Locks
Resource Locks prevent any user, regardless of their RBAC role, from deleting or modifying resources (depending on lock type: Delete or ReadOnly).
D
Management Groups
Why wrong: Management groups organize subscriptions; they do not provide locks on resources.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Resource Locks
Resource Locks are the correct choice because they provide a way to prevent accidental deletion or modification of critical Azure resources by applying a lock at the resource, resource group, or subscription level. Even users with Contributor or Owner permissions are blocked from performing delete or modify operations when a lock is set to 'CanNotDelete' or 'ReadOnly'. This ensures that production resources are protected beyond the permissions granted by RBAC.
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.
✗
Azure Policy
Why it's wrong here
Azure Policy enforces compliance rules but does not prevent deletion or modification when a user has Contributor role; it audits or denies based on conditions.
✗
Role-Based Access Control (RBAC)
Why it's wrong here
RBAC manages who can perform actions, but a Contributor can delete resources. RBAC alone cannot prevent a user with that role from deleting.
✓
Resource Locks
Why this is correct
Resource Locks prevent any user, regardless of their RBAC role, from deleting or modifying resources (depending on lock type: Delete or ReadOnly).
Related concept
Read the scenario before looking for a memorised answer.
✗
Management Groups
Why it's wrong here
Management groups organize subscriptions; they do not provide locks on resources.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Azure Policy with Resource Locks, thinking Policy can prevent deletion, but Policy only audits or enforces configuration rules, not operational actions like delete or modify.
Detailed technical explanation
How to think about this question
Resource Locks are applied as a deny override on top of RBAC permissions, using the Azure Resource Manager (ARM) authorization system. When a lock is set, ARM evaluates it during the authorization check, and any operation that would violate the lock is denied with an HTTP 403 Forbidden error, even if the user has an RBAC role that allows the action. This is particularly useful in production environments where a user with Contributor rights might accidentally delete a resource group, as the lock prevents the delete operation at the ARM level regardless of the user's role.
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 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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-900 question in full detail.
Describe Azure management and governance — This question tests Describe Azure management and governance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Resource Locks — Resource Locks are the correct choice because they provide a way to prevent accidental deletion or modification of critical Azure resources by applying a lock at the resource, resource group, or subscription level. Even users with Contributor or Owner permissions are blocked from performing delete or modify operations when a lock is set to 'CanNotDelete' or 'ReadOnly'. This ensures that production resources are protected beyond the permissions granted by RBAC.
What should I do if I get this AZ-900 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-900 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-900 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.