Some users intermittently receive temporary local profiles or errors stating their FSLogix profile is in use. You want to reduce profile lock conflicts and avoid local-profile fallback when the container should mount. Which two configurations should you implement? (Choose two)

To reduce profile lock conflicts and avoid local profile fallback, two key FSLogix configurations are crucial. Setting DeleteLocalProfileWhenVHDShouldApply=1 ensures that if a local profile exists when FSLogix expects to attach a container, the local profile is deleted, preventing conflicts and forcing the use of the FSLogix profile. Increasing LockedRetryCount and adjusting LockedRetryInterval gives FSLogix more attempts and time to acquire a lock on the profile container if it's temporarily in use, reducing the likelihood of a failed attachment and subsequent local profile creation. Enabling Windows roaming profiles alongside FSLogix is not recommended as it adds complexity and can introduce new conflicts rather than resolving existing ones. Moving the FSLogix container to an NFS share is not a standard or recommended solution for resolving profile lock issues in Azure Virtual Desktop, which typically uses SMB shares. Disabling multiple sessions per host pool would severely limit scalability and is not a practical solution for addressing profile lock conflicts, which can still occur in single-session scenarios.