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
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.
A is correct for sure
Usage Notes
The far sync instance must already exist before you can add it to a broker configuration.
D is incorrect for sure
Usage Notes
A far sync instance that has its RedoRoutes property set cannot be disabled.
B is true for sure
DISABLE FAR_SYNC
Disables broker management of a far sync instance.
C is incorrect
Hi
Yes B is true
http://docs.oracle.com/database/121/DGBKR/dgmgrl.htm#DGBKR3685
A far sync instance that has its RedoRoutes property set cannot be disabled.
So correct answers are A and B
A – This is correct! The far sync instance is disabled after creation. You must explicitly enable it before the broker can ship redo to and from it.
B – This is correct! You cannot disable a far sync instance if it is specified in the RedoRoutes property of any other configuration member.
C – I’m not sure, but i think that this can be did under Oracle Enterprime Manager Cloud Control
D – This is wrong! The Data Guard Broker can’t create a Far Sync Instance, this can be did manually, then added to the broker configuration; ADD FAR_SYNC – Adds an existing far sync instance to an Oracle Data Guard broker configuration.
A, B
A and B are correct