mediummulti selectObjective-mapped

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.

Question 1mediummulti select
Full question →

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.

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

Best answer

Apply a CanNotDelete lock to the resource group.

CanNotDelete blocks deletion while still allowing normal write operations such as updates and scaling. That makes it the right lock when the organization wants protection from accidental removal but still needs management access.

B

Distractor review

Apply a ReadOnly lock to the resource group.

ReadOnly blocks most write operations, which would interfere with updates, scaling, and other routine administration tasks. It is too restrictive for a production environment that still needs active maintenance.

C

Distractor review

Apply a CanNotDelete lock only to the individual virtual machines.

Locking only the virtual machines would leave the resource group itself and other resources deletable. The requirement is to protect the whole group and everything inside it during maintenance windows.

D

Best answer

Apply the lock at the resource group scope so it covers child resources.

Placing the lock on the resource group extends the protection to resources within that group. This is the cleanest way to prevent accidental deletion of the group or its contents while keeping the group manageable.

E

Distractor review

Use tags to mark the resources as production and prevent deletion.

Tags are useful for organization and reporting, but they do not enforce protection. They cannot block delete operations or change Azure behavior during maintenance windows.

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: Apply a CanNotDelete lock to the resource group. — The correct protection is a CanNotDelete lock at the resource group scope. This prevents accidental deletion of the group and its child resources while still allowing administrators to perform normal operational tasks such as updates, scaling, and restarts. ReadOnly is too restrictive because it blocks many legitimate changes. The question tests the practical difference between a protective lock and an overly restrictive one. Why others are wrong: ReadOnly blocks too much, individual resource locks are too narrow, and tags provide no enforcement at all. The key choice is between protecting against deletion and preserving day-to-day operations. CanNotDelete at the resource group scope achieves both.

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.