Question 820
The runbook says Cloud Cache profile performance test was enabled to identify whether extra remote write replication creates unacceptable logoff latency for a demanding group. Which reported behavior proves that step worked?
Explanation
Correct Answer
This is the direct functional outcome for Cloud Cache profile performance test: measured attach, sign-out and provider sync timing meet the expected session SLA. Multiple storage backends can change the profile I/O performance characteristics. The observed behavior supports the specified acceptance requirement.
Incorrect Answers
That evidence concerns FSLogix CCDLocations multiple provider strings, used to specify two named profile storage backends for Cloud Cache rather than a single fixed VHDLocations path. It does not establish whether Cloud Cache profile performance test satisfies the current requirement to identify whether extra remote write replication creates unacceptable logoff latency for a demanding group.
That evidence concerns Cloud Cache write synchronization monitor, used to verify changes made during temporary network isolation eventually reach approved remote storage providers. It does not establish whether Cloud Cache profile performance test satisfies the current requirement to identify whether extra remote write replication creates unacceptable logoff latency for a demanding group.
That evidence concerns Cloud Cache provider failover drill, used to demonstrate that an alternate profile provider can support continuation after a planned primary storage fault. It does not establish whether Cloud Cache profile performance test satisfies the current requirement to identify whether extra remote write replication creates unacceptable logoff latency for a demanding group.






Configuring and Operating Microsoft Azure Virtual Desktop (AZ-140) Practice Tests