A multinational company uses FlexCache to cache data from an origin in New Jersey. Users report latency spikes when accessing files that were recently modified at the origin. Which explanation best fits this behavior?

A multinational company uses FlexCache to cache data from an origin in New Jersey. Users report latency spikes when accessing files that were recently modified at the origin. Which explanation best fits this behavior?

• A. FlexCache does not support coherency, so updates are never reflected.
• B. The FlexCache volume must be re-created after any origin modification to refresh its contents.
• C. The FlexCache volume automatically purges stale cached data and retrieves the updated content from the origin, causing a delay.
• D. ONTAP requires manual re-synchronization between FlexCache and the origin volume.

Answer: (C)

FlexCache must stay coherent with the origin. When a file is modified at the origin, the cached copy can become stale. The system automatically invalidates those stale entries and retrieves the updated data from the origin on the next access. That refresh involves a round trip to the origin, causing a delay and thus latency spikes for recently modified files. No manual re-creation or re-synchronization is needed—coherence is maintained automatically by purging stale cached data and fetching fresh content from the origin.

FlexCache must stay coherent with the origin. When a file is modified at the origin, the cached copy can become stale. The system automatically invalidates those stale entries and retrieves the updated data from the origin on the next access. That refresh involves a round trip to the origin, causing a delay and thus latency spikes for recently modified files. No manual re-creation or re-synchronization is needed—coherence is maintained automatically by purging stale cached data and fetching fresh content from the origin.