AZ-140 · Question #200
You have an Azure subscription that contains an Azure Compute Gallery named Gallery1 and a virtual machine named Template1. Template1 has custom apps and settings configured. You plan to deploy…
The correct answer is C. From Template1, capture a generalized virtual machine image. The requirement that 'all new session hosts must have unique computer names and identifiers' means each deployed VM must be treated as a brand-new machine with its own SID, hostname, and identity. This is only possible with a generalized image - one that has been sysprepped to…
Question
You have an Azure subscription that contains an Azure Compute Gallery named Gallery1 and a virtual machine named Template1. Template1 has custom apps and settings configured. You plan to deploy Azure Virtual Desktop session hosts by using a custom virtual machine image. The solution must meet the following requirements:
- The custom image must be stored in Gallery1.
- The custom image must be based on Template1.
- All new session hosts must have unique computer names and
identifiers. You need to create the custom image. What should you do in the Azure portal?
Options
- AFrom Gallery1, create a new VM application definition.
- BFrom Gallery1, create a new VM image definition.
- CFrom Template1, capture a generalized virtual machine image.
- DFrom Template1, capture a specialized virtual machine image.
How the community answered
(36 responses)- A3% (1)
- B3% (1)
- C83% (30)
- D11% (4)
Explanation
The requirement that 'all new session hosts must have unique computer names and identifiers' means each deployed VM must be treated as a brand-new machine with its own SID, hostname, and identity. This is only possible with a generalized image - one that has been sysprepped to remove machine-specific information. When a new VM is provisioned from a generalized image, Windows runs through OOBE/Sysprep mini-setup and assigns a new unique SID and computer name. A specialized image (D) retains the original computer name and SID from Template1, which would cause identity conflicts if deployed to multiple VMs. Creating a VM application definition (A) is for packaging software installers, not OS images. Creating only a VM image definition (B) in the gallery is a prerequisite step but does not by itself capture Template1's content - you must capture a generalized image from Template1 and store the resulting image version in Gallery1.
Topics
Community Discussion
No community discussion yet for this question.