mediummultiple choiceObjective-mapped

A production resource group contains several VMs and a storage account. The operations manager wants to prevent accidental deletion of the resource group and its resources, but still allow normal configuration changes during maintenance windows. Which lock should be applied to the resource group?

Question 1mediummultiple choice
Full question →

A production resource group contains several VMs and a storage account. The operations manager wants to prevent accidental deletion of the resource group and its resources, but still allow normal configuration changes during maintenance windows. Which lock should be applied to the resource group?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Distractor review

ReadOnly lock at the resource group scope.

ReadOnly blocks write operations such as updates, which would interfere with routine maintenance. It would be too restrictive for a production group that still needs normal configuration changes.

B

Best answer

CanNotDelete lock at the resource group scope.

CanNotDelete is the correct lock when the goal is to prevent accidental removal while still allowing updates. It blocks delete operations for the resource group and its resources, but it does not stop normal configuration changes such as resizing, tagging, or network updates. That makes it suitable for production protection without freezing administration.

C

Distractor review

Azure Policy assignment that denies all delete requests.

Azure Policy can enforce configuration rules, but this scenario is specifically about a lock that protects a resource group from deletion. Policy is not the same mechanism as a management lock, and it would be more complex than needed here.

D

Distractor review

Apply the lock only to individual virtual machines.

Locking each VM would not cover the resource group itself or the storage account consistently. It also adds unnecessary management overhead compared with protecting the entire resource group with one lock.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-104 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: CanNotDelete lock at the resource group scope. — CanNotDelete is the lock used when administrators want to prevent accidental deletion but still allow normal changes. Applied at the resource group scope, it protects the group and the resources inside it from deletion while leaving write operations available. That balance is appropriate for production environments where maintenance changes must continue. Why others are wrong: ReadOnly is too restrictive because it blocks ordinary updates. Azure Policy is a governance tool, not the lock mechanism requested by the question. Locking individual resources is incomplete and harder to maintain than a single resource group lock. The requirement specifically matches CanNotDelete at the resource group scope.

What should I do if I get this AZ-104 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.