The architect documented a requirement for 99.95% high availability to meet the customer's resiliency needs. Which two physical design decisions will help meet this requirement in the management…

Question

Options

• AManagement Port Group: Route based on physical NIC load
• BHost Overlay DHCP Scope Lease: 14 Days
• CPhysical Switch MTU: 9000
• DvSAN Cache Tier Sizing: 800GB
• EHost isolation response: Power Off and restart VM

• A
  71% (24)
• B
  18% (6)
• D
  3% (1)
• E
  9% (3)

Explanation

Options A and C are correct because they address physical network redundancy and proper encapsulation support - two foundational pillars for achieving 99.95% availability in the management domain.

A (Route based on physical NIC load) configures NIC teaming on the management port group to distribute traffic across multiple physical NICs and automatically reroute if one fails, eliminating a single point of failure at the physical adapter layer. C (Physical Switch MTU: 9000) enables jumbo frames, which is required for NSX overlay traffic (GENEVE encapsulation adds ~50–80 bytes of overhead); without it, packets fragment or drop silently, causing intermittent management plane failures that directly threaten availability.

B (DHCP lease duration) is an IP lifecycle setting - it has no impact on redundancy or fault tolerance. D (vSAN cache tier sizing) is a storage performance decision, not a management network design decision. E (Host isolation response: Power Off) is a vSphere HA logical policy, not a physical design decision, and "Power Off" is actually a more disruptive response that can cause unnecessary downtime if isolation is a false positive.

Memory tip: For HA in the management domain, think "traffic must keep flowing physically" - NIC teaming keeps traffic flowing if a NIC dies (A), and correct MTU keeps overlay packets intact in flight (C). Everything else here is either storage, software policy, or administrative tuning.

No community discussion yet for this question.