A.JMS Persistent Store
B.JMS Server  
C.JMS Distributed Destination
D.JMS Store and Forward  
E.Automatic Service Migration

A.ability to automatically convert Spring application to JavaEE 6 framework
B.ability to export the WebLogic Container feature to another Spring enabled JavaEE server
C.ability to extend the WebLogic Server console with some Spring-related pages
D.official support of Spring apps inside WebLogic by Oracle Support
E.support for injection of WebLogic MBeans and Resources into Spring applications

A.JDBC
B.JCA
C.JMS
D.EJB
E.Java EE

A.Configure multiple physical data sources and reuse the same JNDI name for each.
B.Use the "compatibility" option of Active GridLink to enable compatibility with non-Oracle  databases.
C.Configure a single physical data source for each node in a database cluster and wrap it using  Multi Data Source.
D.Configure a Data Source Group that contains a physical connection pool to each node in the  database cluster.

A.JMS Server
B.JMS Module
C.Node Manager
D.Queue Manager
E.Persistent Store

A.Domains can be created using the Configuration Wizard.
B.Domains can be created using WLST.  
C.Domain configuration files are located in the WebLogic home directory.
D.Domains can be created based on a domain template.

A.In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize and extend the domain if needed. These steps will only clone only the domain configuration. Binaries with deployments are needed  to be cloned by operation on the file system.  
B.In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain"  from the context menu. In the graphical wizard, customize the domain. These steps clone the  binaries and domain configuration. If the extension is needed, perform it after cloning in the  WebLogic web-based console. 
C.In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain" from the context menu. In the graphical wizard, customize and extend the domain if it is needed. These steps clone the binaries and domain configuration.  
D.In the Enterprise Manager, find the domain to be cloned. Choose "Clone WebLogic Domain"  from the context menu. These steps clone the binaries and domain configuration. If the customization or extension is needed, complete that after cloning in the WebLogic web-based console.  
E.In the file system, copy the domain structure of the configuration directory and paste it in the new location. Modify configuration files for address and port. If further customization is needed, open the WebLogic web-based console and perform these modifications.

A.wls:unzip, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
B.wls:install, wls:install-domain, wls:start-domain, wls:wlst, wls:appc
C.wls:unzip, wls:create-domain, wls:start-domain, wls:wlst, wls:appc
D.wls:install, wls:create-domain, wls:start-server, wls:wlst, wls:appc

A.automated process using the Admin Server
B.automated using JDeveloper
C.manual process with or without Smart Update
D.scripted with WLST
E.automated process using Enterprise Manager 12c

A.after the subscriber is unavailable for 10 minutes
B.when the subscriber is available
C.after the subscriber is unavailable for after an hour
D.are available until the specified time elapses
E.are expired instantly

A.Ensure the maximum size is increased to an appropriate setting.
B.Set the minimum and maximum size of the connection pool to the same value.
C.Increase the statement cache size.
D.Add more heap to the JVM.
E.Add more nodes to the cluster.