What happens when the dasher node fails?

A customer is using the policy-managed database by name RACDB on a 4-node cluster. The server
names in the Cluster are: dasher, vixen, comet, and dancer.
There are two server pools defined, frontoffice and backoffice. The attributes are as follows:
ServerpoolImportance MinMax
Frontoffice1022
BackOffice512
There are two uniform services being created, crmsrv and hrsrv.
crmsrv is being assigned to serverpoolfrontoffice and hrsrv is assigned to backoffice.
Currently, all four nodes are up and running. The database and its services are running as follows:
The serverpoolfronoffice, which is running the crmsrv service is being run on the dasher and vixen
hosts.
The serverpoolbackoffice, which is running hrsvc service is being run on comet and dancer hosts.
What happens when the dasher node fails?

A.
Nothing happens because any service relocation is a major interruption to the clients who are
connecting to the services.

B.
One of the nodes is moved from the backofficeserverpool to the fronofficeserverpool. This is
moved with the consideration of importance and minimum attributes configured. Effectively, the
crmsrv service will run in two nodes and hrsvc will run in one node.

C.
Rebootlescrs cluster stack will be tried in all the cluster nodes to resolve the issue. If this is not
resolved, all nodes in the cluster get bounced to resolve the issues.

D.
Because the crmsrv service is defined as uniform service the cluster ensures at least one node is
up and running, which is the current case. So, there will be no service relocation that will happen.