After implementing a FlexCache volume, a user updates a file on the origin; another user reads the same file from the cache and sees the old version. What is the most likely cause?

After implementing a FlexCache volume, a user updates a file on the origin; another user reads the same file from the cache and sees the old version. What is the most likely cause?

• A. FlexCache does not automatically invalidate stale cached blocks.
• B. The FlexCache volume is configured for write-only mode.
• C. The cache consistency interval has not yet expired, delaying block update propagation.
• D. The cache volume is disconnected from the origin SVM.

Answer: (C)

FlexCache relies on a cache consistency interval to balance performance with data freshness. When the origin file is updated, the blocks cached on the cache volume aren’t refreshed immediately; they remain the old data until that interval expires. During this window, a user reading the file from the cache will continue to see the previous version. So the most likely cause is that the cache consistency interval has not yet expired, delaying propagation of the update to the cache. In contrast, a truly write-only mode wouldn’t produce cache reads of old data, and a disconnected cache would typically cause broader cache failures or inability to serve data, not the normal, expected delay seen here.

FlexCache relies on a cache consistency interval to balance performance with data freshness. When the origin file is updated, the blocks cached on the cache volume aren’t refreshed immediately; they remain the old data until that interval expires. During this window, a user reading the file from the cache will continue to see the previous version. So the most likely cause is that the cache consistency interval has not yet expired, delaying propagation of the update to the cache.

In contrast, a truly write-only mode wouldn’t produce cache reads of old data, and a disconnected cache would typically cause broader cache failures or inability to serve data, not the normal, expected delay seen here.