Which three actions should be performed to check whether the new nodes are ready for running addNode.sh and to help correct any problems?

After evaluating the various methods for extending a cluster, you decide to use addNode.sh.
The cluster originally consisted of four nodes: RACNODE1, RACNODE2, RACNODE3, and
RACNODE4. Now two nodes called RACNODES and RACNODE6 have been installed and
connected to the cluster by OS administrations.
Which three actions should be performed to check whether the new nodes are ready for running
addNode.sh and to help correct any problems?

A.
cluvfy stage -pre crsinst -n RACNODE5/ RACNODE6 -C + DATA -q +VOTE -orainv

B.
<oinstall group> -fixup -verbose

C.
cluvfy stage -post hwos -n RACNODE5, RACNODE6 -verbose

D.
cluvfy comp peer -refnode RACNODE1 -n RACNODE5, RACNODE6 -orainv <oinstall group> -osdba <asmdba group> -verbose

E.
cluvfy stage -post hwos -n all -verbose

F.
cluvfy stage -pre nodeadd -n RACNODE5, RACNODE6 -fixup

G.
cluvfy comp peer -refnode RACNODES -n RACNODE6 -orainv <oinstall group> -osdba
<asmdba group> -verbose

Explanation:
$ cluvfy stage -post nodeadd -n node3 [-verbose]
Use the cluvfy comp peer component verification command to check the compatibility and
properties of the specified nodes against a reference node. You can check compatibility for non-default user group names and for different releases of the Oracle software. This command

compares physical attributes, such as memory and swap space, as well as user and group values,
kernel settings, and installed operating system packages.
Syntax
cluvfy comp peer -n node_list [-refnode node] [-r {10gR1 | 10gR2 | 11gR1 | 11gR2}] [-orainv
orainventory_group][-osdba osdba_group] [-verbose]
Usage Notes
Peer comparison with the -refnode option compares the system properties of other nodes against
the reference node. If the value does not match (the value is not equal to reference node value),
then CVU flags that comparison as a deviation from the reference node. If a group or user does
not exist on reference node as well as on the other node, CVU reports this comparison as ‘passed’
because there is no deviation from the reference node. Similarly, CVU reports as ‘failed’ a
comparison with a node that has more total memory than the reference node.
$ cluvfy stage -pre nodeadd -n node3 [-fixup [-fixupdir fixup_dir]] [-verbose]
You can specify the -fixup option and a directory into which CVU prints instructions to fix the
cluster or node if the verification fails.
Oracle Clusterware Administration and Deployment Guide