What is the primary purpose of FlexCache in a global read scenario?

• A. To offload read traffic from origin and reduce latency for remote users.
• B. To mirror writes to the origin with low latency.
• C. To compress data before it reaches clients.
• D. To provide disaster recovery via snapshots.

Answer: (A)

FlexCache is about bringing data closer to users by caching recently accessed content at remote sites. In a global read scenario, its main purpose is to serve read requests locally from the remote cache instead of pulling every read from the origin. This significantly reduces WAN traffic and cuts latency for remote users. When a client requests data, the cache checks locally first; if the data is already cached, it is returned quickly. If not, the data is fetched from the origin, returned to the client, and stored in the cache for future requests. Writes continue to be handled at the origin, preserving data integrity, so this feature is focused on improving read performance and bandwidth efficiency. The other options describe capabilities (compression, disaster recovery, or write mirroring) that aren’t the primary role of FlexCache in this scenario.