Explanation/Reference:
A: Maximum Performance
This protection mode provides the highest level of data protection that is possible without affecting the performance of a primary database. This is accomplished by allowing transactions to commit as soon as all redo data generated by those transactions has been written to the online log. Redo data is also written to one or more standby databases, but this is done asynchronously with respect to transaction commitment, so primary database performance is unaffected by delays in writing redo data to the standby database(s).
E: Increasing the bandwidth would decrease the lag.
Note: If STANDBY_MAX_DATA_DELAY is set to a non-zero value, a query issued to a physical standby database will be executed only if the apply lag is less than or equal to STANDBY_MAX_DATA_DELAY.
Otherwise, an ORA-3172 error is returned to alert the client that the apply lag is too large.
References:
https://docs.oracle.com/cd/B28359_01/server.111/b28294/protection.htm
http://docs.oracle.com/html/E26088_02/statements_2013.htm