Which statement is true about subsequent reads after data is fetched from the origin?

Which statement is true about subsequent reads after data is fetched from the origin?

• A. All subsequent reads are served from the origin regardless of cache.
• B. All subsequent reads are served from FlexCache until data changes at the origin.
• C. The cache must be manually refreshed to serve subsequent reads.
• D. Writes bypass the cache entirely.

Answer: (B)

When data is fetched from the origin into FlexCache, NetApp stores a copy locally. Subsequent reads are served from that local cache, not from the origin, as long as the cached data remains valid. If the origin data changes, the cached copy is invalidated and will be refreshed on the next access, so manual refreshing isn’t required. Writes behavior can vary with policy, but for reads the cache continues to satisfy requests until the origin updates.

When data is fetched from the origin into FlexCache, NetApp stores a copy locally. Subsequent reads are served from that local cache, not from the origin, as long as the cached data remains valid. If the origin data changes, the cached copy is invalidated and will be refreshed on the next access, so manual refreshing isn’t required. Writes behavior can vary with policy, but for reads the cache continues to satisfy requests until the origin updates.