Not a Recommended Practice for FSLogix Profile Containers

Correct Answer: B

Here are some general recommended practices/guidelines for FSLogix profile containers: For the best performance, the profile container and the storage solution should exist in the same data center location.

To evade the performance bottlenecks, don't include the VHD(X) documents for FSLogix profile containers in antivirus scanning.

In the case of 2 active sessions, use a different profile container for each host pool.

Option A is incorrect.

One of the best practices is that the FSLogix profile container and the storage solution should exist in the same data center location for better performance.

Option B is correct.

The recommended practice is to have the FSLogix profile container and the storage solution in the data center location, not the different ones.

Option C is incorrect.

Not including the VHD(X) documents for FSLogix profile containers in antivirus scanning to evade performance bottlenecks is one of the best practices.

Option D is incorrect.

Using a different profile container for each host pool in the case of 2 active sessions is one of the best practices.

The correct answer is B. FSLogix profile container and the storage solution should be in different data center locations for better performance.

FSLogix Profile Container is a solution that provides a way to store user profiles in a virtual hard disk (VHD or VHDx) container. The container is stored on a file server or in Azure Blob storage. The user profile data can be quickly mounted and unmounted to the host session. FSLogix profile containers can help to improve the user experience and simplify the management of user profiles.

The recommended practices for using FSLogix profile containers are:

A. FSLogix profile container and the storage solution should be in the same data center location for better performance. This means that the storage should be located in the same region as the Azure Virtual Desktop host pool to minimize latency and network traffic.

C. Not including the VHD(X) documents for FSLogix profile containers in antivirus scanning to evade performance bottlenecks. Antivirus scanning can cause delays when accessing the profile container, so it is recommended to exclude the profile container from antivirus scanning.

D. In the case of 2 active sessions, use a different profile container for each host pool. This means that each user should have their own profile container, and if a user logs in to a different host pool, they should use a different profile container.

Option B is not a recommended practice because storing the FSLogix profile container and the storage solution in different data center locations can cause latency and network traffic, which can lead to poor user experience and slow performance.

In summary, to optimize the performance of FSLogix profile containers, it is recommended to store the container and storage solution in the same data center location, exclude the container from antivirus scanning, and use a different container for each user session.