AZ-104 Deploy and Manage Azure Compute Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Boot diagnostics

  Why it's wrong here

  Boot diagnostics is a debugging feature that captures the VM's serial console output and screenshots during startup, storing them in an Azure managed storage account for troubleshooting boot failures, kernel panics, or OS crashes. It provides visibility into the boot process only; it has no execution engine and cannot invoke scripts or install software. It is a diagnostic telemetry channel, not a management or configuration capability.

  When this WOULD be correct

  When you need to troubleshoot a VM that fails to boot or crashes, and you require access to console logs or screenshots to diagnose the issue without RDP/SSH.

• ✓

  Custom Script Extension

  Why this is correct

  Custom Script Extension is an Azure VM extension that executes arbitrary scripts at deployment completion through the VM agent. It runs as SYSTEM/root via the extension handler, can source script content from Azure Storage, GitHub, or inline, and returns provisioning status after successful execution. This makes it the native post-deployment automation mechanism for installing software, unlike telemetry or network controls.

• ✗

  An inbound NSG rule for WinRM

  Why it's wrong here

  An inbound NSG rule permitting WinRM (TCP/5985 or 5986) would expose the management endpoint to the network, allowing remote PowerShell sessions to connect to the VM. Merely opening the port does not initiate a deployment-time install; it requires a separate automation client to connect and execute commands, and broad inbound access violates security best practices. The requirement is to run a script immediately after deployment, which requires an agent-driven extension, not a network permit.

  When this WOULD be correct

  If the question required remote management of a VM after deployment (e.g., to run a script or configure settings) and allowed opening management ports, then an inbound NSG rule for WinRM would be correct. For example: 'You need to remotely execute PowerShell commands on a VM after deployment. What should you configure?'

• ✗

  A proximity placement group

  Why it's wrong here

  A proximity placement group is a logical grouping used to force virtual machines into the same Azure datacenter or network backbone to reduce inter-VM network latency for tightly coupled workloads such as HPC or low-latency tiers. It influences physical placement and availability topology, and does not interact with the OS, run scripts, or perform software installation. Its purpose is scheduling/locality, not configuration management.

  When this WOULD be correct

  You need to ensure that multiple VMs in an availability set are as close as possible to minimize network latency for a latency-sensitive application. A proximity placement group would be the correct choice to co-locate the VMs.

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.

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?”