When a requested block is not cached in a FlexCache volume, what happens on the first read?

When a requested block is not cached in a FlexCache volume, what happens on the first read?

• A. The read goes to the origin.
• B. The read is served from the local cache.
• C. The read fails.
• D. The read triggers a cache purge.

Answer: (A)

When the requested block isn’t in the local FlexCache, the system treats it as a cache miss and fetches the data from the origin (the back-end NAS/ONTAP system). After the data is retrieved, it is stored in the local cache so that subsequent reads for that block can be served quickly from the cache. On this first read, there’s no cache hit, no failure, and no purge—the data simply comes from the origin and then gets cached for future access.

When the requested block isn’t in the local FlexCache, the system treats it as a cache miss and fetches the data from the origin (the back-end NAS/ONTAP system). After the data is retrieved, it is stored in the local cache so that subsequent reads for that block can be served quickly from the cache. On this first read, there’s no cache hit, no failure, and no purge—the data simply comes from the origin and then gets cached for future access.