Which action can trigger a FlexCache to invalidate cached data?

Which action can trigger a FlexCache to invalidate cached data?

• A. File modification or deletion on the origin volume.
• B. Client read requests from the origin.
• C. Volume move operation of the origin.
• D. Cluster peering refresh or DNS update.

Answer: (A)

FlexCache keeps data consistent by invalidating cached content when the origin data changes. If a file on the origin volume is modified or deleted, the cached copy may no longer reflect the current state, so the cache invalidates those blocks. This ensures subsequent reads fetch fresh data from the origin. Reading client requests from the origin don’t modify data and therefore don’t trigger invalidation. A volume move is an administrative change to location/mounts and isn’t, by itself, a reason to invalidate cached data. DNS updates or cluster peering refreshes affect metadata or routing, not the actual file contents, so they don’t cause invalidation either.

FlexCache keeps data consistent by invalidating cached content when the origin data changes. If a file on the origin volume is modified or deleted, the cached copy may no longer reflect the current state, so the cache invalidates those blocks. This ensures subsequent reads fetch fresh data from the origin. Reading client requests from the origin don’t modify data and therefore don’t trigger invalidation. A volume move is an administrative change to location/mounts and isn’t, by itself, a reason to invalidate cached data. DNS updates or cluster peering refreshes affect metadata or routing, not the actual file contents, so they don’t cause invalidation either.