Exam AZ-801 topic 5 question 15 discussion

This is almost literally the same question as in topic 5, question 7. There the Azure Diagnostics Extension was given as the correct answer. I believe that is correct - because the link provided there proves it: https://docs.microsoft.com/en-us/azure/azure-monitor/agents/diagnostics-extension-overview

Not sure answer D is correct, possibly E since only the diagnostics extension can send data to Azure Storage: https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agents-overview

E. the Azure Diagnostics extension

https://learn.microsoft.com/en-us/azure/azure-monitor/agents/diagnostics-extension-overview Comparison to Log Analytics agent The Log Analytics agent in Azure Monitor can also be used to collect monitoring data from the guest operating system of virtual machines. You can choose to use either or both depending on your requirements. For a comparison of the Azure Monitor agents, see Overview of the Azure Monitor agents. The key differences to consider are: Azure Diagnostics Extension can be used only with Azure virtual machines. The Log Analytics agent can be used with virtual machines in Azure, other clouds, and on-premises. Azure Diagnostics extension sends data to Azure Storage, Azure Monitor Metrics (Windows only) and Azure Event Hubs. The Log Analytics agent collects data to Azure Monitor Logs. The Log Analytics agent is required for retired solutions, VM insights, and other services such as Microsoft Defender for Cloud. So, to send [performance] collected data to Storage Account must use Azure Diagnostics Extension.

Given answer is correct. The Azure Diagnostics extension is deprecated and is no longer recommended for new deployments. It was previously used to collect diagnostic data and logs from Azure virtual machines, but its functionality has been replaced by the Azure Monitor agent. Using the Azure Diagnostics extension for new deployments is not recommended, and it does not support sending data directly to Azure Storage accounts. In summary, options A, B, C, and E are incorrect because they either do not support collecting performance data from Azure virtual machines or are not recommended for new deployments. The Azure Monitor agent (option D) is the appropriate choice for this scenario as it is specifically designed for collecting performance data from Azure virtual machines and sending it directly to Azure Storage accounts.

For sending collected performance data directly to an Azure Storage account from Azure virtual machines, you should use the Azure Diagnostics extension. This extension enables the collection of monitoring data from the guest operating system of virtual machines and additional data from Azure resources. It is specifically designed for such purposes and integrates well with Azure Storage accounts for data storage. Therefore, the correct option is: Option E. the Azure Diagnostics extension

At time of writing the Monitoring agent does not support Azure Storage which is a requirement in the question therefor answer should be the Diagnostics Extension eventho the Monitoring agent will replace the Diagnostics Extension. Supported by the Comapre to legacy agents overvier in this link: https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agents-overview#supported-services-and-features

Per the documenation: https://docs.microsoft.com/en-us/azure/azure-monitor/agents/diagnostics-extension-overview "Azure Diagnostics extension sends data to Azure Storage, Azure Monitor Metrics (Windows only) and Azure Event Hubs. The Log Analytics agent collects data to Azure Monitor Logs."

https://learn.microsoft.com/en-us/azure/azure-monitor/agents/diagnostics-extension-overview Use Azure Diagnostics extension if you need to: Send data to Azure Storage for archiving Answer is E

In the future Answere D is correct https://learn.microsoft.com/en-us/azure/azure-monitor/agents/agents-overview#consolidating-legacy-agents

E is the correct answer.

E is the correct answer, as stated in an earlier question in this list.

Diagnostic extension is required to send data directly to Azure Storage