A.Modify the applications to use the same version that WebLogic uses internally.
B.Based on available examples of Filtering Classloader entries, try to modify get the proper  entries.
C.Deploy and use the Classloader Analyzing Tool to resolve all conflicts with conflicting libraries.  This tool will generate all proper entries.
D.Split the application into separate WebLogic containers and use different WLS versions of  Xerces but identical that applications require.
E.Look for a WebLogic release that uses the same version of Xerces that the applications use.

A.execution of unit and integration tests
B.management of the life cycle of a WebLogic domain including creation, configuration, and server life-cycle management
C.deployment and undeployment of applications
D.Java profiling

A.Move domain logs to a highly available database.
B.Move server logs to a highly available database.
C.Move transaction logs to a highly available database. 
D.Move JMS persistent stores to a highly available database.
E.Move error logs to a highly available database.

A.OPTIONAL
B.REQUISITE
C.REQUIRED
D.SUFFICIENT
E.MANDATORY

A.collecting run-time metrics and sending an email if user-defined thresholds are exceeded
B.configuring Clusters and Managed Servers
C.starting Managed Servers using the Node Manager
D.installing WebLogic binaries on a remote machine using Node Manager
E.configuring a Managed Server on a remote machine where the Node Manager is installed but  no other Managed Servers from the domain exist

A.Configure one Node Manager per domain (for example, if there are two domains on one  machine, then you will need to configure two Node Managers).
B.Configure one Node Manager per machine with any number of WebLogic instances running on it.
C.Configure one Node Manager per machine for all WebLogic, OHS, and OEM running on the  same machine.
D.Configure one Node Manager for every WebLogic instance.
E.Configure two or more Node Managers for every WebLogic instance.

A.SAF Target
B.SAF Imported Destination
C.SAF Client
D.SAF Server
E.Distributed SAF JMS

A.Keep environmental data in the global settings of domain and the application can read it from the domain where it runs.
B.Keep environmental data in Deployment Plan XML files. It allows you to change parameters in the deployment descriptor without opening the archive file.
C.Keep environmental data in the database because it is the most effective way of parametrizing the environment.  
D.Keep archive in exploded format so the customer does not have to open the archive files.
E.Eliminate all environmental settings from the application. There should not to be any environmental settings in the application. 

A.Websphere Developer Studio
B.NetBeans
C.InteliJ IDIA
D.JDeveloper
E.Eclipse
F.WebLogic Workshop

A.Provide the team with a WebLogic domain template with the testing data sources configured.
B.Provide the development team with a preconfigured domain archive file.
C.Provide the development team with the [datasource] -jdbc.xml file to overwrite their local copy.
D.Create the data sources on behalf each of the developer.
E.Provide the development team with WLST scripts to create and configure the testing data  sources.

A.simplified disaster recovery architecture and efforts
B.better performance than writing logs to a file store
C.common storage of transaction logs with application data
D.common replication of transaction logs with application data
E.higher transaction throughput