nerdexam
Microsoft

AZ-801 · Question #92

You have an Azure virtual machine named VM1 that runs Windows Server. When you attempt to install the Azure Performance Diagnostics extension on VM 1, the installation fails. You need to identify…

The correct answer is A. Sign in to VM1 and verify the WaAppAgent.log file. To identify the cause of an Azure Performance Diagnostics extension installation failure on a Windows Server VM, directly checking the WaAppAgent.log file on the VM is a primary troubleshooting step.

Monitor and troubleshoot Windows Server environments

Question

You have an Azure virtual machine named VM1 that runs Windows Server. When you attempt to install the Azure Performance Diagnostics extension on VM 1, the installation fails. You need to identify the cause of the installation failure. What are two possible ways to achieve the goal? Each correct answer represents a complete solution. NOTE: Each correct selection is worth one point.

Options

  • ASign in to VM1 and verify the WaAppAgent.log file.
  • BFrom the Azure portal, view the alerts for VM1.
  • CFrom the Azure portal, view the activity log for VM1.
  • DSign in to VM1 and verify the MonitorhAgent.log file.

How the community answered

(53 responses)
  • A
    79% (42)
  • B
    8% (4)
  • C
    11% (6)
  • D
    2% (1)

Why each option

To identify the cause of an Azure Performance Diagnostics extension installation failure on a Windows Server VM, directly checking the WaAppAgent.log file on the VM is a primary troubleshooting step.

ASign in to VM1 and verify the WaAppAgent.log file.Correct

The WaAppAgent.log file, located on the Azure virtual machine, logs operations performed by the Windows Azure Guest Agent, which includes the installation and management of VM extensions. Reviewing this log provides detailed information and error messages specific to the extension installation failure, making it a crucial resource for root cause analysis.

BFrom the Azure portal, view the alerts for VM1.

Viewing alerts for VM1 from the Azure portal provides high-level notifications about VM health or service issues but typically does not offer specific, detailed logs for why an extension installation failed.

CFrom the Azure portal, view the activity log for VM1.

While the Activity log for VM1 in the Azure portal will record the event of an extension installation attempt and its failure status, it usually provides only a summary error message, lacking the granular details found in the VM's agent logs.

DSign in to VM1 and verify the MonitorhAgent.log file.

The MonitorhAgent.log is not a standard log file for general Azure VM extension failures; failures related to the core extension installation process are typically recorded by the Azure Guest Agent in the WaAppAgent.log.

Concept tested: Troubleshooting Azure VM extension installation failures

Source: https://learn.microsoft.com/en-us/azure/virtual-machines/windows/log-files

Topics

#Azure VM Extensions#Troubleshooting#Azure VM Agent#Logging

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-801 Practice