Correct Answer: Enable Snapshot policies on the Azure NetApp Files volume and configure the 'Previous Versions' tab in Windows.
Azure NetApp Files supports fast, volume-level snapshots. By enabling snapshots and integrating with the Windows 'Previous Versions' feature via the hidden ~snapshot directory, use...
Correct Answer
Enable Snapshot policies on the Azure NetApp Files volume and configure the 'Previous Versions' tab in Windows.
Why This Answer Is Correct
Azure NetApp Files supports fast, volume-level snapshots. By enabling snapshots and integrating with the Windows 'Previous Versions' feature via the hidden ~snapshot directory, users can self-service file restorations directly from their mounted profiles.
This question evaluates your knowledge of Azure Virtual Desktop Storage & FSLogix — a core concept tested in Microsoft Certified: Azure Virtual Desktop Specialty (AZ-140). Understanding Azure Virtual Desktop Storage & FSLogix is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are configuring FSLogix Profile Containers for a large Azure Virtual Desktop deployment. You want to provide high-availability profile storage that can survive a regional outage. You decide to store profiles in two different Azure regions and keep them synchronized. Which FSLogix capability should you configure?
You are configuring FSLogix Profile Containers using Azure Files. You want to implement NTFS permissions on the file share. Which Active Directory credential configuration is supported for securing Azure Files access directly from AVD session hosts?
You are configuring FSLogix Profile Containers on Azure Files. You want to implement folder exclusions (such as excluding Temp folders or browser caches) to reduce the profile size. Which file must you configure and place in the user profile directory?
You have an FSLogix profile container implementation. Users report that when they log in, they receive a temporary local profile instead of their FSLogix profile. What is the most common cause of this issue?