A Bicep deployment creates only Microsoft.DesktopVirtualization/hostPools with the desired properties. No VMs, extensions or application groups are included. What is the expected result?

✓ Correct answer

• A host-pool service resource exists, but additional deployment and registration work is required before users can launch desktops.

Infrastructure as code must cover the complete desired deployment. Provisioning a host-pool object is one component, not a functioning desktop service. Option explanations: A. A host-pool service resource exists, but additional deployment and registration work is required before users can launch desktops.: The resource declaration establishes pool settings, not the complete session-host and publication workflow. B. The template installs and registers an AVD Agent on every VM in the subscription.: The template does not contain that VM/extension deployment logic. C. AVD automatically creates ten hosts because the pool is pooled.: A pooled host-pool declaration does not imply a VM count or independent provisioning. D. All licensed tenant users automatically receive a desktop assignment.: Licensing does not automatically create application-group assignments. Sources: Host pool ARM and Bicep reference — https://learn.microsoft.com/en-us/azure/templates/microsoft.desktopvirtualization/2024-04-03/hostpools; Deploy Azure Virtual Desktop — https://learn.microsoft.com/en-us/azure/virtual-desktop/deploy-azure-virtual-desktop

Read the source reference