The new Parks Tier-1 gateway must reach the city's ISP. What should the operator configure on that Tier-1 in the NSX GUI?
Select an answer to reveal the explanation.
Short Explanation
Parks is a department lobby that still needs the city's front door. On the Tier-1 form, link it to the existing Tier-0 that already faces the ISP. Do not BGP the ISP on the T1, and do not pretend Horizon or DFW is a next hop.
Full Explanation
Northbound connectivity for a Tier-1 is configured by connecting, or linking, that Tier-1 to a Tier-0 on the Tier-1 form. Parks is a department lobby that still needs the city's front door—the existing Tier-0 that already faces the ISP. ISP BGP peering belongs on the Tier-0, not as a direct neighbor on the tenant gateway. Horizon Unified Access Gateway is an EUC edge, not an NSX northbound hop. Distributed Firewall Ethernet rules do not create a route to the ISP. Exam caveat: linking Tier-1 to Tier-0 is the standard two-tier northbound step; skipping Tier-0 for direct ISP BGP on Tier-1 is the distractor this item rejects. Operational check: on the Parks Tier-1 form, set the Tier-0 link, advertise or confirm routes, test reachability from a Parks VM toward the ISP path, and reject direct T1 BGP, UAG, and DFW Ethernet as the northbound config. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish. Document the civic rationale in the change record so the next operator can restate why the correct control matches the agency outcome, why each distractor fails by concept, and which NSX Manager view confirms the result after publish.