Home » Oracle » 1z0-134 » How would you package your GAR as part of the WebLogic Server deployment process for your application?
Your development team has created a GAR deployment that enables Coherence caching for an application. The GAR file is configured to work within both storage-enabled and storage-disabled nodes.
How would you package your GAR as part of the WebLogic Server deployment process for your application? (Choose the best answer.)
A. as an EAR module on storage-disabled nodes and standalone on storage-enabled nodes
B. as an EAR module on storage-enabled nodes and standalone on storage-disabled nodes
C. within a WAR on storage-disabled nodes and within an EAR on storage-enabled nodes
D. within a WAR on storage-enabled nodes and within an EAR on storage-disabled nodes
Correct Answer: A
Explanation/Reference:
Managed Coherence servers are distinguished by their role in the cluster. A best practice is to use different managed server instances (and preferably different
WebLogic Server clusters) for each cluster role.
* storage-enabled – a managed Coherence server that is responsible for storing data in the cluster. Coherence applications are packaged as Grid ARchives
(GAR) and deployed on storage-enabled managed Coherence servers.
* storage-disabled – a managed Coherence server that is not responsible for storing data and is used to host Coherence applications (cache clients). A
Coherence application GAR is packaged within an EAR and deployed on storage-disabled managed Coherence servers.
Reference: https://docs.oracle.com/middleware/1212/wls/CLUST/coherence.htm#CLUST629
|
Download Printable PDF. VALID exam to help you PASS.
|
 |
