Question 470
In the Valleyline Partners pilot environment, a controlled verification is required for: An FSLogix Cloud Cache rollout writes profile data to two locations but ignores local disk cache capacity, filling session-host system drives. What evidence best demonstrates that the reported AVD issue is resolved?
Explanation
Correct Answer
A sustained sign-in test leaves sufficient system disk space and Cloud Cache telemetry shows normal flush behavior. This is an independently observable result of the targeted change: Size and monitor Cloud Cache local cache space and configure supported cleanup and storage paths for the workload. It closes the specific Valleyline Partners failure: An FSLogix Cloud Cache rollout writes profile data to two locations but ignores local disk cache capacity, filling session-host system drives.
Incorrect Answers
A pilot user moves between two hosts and sees the same Start menu and application settings after a clean sign-in. This is evidence for a DIFFERENT remediation: Recommend FSLogix Profile Containers with supported persistent storage and identity access for the nonpersistent host pool. That remediation addresses: An AVD pool stores full roaming user settings directly in local Windows profiles and users lose personalization when switching between pooled hosts. It does not establish resolution of the Valleyline Partners problem: An FSLogix Cloud Cache rollout writes profile data to two locations but ignores local disk cache capacity, filling session-host system drives. The required outcome here is: A sustained sign-in test leaves sufficient system disk space and Cloud Cache telemetry shows normal flush behavior.
The FSLogix log records the intended VHDX attached and a user profile persists across a host change. This is evidence for a DIFFERENT remediation: Configure the correct FSLogix Profile Container path and validate SMB resolution and share permissions on every host. That remediation addresses: A session host logs FSLogix profile attach failures because the configured VHDLocations value points to a nonexisting network folder. It does not establish resolution of the Valleyline Partners problem: An FSLogix Cloud Cache rollout writes profile data to two locations but ignores local disk cache capacity, filling session-host system drives. The required outcome here is: A sustained sign-in test leaves sufficient system disk space and Cloud Cache telemetry shows normal flush behavior.
A controlled storage-endpoint outage permits the approved profile workflow and the replicas reconcile after recovery. This is evidence for a DIFFERENT remediation: Design supported FSLogix Cloud Cache providers for the chosen locations and test failover and write consistency behavior. That remediation addresses: A remote branch must continue attaching profiles during a temporary outage of the primary FSLogix file share, but only one provider is configured. It does not establish resolution of the Valleyline Partners problem: An FSLogix Cloud Cache rollout writes profile data to two locations but ignores local disk cache capacity, filling session-host system drives. The required outcome here is: A sustained sign-in test leaves sufficient system disk space and Cloud Cache telemetry shows normal flush behavior.