2V0-41.23 Exam Dumps : VMware NSX 4.x Professional

The answer is A. SR is instantiated and automatically connected with DR.

SR stands for Service Router and DR stands for Distributed Router. They are components of the NSX Edge node that provide different functions1

The SR is responsible for providing stateful services such as NAT, firewall, load balancing, VPN, and DHCP. The DR is responsible for providing distributed routing and switching between logical segments and the physical network1

When a stateful service is enabled for the first time on a Tier-0 Gateway, the NSX Edge node automatically creates an SR instance and connects it with the existing DR instance. This allows the stateful service to be applied to the traffic that passes through the SR before reaching the DR2

According to the VMware NSX 4.x Professional Exam Guide, understanding the SR and DR components and their functions is one of the exam objectives3

To learn more about the SR and DR components and how they work on the NSX Edge node, you can refer to the following resources:

• VMware NSX Documentation: NSX Edge Components 1
• VMware NSX 4.x Professional: NSX Edge Architecture
• VMware NSX 4.x Professional: NSX Edge Routing

The sequence of commands that could be used to check the BGP connection status between the Tier-O Gateway and the upstream physical router on NSX Edge node is get gateways, vrf , get bgp neighbor. These commands can be executed on the NSX Edge node CLI after logging in as admin6. The first command, get gateways, displays the list of logical routers (gateways) configured on the Edge node, along with their IDs and VRF numbers7. The second command, vrf , switches to the VRF context of the desired Tier-O Gateway, where is the VRF number obtained from the previous command7. The third command, get bgp neighbor, displays the BGP neighbor summary for the selected VRF, including the neighbor IP address, AS number, state, uptime, and prefixes received8. The other options are incorrect because they either use invalid or incomplete commands or do not switch to the correct VRF context. References: NSX-T Command-Line Interface Reference, NSX Edge Node CLI Commands, Troubleshooting BGP on NSX-T Edge Nodes

The following L2 VPN clients are recommended:

1. NSX Managed NSX Edge in a separate NSX Managed environment.

• Overlay and VLAN segments can be extended.

2. Autonomous Edge:

• Enables L2 VPN access from a non-a NSX environment to NSX environments.

• Deployed by using an OVF file on a host that is not managed by NSX.

• Only VLAN segments can be extended.