Review the diagram below. It depicts the following:
A WebLogic domain that consists of two WebLogic clusters that are each included in a Coherence

cluster
The Coherence cluster includes a configuration for Coherence*Web HTTP session storage

An application deployed on cluster 1 that is configured to use Coherence*Web

A client is using a web browser to interact with the application on cluster 1 (via a proxy)

The client's HTTP session is stored by Coherence*Web on the Server in the upper right-hand corner

The server where the client's HTTP session is stored crashes


Assuming the next request for an HTTP session attribute is a new attribute that is not stored in a near- cache, the client's session attribute is fetched from the remaining storage-enabled server in cluster 2.
Why is the session attribute retrieved from this other server's cache? (Choose the best answer.)