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.) 

Answer options:

A. For each server (or cluster), set RestartInterval to an appropriate positive integer.
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.
C. Start the servers by executing the restartManagedWebLogic.sh script in the domain’s /bin directory.
D. Make sure all managed servers are members of a cluster with ReplicationGroupsEnabled set to true.

BC

B: The nmStart command identifies the server instance to start. You define the number of restarts by setting the RestartMax property in a Node Manager startup.properties file. If you use the nmStart command with WLST connected to a Node Manager, Node Manager supports monitoring, stopping, and restarting the Administration Server. /bin/ startManagedWebLogic.sh. Reference: https://docs.oracle.com/cd/E13222_01/wls/docs90/server_start/overview.html