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 3 Question 95 Discussion

Actual exam question for Oracle's 1Z0-134 exam
Question #: 95
Topic #: 3
[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:

Esteban
5 months ago
Ah, the joys of Coherence caching! It's like a game of cache and seek, except the only prize is a headache. But I'm feeling lucky today, so I'll go with B) 4 round trips. After all, who needs sleep when you can spend all night trying to figure out these cache conundrums?
upvoted 0 times
...
Kathrine
5 months ago
This is a real head-scratcher, isn't it? Let me see if I can crack this nut. Okay, so the first request hits the near cache, no round trip. The second request also hits the near cache, still no round trip. But then the server needs to fetch the data from the distributed cache, that's one round trip. And when the data is returned to the application, that's another round trip. So that's a total of 2 network round trips. D) 2 is the way to go, my friends.
upvoted 0 times
Kandis
5 months ago
Yeah, I agree. The first two requests don't require any round trips, but the last two do.
upvoted 0 times
...
Jannette
5 months ago
I think you're right, it does seem like the answer is 2 network round trips.
upvoted 0 times
...
...
Dorethea
5 months ago
Wait, wait, wait. If the data is already in the distributed cache, then the first request from the application should hit the near cache, no round trip. The second request also hits the near cache, still no round trip. But then the server needs to fetch the data from the distributed cache, that's one round trip. So the total is 1 network round trip. C) 1 is the answer.
upvoted 0 times
...
Yan
5 months ago
Hmm, this is tricky. I'm thinking the first request hits the near cache, no round trip. The second request also hits the near cache, still no round trip. But then the server needs to fetch the data from the distributed cache, that's one round trip. And when the data is returned to the application, that's another round trip. So that's a total of 2 network round trips. I'll go with D) 2.
upvoted 0 times
Mira
4 months ago
Agreed, let's go with that.
upvoted 0 times
...
Martina
4 months ago
So, D) 2 is the best answer.
upvoted 0 times
...
Nan
4 months ago
Yeah, the near cache saves us some trips.
upvoted 0 times
...
Ilene
5 months ago
I think it's 2 round trips too.
upvoted 0 times
...
...
Shasta
5 months ago
You make a good point, maybe the answer is actually A) 3 after all.
upvoted 0 times
...
Amber
5 months ago
Okay, let me think this through. If the data is already in the distributed cache, then the first request should hit the near cache, no network round trip. The second request should also hit the near cache, so still no network round trip. But the first access from the server to the distributed cache would require one round trip. So the total is 1 network round trip. I'll go with C) 1.
upvoted 0 times
Tori
4 months ago
Yes, I agree. The total network round trips would be 1.
upvoted 0 times
...
Linsey
5 months ago
I think the answer is C) 1.
upvoted 0 times
...
...
Peter
5 months ago
But doesn't the application request the data twice, causing additional network round trips?
upvoted 0 times
...
Shasta
6 months ago
I disagree, I believe the answer is D) 2 because the data is already in the distributed cache.
upvoted 0 times
...
Peter
6 months ago
I think the answer is A) 3 because the data is requested twice and there is a local near cache involved.
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