Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-134 Topic 4 Question 99 Discussion

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

Review this scenario of an application running on a storage-disabled, managed Coherence server that uses a Coherence two-tier near cache:

Cache data is already written to the distributed cache.

There is a local near cache configured on the application side (storage-disabled node).

Application requests the data from Coherence twice.

Assuming this is the server's first access of this data from the cache, how many network round trips between Coherence cluster instances take place in total? (Choose the best answer.)

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Emelda
3 months ago
That makes sense, but wouldn't the near cache still need to be accessed?
upvoted 0 times
...
Quinn
3 months ago
I disagree, I believe the answer is D) 2 because the data is already in the distributed cache.
upvoted 0 times
...
Una
3 months ago
This question is like a riddle wrapped in a mystery inside an enigma... but I think I've got it. The data is already in the distributed cache, so the first request would hit the near cache and get it from there. The second request would also find it in the near cache. That's 2 network round trips total, so I'm choosing D.
upvoted 0 times
Latrice
3 months ago
Yeah, I agree. It's definitely 2 round trips in total.
upvoted 0 times
...
Ollie
3 months ago
I think you're right, the data is already in the near cache so it would only be 2 network round trips.
upvoted 0 times
...
...
Tasia
3 months ago
Wait, wait, wait... if the data is already in the distributed cache, and the near cache is configured, shouldn't the application just be able to grab it from the near cache on the first try? That's 1 network round trip, right? I'm going with C, and I'm also going to grab a coffee while I wait for the results.
upvoted 0 times
Marge
3 months ago
I'm with you both on this one. Option C seems to be the most logical answer based on the scenario provided. Let's see if we're correct after grabbing that coffee.
upvoted 0 times
...
Thaddeus
3 months ago
Yeah, I also believe it should be 1 network round trip since the data is already in the distributed cache and the near cache is configured. Option C sounds like the correct choice.
upvoted 0 times
...
Marcelle
3 months ago
I think you're right, the data should be retrieved from the near cache on the first try. So, it should be just 1 network round trip. I agree with you, let's go with option C.
upvoted 0 times
...
...
Emelda
3 months ago
I think the answer is A) 3 because the data is requested twice.
upvoted 0 times
...
Anthony
3 months ago
You're right, I see your point now. The answer might indeed be A) 3.
upvoted 0 times
...
Tamar
4 months ago
Ah, the classic Coherence two-tier near cache scenario. I'd say 1 round trip, because the data is already in the distributed cache, so the near cache should serve it up without needing to go back to the cluster. C is the way to go, my friend.
upvoted 0 times
...
Buck
4 months ago
But doesn't the application request the data twice, causing additional network round trips?
upvoted 0 times
...
Anthony
4 months ago
I disagree, I believe the answer is D) 2 because the data is already in the distributed cache.
upvoted 0 times
...
Ruth
4 months ago
3 network round trips? Nah, that's too many. Since the data is already in the distributed cache, the application should only need to check the near cache first, and then fetch from the distributed cache if it's not there. That's 2 round trips, so I'm going with D.
upvoted 0 times
Beckie
2 months ago
D it is then, makes sense.
upvoted 0 times
...
Lisbeth
3 months ago
Definitely D, only 2 round trips needed.
upvoted 0 times
...
Evelynn
3 months ago
Yeah, I agree. D is the best option.
upvoted 0 times
...
Yaeko
3 months ago
I think it's 2 round trips too. D sounds right.
upvoted 0 times
...
...
Buck
4 months ago
I think the answer is A) 3 because the data is requested twice from the Coherence cluster.
upvoted 0 times
...
Aaron
4 months ago
Hmm, let me think about this. If the data is already in the distributed cache, and the near cache is on the application side, I'd say 2 network round trips would be needed to fetch the data. The first one to check the near cache, and the second one to get it from the distributed cache if it's not in the near cache. Pretty straightforward, I'd go with D.
upvoted 0 times
Norah
3 months ago
Yeah, I think D makes the most sense in this scenario.
upvoted 0 times
...
Lisbeth
3 months ago
I agree with you, D seems like the most logical choice here.
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