When setting up a Data Guard Broker configuration for a primary database and its physical standby, the following prerequisites must be met:
A: Oracle Net connectivity must be defined on both the primary and standby hosts to enable the respective database instances to communicate with each other.
B: Supplemental logging is required on the primary database because it provides additional logging necessary for the standby database to be able to apply changes from the primary database accurately.
F: The DG_BROKER_START parameter must be set to TRUE for both the primary and standby database instances. This parameter is used to start the Data Guard Broker process which manages the configuration.
Options C and D are not prerequisites for creating a Data Guard Broker configuration. Additionally, while FORCE LOGGING mode (option E) is recommended as a best practice to prevent possible data inconsistencies during media recovery, it is not a strict prerequisite for creating a Data Guard Broker configuration.

The command performs a comprehensive set of database checks prior to a role change (A): The VALIDATE DATABASE command in Data Guard Manager (DGMGRL) is designed to perform an exhaustive check of a specified database's readiness for a role change, such as a switchover or failover.
The command performs network connectivity checks between members of a broker configuration (C): One of the checks includes verifying that the necessary network connectivity exists between the databases in a Data Guard Broker configuration.
The command can be used for a logical standby database (D): The VALIDATE DATABASE command is versatile and can be used for both physical and logical standby databases to ensure their readiness for role changes.
Reference:
Oracle Data Guard Broker documentation
Oracle Data Guard Concepts and Administration Guide

In a Data Guard configuration where the protection mode is set to Maximum Availability and synchronous redo transport is enabled, if the standby destination fails to acknowledge the reception of redo within the net_timeout period, the primary database will terminate the synchronous redo transport mode connections to the standby database to protect the primary database from hanging (C). The primary database then operates in a Maximum Performance mode until the issue is resolved. This behavior ensures that the primary database can continue to process transactions even when the standby database is temporarily unavailable.
Reference:
The Oracle Data Guard Broker documentation and Oracle Data Guard Concepts and Administration guide detail the behavior of different protection modes and the response to network timeouts, including the fallback to asynchronous redo transport to maintain primary database availability.