1Y0-401 · Question #105
Scenario: CGE needs to define its management process for desktop image releases. Some groups need a process for version control that includes thorough testing prior to production. Why does using…
The correct answer is B. It provides centralized, automated, single-image management. Using hypervisor templates combined with API-driven deployment streamlines desktop image versioning by enabling a centralized, automated approach to managing a single golden image. This method ensures all deployed desktops originate from a controlled, tested source, simplifying…
Question
Options
- AIt allows for the automatic upgrade of the virtual desktops to the latest OS version.
- BIt provides centralized, automated, single-image management.
- CIt facilitates consistent deployment of base images.
- DIt allows for templates to be stored on shared or local storage.
How the community answered
(35 responses)- A3% (1)
- B94% (33)
- C3% (1)
Why each option
Using hypervisor templates combined with API-driven deployment streamlines desktop image versioning by enabling a centralized, automated approach to managing a single golden image. This method ensures all deployed desktops originate from a controlled, tested source, simplifying updates and consistency.
While templates can be used to deploy new OS versions, automatic upgrade of existing virtual desktops to the latest OS version is not a primary function of templates and APIs for managing image versioning.
Using hypervisor templates provides a single, master image, centralizing the management of the desktop's base configuration. Leveraging the Hypervisor API allows for the programmatic and automated control over the deployment, modification, and versioning of this single image, thereby providing centralized, automated, single-image management critical for a robust image versioning process.
While templates facilitate consistent deployment, choice B better encompasses the 'centralized' and 'automated' aspects of managing image versioning, which is the core of the question's focus on the process.
Storing templates on shared or local storage is an operational detail of template management but does not directly explain why it helps manage the image versioning process itself in a centralized and automated way.
Concept tested: Hypervisor template and API for image management
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-115982D4-3BC6-4131-B0B8-BF949E345C8A.html
Topics
Community Discussion
No community discussion yet for this question.