A regional emergency-management organization runs workloads across multiple Availability Zones but terminates all Direct Connect virtual interfaces on a single path lacking diversity. What should a resilience review recommend?
Select an answer to reveal the explanation.
Short Explanation
Multi-AZ apps with one skinny Direct Connect straw still choke when that straw breaks. Spread DX locations or connections so hybrid ingress matches the resilience you built in the Region. AZ diversity in compute does not magically duplicate your circuit.
Full Explanation
Resilient hybrid architectures require path diversity for Direct Connect—commonly multiple connections and/or distinct Direct Connect locations—plus routing that can fail over. Multi-AZ placement of workloads improves infrastructure resilience inside the Region but does not substitute for redundant hybrid circuits. Eliminating private hybrid connectivity or collapsing to a single AZ weakens emergency-management posture.