Free Access Oracle.1z0-134.v2023-10-31.q110 Practice Test (Page 17)

Question 76

You intend to introduce ordering in message processing for your JMS destination by creating a destination key.
Which statement is true about the JMS Destination Key configuration? (Choose the best answer.)

A.A JMS Destination Key cannot be specified using WLST.

B.A JMS Destination Key cannot be used to sort messages in a Last In First Out order.

C.A JMS Destination Key allows a user-defined sort key.

D.A Destination Key can be applied to the message body.

Question 77

You are managing a WebLogic domain that has the default built-in diagnostic module configured for each server in the domain.
You have the following requirements:
What are two approaches you can apply to achieve this result? (Choose two.)

A.Clone the built-in module, add now metrics to it, deactivate the existing module, and activate your new module.

B.Leave the built-in module, create a new module and add metrics to it, and activate your new module alongside the built-in module.

C.Leave the built-in module, create an external resource descriptor module and add metrics to it, and activate your new module alongside the built-in module.

D.Remove the built-in module, create an external resource descriptor module and add built-in and new metrics to it, and activate your new module alongside the built-in module.

Question 78

You are required to configure a Coherence cluster for a WebLogic domain. Review the image below for the architecture of the WebLogic domain.

The configuration represents the following:
Two WebLogic clusters of n number of servers each

One cluster contains an EAR deployment that contains a WAR module and a GAR module

One cluster contains a GAR deployment

Application data flows into the cluster with the EAR deployment and then to the cluster with the

standalone GAR deployment
Based on this configuration, what is the typical configuration of a Coherence cluster for this domain?

A.Single Coherence cluster that includes both WebLogic clusters.
EAR cluster is storage-disabled.
GAR cluster is storage-enabled.

B.Single Coherence cluster that includes both WebLogic clusters/
EAR cluster is storage-enabled.
GAR cluster is storage-disabled.

C.A Coherence cluster for each WebLogic cluster.
EAR and GAR clusters use a replicated topology with storage enabled.

D.Single Coherence cluster that includes both WebLogic clusters.
EAR and standalone GAR clusters are both storage-enabled.

Question 79

Review the diagram below. It depicts the following:

Assuming the next request for an HTTP session attribute is a new attribute that is not stored in a near-cache, the client's session attribute is fetched from the remaining storage- enabled server in cluster 2.
Why is the session attribute retrieved from this other server's cache? (Choose the best answer.)

A.Coherence*Web stores sessions in a distributed cache on the back end and the request fails over to the new location after partition re-balancing takes place.

B.Coherence*Web stores sessions in a replicated cache on the back end and the request fails over to the new location automatically.

C.Coherence*Web stores sessions in a shared disk cache on the back end and Coherence*Web automatically load balances requests.

D.Coherence*Web stores sessions in a cache that is backed by a database cache loader.
The data is fetched from the database and placed into the cache on the new server.

Question 80

Review the diagram below. It depicts the following:
* A WebLogic domain that consists of two WebLogic clusters that are each included in a Coherence cluster
* The Coherence cluster includes a configuration for Coherence*Web HTTP session storage
* An application deployed on cluster 1 that is configured to use Coherence*Web
* A client is using a web browser to interact with the application on cluster 1 (via a proxy)
* The client's HTTP session is stored by Coherence*Web on the server in the upper right-hand corner
* The server where the client's HTTP session is stored crashes

Assuming the next request for an HTTP session attribute is a new attribute that is not stored in a near-cache, the client's session attribute is fetched from the remaining storage-enabled server in cluster 2.
Why is the session attribute retrieved from this other server's cache? (Choose the best answer.)