2V0-621 · Question #51
Which two features are deprecated in Network I/O Control 3 (NIOC3)? (Choose two.)
The correct answer is A. Class Of Service (COS) Tagging C. User-defined network resource pools. Network I/O Control version 3 removed two features present in earlier versions to streamline bandwidth management and align QoS responsibilities with physical network infrastructure.
Question
Which two features are deprecated in Network I/O Control 3 (NIOC3)? (Choose two.)
Options
- AClass Of Service (COS) Tagging
- BBandwidth Allocation
- CUser-defined network resource pools
- DAdmission control
How the community answered
(50 responses)- A94% (47)
- B4% (2)
- D2% (1)
Why each option
Network I/O Control version 3 removed two features present in earlier versions to streamline bandwidth management and align QoS responsibilities with physical network infrastructure.
Class of Service (CoS) tagging was deprecated in NIOC3 because QoS marking at layer 2 is now expected to be handled by the physical network rather than by NIOC, removing the ability to set CoS values from within the vSphere networking stack.
Bandwidth allocation - including shares, reservations, and limits - is a core and retained capability of NIOC3, not a deprecated feature.
User-defined network resource pools were deprecated in NIOC3 and replaced by per-virtual-machine bandwidth reservations tied to system traffic types, eliminating the ability to create and manage custom named resource pools.
Admission control remains active in NIOC3 to enforce that bandwidth reservations are only accepted when the physical uplink capacity can satisfy them.
Concept tested: Deprecated features in Network I/O Control version 3
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-DCFD1D49-2CF8-4A5E-B8CC-12E5DEB4B2E4.html
Topics
Community Discussion
No community discussion yet for this question.