The answer is Azure Resource Locks, the feature designed to prevent accidental deletion of Azure resources and safeguard critical infrastructure from unintended changes. This is correct because Resource Locks operate at the subscription, resource group, or individual resource level, enforcing either a CanNotDelete lock—which blocks deletion while still permitting modifications—or a ReadOnly lock, which prevents both deletion and modification entirely. On the Microsoft Azure Fundamentals AZ-900 exam, this concept tests your understanding of governance and protection mechanisms, often appearing in scenario-based questions where you must choose the right tool to secure a production database or virtual machine from human error. A common trap is confusing Resource Locks with Role-Based Access Control (RBAC); remember that locks override all permissions, even for the Owner role, making them a final safety net. For a quick memory tip, think of a padlock on a door: CanNotDelete locks the door shut but lets you paint it, while ReadOnly locks it completely and throws away the key.
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.
Which Azure feature allows you to prevent accidental deletion or modification of critical Azure resources?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Resource Locks
Azure Resource Locks are designed to prevent accidental deletion or modification of critical Azure resources by applying a lock at the subscription, resource group, or resource level. There are two types: CanNotDelete (prevents deletion but allows modifications) and ReadOnly (prevents both deletion and modification). This directly addresses the scenario of protecting resources from unintended changes.
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 RBAC
Why it's wrong here
RBAC controls who can perform actions; Resource Locks additionally prevent even authorized users from deleting or modifying.
✗
Azure Policy
Why it's wrong here
Policy enforces compliance rules at deployment; it does not prevent modification of existing resources.
✓
Azure Resource Locks
Why this is correct
Resource Locks prevent accidental deletion or modification by overriding user permissions for those specific operations.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Blueprints
Why it's wrong here
Blueprints define repeatable environments; they do not protect deployed resources from modification.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Azure Policy (which enforces rules during creation) with Resource Locks (which protect existing resources from deletion/modification), or they assume RBAC alone is sufficient to prevent accidental changes by authorized users.
Detailed technical explanation
How to think about this question
Resource Locks are implemented as a deny-only authorization that overrides any RBAC permissions, meaning even an Owner cannot delete a resource with a CanNotDelete lock without first removing the lock. Locks are inherited from parent scopes (e.g., a lock on a resource group applies to all child resources), and they are evaluated during Azure Resource Manager (ARM) API calls, returning a 403 Forbidden error if a locked resource is targeted for deletion or modification. A real-world scenario is locking a production database server to prevent accidental deletion during maintenance windows.
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: Azure Resource Locks — Azure Resource Locks are designed to prevent accidental deletion or modification of critical Azure resources by applying a lock at the subscription, resource group, or resource level. There are two types: CanNotDelete (prevents deletion but allows modifications) and ReadOnly (prevents both deletion and modification). This directly addresses the scenario of protecting resources from unintended changes.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. Which Azure security feature prevents accidental deletion of a critical production resource group?
medium
A.Assigning Reader role to all users
✓ B.Applying a CanNotDelete resource lock to the resource group
C.Setting an Azure Policy to deny resource group deletion
D.Enabling Azure Backup for the resource group
Why B: A CanNotDelete resource lock prevents any user or process from deleting the resource group, regardless of their permissions (including Owner). This is the correct mechanism to guard against accidental deletion of critical production resources because it overrides role-based access control (RBAC) permissions for delete operations.
Last reviewed: Jun 11, 2026
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.
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.