Which three steps must be completed to configure Fast Connection Failover for the CRM service with an Oracle Call Interface client?

Which three steps must be completed to configure Fast Connection Failover for the CRM service
with an Oracle Call Interface client?

A.
Ensure that the CRM service has Advanced Queuing notifications enabled by setting the
services values of AQ_HA_NOTIFICATIONS to TRUE.
For example:
$ srvctl modify service -d crm -s gl.us.oracle. com \
-q TRUE -P BASIC -e SELECT -z 180 -w 5 -j LONG

B.
Enable OCI_EVEINTS on the client at environment creation time by using the
OCIEnvCreate(�) function.

C.
Use Oracle Call Interface to configure UP events for the service.

D.
Client applications must be linked with the client thread or operating system library.

Explanation:
Configuring FCF for OCI Clients
OCI applications must connect to an Oracle RAC instance to enable HA event notification.
Furthermore, these applications must perform the following steps to configure FCF for an OCI
client:
Configure the service for your OCI connection pool to enable connection load balancing and
runtime connection load balancing. Also configure the service to have Advanced Queuing
notifications enabled, as shown in the following example:
$ srvctl modify service -d crm -s ociapp.example.com -q TRUE -B THROUGHPUT -j LONG
Set the context of the environment for OCI calls on the client to enable subscriptions by using the
OCIEnvCreate() call, setting the MODE parameter value to OCI_EVENTS, as follows:
(void) OCIEnvCreate(&myenvhp, OCI_EVENTS|OCI_OBJECT, …);
Link the application with a thread library.
After linking with the thread library, the applications can register a callback that is invoked
whenever a FAN event occurs.
Oracle Real Application Clusters Administration and Deployment Guide
11g Release 2 (11.2)