Question 80
In the Mariner Finance pilot environment, a controlled verification is required for: A high-concurrency AVD pool keeps exclusive profile VHDX locks after failed logoffs and subsequent sessions fall back to local temporary profiles. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A controlled logoff and reconnect releases or safely resolves the old mount and attaches the expected profile disk without data loss. This is an independently observable result of the targeted change: Use supported FSLogix profile container lock handling and investigate stale sessions and share availability before permitting reattachment. It closes the specific Mariner Finance failure: A high-concurrency AVD pool keeps exclusive profile VHDX locks after failed logoffs and subsequent sessions fall back to local temporary profiles.
Incorrect Answers
A session host connects to the ANF SMB volume and completes read/write profile validation with the intended identity. This is evidence for a DIFFERENT remediation: Configure the required delegated subnet and supported ANF SMB volume network and directory integration before publishing the UNC path. That remediation addresses: A team deploys Azure NetApp Files for profiles but neglects the delegated subnet and volume network access requirements, causing all mount attempts to fail. It does not establish resolution of the Mariner Finance problem: A high-concurrency AVD pool keeps exclusive profile VHDX locks after failed logoffs and subsequent sessions fall back to local temporary profiles. The required outcome here is: A controlled logoff and reconnect releases or safely resolves the old mount and attaches the expected profile disk without data loss.
The FSLogix operational log reports a successful VHDX attach and the user receives the same persistent profile on another host. This is evidence for a DIFFERENT remediation: Configure the supported profile container UNC path and appropriate share and file permissions for the host identities and users. That remediation addresses: FSLogix Profile Containers are configured to use an SMB path that session hosts cannot authenticate to, causing users to receive temporary profiles. It does not establish resolution of the Mariner Finance problem: A high-concurrency AVD pool keeps exclusive profile VHDX locks after failed logoffs and subsequent sessions fall back to local temporary profiles. The required outcome here is: A controlled logoff and reconnect releases or safely resolves the old mount and attaches the expected profile disk without data loss.
A domain-eligible session host mounts the share via its private address and public network access can remain disabled. This is evidence for a DIFFERENT remediation: Configure storage-account private endpoints, SMB connectivity, private DNS, and identity-based access for Azure Files profile storage. That remediation addresses: An Azure Files profile share is created with a public endpoint even though session hosts must access storage exclusively through private networking. It does not establish resolution of the Mariner Finance problem: A high-concurrency AVD pool keeps exclusive profile VHDX locks after failed logoffs and subsequent sessions fall back to local temporary profiles. The required outcome here is: A controlled logoff and reconnect releases or safely resolves the old mount and attaches the expected profile disk without data loss.