Question 829 of 1,170
Manage Azure Identities and GovernanceeasyMultiple ChoiceObjective-mapped

Quick Answer

The answer is the CanNotDelete lock on the resource group. This lock prevents deletion of the resource group and all resources within it, while still allowing read and update operations such as modifying VM sizes and tags, which perfectly meets the requirement to block deletions during a freeze without restricting needed updates. On the AZ-104 exam, this scenario tests your understanding of Azure lock levels and their practical application in governance scenarios like change freezes. A common trap is choosing ReadOnly, which would block all write operations including the required VM size changes, so remember that CanNotDelete is the middle ground—it stops removal but lets you keep working. For a memory tip, think of it as a “freeze but not a fossil”: you can still change things, you just can’t throw them away.

AZ-104 Manage Azure Identities and Governance Practice Question

This AZ-104 practice question tests your understanding of manage azure identities and governance. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

During a change freeze, administrators must prevent deletion of a production resource group and all resources inside it, but they still need to update VM sizes and tags. Which lock should be applied?

Question 1easymultiple choice
Full question →

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

CanNotDelete on the resource group

The CanNotDelete lock on the resource group prevents deletion of the resource group and all resources within it, while still allowing read and update operations such as modifying VM sizes and tags. This meets the requirement of blocking deletions during the change freeze without restricting updates. ReadOnly locks would block all write operations, including the needed updates.

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.

  • ReadOnly on the resource group

    Why it's wrong here

    ReadOnly blocks write operations, so it would also prevent the VM size and tag changes that must remain allowed.

  • CanNotDelete on the resource group

    Why this is correct

    CanNotDelete is the correct lock when you want to stop accidental deletion but still allow configuration changes. Applied at the resource group scope, it protects the group and the resources inside it from being deleted while still permitting updates such as resizing a VM or changing tags. That makes it ideal for a maintenance freeze.

    Related concept

    Read the scenario before looking for a memorised answer.

  • CanNotDelete on the management group

    Why it's wrong here

    That would protect far more than the single production resource group and could affect unrelated subscriptions.

  • An Azure Policy deny assignment

    Why it's wrong here

    Policy can enforce rules, but this question specifically asks for a lock that prevents deletion while allowing writes.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse CanNotDelete with ReadOnly, assuming that any lock will block updates, but CanNotDelete specifically allows modifications while only preventing deletion.

Detailed technical explanation

How to think about this question

Azure resource locks operate at the Azure Resource Manager (ARM) layer, applying to control plane operations (e.g., DELETE, PUT) but not to data plane operations. The CanNotDelete lock specifically blocks DELETE requests on the resource group and its child resources, while allowing PUT and PATCH requests for updates. This lock is inherited by all resources within the scope, so applying it at the resource group level ensures that no resource inside can be deleted, even if a user has Contributor or Owner permissions.

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

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

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.

Related practice questions

Related AZ-104 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-104 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-104 question test?

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: CanNotDelete on the resource group — The CanNotDelete lock on the resource group prevents deletion of the resource group and all resources within it, while still allowing read and update operations such as modifying VM sizes and tags. This meets the requirement of blocking deletions during the change freeze without restricting updates. ReadOnly locks would block all write operations, including the needed updates.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on AZ-104

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 production resource group contains web and data resources. Administrators must be able to update, scale, and restart resources, but they must not delete the resource group or any resource inside it during maintenance windows. Which two actions should the administrator take? Select two.

medium
  • A.Apply a CanNotDelete lock to the resource group.
  • B.Apply a ReadOnly lock to the resource group.
  • C.Apply a CanNotDelete lock only to the individual virtual machines.
  • D.Apply the lock at the resource group scope so it covers child resources.
  • E.Use tags to mark the resources as production and prevent deletion.

Why A: Option A is correct because applying a CanNotDelete lock to the resource group prevents the deletion of the resource group and all resources within it, while still allowing administrators to update, scale, and restart resources. This lock type blocks delete operations but permits read and update operations, which aligns with the requirement to perform maintenance actions without risking deletion. The lock is inherited by all child resources in the resource group, ensuring comprehensive protection.

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.

Loading comments…

Sign in to join the discussion.

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.