Which type of session replication in WebLogic is recommended?

A customer has a web application with HTTP Sessions that need to be replicated to a backup site
that is more than 100 miles away from the primary site, connected over the Internet.
Which type of session replication in WebLogic is recommended?

A.
MAN Replication

B.
WAN Replication

C.
Synchronous Replication

D.
Asynchronous Replication

E.
Database Replication

Explanation:
WAN HTTP Session State Replication
Resources in a wide area network (WAN) are frequently spread across separate geographical
regions. In addition to requiring network traffic to cross long distances, these resources are often
separated by multiple routers and other network bottle necks. Network communication in a WAN
generally has higher latency and slower interconnect.
Slower network performance within a WAN makes it difficult to use a synchronous replication
mechanism like the one used within a MAN. WebLogic Server provides failover across clusters in
WAN by using an asynchronous data replication scheme.
Note:
HTTP Session State Replication

Weblogic Server uses two methods for replicating HTTP session state across clusters:
in-memory replication
* Using in-memory replication, WebLogic Server copies a session state from one server instance
to another. The primary server creates a primary session state on the server to which the client
first connects, and a secondary replica on another WebLogic Server instance in the cluster. The
replica is kept up-to-date so that it may be used if the server that hosts the servlet fails.
* JDBC-based persistence
In JDBC-based persistence, WebLogic Server maintains the HTTP session state of a servlet or
JSP using file-based or JDBC-based persistence.
JDBC-based persistence is also used for HTTP session state replication within a Wide Area
Network (WAN).