You wish to provide failover for HTTP sessions within a cluster. However, you are limited by the
following constraints:
1. While under load, your servers have very little free memory.
2. you do not have appropriate access rights to modify your company’s database.
Which is the best option, given these restrictions?
A.
in-memory replication
B.
automatic migration
C.
file persistence
D.
JDBC persistence
E.
replication groups
Explanation:
File persistence use less memory than in-memory replication, and does not need
access rights to the company’s database.
Note:
You use session persistence to permanently store data from an HTTP session object to enable
failover and load balancing across a cluster of WebLogic Servers. When your applications stores
data in an HTTP session object, the data must be serializable.
There are five different implementations of session persistence:
* Memory (single-server, non-replicated)
* File system persistence
* JDBC persistence
* Cookie-based session persistence
* In-memory replication (across a cluster)
Reference: Oracle Fusion Middleware Developing Web Applications, Servlets, and JSPs for
Oracle WebLogic Server, Using Sessions and Session Persistence