Which statement describes Local Cache behavior?

Which statement describes Local Cache behavior?

• A. Cache data is replicated on each node
• B. Cache data is evenly distributed across all Confluence nodes in a cluster
• C. Cache data is stored in a central repository
• D. Cache data is invalidated periodically by a central controller

Answer: (A)

Local cache means each node in a cluster keeps its own copy of the cached data, so reads can be served locally without reaching other nodes. The statement that best matches this behavior is that cache data is replicated on each node. By having identical cached data on every node, the system can handle requests quickly, reduce cross-node traffic, and improve overall responsiveness. If cache data were evenly distributed across nodes, that would describe a distributed or partitioned cache, not local caching. Storing the cache in a central repository would be centralized caching, which contradicts the idea of a node-local cache. Relying on a central controller to invalidate the cache periodically suggests a centralized invalidation approach rather than per-node local caches maintaining their own copies. Remember, replication across nodes speeds access but requires proper invalidation strategies to keep data consistent when underlying data changes.

Local cache means each node in a cluster keeps its own copy of the cached data, so reads can be served locally without reaching other nodes. The statement that best matches this behavior is that cache data is replicated on each node. By having identical cached data on every node, the system can handle requests quickly, reduce cross-node traffic, and improve overall responsiveness.

If cache data were evenly distributed across nodes, that would describe a distributed or partitioned cache, not local caching. Storing the cache in a central repository would be centralized caching, which contradicts the idea of a node-local cache. Relying on a central controller to invalidate the cache periodically suggests a centralized invalidation approach rather than per-node local caches maintaining their own copies. Remember, replication across nodes speeds access but requires proper invalidation strategies to keep data consistent when underlying data changes.