Which statement describes FlexCache data population?

Which statement describes FlexCache data population?

• A. It fully replicates the dataset to all caches before serving reads
• B. It is sparsely populated and stores only frequently accessed blocks
• C. It mirrors all writes back to origin
• D. It caches all metadata only

Answer: (B)

FlexCache populations data on demand using a sparse approach. When a client reads, only the specific data blocks that are accessed are loaded into the cache, and they stay there if they’re accessed frequently. This means the cache holds mostly hot data, rather than the entire dataset, which keeps cache space focused on what’s most often used and avoids filling up with rarely accessed blocks. If a requested block isn’t in the cache, it’s fetched from the origin and then may stay in the cache if it proves to be useful again soon. This on-demand, frequency-based loading is what “sparsely populated and stores only frequently accessed blocks” describes. Full replication to every cache would waste space and time, so that isn’t how it works. Caching only metadata would miss most data reads, which isn’t accurate for FlexCache. Writes’ behavior is about how changes propagate, not about how data gets populated into the cache.

FlexCache populations data on demand using a sparse approach. When a client reads, only the specific data blocks that are accessed are loaded into the cache, and they stay there if they’re accessed frequently. This means the cache holds mostly hot data, rather than the entire dataset, which keeps cache space focused on what’s most often used and avoids filling up with rarely accessed blocks. If a requested block isn’t in the cache, it’s fetched from the origin and then may stay in the cache if it proves to be useful again soon. This on-demand, frequency-based loading is what “sparsely populated and stores only frequently accessed blocks” describes.

Full replication to every cache would waste space and time, so that isn’t how it works. Caching only metadata would miss most data reads, which isn’t accurate for FlexCache. Writes’ behavior is about how changes propagate, not about how data gets populated into the cache.