2V0-622 · 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 deprecated CoS tagging and user-defined network resource pools, replacing the pool model with per-VM bandwidth allocation tied to system-defined traffic types.
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
(40 responses)- A90% (36)
- B3% (1)
- D8% (3)
Why each option
Network I/O Control version 3 deprecated CoS tagging and user-defined network resource pools, replacing the pool model with per-VM bandwidth allocation tied to system-defined traffic types.
Class of Service (CoS) tagging was deprecated in NIOC3 because bandwidth scheduling shifted to a reservation and limit model rather than relying on 802.1p CoS markings to prioritize traffic classes.
Bandwidth Allocation is a core capability that was enhanced in NIOC3 - introducing per-VM bandwidth reservations and limits - making it an added feature rather than a deprecated one.
User-defined network resource pools were deprecated in NIOC3; the model changed to associating bandwidth allocations directly with system-defined traffic types and individual virtual machines rather than administrator-created pools.
Admission control is a feature available in NIOC3 that enforces bandwidth reservations by preventing VMs from powering on if their reserved bandwidth cannot be guaranteed, so it was not deprecated in version 3.
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-ABFB6E74-D694-4C1B-BDCC-3F12D2FD1AA4.html
Topics
Community Discussion
No community discussion yet for this question.