2V0-621 · Question #136
Which three troubleshooting actions should an administrator take to address slow performance when deploying a virtual machine template? (Choose three.)
The correct answer is A. Increase network throughput by adding additional uplinks to the vSwitch. B. Change the destination datastore or volume for the virtual machine template. C. Configure a Provisioning Traffic vmkernel port to perform the deployment operation. Slow VM template deployment is primarily a network and storage I/O problem; the correct remediations address bandwidth, storage path selection, and dedicated provisioning traffic routing.
Question
Which three troubleshooting actions should an administrator take to address slow performance when deploying a virtual machine template? (Choose three.)
Options
- AIncrease network throughput by adding additional uplinks to the vSwitch.
- BChange the destination datastore or volume for the virtual machine template.
- CConfigure a Provisioning Traffic vmkernel port to perform the deployment operation.
- DReduce the size of the virtual machine template's virtual disk.
- EDeploy the virtual machine template to the cluster and allow Distributed Resource Scheduler to
How the community answered
(33 responses)- A67% (22)
- D9% (3)
- E24% (8)
Why each option
Slow VM template deployment is primarily a network and storage I/O problem; the correct remediations address bandwidth, storage path selection, and dedicated provisioning traffic routing.
Template deployments and cloning operations are bandwidth-intensive; adding additional physical uplinks to the vSwitch increases available network throughput, reducing the time required to transfer the template data across the network.
Storage contention on a busy or slow datastore directly throttles deployment speed; moving the destination to a less-utilized or higher-performance datastore or volume reduces I/O wait and accelerates the clone operation.
VMware vSphere supports a dedicated 'Provisioning Traffic' vmkernel port type that is specifically optimized for virtual machine migration, cloning, and template deployment operations; configuring a dedicated vmkernel port for this traffic type isolates and prioritizes provisioning I/O from other vmkernel traffic.
Reducing the virtual disk size of a template changes the total data to transfer but does not address the underlying network or storage throughput bottleneck causing the slow deployment, and resizing a template disk is typically impractical.
DRS (Distributed Resource Scheduler) optimizes compute resource placement (CPU and memory) across a cluster but does not influence or accelerate the network and storage I/O operations that govern template deployment speed.
Concept tested: Optimizing VM template deployment performance in vSphere
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-59C47C6E-1BE9-4B38-9E50-54F8A5CB2F1E.html
Topics
Community Discussion
No community discussion yet for this question.