An architect is creating a network design for a new vSphere environment.
Based on customer requirements, the environment must support the following types of traffic:
✑ Management
✑ vMotion
✑ vSAN
✑ Fault Tolerance
✑ Virtual machine traffic, which cannot be impacted by other types of traffic
Which design recommendation can the architect make for a resilient infrastructure with vSphere network service tiering?
To ensure a resilient infrastructure where virtual machine traffic is prioritized and cannot be impacted by other types of traffic, the best approach is to use Network I/O Control (NIOC). NIOC allows for the definition of share values for different types of traffic, ensuring that virtual machine traffic receives the appropriate priority. This method distributes network resources according to the importance of each traffic type, safeguarding virtual machine operations from disruptions caused by other network traffic.
B. Use Network I/O Control and ensure appropriate share value is defined for different types of traffic giving priority to the virtual machines traffic "Virtual machine traffic, which cannot be impacted by other types of traffic” "resilient infrastructure" That rules out C as a single adapter per vSwitch is not "resilient". This rules out D as that NIC teaming policy could give preference to any other traffic type. A is ruled out as it doesn't provide any network preference to VM traffic.
Isn't it B?
B will be the correct answer
This question is not clear because we do not know how many physical NICs are available to design a "resilient infrastructure" Example 1: We only have 2 physical NICs - In this case, answer should be B. Create a VDS, enable Network I/O and assign a hight bandwidth reservation to the "Virtual machine traffic" Note: We can reserve no more than 75% of the bandwidth of a physical NIC https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-E1983465-4EEB-4526-ADC8-939159335284.html Example 2: We have 4 physical NICs - The answer should be A https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-B57FBE96-21EA-401C-BAA6-BDE88108E4BB.html
Answer is B A : segregating traffic in VLANs will not meet the VM traffic priority requirement B : the keyword is network tiering (so Network I/O Control). We may have to use reservations to ensure VMs traffic is not impacted C : with a single adapted in each vSwitch, we have a SPOF, and then not a resilient architecture as requested D : this one will only globally load balance between the physical NICs, and will not prioritize the VM traffic
B. Use Network I/O Control and ensure appropriate share value is defined for different types of traffic, giving priority to the virtual machine traffic:
B for me. I think the key word here is "network tiering". With Network I/O you can create Shares, Reservations and Limits. Is recommended in case you have to share nics between many services, specially vSan https://docs.vmware.com/en/VMware-vSphere/7.0/vsan-network-design-guide/GUID-6B00B437-53A3-4ACD-8CD7-AC9D0CE5BA8E.html
Yes B, https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan-planning.doc/GUID-031F9637-EE29-4684-8644-7A93B9FD8D7B.html
Reading this: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-B57FBE96-21EA-401C-BAA6-BDE88108E4BB.html I think is A (Isolate from one another the networks for host management, vSphere vMotion, vSphere FT, and so on, to improve security and performance.)
A is more about security and performance ,i agree . but this question has a key word " resilient", i think B