Home » VMware » VCP550D » Why would an administrator be unable to locate an IP address for a vSphere vmnic uplink?
Why would an administrator be unable to locate an IP address for a vSphere vmnic uplink?
A. IP addresses are defined at the virtual nic level, not the vmnic level.
B. ESXi host vmnics communicate with physical switches on layer 3.
C. ESXi hosts use NAT translation to mask the actual vmnic IP address.
D. The IP address of the vmnic is not shown in the vSphere Client.
Correct Answer: A
Explanation/Reference:
Explanation:
The process of adding a virtual NIC to a virtual switch requires you to specify a static IP address, before the virtual NIC is added. Therefore, it is safe to say that IP addresses are defined at the virtual nic level, and not at the vmnic level.
Incorrect Options:
B: This option allows systems in different VLANs to communicate.
C: When NAT translation is used, virtual machines are able to reach the outside network and they can receive replies to the packages they send out.
D: IP addresses are defined at the virtual nic level, not the vmnic level. It will not be visible in the vSphere Client.
Reference:
Atkinson, Brian, VMware Certified Professional-Data Center Virtualization on vSphere 5.5 Study Guide: VCP-550, Sybex, Indianapolis, 2014, p 186
http://rickardnobel.se/vswitch-and-vlan-tagging-part-1/