After applying a custom image, a Linux VM stops at a black screen before the sign-in prompt. The administrator cannot use RDP or SSH and needs the fastest way to inspect the boot process. Which two actions should they take? Select two.

Reimage the VM immediately to a clean managed disk.

Incorrect. Reimaging removes evidence of the problem and is not the fastest diagnostic step.

Increase the VM size to a larger SKU.

Incorrect. More CPU or RAM will not help if the operating system is failing before login.

Reset the network interface configuration from the portal.

Incorrect. A black screen before sign-in usually indicates boot or OS issues, not a NIC-only problem.

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: Enable Boot diagnostics on the virtual machine. — When a VM fails before you can sign in, Boot diagnostics is the fastest low-level tool because it preserves the serial console output and a screenshot from the guest boot process. Enabling it and then reviewing the logs lets the administrator see kernel panics, startup service failures, or image corruption without needing remote login. That is much more effective than changing size or reimaging first. Why others are wrong: Reimaging destroys the current evidence and should come after diagnosis, not before. Resizing changes capacity, not boot behavior. Resetting network settings is useful for connectivity problems, but it does not explain a black screen that appears before the login prompt.

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.