D.

Use flag -version when redeploying the application. This will switch on the Side By Side
deployment feature and preserve existing sessions.

Restrictions on Production Redeployment Updates
WebLogic Server can host a maximum of two different versions of an application at one
time.
Note:
* When you redeploy a new version of an application, you cannot change:
An application's deployment targets
An application's security model
A Web application's persistent store settings
To change any of the above features, you must first undeploy the active version of the
application.
Incorrect:
* (not A)
Production redeployment enables you to update and redeploy an application in a
production environment without stopping the application or otherwise interrupting the
application's availability to clients. Production redeployment saves you the trouble of
scheduling application downtime, setting up redundant servers to host new application
versions, manually managing client access to multiple application versions, and manually
retiring older versions of an application.
* (not C) Not dependant on whether the application is JRockit or Hotspot.
* (not E)
The production redeployment strategy is supported for:
Standalone Web Application (WAR) modules and enterprise applications (EARs) whose
clients access the application via a Web application (HTTP).
Enterprise applications that are accessed by inbound JMS messages from a global JMS
destination, or from inbound JCA requests.
All types of Web Services, including conversational and reliable Web Services, but not 8.x
Web Services.
Production redeployment is not supported for:
Standalone EJB or RAR modules. If you attempt to use production redeployment with such
modules, WebLogic Server rejects the redeployment request. To redeploy such modules,
remove their version identifiers and explicitly redeploy the modules.
Applications that use JTS drivers. For more information on JDBC application module
limitations, see JDBC Application Module Limitations in Configuring and Managing JDBC
Data Sources for Oracle WebLogic Server.
Applications that obtain JDBC data sources via the DriverManager API; in order to use
production redeployment, an application must instead use JNDI to look up data sources.
Applications that include EJB 1.1 container-managed persistence (CMP) EJBs. To use
production redeployment with applications that include CMP EJBs, use EJB 2.x CMP
instead of EJB 1.1 CMP.
Reference: Reference; Deploying Applications to Oracle WebLogic Server 12c,
Redeploying Applications in a Production Environment

A.

isolates WebLogic from RAC changes

B.

has a simple configuration

D.

performs faster failure detection and failover

B: With Active GridLink for RAC, WebLogic instances are isolated from
RAC configuration changes, and DBAs only need to contend with a single data source
rather than multiple data sources.
D: Active GridLink for RAC distributes work based on different backend node capacities,
automatically detecting and adapting to overworked nodes and hangs. It enables smart
load balancing across RAC nodes. This makes it easier to route traffic around node
failures, enhancing availability and performance.
Reference: Introducing WebLogic Server 12c

A.

JMS Server

B.

JMS Module

E.

Persistent Store

The major components of the WebLogic JMS Server architecture, as
illustrated in the figure below.
* (A) JMS servers that can host a defined set of modules and any associated persistent
storage that reside on a WebLogic Server instance.
* (B) JMS modules contains configuration resources (such as queues, topics, and
connections factories) and are defined by XML documents that conform to the weblogicjmsmd.
xsd schema.
* Client JMS applications that either produce messages to destinations or consume
messages from destinations.
* JNDI (Java Naming and Directory Interface), which provides a resource lookup facility.
JMS resources such as connection factories and destinations are configured with a JNDI
name. The runtime implementations of these resources are then bound into JNDI using the
given names.
* (E) WebLogic persistent storage (file store or JDBC-accessible) for storing persistent
message data.
The following figure illustrates the WebLogic JMS architecture

Understanding WebLogic JMS

C.

Support Workbench

Support Workbench is a feature where, on identification of a problem,
targeted diagnostics data is dumped in a well-known format and location, for further
analysis by administrators, Oracle Support and development. In case of Support
Workbench for FMW, this feature works for Weblogic Server Targets.

A.

Active GridLink for RAC

B.

support for enterprise Web Services standards beyond Java EE specification

E.

Java EE6 Specification Support

Java EE Enterprise Web Services is supported.
E: New or enhanced WebLogic 12c features include
JAVA EE 6 support all kinds of JEE6 specifications are implemented like :
JSF 2.0,Java Servlets 3.0 JPA 2.0 and EJB 3.1.
Managed Beans 1.0
F: WebLogic 12c also supports supports Java SE 7 (and Java SE 6).
Java language optimizations and Internationalization
Client and server support
SSL/TLS 1.2 in JSSE to support JAVA Socket Transport security
Converged Java VM:JRockit and HotSpot are incorporated with the best features from
both. Oracle’s Publisher Seminar 2011 during OOW
Incorrect:
not C:

C.

Oracle WebLogic Server clusters; Oracle Database RAC

The WebLogic Server JDBC subsystem has supported Oracle RAC since
WLS
version 8.1 SP5, originally developed for Oracle9i RAC. This support is based on a
particular type of data source configuration, called a multi data source. A multi data
source is a data source abstraction over one or more individual data sources. It
serves JDBC connections from each of the member data sources according to a
specified policy2. A RAC multi data source configuration requires that each
member data source obtain connections to a particular RAC instance, as illustrated
in the following diagram of a three-node RAC cluster configuration.

Reference: Oracle WebLogic Server Active GridLink for Oracle Real Application
Clusters(RAC)

A.

JMS Persistent Store

Note:
* Persistent messages are saved in the persistent store on the sending side until they are
successfully forwarded to and acknowledged by the receiving side.

C.

 in the subdirectory /ctxl in the root of the archive