Which statement about FlexCache is not true?

Which statement about FlexCache is not true?

• A. Clients mounting the FlexCache or origin volume see the same data.
• B. FlexCache requires full dataset synchronization before serving clients.
• C. FlexCache is sparsely populated and only stores frequently accessed blocks.
• D. FlexCache can exist on a different ONTAP cluster than the origin.

Answer: (B)

FlexCache acts as a caching layer in front of an origin volume, so clients that mount either the FlexCache or the origin see the same data because the cache transparently serves data and maintains coherence with the origin. The cache is sparsely populated, storing only the actively used blocks and evicting data as needed, which keeps storage overhead low while still delivering fast access for hot data. FlexCache can reside on a different ONTAP cluster than the origin, enabling deployment topology that brings data closer to clients. Importantly, it does not require a full dataset to be synchronized before serving clients; blocks are populated in the cache on demand (with options to seed ahead of time if desired), so clients can start reading data as the cache fills.

FlexCache acts as a caching layer in front of an origin volume, so clients that mount either the FlexCache or the origin see the same data because the cache transparently serves data and maintains coherence with the origin. The cache is sparsely populated, storing only the actively used blocks and evicting data as needed, which keeps storage overhead low while still delivering fast access for hot data. FlexCache can reside on a different ONTAP cluster than the origin, enabling deployment topology that brings data closer to clients. Importantly, it does not require a full dataset to be synchronized before serving clients; blocks are populated in the cache on demand (with options to seed ahead of time if desired), so clients can start reading data as the cache fills.