Question 70
In the Bayview Compliance pilot environment, a controlled verification is required for: A geographically dispersed user population stores profiles in a single remote region and sees severe logon delays despite adequate host CPU. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
Pilot users in both target regions complete profile attachment and logon within the agreed latency objective. This is an independently observable result of the targeted change: Choose profile-storage placement and replication or cache strategy around user latency, session-host geography, and approved recovery needs. It closes the specific Bayview Compliance failure: A geographically dispersed user population stores profiles in a single remote region and sees severe logon delays despite adequate host CPU.
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 Bayview Compliance problem: A geographically dispersed user population stores profiles in a single remote region and sees severe logon delays despite adequate host CPU. The required outcome here is: Pilot users in both target regions complete profile attachment and logon within the agreed latency objective.
A simulated 200-user sign-in peak stays inside measured storage latency and throughput targets without profile-mount failures. This is evidence for a DIFFERENT remediation: Estimate storage IOPS, throughput, per-profile capacity, concurrent logon demand, and recovery targets before selecting Azure Files or Azure NetApp Files. That remediation addresses: A large desktop estate selects a profile storage tier based on total gigabytes only, then encounters file-open latency at a morning logon peak. It does not establish resolution of the Bayview Compliance problem: A geographically dispersed user population stores profiles in a single remote region and sees severe logon delays despite adequate host CPU. The required outcome here is: Pilot users in both target regions complete profile attachment and logon within the agreed latency objective.
A user mounts only their own profile while another nonadministrator account cannot read or modify that VHDX path. This is evidence for a DIFFERENT remediation: Apply documented FSLogix storage share and NTFS ACL patterns with per-user isolation and the required session-host access model. That remediation addresses: A profile container system stores VHDX files without predictable ownership or access-control inheritance, giving unrelated users access to profiles. It does not establish resolution of the Bayview Compliance problem: A geographically dispersed user population stores profiles in a single remote region and sees severe logon delays despite adequate host CPU. The required outcome here is: Pilot users in both target regions complete profile attachment and logon within the agreed latency objective.