A Cloud Cache host has unsynchronized local writes. All providers are unavailable, HealthyProvidersRequiredForUnregister=1 and CcdUnregisterTimeout=0. Sign-out is waiting. Which first action best preserves the user’s data?

✓ Correct answer

• Restore provider availability and inspect synchronization before forcing unregister or deleting the host.

With no healthy required provider and no timeout, sign-out can wait indefinitely. Unsynchronized writes may exist only locally, so restore and verify provider synchronization before destructive recovery. Option explanations: A. Restore provider availability and inspect synchronization before forcing unregister or deleting the host.: This addresses the unmet healthy-provider requirement while preserving the only possible copy of recent writes. B. Enable ClearCacheOnForcedUnregister and force sign-out to discard the cache.: Discarding the unsynchronized cache conflicts with the data-preservation requirement. C. Clear the local cache immediately because the provider replicas must already contain every write.: Asynchronous replication means the remote copies may not contain the unsynchronized data. D. Delete and recreate the VM to release the waiting session.: Destroying the host can lose writes that exist only in its cache. Sources: FSLogix configuration setting reference — https://learn.microsoft.com/fslogix/reference-configuration-settings; FSLogix Cloud Cache overview — https://learn.microsoft.com/fslogix/concepts-fslogix-cloud-cache

Read the source reference