Oracle Exam 1Z0-900 Topic 5 Question 83 Discussion

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

Question #: 83
Topic #: 5

Given:

Which annotation do you use on line 1 to ensure that clients immediately time out when attempting to concurrently invoke callMethod () while another client is already accessing the bean?

A@AccessTimeout (value = 1, unit = TimeUnit.SECONDS)

B@AccessTimeout (null)

C@AccessTimeout (-1)

D@AccessTimeout (0)

Show Suggested Answer

Suggested Answer: D

by Val at Jun 19, 2024, 02:16 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Kristeen

5 months ago

D) @AccessTimeout (0) all the way! I want my clients to feel the need for speed, even if it means they crash and burn every time they try to access the bean.

upvoted 0 times

...

Gianna

5 months ago

B) @AccessTimeout (null) has got to be the way to go. Nothing says 'I don't care about concurrency' like a nice, relaxed null timeout.

upvoted 0 times

Brittni

3 months ago

@AccessTimeout (null) does seem like it doesn't care about concurrency.

upvoted 0 times

...

Myra

3 months ago

Really? I would go with @AccessTimeout (0) to immediately time out.

upvoted 0 times

...

Heidy

3 months ago

I think @AccessTimeout (null) is the best option.

upvoted 0 times

...

Ezekiel

4 months ago

@AccessTimeout (null) does seem risky for concurrency issues.

upvoted 0 times

...

Justine

4 months ago

Really? I would go with @AccessTimeout (0) to immediately time out.

upvoted 0 times

...

Barrett

4 months ago

I think @AccessTimeout (null) is the best option.

upvoted 0 times

...

Genevive

4 months ago

I agree, @AccessTimeout (null) does not provide the desired concurrency control.

upvoted 0 times

...

Genevive

5 months ago

I think @AccessTimeout (null) is not the best option for ensuring immediate timeout.

upvoted 0 times

...

Tammara

5 months ago

I believe option C) @AccessTimeout (-1) would mean no timeout, so that might not be the best choice

upvoted 0 times

...

Malinda

5 months ago

I'm going with C) @AccessTimeout (-1). Seems like a good way to make sure no one can ever access the bean. Gotta love those aggressive timeouts!

upvoted 0 times

Zoila

4 months ago

Yeah, D) @AccessTimeout (0) might not be the best choice for handling concurrent access. It's important to consider the implications of the timeout value.

upvoted 0 times

...

Nicolette

4 months ago

I'm not sure, but I think D) @AccessTimeout (0) would mean no timeout at all, which could cause concurrency issues.

upvoted 0 times

...

Fabiola

5 months ago

I agree, maybe A) @AccessTimeout (value = 1, unit = TimeUnit.SECONDS) would be a better option for a short timeout.

upvoted 0 times

...

Carmelina

5 months ago

I think C) @AccessTimeout (-1) is too aggressive. It will block everyone from accessing the bean.

upvoted 0 times

...

Tonette

5 months ago

I'm not sure, but I think option B) @AccessTimeout (null) might also work

upvoted 0 times

...

Marge

5 months ago

I agree with Lamonica, using a value of 1 second makes sense to ensure quick timeout

upvoted 0 times

...

Raymon

5 months ago

A) @AccessTimeout (value = 1, unit = TimeUnit.SECONDS) seems like the correct answer here. This will ensure that clients time out immediately if another client is already accessing the bean.

upvoted 0 times

Emmanuel

4 months ago

Yes, that option will make sure clients time out quickly if needed.

upvoted 0 times

...

Horace

5 months ago

I agree, @AccessTimeout (value = 1, unit = TimeUnit.SECONDS) is the way to go.

upvoted 0 times

...

Lamonica

5 months ago

I think the correct annotation is A) @AccessTimeout (value = 1, unit = TimeUnit.SECONDS)

upvoted 0 times

...