In an NSX environment, an administrator is observing low throughput and congestion between the Tier-O Gateway and the upstream physical routers. Which two actions could address low throughput and congestion? (Choose two.)
Correct Answer: B,C
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 cluster2. The ECMP routing paths are used to load balance traffic and provide fault tolerance for failed paths2. The tier-0 logical router must be in active-active mode for ECMP to be available2. A maximum of eight ECMP paths are supported2. 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 node1. 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 balancer1. 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 VPN1. 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-429 NSX Edge VM System Requirements - VMware Docs(https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.2/installation/GUID-22F87CA8-01A9-4F2E-
Question 62
What are tour NSX built-in rote-based access control (RBAC) roles? (Choose four.)
What is the VMware recommended way to deploy a virtual NSX Edge Node?
Correct Answer: D
Through the NSX UI. According to the VMware NSX Documentation2, you can deploy NSX Edge nodes as virtual appliances through the NSX UI by clicking Add Edge Node and providing the required information. The other options are either outdated or not applicable for virtual NSX Edge nodes.
Question 64
Match the NSX Intelligence recommendations with their correct purpose.
Correct Answer:
Explanation Security policy recommendations: Are East-West distributed firewall (DFW) security policies in the application category12. Security group recommendations: Are VMs or physical servers whose traffic flows were analyzed for the time period and the boundary you had specified12. Service recommendations: Are service objects that were used by applications in the VMs or physical servers that you had specified, but the services are not yet defined in the NSX inventory12. https://docs.vmware.com/en/VMware-NSX-Intelligence/4.1/user-guide/GUID-BA3B0D67-4AA8-439E-A845-4
Question 65
Which command is used to display the network configuration of the Tunnel Endpoint (TEP) IP on a bare metal transport node?
Correct Answer: B
Explanation The command ifconfig is used to display the network configuration of the Tunnel Endpoint (TEP) IP on a bare metal transport node2. 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
