Courseiva
Implement and Manage StoragehardMultiple SelectObjective-mapped

AZ-104 Implement and Manage Storage Practice Question

A help desk group must use the Azure portal to start a virtual machine, stop or deallocate it, and see its current state, but they must not change any other VM settings. Which three Microsoft.Compute actions should be included in a custom role? Select three.

⚠ Common exam trap

Test-takers frequently confuse the write action with the specific start and deallocate actions, incorrectly assuming that write is needed for power operations, when in fact write grants full configuration change capabilities that exceed the required scope.

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

Microsoft.Compute/virtualMachines/read

The Microsoft.Compute/virtualMachines/read permission is required to view the current state of a virtual machine in the Azure portal. Without this read action, the help desk group would not be able to see the VM's status, which is essential for their task of monitoring and managing the VM lifecycle.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Microsoft.Compute/virtualMachines/read

    Why this is correct

    The Microsoft.Compute/virtualMachines/read permission is the foundational control-plane read that lets the Azure portal query the VM's properties, current power state, and resource group metadata. Without it, the help desk cannot see the VM in the portal list or open its overview blade, making it impossible to even select the machine they are supposed to start. This read action is a prerequisite for all subsequent management operations, but it confers no ability to change or start the VM by itself.

  • Microsoft.Compute/virtualMachines/start/action

    Why this is correct

    The Microsoft.Compute/virtualMachines/start/action permission authorizes the specific POST operation that transitions a virtual machine from a stopped or deallocated state into a running state. This is a discrete control-plane action, not implied by read or write, and it must be explicitly granted in an Azure RBAC role. It allows the help desk to perform exactly the requested start function without permitting broader configuration changes or destructive operations.

  • Microsoft.Compute/virtualMachines/deallocate/action

    Why this is correct

    The Microsoft.Compute/virtualMachines/deallocate/action permission is required to stop and deallocate a VM, which releases the compute resources and, if applicable, its dynamic public IP address. In Azure, a simple power-off (stop without deallocate) is a separate action, but the common help desk task of 'stopping' a VM is usually implemented as deallocation to avoid ongoing compute billing. Granting this action lets the help desk stop VMs as needed without giving them permission to delete or reconfigure the resource.

  • Microsoft.Compute/virtualMachines/write

    Why it's wrong here

    The Microsoft.Compute/virtualMachines/write permission grants broad control over VM configuration, including resizing, changing hardware profile, adding or removing disks, updating network interfaces, and other administrative modifications. While write is needed for some scenarios like deploying or updating a VM, it is not required to start an existing VM and violates least privilege for a help desk group. Allowing write would let the help desk unintentionally alter critical VM settings that are outside the scope of their start-only responsibilities.

    When this WOULD be correct

    In a scenario where help desk needs to modify VM settings (e.g., change VM size, update tags, or attach disks) via the portal, Microsoft.Compute/virtualMachines/write would be required.

  • Microsoft.Compute/virtualMachines/delete

    Why it's wrong here

    The Microsoft.Compute/virtualMachines/delete permission is destructive because it removes the entire virtual machine resource, including its associated OS disk, data disks, NIC, and extensions. This goes far beyond the help desk's requirement to start a VM and would expose the organization to accidental or malicious data loss. Under least privilege, delete must never be granted when the only required operation is starting a virtual machine; operational support needs start/action and read, not resource removal.

    When this WOULD be correct

    In a scenario where a custom role is needed for a team responsible for decommissioning and removing VMs that are no longer needed, such as a cleanup or lifecycle management team, Microsoft.Compute/virtualMachines/delete would be required.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Microsoft.Compute/virtualMachines/readCorrect answer

Why this is correct

The Microsoft.Compute/virtualMachines/read permission is the foundational control-plane read that lets the Azure portal query the VM's properties, current power state, and resource group metadata. Without it, the help desk cannot see the VM in the portal list or open its overview blade, making it impossible to even select the machine they are supposed to start. This read action is a prerequisite for all subsequent management operations, but it confers no ability to change or start the VM by itself.

Microsoft.Compute/virtualMachines/writeWrong answer — click to see why

Why this is wrong here

The write action allows modifying all VM settings, which exceeds the required permissions of only starting, stopping, and viewing state.

★ When this WOULD be the correct answer

In a scenario where help desk needs to modify VM settings (e.g., change VM size, update tags, or attach disks) via the portal, Microsoft.Compute/virtualMachines/write would be required.

Why candidates choose this

Candidates may think 'write' is needed to change the VM state (start/stop), but state changes are controlled by specific actions, not the generic write permission.

Microsoft.Compute/virtualMachines/deleteWrong answer — click to see why

Why this is wrong here

The delete action would allow the help desk group to remove the VM entirely, which is beyond the required permissions of starting, stopping, deallocating, and viewing state.

★ When this WOULD be the correct answer

In a scenario where a custom role is needed for a team responsible for decommissioning and removing VMs that are no longer needed, such as a cleanup or lifecycle management team, Microsoft.Compute/virtualMachines/delete would be required.

Why candidates choose this

Candidates might mistakenly think that stopping or deallocating a VM requires delete permission, or they may confuse the deallocate action with deletion.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

About these practice questions

This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

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.