Cloud concept · Updated

Path Diversity - Path diversity is the use of multiple network routes with sufficiently independent infrastructure so that one failure does not interrupt all connectivity.

In short

Multiple connections provide meaningful resilience only when they avoid shared failure points such as routers, fiber conduits, carrier facilities, and cloud access locations. In hybrid cloud networks, path diversity combines independent connectivity with routing policies that move traffic onto surviving paths when a failure occurs.

Cloud Concepts Hub →

6 key aspects of Path Diversity

Effective path diversity combines verified infrastructure independence, predictable routing, adequate backup capacity, and tested recovery.

01
Independent failure domains

Separate paths across the components whose failure must be tolerated, including routers, conduits, facilities, and cloud access locations. Treat every shared component as a potential common cause of outage.

02
Verified physical separation

Obtain carrier route information and confirm building entrances, last-mile facilities, and underlying transport dependencies. Different providers or circuit identifiers do not establish physical independence.

03
Deliberate route selection

Use routing policies to implement active-active or active-passive operation and ensure alternate routes become usable after failure. Check prefix specificity, route-source precedence, advertisements, and return-path behavior.

04
End-to-end resilience

Evaluate the complete path rather than only the cloud-facing connection. Redundant cloud endpoints cannot compensate for a single customer router, firewall, power source, or access circuit.

05
Surviving-path capacity

Size remaining connections for the traffic they must carry during an outage. If backup connectivity cannot support the full workload, define which applications receive priority and validate the resulting performance.

06
Measured failover behavior

Test representative failures and measure detection time, routing convergence, packet loss, and application recovery. Include failures that impair forwarding without immediately bringing down a routing session.

Cloud services for Path Diversity

AWS Direct Connect supplies private hybrid connectivity, while AWS Site-to-Site VPN can provide an internet-based alternative with different transport dependencies. AWS Transit Gateway can bring these connectivity options together for multiple VPCs, using a Direct Connect gateway for the Direct Connect side and VPN attachments for the VPN side. Engineers must coordinate route propagation, advertisements, and route-selection behavior so the intended path is used during normal operation and failures. The services do not establish end-to-end independence automatically: customer routers, internet access, carrier facilities, and physical cable routes still require separate design and validation. Test surviving-path capacity and failover in both traffic directions.

AWS Direct ConnectAWS Direct Connect

Connections at separate Direct Connect locations can provide independent cloud access paths when paired with diverse carrier transport and customer equipment. Multiple connections at one location improve some forms of redundancy but retain a shared location-level risk.

AWS Site-to-Site VPNAWS Site-to-Site VPN

Internet-based IPsec connectivity can provide an alternative transport path to private circuits. Configure both tunnels, and use additional customer gateways and independent internet access where customer-side failure tolerance is required.

AWS Transit GatewayAWS Transit Gateway

Transit Gateway can connect VPCs with Direct Connect connectivity through a Direct Connect gateway and with Site-to-Site VPN attachments. Its route tables and propagation settings help control which hybrid paths are available, but do not create physical diversity in the underlying circuits.

Path Diversity exam questions

Real practice exam questions on Path Diversity, with the correct answer and its explanation. Answer them with every option in the exam simulator.

SAP-C03

A healthcare company runs clinical applications in AWS that continuously access an on-premises patient-record system. The company currently has two dedicated 10-Gbps AWS Direct Connect connections at one Direct Connect location. The connections terminate on separate AWS devices and use independent customer routers and physically diverse carrier paths. Either connection can carry the entire production workload.

An architecture review requires the connectivity design to protect against device failures, connectivity failures, and the complete loss of a Direct Connect location. The company also requires a topology that supports eligibility for the 99.99% Direct Connect SLA, subject to satisfying all other SLA requirements. Internet-based backup connectivity cannot substitute for this SLA requirement. Routing is already configured to use surviving connections automatically.

Which change meets these requirements with the FEWEST additional dedicated connections?

Show answerCORRECT ANSWER

Retain the existing connections and add two dedicated connections at a second Direct Connect location. Terminate the new connections on separate AWS devices and use independent customer routers and physically diverse carrier paths.

This creates the maximum resiliency model: two connections on separate devices at each of multiple locations. It protects against device, connectivity, and complete location failures and supports a 99.99% SLA target when all Direct Connect SLA requirements are met. Two additional dedicated connections are needed to complete this topology.

ANS-C01

A company is designing private connectivity from its data center to 40 VPCs distributed across two AWS Regions. Each Region will have an AWS Transit Gateway that provides connectivity for that Region's VPCs. The VPC CIDR blocks do not overlap.

The architecture must maintain connectivity to both Regions if an entire Direct Connect location becomes unavailable. Each surviving connection must support the full production workload. Traffic must not traverse the internet or use inter-Region transit gateway peering. The company wants to use a single Direct Connect gateway to provide access to both regional transit gateways.

Which design meets these requirements?

Show answerCORRECT ANSWER

Provision two adequately sized Direct Connect connections at separate Direct Connect locations, using independent customer routers and physically diverse access circuits. Create a transit virtual interface on each connection to the shared Direct Connect gateway. Associate both regional transit gateways with that gateway, assigning distinct Amazon-side ASNs to the transit gateways and an ASN to the Direct Connect gateway that differs from both.

Separate Direct Connect locations, independent routers, and diverse access circuits protect against a location-level failure. Transit virtual interfaces connect Direct Connect connections to a Direct Connect gateway that can be associated with transit gateways in multiple Regions. The regional transit gateways must have unique ASNs, and their ASNs must differ from the Direct Connect gateway ASN. With appropriate BGP advertisements and routing, either adequately sized connection can provide access to both Regions.

Practice Path Diversity in a full exam

Questions on Path Diversity in each practice exam, with every answer option and an explanation for each:

Start a free practice exam

What is Path Diversity

3 min read

Path diversity reduces the chance that a single network failure disconnects an application, site, or cloud environment. The objective is not simply to purchase two circuits, but to understand which physical and logical components those circuits share. Two connections can have different circuit identifiers and still traverse the same building entrance, underground conduit, carrier aggregation router, or cloud interconnection facility. A failure at any shared component can interrupt both connections.

Start by defining the failures the architecture must tolerate. Surviving a router failure requires different measures from surviving a fiber cut, an entire colocation facility outage, or the loss of an on-premises site. Trace each path from the application network through customer routers, firewalls, access circuits, carrier networks, cloud connectivity locations, and cloud routing attachments. Document shared dependencies and ask carriers to confirm physical route separation. Different carrier names alone do not prove independence because carriers can lease the same underlying fiber.

For an AWS hybrid network, a common design uses AWS Direct Connect connections at separate Direct Connect locations, with independent customer routers and diverse access circuits. Connections on different devices at one location improve device resilience but still share a location-level failure domain. A link aggregation group increases aggregate capacity and can tolerate individual member-link failures, but its links terminate on the same AWS device and do not provide location diversity. Requirements for higher resilience can justify multiple connections at each of multiple locations.

AWS Site-to-Site VPN can provide an alternative path over the internet when Direct Connect connectivity fails. Its independence depends on the underlying internet access: a VPN using the same customer router, carrier access circuit, or building entrance as Direct Connect may fail at the same time. Each VPN connection supplies two tunnels for AWS-side endpoint redundancy, but those tunnels do not by themselves eliminate a shared customer gateway or internet circuit. Greater customer-side resilience requires additional gateway devices and appropriately independent connectivity.

Physical diversity must be paired with deliberate routing. BGP can exchange reachable prefixes and withdraw routes when a session or path fails. Configure route advertisements and preferences for the intended active-active or active-passive behavior, and evaluate both traffic directions. AWS route-selection rules vary by gateway and route type, so do not assume that a preferred outbound path automatically becomes the preferred return path. More-specific advertisements, static routes, or inconsistent filtering can prevent the expected failover. Asymmetric routing can also disrupt traffic through stateful firewalls.

For example, a company might connect two edge routers to two Direct Connect locations and maintain an internet-based VPN as an additional recovery path. If one location becomes unavailable, the remaining Direct Connect path should carry the required workload. If both private paths fail, the VPN may preserve critical applications, provided its throughput, latency, tunnel configuration, and routing policies are suitable. Backup capacity must be evaluated under failure conditions rather than normal load alone.

The trade-offs include additional circuit charges, equipment, carrier coordination, routing complexity, and operational testing. Diversity does not guarantee uninterrupted sessions: failure detection and routing convergence take time, and some failures leave routing sessions established while application traffic is impaired. Test circuit, router, tunnel, and location failures; measure packet loss and convergence; and verify application recovery. The strongest evidence of useful path diversity is demonstrated connectivity through the failures the design is intended to withstand.

Learn Path Diversity in lessons

1 short lesson on Path Diversity in 1 certification course.

Open the lessons