An administrator is configuring a new virtual machine named VM1 in the East US region. The deployment has the following requirements:
- The OS disk must be deployed as an Ephemeral OS disk using the virtual machine's local temp disk to reduce read/write latency.
- The virtual machine must use the Standard_D4s_v5 size, which features vCPUs, GB of RAM, a GB cache limit, and a GB temp disk.
- The operating system must be deployed using a custom Windows Server 2022 image that has a size of GB.
What is the result when the administrator attempts to deploy this virtual machine?
- The deployment fails because the GB size of the custom OS image exceeds the GB local temp disk capacity of the Standard_D4s_v5 virtual machine size.Answer
- BThe deployment fails because Ephemeral OS disks are unsupported when deploying virtual machines to an Availability Zone.
- CThe deployment fails because the custom image must first be converted to a zone-redundant storage (ZRS) tier before it can be used for Ephemeral OS disk creation.
- DThe deployment succeeds, but the OS disk is automatically provisioned as a Premium SSD managed disk, which will incur standard monthly storage charges.
Answer
The deployment fails because the custom OS image size exceeds the local temp disk capacity of the virtual machine size.
The correct option states that the deployment will fail because the custom OS image size ( GB) exceeds the capacity of the local temp disk ( GB) of the Standard_D4s_v5 virtual machine size. Ephemeral OS disks are hosted on the local storage of the Azure VM host. Therefore, the size of the custom OS image cannot exceed the local cache or temp disk limit specified by the VM size.
Step-by-Step Solution
Key Concept
Ephemeral OS Disk Sizing Limitations
Estimated Time:2m 0s