which outcome would you expect?

Your domain includes a cluster of five servers, but only three are currently running. A colleague
then uses the administration console to install and deploy a new EJB application to the cluster.
By default, which outcome would you expect?

A.
The application deploys successfully on the three servers that are running.

B.
The deployment fails because the entire cluster is not running.

C.
The deployment succeeds, but the application is not accessible.

D.
The user is prompted to start the two unavailable servers before continuing.

E.
The two unavailable servers are automatically removed from the cluster.

Explanation:
Note #1: If your EJBs will run on a WebLogic Server cluster, Oracle recommends that you deploy
them homogeneously—to each Managed Server in the cluster. Alternatively, you can deploy an
EJB to only to a single server in the cluster (that is, “pin” a module to a server). This type of
deployment is less common, and should be used only in special circumstances where pinned
services are required.
Note #2: When you deploy an EJB, you specify the servers and clusters to which the EJB
deployment is targeted. After you have deployed an EJB, you can update the servers and clusters
to which it is targeted.
To set target servers and clusters for a deployed EJB:
The right pane lists the EJBs and other modules that you have deployed, or tried to deploy.
Servers and clusters in the domain are displayed.
By default, the Administration Console deploys an EJB to all server instances in the cluster (the “
All servers in the cluster” option). To deploy the EJB to selected servers in a cluster, select “
Part of the cluster”, and then select the individual server instances to which you want to deploy
the EJB.