2V0-622 · 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 caused by network or storage bottlenecks, and the correct remediation steps directly target those specific layers.
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
(57 responses)- A44% (25)
- D16% (9)
- E40% (23)
Why each option
Slow VM template deployment is caused by network or storage bottlenecks, and the correct remediation steps directly target those specific layers.
Adding additional uplinks to the vSwitch increases available network bandwidth for the deployment, which is a network I/O-bound operation when copying template data across hosts or datastores.
Changing the destination datastore or volume can resolve bottlenecks caused by a slow or congested storage target, directing the deployment to a higher-performing storage resource.
Configuring a dedicated Provisioning Traffic vmkernel port isolates cloning and deployment I/O onto a separate network path, preventing contention with management or vMotion traffic and improving deployment throughput.
Reducing the size of an existing template's virtual disk is not a standard troubleshooting action and does not address the underlying network or storage bottleneck causing the slowness.
Deploying to a cluster and relying on DRS addresses compute resource balancing, not the storage or network throughput limitations that cause slow template deployments.
Concept tested: Optimizing vSphere VM template deployment performance
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-DCE3DEB0-DE6C-4A74-B7D9-C43F6B4B4FAA.html
Topics
Community Discussion
No community discussion yet for this question.