What are two benefits of migrating from a vPC design to FabricPath? (Choose two.)

FabricPath uses a routed Layer 2 architecture with IS-IS for topology distribution and ECMP for load balancing, allowing networks to scale to hundreds of switches across a flat Layer 2 domain - far beyond the two-switch vPC peer limitation.

FabricPath does not inherently provide lower latency than a well-designed vPC topology; both operate at similar switching speeds and latency is not a primary differentiator.

FabricPath introduces additional complexity including IS-IS configuration, FabricPath-capable hardware requirements, and new design considerations, making it more complex to configure than vPC.

FabricPath eliminates Spanning Tree Protocol entirely and replaces it with IS-IS-based topology calculation and loop-free ECMP forwarding, removing the instability risks associated with STP topology changes, TCNs, and vPC peer-link failures.

FabricPath is generally considered more operationally complex than vPC due to its IS-IS control plane and specialized hardware requirements, so ease of management is not a benefit.