Question 682 of 1,170
Manage Azure Identities and GovernancehardMultiple SelectObjective-mapped

Quick Answer

The answer is that changing the size of an existing virtual machine and deleting a storage account will both fail under a ReadOnly lock on a resource group. This is because a ReadOnly lock explicitly blocks all write and delete operations at the scope it is applied, while leaving read operations like viewing resources or listing properties fully functional. Resizing a VM modifies its configuration, making it a write operation, and deleting a storage account is a delete operation—both are prohibited by the lock. On the AZ-104 exam, this question tests your understanding of Azure lock inheritance and scope; a common trap is assuming ReadOnly only prevents edits to the lock itself or that it allows deletions. Remember the memory tip: “ReadOnly locks read, but block write and delete—so if you’re changing or removing, it’s a no-go.”

AZ-104 Manage Azure Identities and Governance Practice Question

This AZ-104 practice question tests your understanding of manage azure identities 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 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 →

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

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

A is correct because changing the size of an existing virtual machine is a write operation that modifies the VM's configuration. A ReadOnly lock on the resource group prevents all write and delete operations, so any attempt to resize the VM will fail. The lock does not affect read operations, which remain functional.

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.

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

    Why this is correct

    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.

    Related concept

    Read the scenario before looking for a memorised answer.

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

    Why this is correct

    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.

    Related concept

    Read the scenario before looking for a memorised answer.

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

    Why it's wrong here

    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.

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

    Why it's wrong here

    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.

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

    Why it's wrong here

    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 traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse ReadOnly locks with read-only permissions, incorrectly assuming that all read operations (like listing resources or fetching configurations) are also blocked, when in fact only write and delete operations are denied.

Trap categories for this question

  • Similar concept trap

    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.

  • Command / output trap

    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.

Detailed technical explanation

How to think about this question

Under the hood, Azure Resource Manager locks are applied at the management plane level, using Azure RBAC to deny all write and delete operations (PUT, PATCH, DELETE) while allowing read operations (GET). This is enforced via the `Microsoft.Authorization/locks` resource type, which creates a deny assignment that overrides any role-based permissions. In a real-world scenario, a ReadOnly lock is commonly used on production resource groups to prevent accidental modifications, such as resizing a VM or deleting a storage account, while still allowing monitoring and auditing via read operations.

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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

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: Changing the size of an existing virtual machine in the resource group will fail because it is a write operation. — A is correct because changing the size of an existing virtual machine is a write operation that modifies the VM's configuration. A ReadOnly lock on the resource group prevents all write and delete operations, so any attempt to resize the VM will fail. The lock does not affect read operations, which remain functional.

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

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.