What should an NSX administrator check to verify that VMware Identity Manager Integration Is successful?

What should an NSX administrator check to verify that VMware Identity Manager Integration Is successful?
A . From VMware Identity Manager the status of the remote access application must be green.
B . From the NSX UI the status of the VMware Identity Manager Integration must be "Enabled".
C . From the NSX CLI the status of the VMware Identity Manager Integration must be "Configured".
D . From the NSX UI the URI in the address bar must have "locaNfatse" part of it.

Answer: B

Explanation:

From the NSX UI the status of the VMware Identity Manager Integration must be “Enabled”. According to the VMware NSX Documentation1, after configuring VMware Identity Manager integration, you can validate the functionality by checking the status of the integration in the NSX UI. The status should be “Enabled” if the integration is successful. The other options are either incorrect or not relevant.

Which two CLI commands could be used to see if vmnic link status is down? (Choose two.)

Which two CLI commands could be used to see if vmnic link status is down? (Choose two.)
A . esxcfg-nics -1
B . excli network nic list
C . esxcli network vswitch dvs wmare list
D . esxcfg-vmknic -1
E . esxcfg-vmsvc/get.network

Answer: A B

Explanation:

esxcfg-nics -l and esxcli network nic list are two CLI commands that can be used to see the vmnic link status on an ESXi host. Both commands display information such as the vmnic name, driver, link state, speed, and duplex mode. The link state can be either Up or Down, indicating whether the vmnic is connected or not.

For example, the output of esxcfg-nics -l can look like this:

Name PCI Driver Link Speed Duplex MAC Address MTU Description

vmnic0 0000:02:00.0 igbn Up 1000Mbps Full 00:50:56:01:2a:3b 1500 Intel Corporation I350 Gigabit Network Connection

vmnic1 0000:02:00.1 igbn Down 0Mbps Half 00:50:56:01:2a:3c 1500 Intel Corporation I350 Gigabit Network Connection

Which command on ESXI is used to verify the Local Control Plane connectivity with Central Control Plane?

Which command on ESXI is used to verify the Local Control Plane connectivity with Central Control Plane?

A)

B)

C)

D)

A . Option A
B . Option B
C . Option C
D . Option D

Answer: B

Explanation:

According to the web search results, the command that is used to verify the Local Control Plane (LCP) connectivity with Central Control Plane (CCP) on ESXi is get control-cluster status. This command displays the status of the LCP and CCP components on the ESXi host, such as the LCP agent, CCP client, CCP server, and CCP connection. It also shows the IP address and port number of the CCP server that the LCP agent is connected to. If the LCP agent or CCP client are not running or not connected, it means that there is a problem with the LCP connectivity.

Which of the following pool configuration settings needs to be adjusted to resolve the problem?

Refer to the exhibit.

An administrator configured NSX Advanced Load Balancer to redistribute the traffic between the web servers.

However, requests are sent to only one server

Which of the following pool configuration settings needs to be adjusted to resolve the problem? Mark the correct answer by clicking on the image.

Answer: Load Balancing Algorithm

Which failover policy meets this requirement?

An NSX administrator is creating a Tier-1 Gateway configured In Active-Standby High Availability Mode. In the event of node failure, the failover policy should not allow the original tailed node to become the Active node upon recovery.

Which failover policy meets this requirement?
A . Non-Preemptive
B . Preemptive
C . Enable Preemptive
D . Disable Preemptive

Answer: A

Explanation:

According to the VMware NSX Documentation, a non-preemptive failover policy means that the original failed node will not become the active node upon recovery, unless the current active node fails again. This policy can help avoid unnecessary failovers and ensure stability.

The other options are either incorrect or not available for this configuration. Preemptive is the opposite of non-preemptive, meaning that the original failed node will become the active node upon recovery, if it has a higher priority than the current active node. Enable Preemptive and Disable Preemptive are not valid options for the failover policy, as the failover policy is a drop-down menu that only has two choices: Preemptive and Non-Preemptive.

When collecting support bundles through NSX Manager, which files should be excluded for potentially containing sensitive information?

When collecting support bundles through NSX Manager, which files should be excluded for potentially containing sensitive information?
A . Controller Files
B . Management Files
C . Core Files
D . Audit Files

Answer: C D

Explanation:

According to the VMware NSX Documentation1, core files and audit logs can contain sensitive information and should be excluded from the support bundle unless requested by VMware technical support. Controller files and management files are not mentioned as containing sensitive information.

What are two valid BGP Attributes that can be used to influence the route path traffic will take? (Choose two.)

What are two valid BGP Attributes that can be used to influence the route path traffic will take? (Choose two.)
A . AS-Path Prepend
B . BFD
C . Cost
D . MED

Answer: A D

Explanation:

– AS-Path Prepend: This attribute allows you to prepend one or more AS numbers to the AS path of a route, making it appear longer and less preferable to other BGP routers. You can use this attribute to manipulate the inbound traffic from your BGP peers by advertising a longer AS path for some routes and a shorter AS path for others.

– MED: This attribute stands for Multi-Exit Discriminator and allows you to specify a preference value for a route among multiple exit points from an AS. You can use this attribute to manipulate the outbound traffic to your BGP peers by advertising a lower MED value for some routes and a higher MED value for others.

Which failover detection protocol must be used to meet this requirement?

An NSX administrator wants to create a Tler-0 Gateway to support equal cost multi-path (ECMP) routing.

Which failover detection protocol must be used to meet this requirement?
A . Bidirectional Forwarding Detection (BFD)
B . Virtual Router Redundancy Protocol (VRRP)
C . Beacon Probing (BP)
D . Host Standby Router Protocol (HSRP)

Answer: A

Explanation:

According to the VMware NSX 4.x Professional documents and tutorials, BFD is a failover detection protocol that provides fast and reliable detection of link failures between two routing devices. BFD can be used with ECMP routing to monitor the health of the ECMP paths and trigger a route change in case of a failure12. BFD is supported by both BGP and OSPF routing protocols in NSX-T3. BFD can also be configured with different timers to achieve different detection times3.

Which command Is used to test management connectivity from a transport node to NSX Manager?

Which command Is used to test management connectivity from a transport node to NSX Manager?

A)

B)

C)

D)

A . Option A
B . Option B
C . Option C
D . Option D

Answer: C

Explanation:

According to the web search results, the command that is used to test management connectivity from a transport node to NSX Manager is get managers. This command displays the status, IP address, and thumbprint of the NSX Manager that the transport node is connected to. It also shows the connection state, which can be UP or DOWN. If the connection state is DOWN, it means that there is a problem with the management connectivity.

Which is an advantages of a L2 VPN In an NSX 4.x environment?

Which is an advantages of a L2 VPN In an NSX 4.x environment?
A . Enables Multi-Cloud solutions
B . Achieve better performance
C . Enables VM mobility with re-IP
D . Use the same broadcast domain

Answer: D

Explanation:

L2 VPN is a feature of NSX that allows extending Layer 2 networks across different sites or clouds over an IPsec tunnel. L2 VPN has an advantage of enabling VM mobility with re-IP, which means that VMs can be moved from one site to another without changing their IP addresses or network configurations. This is possible because L2 VPN allows both sites to use the same broadcast domain, which means that they share the same subnet and VLAN.