Eager to master hybrid server management? Discover how to administer Windows Server Hybrid Core Infrastructure on Azure, setting your path towards the Microsoft Certified: Azure Hybrid Infrastructure Administrator Associate certification!
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
A company has Azure File Sync deployed with cloud tiering enabled on several Windows Servers. Users report that some files that should be tiered are still consuming local disk space, and some tiered files are failing to recall. The administrator needs to investigate these issues efficiently.
Which monitoring tools and event logs should the administrator primarily use on the Windows Server to diagnose why files are failing to tier and recall, and to check the overall health of the server endpoint?
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
This solution combines the strengths of Azure Monitor for comprehensive, long-term monitoring and Windows Server event logs for granular, server-side diagnostics. Azure Monitor is a service that collects, analyzes, and acts on telemetry data from your Azure and on-premises environments. It provides capabilities for visualizing metrics, creating alerts, and querying logs over extended periods, offering a holistic view of the Azure File Sync service and its components. On the Windows Server, the Telemetry event log (located under Applications and Services\Microsoft\FileSync\Agent) captures general sync, registered server, and cloud tiering health events. The TieringResults and RecallResults event logs (also under Microsoft-FileSync-Agent) provide specific, per-file error details for tiering and recall operations, including HRESULT codes and remediation guidance.
StudyCerts
StudyCertsDataTransferHresult for successful or failed recalls. The Telemetry log includes Event IDs 9005, 9006, 9009, and 9059 for recall activity and error distribution.This approach is optimal because it leverages the strengths of both cloud-based and server-side monitoring. Azure Monitor provides the aggregated view, historical context, and alerting capabilities necessary for managing a hybrid environment at scale. Simultaneously, the dedicated event logs on the Windows Server offer the precise, per-item error details that are indispensable for diagnosing specific file-related issues with cloud tiering and recall. Without the detailed server-side logs, diagnosing individual file failures would be extremely difficult, and without Azure Monitor, tracking long-term trends and setting up proactive alerts would be cumbersome or impossible. This combination ensures both efficient high-level oversight and effective deep-dive troubleshooting.