VCPN610 無料問題集「VMware Certified Professional - Network Virtualization」

（A）At the Logical Switch virtual port that the Virtual Machine connects to.

（B）At the NSX Controller's firewall kernel module.

（C）At the Virtual Machine's virtual Network Interface Card (vNIC).

（D）At the ESXi host vmnic used by the vSphere Distributed Switch.

（A）Configure NSX High Availability.

（B）Configure the NSX Manager virtual machine(s) for Fault Tolerance

（C）Install multiple NSX Managers per vCenter Server installation.

（D）Configure the use of vSphere HA and DRS.

（A）VXLAN to PVLAN bridge

（B）VCD-NI to VLAN bridge

（C）VCD-NI to PVLAN bridge

（D）VXLAN to VLAN bridge

（A）Extend the network security to physical devices in the physical network by use of the Distributed Firewall.

（B）Allow clustering of multiple NSX Managers in a single vCenter Server instance.

（C）Extend physical services to Virtual Machines in virtual network.

（D）Allow physical devices in the physical network to use the NSX Edge Gateway as a default router.

（A）By deploying firewall software on a per virtual machine basis, firewall services will be distributed across multiple compute nodes.

（B）Firewall services are implemented as kernel modules and provide traffic filtering between the virtual machine's vNIC and the vSwitch.

（C）Firewall services are distributed as a software firewall appliance and may be deployed on more than one ESXi host for scalability and high availability.

（D）By decoupling the firewall services from the virtualization layer, traffic is directed to the distribution layer for firewall processing within a service module.

（A）MS-CHAP

（B）TACACS+

（C）Active Directory

（D）RSA Secure ID

（A）Each Virtual Machine identified in the Destination field of the Logical Firewall Rule.

（B）Each Virtual Machine identified in the Applied To field of the Logical Firewall Rule.

（C）Each Virtual Machine defined in the Source and Destination fields of the Logical Firewall Rule.

（D）Each Virtual Machine defined in the Security Group.

（A）HA will start the NSX Edge Load Balancer on another ESXi host in the cluster. All existing flows will need to have their connections reestablished.

（B）The secondary NSX Edge Load Balancer assumes the role of primary. The NSX Controller caches existing flows and hands them to the Load Balancer when it is back up.

（C）HA will start the NSX Edge Load Balancer on another ESXi host in the cluster. The NSX Controller caches existing flows and hands them to the Load Balancer when it is back up.

（D）The secondary NSX Edge Load Balancer assumes the role of primary. Existing Flows will need to have their connections reestablished.

（A）On the Installation > Host Preparation page of the Networking & Security section of the vSphere Web Client, click the Install link for the new cluster.

（B）On the Installation > Logical Network Preparation page of the Networking & Security section of the vSphere Web Client, create a new Transport Zone for the new cluster.

（C）On the Installation > Management page of the Networking & Security section of the vSphere Web Client, click the green plus sign to deploy a new NSX controller node to the new cluster.

（D）On the Installation > Host Preparation page of the Networking & Security section of the vSphere Web Client, click the Install link for each of the new hosts.

（A）NSX Administrator

（B）Auditor

（C）Enterprise Administrator

（D）Security Administrator