What is true about the attributes that may be set to control the application?

As part of your data center’s high availability strategy, you are creating resource definitions to
control the management of a web-based application by the Oracle Grid Infrastructure clusterware
stack.
The application and its VIP are normally online on one node of a four-node cluster due to the
CARDINALITY of the resource type being set to 1.
You have chosen a policy-managed resource type for the application by using a server pool that
uses only RACNODE3 and RACNODE4. The START ATTEMPTS attribute for the resource is set
to 2 and FAILURE
INTERVAL is set to 60.
What is true about the attributes that may be set to control the application?

A.
The clusterware will attempt to start the application on the same node twice within the server
pool as long as that node is up. If the node fails, then the VIP and the application will be failed over
to the other node in the server pool immediately.

B.
The clusterware will attempt to start the application on the same node twice within the server
pool as long as that node is up. If the node fails, then the VIP and the application will be failed over
to the other node in the server pool only after two 60-second intervals have elapsed.

C.
The clusterware will attempt to start the application on the same node twice within the server
pool as long as that node is up. If the application fails to start after 60 seconds, but the node is still
up, then the VIP and the application will NOT be failed over to the other node in the server pool.

D.
The clusterware will attempt to start the application on the same node twice within the server
pool as long as that node is up. If the application fails to start immediately but the node is still up,
then the VIP and the application will NOT be failed over to the other node in the server pool.

Explanation:
CARDINALITY
The number of servers on which a resource can run, simultaneously. This is the upper limit for
resource cardinality.
RESTART_ATTEMPTS
The number of times that Oracle Clusterware attempts to restart a resource on the resource’s
current server before attempting to relocate it. A value of 1 indicates that Oracle Clusterware only
attempts to restart the resource once on a server. A second failure causes Oracle Clusterware to
attempt to relocate the resource. A value of 0 indicates that there is no attempt to restart but
Oracle Clusterware always tries to fail the resource over to another server.
FAILURE_INTERVAL
The interval, in seconds, before which Oracle Clusterware stops a resource if the resource has
exceeded the number of failures specified by the FAILURE_THRESHOLD attribute. If the value is
zero (0), then tracking of failures is disabled.
FAILURE_THRESHOLD
The number of failures of a resource detected within a specified FAILURE_INTERVAL for the
resource before Oracle Clusterware marks the resource as unavailable and no longer monitors it.
If a resource fails the specified number of times, then Oracle Clusterware stops the resource. If the
value is zero (0), then tracking of failures is disabled. The maximum value is 20.
Oracle Clusterware Administration and Deployment Guide
11g Release 2 (11.2)