Refer to the exhibit. A new high availability DB server cluster is installed in the network. These two servers require high bandwidth and low latency Layer 2 connectivity for database replication…

LACP trunk aggregates bandwidth effectively but the inclusion of STP means redundant ports will be blocked or face reconvergence delays of up to 30-50 seconds with classic STP, which is incompatible with the low-latency requirement for DB replication.

Configuring the new links as separate REP segments 1 and 2 conflicts with existing segment IDs already assigned in the ring, causing a configuration error and failing to properly integrate the DB servers into the current REP ring topology.

REP secondary links add an alternate port within an existing REP segment, allowing the DB servers to leverage the ring topology's fast failover (under 50ms) without the blocking delays inherent to STP. This approach maintains the existing ring architecture, provides dedicated high-bandwidth Layer 2 paths, and meets the low-latency requirement for synchronous database replication.

Adding a new REP segment 3 between SW1 and SW2 creates an isolated segment outside the established ring topology, which does not leverage the ring's redundancy mechanism and does not provide an optimal Layer 2 path for the DB cluster.