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-134 Topic 9 Question 98 Discussion

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

For some reason, servers in your domain are failing. The host machines are pingable and the WebLogic JVM processes are running but the getState() method on the ServerRuntimeMBean reports FAILED.

In the future, when this happens, you want these failed servers to be shut down and then restarted automatically without human intervention. At the same time, you want to constrain how much time will be spent restarting those servers and how many restart attempts will be made.

Pick the two options that would help with this situation. (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Margret
28 days ago
A 'positive integer' - so no negatives or decimals? Whew, that narrows it down!
upvoted 0 times
Stacey
7 days ago
B) When starting Node Manager, use the WLST nmStart command and pass in a WLST properties object with RestartMax set to an appropriate positive integer.
upvoted 0 times
...
Ellsworth
14 days ago
A) For each server (or cluster), set RestartInterval to an appropriate positive integer.
upvoted 0 times
...
...
Owen
30 days ago
Rima
upvoted 0 times
...
Rima
1 months ago
A and B make perfect sense. Gotta love that 'appropriate positive integer' though, sounds like a riddle to solve!
upvoted 0 times
...
Ezekiel
1 months ago
I agree with Moon, A and B are the way to go. Automatic restart with time and attempt constraints is exactly what we need here.
upvoted 0 times
Edmond
18 days ago
I think A and B are the best options for automatically restarting the failed servers.
upvoted 0 times
...
...
Fairy
1 months ago
C is not a good choice since it requires manual intervention. D is about replication, which is not relevant to the problem at hand.
upvoted 0 times
Lilli
1 days ago
B) When starting Node Manager, use the WLST nmStart command and pass in a WLST properties object with RestartMax set to an appropriate positive integer.
upvoted 0 times
...
Irving
11 days ago
A) For each server (or cluster), set RestartInterval to an appropriate positive integer.
upvoted 0 times
...
...
Moon
2 months ago
A and B seem like the right options to automate the restart process and control the time and number of attempts.
upvoted 0 times
Luther
7 days ago
A and B seem like the right options to automate the restart process and control the time and number of attempts.
upvoted 0 times
...
Phillip
17 days ago
B) When starting Node Manager, use the WLST nmStart command and pass in a WLST properties object with RestartMax set to an appropriate positive integer.
upvoted 0 times
...
Eun
2 months ago
A) For each server (or cluster), set RestartInterval to an appropriate positive integer.
upvoted 0 times
...
...
Ernest
3 months ago
I agree with Winfred. Option B also seems useful as setting RestartMax would limit the number of restart attempts.
upvoted 0 times
...
Winfred
3 months ago
I think option A would help because setting RestartInterval would control how often the servers are restarted.
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