Which of the following is a primary reason to implement FlexCache?

• A. To offload heavily accessed volumes and reduce origin I/O load.
• B. To replicate the full dataset for disaster recovery.
• C. To replace SnapMirror for synchronous replication.
• D. To provide write-back caching for high-write workloads.

Answer: (A)

FlexCache is a local read cache for data stored on a remote origin, so its main purpose is to keep frequently accessed blocks close at hand. By serving repeated reads from the local cache rather than from the origin, it reduces the load on the origin storage and lowers latency for clients. That offloading of read I/O is the key value of implementing FlexCache. It isn’t a disaster-recovery or full-dataset replication solution, and it isn’t primarily a write-back caching mechanism for high-write workloads—the benefit comes from speeding up reads and easing WAN bandwidth by caching hot data locally.