Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-133 Topic 4 Question 66 Discussion

Actual exam question for Oracle's 1Z0-133 exam
Question #: 66
Topic #: 4
[All 1Z0-133 Questions]

You require high availability for HTTP sessions in a web application. In addition, you have the following constraints:

* There is little free memory on the machines hosting the cluster.

* HA must be guaranteed even when multiple machines fall simultaneously.

* You are not allowed to update the production databases schem

a.

Which is the best session persistence option?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Daren
2 months ago
Database persistence? No way, not with that production database schema restriction. File persistence? Sounds like a recipe for disaster. In-memory replication is the clear winner here, assuming you have the RAM to spare.
upvoted 0 times
Tawanna
25 days ago
Definitely, it's the most suitable choice for high availability.
upvoted 0 times
...
Albina
1 months ago
Agreed, it's the best option given the constraints.
upvoted 0 times
...
Dorinda
1 months ago
In-memory replication
upvoted 0 times
...
...
Hoa
2 months ago
Ah, the age-old session persistence dilemma. In-memory replication is the way to go, as long as you have a robust caching solution. Otherwise, you might end up with a memory-hogging 'in-memory' nightmare!
upvoted 0 times
Karan
1 days ago
D: True, as long as we have a robust caching solution
upvoted 0 times
...
Kiera
4 days ago
C: In-memory replication can still work with proper caching
upvoted 0 times
...
Quentin
7 days ago
B: But what about the little free memory constraint?
upvoted 0 times
...
Afton
14 days ago
A: In-memory replication
upvoted 0 times
...
Princess
15 days ago
User 4: Definitely need to avoid that!
upvoted 0 times
...
Asuncion
24 days ago
User 3: Otherwise, it could turn into a memory-hogging nightmare
upvoted 0 times
...
Mitsue
1 months ago
User 2: Agreed, as long as we have a good caching solution
upvoted 0 times
...
Timothy
2 months ago
User 1: In-memory replication
upvoted 0 times
...
...
Lynna
2 months ago
Hmm, I don't know, in-memory replication seems risky with little free memory. Maybe file persistence is a safer bet, even if it's not as performant.
upvoted 0 times
...
Han
2 months ago
I was thinking D) Whole-server migration, but that might be overkill for just session persistence. In-memory replication sounds more appropriate.
upvoted 0 times
...
Nickolas
2 months ago
That's a good point, but I still think C) In-memory replication is more efficient given the constraints we have.
upvoted 0 times
...
Craig
2 months ago
C) In-memory replication seems like the best option here. It meets the high availability requirement while avoiding the database and file system constraints.
upvoted 0 times
Lisha
15 days ago
D) Whole --server migration
upvoted 0 times
...
Xuan
16 days ago
C) In-memory replication
upvoted 0 times
...
Martin
23 days ago
B) File persistence
upvoted 0 times
...
Tamra
1 months ago
A) Database persistence
upvoted 0 times
...
...
Raina
3 months ago
I disagree, I believe A) Database persistence is the best option because it ensures high availability even when multiple machines fall simultaneously.
upvoted 0 times
...
Nickolas
3 months ago
I think the best option is C) In-memory replication because it doesn't require updating the production database schema.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77