FlexCache does not provide a performance benefit in which scenario? Choose the most correct.

FlexCache does not provide a performance benefit in which scenario? Choose the most correct.

• A. Workloads dominated by sequential writes to large files.
• B. Workloads that repeatedly access the same small set of read-only data.
• C. Environments with minimal network latency between clients and origin.
• D. Systems requiring distributed read scalability across continents.

Answer: (A)

FlexCache is designed to accelerate read-intensive workloads by keeping frequently accessed data close to clients, so cache hits reduce latency and offload reads from the origin. When the workload is dominated by sequential writes to large files, there’s little opportunity for data reuse—once data is written, it isn’t being read again soon, and the cache can’t speed up the write path. Writes go to the origin, and any buffering or caching of reads doesn’t translate into meaningful write performance gains. For this reason, sequential, large-file write workloads don’t benefit from FlexCache as much as read-heavy or data-reuse scenarios do.

FlexCache is designed to accelerate read-intensive workloads by keeping frequently accessed data close to clients, so cache hits reduce latency and offload reads from the origin. When the workload is dominated by sequential writes to large files, there’s little opportunity for data reuse—once data is written, it isn’t being read again soon, and the cache can’t speed up the write path. Writes go to the origin, and any buffering or caching of reads doesn’t translate into meaningful write performance gains. For this reason, sequential, large-file write workloads don’t benefit from FlexCache as much as read-heavy or data-reuse scenarios do.