When SYNC redo transport mode is combined with Maximum Protection mode, it ensures that no data loss will occur (requirement 1). The physical standby can be converted to a snapshot standby (requirement 2) and later to a logical standby database (requirement 5), satisfying both transformation requirements. Transactions commit as soon as redo data is received by the standby database (requirement 3). The availability of the primary is not dependent on the standby database in Maximum Protection mode, as the primary database will halt if the standby cannot acknowledge the redo (requirement 4), thus indirectly ensuring its availability. It is also possible to deploy Real Application Clusters on both the primary (requirement 6) and the physical standby database (requirement 7), providing high availability and scalability.
Reference
Oracle Data Guard documentation detailing the requirements for different database roles, protection modes, and redo transport modes, as well as the capabilities and limitations of each configuration.