ECMP (Equal Cost Multi-Path) is a routing protocol that increases the north and south communication bandwidth by adding an uplink to the tier-0 logical router and configure it for each Edge node in an NSX Edge cluster 2 .  The ECMP routing paths are used to load balance traffic and provide fault tolerance for failed paths 2 .  The tier-0 logical router must be in active-active mode for ECMP to be available 2 .  A maximum of eight ECMP paths are supported 2 . Configuring ECMP on the tier-0 gateway can address low throughput and congestion by distributing the traffic among multiple paths and avoiding bottlenecks.

Deploying Large size Edge node/s can also address low throughput and congestion by providing more resources (memory, CPU, disk) for the Edge node to handle the network traffic.  The NSX Edge VM system requirements vary depending on the appliance size, which affects the bandwidth, NAT/firewall, load balancer, and VPN capabilities of the Edge node 1 .  A Large size Edge node has 32 GB memory, 8 vCPU, 200 GB disk space, and can support 2-10 Gbps bandwidth, L2-L4 features, and L7 load balancer 1 .  An Extra Large size Edge node has 64 GB memory, 16 vCPU, 200 GB disk space, and can support more than 10 Gbps bandwidth, L2-L4 features, L7 load balancer, and VPN 1 .  Deploying a larger size Edge node can improve the performance and capacity of the tier-0 gateway.  References :  2 : Understanding ECMP Routing - VMware Docs(https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/administration/GUID-443B6B0D-F179-429E-83F3-E136038332E0.html)  1 : NSX Edge VM System Requirements - VMware Docs(https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/installation/GUID-22F87CA8-01A9-4F2E-B7DB-9350CA60EA4E.html)

 Unicast is the traffic type that an NSX administrator should use for validating connectivity between App and DB virtual machines that reside on different segments.  According to the VMware documentation 1 , unicast traffic is the traffic type that is used to send a packet from one source to one destination.  Unicast traffic is the most common type of traffic in a network, and it is used for applications such as web browsing, email, file transfer, and so on 2 .  To perform a traceflow with unicast traffic, the NSX administrator needs to specify the source and destination IP addresses, and optionally the protocol and related parameters 1 .  The traceflow will show the path of the packet across the network and any observations or errors along the way 3 . The other options are incorrect because they are not suitable for validating connectivity between two specific virtual machines.  Multicast traffic is the traffic type that is used to send a packet from one source to multiple destinations simultaneously 2 .  Multicast traffic is used for applications such as video streaming, online gaming, and group communication 4 .  To perform a traceflow with multicast traffic, the NSX administrator needs to specify the source IP address and the destination multicast IP address 1 .  Broadcast traffic is the traffic type that is used to send a packet from one source to all devices on the same subnet 2 . Broadcast traffic is used for applications such as ARP, DHCP, and network discovery.  To perform a traceflow with broadcast traffic, the NSX administrator needs to specify the source IP address and the destination MAC address as FF:FF:FF:FF:FF:FF 1 . Anycast traffic is not a valid option, as it is not supported by NSX Traceflow. Anycast traffic is a traffic type that is used to send a packet from one source to the nearest or best destination among a group of devices that share the same IP address. Anycast traffic is used for applications such as DNS, CDN, and load balancing.

To enable stateful active-active SNAT on a Tier-0 or Tier-1 gateway, you must configure an Interface Group for the NSX Edge uplinks. An Interface Group is a logical grouping of NSX Edge interfaces that belong to the same failure domain. A failure domain is a set of NSX Edge nodes that share the same physical network infrastructure and are subject to the same network failures.  By configuring an Interface Group, you can ensure that the stateful services are distributed across different failure domains and can recover from network failures 1

According to the VMware NSX Documentation, this VPN type must be configured before enabling a L2VPN. L2VPN stands for Layer 2 VPN and is a feature that allows you to extend your layer 2 network across different sites using an IPSec tunnel. Route-based IPSec VPN is a VPN type that uses logical router ports to establish IPSec tunnels between sites.

https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-86C8D6BB-F185-46DC-828C-1E1876B854E8.html

The insertion point for East-West network introspection is the Guest VM vNIC. Network introspection is a service insertion feature that allows third-party network services to be integrated with NSX. Network introspection enables traffic redirection from the Guest VM vNIC to a service virtual machine (SVM) that runs the partner service.  The SVM can then inspect, monitor, or modify the traffic before sending it back to the original destination 1 . The other options are incorrect because they are not the insertion points for East-West network introspection. The Tier-0 router is used for North-South routing and network services. The partner SVM is the service virtual machine that runs the partner service, not the insertion point. The host physical NIC is not involved in network introspection.  References :  Network Introspection Settings

According to the VMware NSX Documentation, this is the NSX feature that can be leveraged to achieve consistent policy configuration and simplicity across sites:

NSX Federation: This feature allows you to create and manage a global network infrastructure that spans across multiple sites using a single pane of glass. You can use this feature to synchronize policies, segments, gateways, firewalls, VPNs, load balancers, and other network services across sites.

Load Balancing Algorithm  

You specify the following parameters during the creation of a server pool:

• Name: A unique name for the server pool.

• Cloud: The cloud connector details for the NSX environment.

• VRF Context: Virtual Routing Framework (VRF) is a method to isolate traffic in a system. VRF is also called a route domain in the load balancer community. A global VRF context is created by default. Network administrators might create custom VRF contexts to isolate traffic between different tenants or subsets.

• Default Server Port: New connections to servers will use this destination service port. The default port is 80.

• Load-balancing algorithm: The selected load-balancing algorithm controls how the incoming connections are distributed among the servers in the pool.

• Tier-1 gateway (logical router): Specify the Tier-1 gateway that you want to attach the server pool to. This value matches the Tier-1 gateway specified for the virtual service and VIP.

The command  ifconfig  is used to display the network configuration of the Tunnel Endpoint (TEP) IP on a bare metal transport node 2 . The TEP IP is assigned to a network interface on the bare metal server that is used for overlay traffic. The  ifconfig  command can show the IP address, netmask, broadcast address, and other information of the network interface. For example, the following command shows the network configuration of the TEP IP on a bare metal transport node with interface name ens192:

ifconfig ens192

The output of the command would look something like this:

ens192: flags=4163 < UP,BROADCAST,RUNNING,MULTICAST > mtu 1500 inet 10.10.10.10 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::250:56ff:fe9a:1b8c prefixlen 64 scopeid 0x20 < link > ether 00:50:56:9a:1b:8c txqueuelen 1000 (Ethernet) RX packets 123456 bytes 123456789 (123.4 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 234567 bytes 234567890 (234.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

The TEP IP in this example is  10.10.10.10 .

References :

IBM Cloud Docs

 The NSX Application Platform Deployment features are divided into three form factors: Evaluation, Standard, and Advanced.  Each form factor determines which NSX features can be activated or installed on the platform 1 .  The Evaluation form factor supports only NSX Intelligence, which provides network visibility and analytics for NSX-T environments 2 .  The Standard form factor supports both NSX Intelligence and NSX Network Detection and Response, which provides network threat detection and response capabilities for NSX-T environments 3 .  The Advanced form factor supports all four features: NSX Intelligence, NSX Network Detection and Response, NSX Malware Prevention, and NSX Metrics 1 .

https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/nsx-application-platform/GUID-85CD2728-8081-45CE-9A4A-D72F49779D6A.html