Which two are true about management of a far sync insta…

Which two are true about management of a far sync instance when using the Data Guard Broker?

A.
A far sync instance is in a disabled state in the broker configuration immediately after adding it.

B.
A far sync instance that has its RedoRoutes property set may not be disabled in the broker configuration.

C.
Broker management of a far sync instance may only be disabled with the disable configuration DGMGRL
command.

D.
A far sync instance need not exist before adding it to the broker configuration but may not be enabled until
created.

Explanation:
A: ADD FAR_SYNC
Adds an existing far sync instance to an Oracle Data Guard broker configuration.
The far sync instance is disabled after creation. You must explicitly enable it before the broker can ship redo to
and from it.
B: A far sync instance that has its RedoRoutes property set cannot be disabled.
Incorrect Answers:
D: The far sync instance must already exist before you can add it to a broker configuration.
https://docs.oracle.com/database/121/DGBKR/dgmgrl.htm