FlexCache volumes can exist on a different ONTAP cluster than their origin.

FlexCache volumes can exist on a different ONTAP cluster than their origin.

• A. True
• B. False
• C. Only with intercluster LIFs
• D. Not supported

Answer: (A)

FlexCache is designed to cache data from an origin volume that can reside on a different ONTAP cluster. You set up a cache volume on the local (cache) cluster and point it to the origin volume on the remote (origin) cluster, so client requests can be served from the local cache instead of reaching the origin every time. This proximity reduces latency for frequently accessed data and helps offload reads from the origin cluster. The two clusters are connected through a cache relationship, and while network connectivity is required for the cache to fetch data from the origin, there’s no requirement that the cache live on the same cluster as the origin, making cross-cluster caching a supported and common use case. The other options are too restrictive or incorrect, since this cross-cluster caching behavior is intentional and supported.

FlexCache is designed to cache data from an origin volume that can reside on a different ONTAP cluster. You set up a cache volume on the local (cache) cluster and point it to the origin volume on the remote (origin) cluster, so client requests can be served from the local cache instead of reaching the origin every time. This proximity reduces latency for frequently accessed data and helps offload reads from the origin cluster. The two clusters are connected through a cache relationship, and while network connectivity is required for the cache to fetch data from the origin, there’s no requirement that the cache live on the same cluster as the origin, making cross-cluster caching a supported and common use case. The other options are too restrictive or incorrect, since this cross-cluster caching behavior is intentional and supported.