- A
Azure Policy with a Deny effect to block resource deletions.
Why wrong: Azure Policy can deny certain actions on resources based on properties, but it is not the most direct or straightforward feature for preventing accidental deletion of an entire resource group. Resource locks are designed specifically for this purpose and are simpler to apply.
- B
A Read-Only lock on the resource group.
Why wrong: A Read-Only lock prevents both modification and deletion. Since the scenario requires that authorized administrators can still update resources, a Read-Only lock would block those updates and is therefore incorrect.
- C
A Delete lock on the resource group.
A Delete lock prevents deletion of the resource group and its resources while allowing all other operations, including modifications. This directly addresses the requirement to prevent accidental deletion without hindering updates. Resource locks can be applied at the resource group level and only removed by users with Owner or User Access Administrator roles.
- D
An Azure RBAC role assignment that excludes the Delete action for all users.
Why wrong: While RBAC can be used to deny delete permissions, it requires creating a custom role and carefully managing assignments for all users. This approach is more complex and error-prone compared to applying a resource lock. Resource locks provide a simpler, more robust solution for this specific requirement.
Quick Answer
The answer is a Delete lock applied to the resource group. This Azure governance feature is correct because it prevents accidental deletion of Azure resources while still allowing authorized administrators with the Owner role to modify configurations and update the resources. A Delete lock specifically blocks any delete operation on the resource group and all its child resources, yet it does not restrict read or update actions, making it ideal for production environments where configuration changes must continue. On the Microsoft Azure Fundamentals AZ-900 exam, this scenario tests your understanding of Azure Resource Locks as a straightforward governance tool, often appearing as a distractor against role-based access control (RBAC) or Azure Policy—remember that RBAC controls who can act, while locks control what actions are allowed. A common trap is choosing a Read-only lock, which would block all modifications, not just deletions. Memory tip: think of a Delete lock as a “do not delete” sign that only the Owner can remove, keeping your production resources safe from accidental removal.
AZ-900 Describe Azure management and governance Practice Question
This AZ-900 practice question tests your understanding of describe azure management and governance. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 production resource group that contains several Azure virtual machines and a SQL database. The company wants to ensure that no user can accidentally delete these resources, but authorized administrators must still be able to modify the configuration and update the resources. The company needs a straightforward governance feature that can be applied directly to the resource group and can be removed only by an authorized user with the Owner role. Which Azure feature should the company use?
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
A Delete lock on the resource group.
A Delete lock on the resource group prevents users from deleting the resource group and its resources, while still allowing authorized administrators with the Owner role to modify configurations and update resources. This lock can only be removed by a user with the Owner role, meeting the requirement for a straightforward governance feature applied directly to the resource group.
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 with a Deny effect to block resource deletions.
Why it's wrong here
Azure Policy can deny certain actions on resources based on properties, but it is not the most direct or straightforward feature for preventing accidental deletion of an entire resource group. Resource locks are designed specifically for this purpose and are simpler to apply.
- ✗
A Read-Only lock on the resource group.
Why it's wrong here
A Read-Only lock prevents both modification and deletion. Since the scenario requires that authorized administrators can still update resources, a Read-Only lock would block those updates and is therefore incorrect.
- ✓
A Delete lock on the resource group.
Why this is correct
A Delete lock prevents deletion of the resource group and its resources while allowing all other operations, including modifications. This directly addresses the requirement to prevent accidental deletion without hindering updates. Resource locks can be applied at the resource group level and only removed by users with Owner or User Access Administrator roles.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
An Azure RBAC role assignment that excludes the Delete action for all users.
Why it's wrong here
While RBAC can be used to deny delete permissions, it requires creating a custom role and carefully managing assignments for all users. This approach is more complex and error-prone compared to applying a resource lock. Resource locks provide a simpler, more robust solution for this specific requirement.
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 a Deny effect policy is simpler or more appropriate, but Azure Policy is a governance and compliance tool, not a straightforward lock that can be easily toggled by an Owner without policy management overhead.
Trap categories for this question
Scenario analysis trap
A Read-Only lock prevents both modification and deletion. Since the scenario requires that authorized administrators can still update resources, a Read-Only lock would block those updates and is therefore incorrect.
Detailed technical explanation
How to think about this question
Azure resource locks operate at the Azure Resource Manager (ARM) layer, applying a deny on all delete or modify operations at the specified scope, overriding any role-based permissions. A Delete lock specifically blocks DELETE operations via the ARM REST API (e.g., `DELETE /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}`), while allowing PUT, PATCH, and POST operations for configuration changes. This lock is inherited by all child resources within the resource group, ensuring consistent protection without requiring individual resource configuration.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Describe Azure management and governance — study guide chapter
Learn the concepts, then practise the questions
- →
Describe Azure management and governance practice questions
Targeted practice on this topic area only
- →
All AZ-900 questions
1,031 questions across all exam domains
- →
Microsoft Azure Fundamentals AZ-900 study guide
Full concept coverage aligned to exam objectives
- →
AZ-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-900 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Describe cloud concepts practice questions
Practise AZ-900 questions linked to Describe cloud concepts.
Describe Azure architecture and services practice questions
Practise AZ-900 questions linked to Describe Azure architecture and services.
Describe Azure management and governance practice questions
Practise AZ-900 questions linked to Describe Azure management and governance.
AZ-900 Azure services practice questions
Practise AZ-900 questions linked to AZ-900 Azure services.
AZ-900 pricing and support practice questions
Practise AZ-900 questions linked to AZ-900 pricing and support.
AZ-900 security and compliance practice questions
Practise AZ-900 questions linked to AZ-900 security and compliance.
AZ-900 governance practice questions
Practise AZ-900 questions linked to AZ-900 governance.
Practice this exam
Start a free AZ-900 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-900 question test?
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: A Delete lock on the resource group. — A Delete lock on the resource group prevents users from deleting the resource group and its resources, while still allowing authorized administrators with the Owner role to modify configurations and update resources. This lock can only be removed by a user with the Owner role, meeting the requirement for a straightforward governance feature applied directly to the resource group.
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 →
Same concept, more angles
1 more ways this is tested on AZ-900
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. A company has an Azure subscription that contains production resources. The IT manager is concerned that a user who has the Contributor role might accidentally delete the entire subscription. The company wants a solution that prevents anyone from deleting the subscription, even users with the Owner role, while still allowing modifications to the resources inside the subscription. What should the administrator configure?
medium- A.Assign a custom role-based access control (RBAC) role that denies the delete action for all users.
- B.Configure an Azure Policy with the 'Deny' effect to block deletion of the subscription.
- ✓ C.Apply a resource lock of type 'Delete' at the subscription level.
- D.Apply a resource lock of type 'ReadOnly' at the subscription level.
Why C: Option C is correct because a resource lock of type 'Delete' at the subscription level prevents any user, including those with the Owner role, from deleting the subscription. This lock overrides all RBAC permissions, ensuring that while modifications to resources inside the subscription are still allowed, the subscription itself cannot be removed. This directly addresses the IT manager's concern about accidental deletion.
Last reviewed: Jun 11, 2026
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.