Oracle Exam 1Z0-134 Topic 2 Question 108 Discussion

Actual exam question for Oracle's 1Z0-134 exam

Question #: 108
Topic #: 2

[All 1Z0-134 Questions]

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.)

ACoherence*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.

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

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

DCoherence*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.

Show Suggested Answer

Suggested Answer: E

Rolling upgrade applies only to upgrades within a major product version. For example, you can upgrade from 10.0 to 10.3.1, but cannot upgrade from 9.0 to 10.0.

by Lavonna at Nov 18, 2024, 08:35 PM

Limited Time Offer

25%

Off

Get Premium 1Z0-134 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Raelene

1 months ago

Haha, I bet the correct answer is just 'All of the above' and they're trying to trick us. Coherence is so complex, who knows how it really works under the hood!

upvoted 0 times

Lenna

10 days ago

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

upvoted 0 times

...

Chaya

13 days ago

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.

upvoted 0 times

...

Jess

15 days ago

I'm leaning towards 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.

upvoted 0 times

...

Honey

1 months ago

No, I believe it's B) Coherence*Web stores sessions in a replicated cache on the back end and the request fails over to the new location automatically.

upvoted 0 times

...

Yolando

1 months ago

I think it's 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.

upvoted 0 times

...

Alona

2 months ago

D sounds like the most comprehensive answer, mentioning the database cache loader. But I'm not familiar with how Coherence*Web integrates with databases.

upvoted 0 times

Torie

1 months ago

Yes, D seems to be the right choice. It explains how data is fetched from the database.

upvoted 0 times

...

Reita

1 months ago

Response 4: 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.

upvoted 0 times

...

Janey

1 months ago

I think D is correct. Coherence*Web uses a database cache loader to fetch data.

upvoted 0 times

...

Nikita

1 months ago

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

upvoted 0 times

...

Dell

1 months ago

D sounds like the most comprehensive answer, mentioning the database cache loader.

upvoted 0 times

...

Kristel

2 months ago

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

upvoted 0 times

...

Patria

2 months ago

Response 1: 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.

upvoted 0 times

...

Yoko

2 months ago

B seems plausible, but I'm not sure if Coherence*Web uses a replicated cache by default. Gotta read up on the cache topologies.

upvoted 0 times

...

Arlette

2 months ago

But doesn't Coherence*Web use distributed cache for session storage?

upvoted 0 times

...

Yong

2 months ago

I think the answer is A. Coherence*Web uses a distributed cache, so the session should fail over to another server after the original one crashes.

upvoted 0 times

Lili

1 months ago

Coherence*Web does a good job of handling these types of scenarios.

upvoted 0 times

...

Garry

2 months ago

Exactly, it's important for the application to continue functioning smoothly even if a server crashes.

upvoted 0 times

...

Page

2 months ago

I agree, that makes sense. It ensures high availability for session data.

upvoted 0 times

...

Corinne

2 months ago

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.

upvoted 0 times

...

Nakisha

2 months ago

I disagree, I believe the correct answer is D.

upvoted 0 times

...

Arlette

3 months ago

I think the answer is A.

upvoted 0 times

...