hardmulti selectObjective-mapped

A resource group has a ReadOnly lock applied to it. An operator can view the resources, but several portal changes fail. Which two operations will fail because of the lock? Select two.

Question 1hardmulti select
Full question →

A resource group has a ReadOnly lock applied to it. An operator can view the resources, but several portal changes fail. Which two operations will fail because of the lock? 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

Changing the size of an existing virtual machine in the resource group will fail because it is a write operation.

Resizing a VM modifies the resource configuration, so it is a write action. A ReadOnly lock blocks all write operations at the locked scope and below, which means even an otherwise valid size change is rejected while the lock remains in place.

B

Best answer

Deleting a storage account in the resource group will fail because deletion is also blocked by ReadOnly.

ReadOnly locks prevent deletions as well as updates and creations. Deleting a storage account changes the resource state, so the request is denied at the locked scope. This is one reason ReadOnly locks are disruptive and are used only when strict protection is necessary.

C

Distractor review

Reading the resource group's activity log will fail because lock-protected scopes cannot be queried.

Locks do not block read operations. Viewing logs, properties, or inventory remains allowed because the lock is specifically about preventing changes, not preventing observation. This distractor confuses access restrictions with control-plane write protection.

D

Distractor review

Listing the resources in the resource group with Azure CLI will fail because enumeration is a write operation.

Listing resources is a read-only management operation and is not blocked by a ReadOnly lock. The lock prevents create, update, and delete actions, but it does not stop inventory or discovery commands. That makes this option incorrect.

E

Distractor review

Fetching the current VM configuration from the ARM API will fail because reads are denied by the lock.

ARM reads are still allowed under a ReadOnly lock. You can inspect current state, but you cannot modify it. This option reverses the actual behavior of the lock and is therefore incorrect.

Common exam trap

Common exam trap: ACLs stop at the first match

ACLs are processed top to bottom. The first matching entry wins, and an implicit deny usually exists at the end.

Technical deep dive

How to think about this question

ACL questions test precision: source, destination, protocol, port and direction. A generally correct ACL can still fail if it is applied on the wrong interface or in the wrong direction.

KKey Concepts to Remember

  • Standard ACLs match source addresses.
  • Extended ACLs can match source, destination, protocol and ports.
  • The first matching ACL entry is used.
  • There is usually an implicit deny at the end.

TExam Day Tips

  • Check inbound versus outbound direction.
  • Read the ACL from top to bottom.
  • Look for a broader permit or deny above the intended line.

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?

Standard ACLs match source addresses.

What is the correct answer to this question?

The correct answer is: Changing the size of an existing virtual machine in the resource group will fail because it is a write operation. — A ReadOnly lock blocks write operations at the locked scope and child scopes. Changing a VM size and deleting a storage account both require write or delete operations, so both fail. Viewing logs, listing resources, and reading configuration remain allowed because the lock is designed to protect state, not hide information. This distinction is important for troubleshooting locked resources. Why others are wrong: The other options are read-only actions, and read access is still permitted under a ReadOnly lock. The lock is strict for changes, but it does not block viewing logs, listing resources, or reading ARM state.

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.