An administrator sees familiar settings after testing FSLogix on a host that already had a local profile. No container attachment has been verified. What is the most useful validation before approving roaming?

✓ Correct answer

• Use a suitable fresh test user and verify FSLogix logs/container attachment across hosts

Verify the actual profile path and attachment with controlled testing. A familiar desktop on one preexisting local profile does not establish roaming. Option explanations: A. Immediately enable destructive local-profile deletion for every production user: Migration and protection must be planned before using a setting that permanently deletes local profiles. B. Treat a successful public feed download as proof of SMB access: Resource discovery and profile-share access are separate workflows. C. Approve the design from the familiar desktop alone: Existing local profile content can create a misleading result. D. Use a suitable fresh test user and verify FSLogix logs/container attachment across hosts: This exposes whether shared container persistence is actually functioning instead of being masked by local state. Sources: Store FSLogix profile containers on Azure Files using Microsoft Entra ID — https://learn.microsoft.com/en-us/fslogix/how-to-configure-profile-container-entra-id-hybrid; Store FSLogix profile containers on Azure NetApp Files — https://learn.microsoft.com/en-us/fslogix/how-to-configure-profile-container-netapp

Read the source reference