Question 120
In the Riverton Healthcare pilot environment, a controlled verification is required for: A NetApp-backed profile volume is sized without quota headroom and new users receive insufficient-space failures during session creation. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A staged profile growth test stays below the defined capacity alarm and new users can still mount writable disks. This is an independently observable result of the targeted change: Set appropriate volume capacity and monitoring alerts for user growth, snapshots, and expected profile expansion. It closes the specific Riverton Healthcare failure: A NetApp-backed profile volume is sized without quota headroom and new users receive insufficient-space failures during session creation.
Incorrect Answers
A newly onboarded user creates their VHDX and saves settings without being granted full storage-account ownership. This is evidence for a DIFFERENT remediation: Assign the correct SMB share permissions together with effective filesystem ACLs for profile creation and modification. That remediation addresses: A desktop administrator grants Storage File Data SMB Share Reader and expects users to create and update their writable FSLogix profiles. It does not establish resolution of the Riverton Healthcare problem: A NetApp-backed profile volume is sized without quota headroom and new users receive insufficient-space failures during session creation. The required outcome here is: A staged profile growth test stays below the defined capacity alarm and new users can still mount writable disks.
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 Riverton Healthcare problem: A NetApp-backed profile volume is sized without quota headroom and new users receive insufficient-space failures during session creation. The required outcome here is: A staged profile growth test stays below the defined capacity alarm and new users can still mount writable disks.
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 Riverton Healthcare problem: A NetApp-backed profile volume is sized without quota headroom and new users receive insufficient-space failures during session creation. The required outcome here is: A staged profile growth test stays below the defined capacity alarm and new users can still mount writable disks.