What is true concerning this configuration?

You are monitoring your Data Guard broker configuration and issue this set of DGMGRL commands:
DGMGRL> SHOW CONFIGURATION
Configuration – DRSolution
Protection Mode: MaxPerformance
Databases:
Close_by-Primary database
FS_inst- Far Sync
Far_away –Physical standby database
Fast-Start Failover: DISABLED
Configuration Status:
SUCCESS
What is true concerning this configuration?

A.
The Close_by primary database instance forwards redo to the FS_inst Far Sync instance, which forwards the redo in turn to the Far_away physical standby
database instance.

B.
The far sync instance will not forward redo to the Far_away physical standby because the Protection mode is not MaxProtection.

C.
The close_by primary database forwards redo to the Far_away physical standby directly and also sends redo to the FS_inst Far Sync instance.

D.
The far sync instance will not forward redo to the Far_away physical standby because Fast-Start Failover is disabled.

E.
The FS_inst Far Sync instance forwards redo to the Far_away physical standby only if the close_by primary database is not able to do so.

Explanation:
An Oracle Data Guard far sync instance is a remote Oracle Data Guard destination that accepts redo from the primary database and then ships that redo to other
members of the Oracle Data Guard configuration. A far sync instance manages a control file, receives redo into standby redo logs (SRLs), and archives those
SRLs to local archived redo logs, but that is where the similarity with standbys ends. A far sync instance does not have user data files, cannot be opened for

access, cannot run redo apply, and can never function in the primary role or be converted to any type of standby database.

https://docs.oracle.com/database/121/SBYDB/create_fs.htm