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

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.

According to the VMware NSX Documentation, these are two of the ways that you can use to configure Distributed Firewall on VDS:

• NSX API: This is a RESTful API that allows you to programmatically configure and manage Distributed Firewall on VDS using HTTP methods and JSON payloads. You can use tools such as Postman or curl to send API requests to the NSX Manager node.
• NSX UI: This is a graphical user interface that allows you to configure and manage Distributed Firewall on VDS using menus, tabs, buttons, and forms. You can access the NSX UI by logging in to the NSX Manager node using a web browser.

The correct answers are A. Files and anti-malware (file) events from the NSX Edge nodes and the Security Analyzer, D. IDS/IPS events from the ESXi hosts and NSX Edge nodes, and E. Suspicious Traffic Detection events from NSX Intelligence. According to the VMware NSX Documentation3, these are the three data collection sources that are used by NSX Network Detection and Response to create correlations/intrusion campaigns.

The other options are incorrect or not supported by NSX Network Detection and Response. East-West anti-malware events from the ESXi hosts are not collected by NSX Network Detection and Response3. Distributed Firewall flow data from the ESXi hosts are not used for correlation/intrusion campaigns by NSX Network Detection and Response3.