Which statement is true regarding the redo log files for the instance?

You are managing a policy-managed Real Application Cluster (RAC) database, RACDB with
Oracle Managed Files (OMF) enabled. Examine the following outputs:

You added a new server to the server pool using the following command:
[oracle@gr5153 ~]$ srvctl modify srvpool -g POOL1 -i 0 -l 2 -u 4 -n gr5119
The instance on the newly added node is started by the Oracle Clusterware. Automatic Storage
Management (ASM) is used as the storage option.

Which statement is true regarding the redo log files for the instance?

A.
Oracle Clusterware automatically creates and enables a new thread of red

B.
You must create redo log groups for the newly added service.

C.
Redo log members will not be created automatically because storage option used is ASM.

D.
The newly added instance must save full online log groups tracked in the control file.

Explanation:
For a policy-managed database, when you add a new node to the cluster, it is
placed in the Free pool by default. If you increase the cardinality of the database server pool, then
an Oracle RAC instance is added to the new node, racnode3, and it is moved to the database
server pool. No further action is necessary.
Add shared storage for the undo tablespace and redo log files.
If OMF is not enabled for your database, then you must manually add an undo tablespace and
redo logs.
You should create redo log groups only if you are using administrator-managed databases. For
policy-managed databases, if an instance starts due to a change in server pool cardinality, then
Oracle Database automatically creates redo log files, enables a redo thread for the instance if
there is not a redo thread allocated to that instance, and creates the undo tablespace if there is not
an undo tablespace allocated to that instance. The database must be using Oracle Managed Files
and Oracle ASM in this situation.
Oracle Database 2 Day + Real Application Clusters Guide