Which two aspects are considered when designing a dual hub dual DMVPN cloud topology? (Choose two )

Dual hub dual DMVPN is specifically suited to single-tier headend architectures where both hubs reside at the same network tier with no hierarchical relationship between them - a dual-tier (hierarchical) design would use a different topology such as regional hubs feeding a central hub.

In dual hub dual DMVPN, each hub anchors only one DMVPN cloud - spokes have tunnel interfaces into both clouds, but each individual hub does not connect to both clouds.

The core purpose of deploying two hubs across two separate DMVPN clouds is fault tolerance - if one hub or its associated cloud fails, spokes maintain connectivity through the second hub and cloud, which is the definition of high availability.

Spoke-to-spoke traffic behavior is determined by DMVPN phase selection (Phase 1 hubs traffic, Phase 2/3 allows direct spoke tunnels), not by whether a dual hub dual cloud topology is used.

Spoke sites do not require dual Internet connections - a single connection can carry tunnel interfaces to both DMVPN clouds using separate logical tunnel endpoints.