County north-south routing must run Active-Active or Active-Standby on the shared internet Tier-0. At associate GUI depth, where is that HA mode selected rather than BGP neighbor stanzas?
Select an answer to reveal the explanation.
Short Explanation
Active-Active versus Active-Standby is like choosing one mayor or two co-mayors for the internet driveway. That choice lives on the Tier-0 form itself, not on a vSphere HA checkbox and not in BGP neighbor poetry.
Full Explanation
County north-south Active-Active or Active-Standby behavior for the shared internet Tier-0 is selected with the HA Mode field on the Networking > Tier-0 Gateway form. At associate depth, that gateway HA mode is distinct from deep BGP neighbor stanza tuning—operators choose how the Tier-0 Edges share or fail over the civic internet path on the Tier-0 form itself. Security > Context Profiles define application attributes for rules, not Tier-0 HA mode. vSphere HA admission control protects VM restart capacity in a vSphere cluster; it is not the NSX Tier-0 failover mode setting. Backup & Restore schedules protect configuration; they do not set Tier-0 HA mode. Exam caveat: Active-Active vs Active-Standby constrains which stateful services and traffic patterns are supported—do not assume every service works identically in both HA modes. Operational check: open the internet Tier-0, confirm HA Mode matches the county design (AA vs AS), verify both Edges are in the Edge cluster, and run a controlled failover test during a maintenance window; document mode and test results for change control. If the county later enables additional stateful services on the Tier-0 path, revisit HA Mode compatibility in the design review so Active-Active assumptions do not silently break NAT or firewall state requirements.