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

Dual hub dual cloud provides redundancy by maintaining two independent DMVPN clouds, each anchored by a separate hub, so that if one hub fails all spokes can continue communicating through the surviving hub and its cloud.

Spokes do not require dual Internet connections - they connect to both DMVPN clouds for redundancy but can route both tunnel endpoints across a single uplink using different NHS addresses.

With DMVPN Phase 2 or Phase 3, spokes can build direct spoke-to-spoke tunnels via NHRP resolution without transiting the hub, so hub transit is not a defining characteristic specific to the dual hub dual cloud topology.

In a dual hub dual cloud design each hub serves as the NHS for its own dedicated cloud, not both clouds - it is the spokes that connect to both clouds to achieve redundancy.

The dual hub dual cloud design is constrained to a single-tier headend architecture in which each hub directly terminates spoke tunnels - hierarchical or multi-tier designs require different DMVPN topologies such as a dual-tier hub-and-spoke arrangement.