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-900 Topic 9 Question 74 Discussion

Actual exam question for Oracle's 1Z0-900 exam
Question #: 74
Topic #: 9
[All 1Z0-900 Questions]

How can you configure, in a portable way, the number of threads used by a ManagedExecutorService?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Cassi
5 months ago
Overall, it seems like A) is the most straightforward and portable way to configure thread usage in a ManagedExecutorService.
upvoted 0 times
...
Marlon
5 months ago
I think D) configuring the thread pool info in the deployment descriptor is a bit more complex.
upvoted 0 times
...
Alison
5 months ago
I'm not sure about C) This cannot be done because of Java EE Product Provider dependency.
upvoted 0 times
...
Laurel
5 months ago
I believe B) using the ManagedExecutors utility class is also a valid option for configuring thread usage.
upvoted 0 times
...
Kris
5 months ago
I agree with that, it allows for flexibility in setting the number of threads.
upvoted 0 times
...
Eura
5 months ago
I think the correct answer is A) programmatically, using a ManagedExecutorService.
upvoted 0 times
...
Sue
5 months ago
I heard that it depends on the Java EE Product Provider, so it can't be configured.
upvoted 0 times
...
Devora
6 months ago
I think we can also configure the thread pool in the deployment descriptor.
upvoted 0 times
...
India
6 months ago
I'm not sure, maybe we can use the ManagedExecutors utility class.
upvoted 0 times
...
Jannette
6 months ago
I agree with Raul, we can set the number of threads that way.
upvoted 0 times
...
Raul
7 months ago
I think we can configure it programmatically using a ManagedExecutorService.
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