What happens after a FlexCache volume serves a read request for data it didn't have locally?

What happens after a FlexCache volume serves a read request for data it didn't have locally?

• A. The data remains only in memory and is discarded after serving the request.
• B. The data is stored in the FlexCache volume for future requests.
• C. The data is copied permanently to the origin volume.
• D. The data must be re-fetched from the origin every time it is requested.

Answer: (B)

FlexCache operates as a read-through cache: when data isn’t already cached, the system fetches it from the origin and stores a copy in the local FlexCache volume. This cached copy is kept for future requests, so subsequent reads can be served from the cache rather than going back to the origin. That’s why the correct outcome is that the data is stored in the FlexCache volume for future requests. The data isn’t discarded after one read, nor copied permanently to the origin, and it doesn’t require re-fetching from the origin on every access.

FlexCache operates as a read-through cache: when data isn’t already cached, the system fetches it from the origin and stores a copy in the local FlexCache volume. This cached copy is kept for future requests, so subsequent reads can be served from the cache rather than going back to the origin. That’s why the correct outcome is that the data is stored in the FlexCache volume for future requests. The data isn’t discarded after one read, nor copied permanently to the origin, and it doesn’t require re-fetching from the origin on every access.