Topic 08 Practice Test 1 covers Azure Virtual Machines for Microsoft Azure Administrator AZ-104 and maps to the objective: Create and configure virtual machines. For broader exam preparation, review the Microsoft AZ-104 Exam Dumps. Every option includes focused technical reasoning explaining both the Azure concept and its fit to the scenario.
Question 1
Contoso is creating a new Linux VM and needs Ubuntu Server as the operating-system baseline. Which VM creation choice determines that base OS? Choose ONE.
- Choose the required VM image
- Choose an Azure VM size that meets the workload requirements
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
Correct Answer: A
Correct Answer
Answer A is correct because A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. The deciding condition in The Contoso scenario is: the VM must start from an operating-system image that matches the required platform and software baseline. This option fits that condition.
Incorrect Answers
Answer B is incorrect because The required outcome for Contoso is: the VM must start from an operating-system image that matches the required platform and software baseline. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This capability does not satisfy that condition.
Answer C is incorrect because The requirement for Contoso is: the VM must start from an operating-system image that matches the required platform and software baseline. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. The option therefore targets a different Azure capability.
Answer D is incorrect because Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. The mismatch for Contoso is the stated requirement: the VM must start from an operating-system image that matches the required platform and software baseline.
Question 2
Fabrikam must deploy a Windows Server VM from a specific Microsoft-published release. What selection provides the operating-system source? Choose ONE.
- Choose an Azure VM size that meets the workload requirements
- Choose the required VM image
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
Correct Answer: B
Correct Answer
Answer B is correct because The key requirement for Fabrikam is: the VM must start from an operating-system image that matches the required platform and software baseline. A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements.
Incorrect Answers
Answer A is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. The Fabrikam scenario instead calls for this outcome: the VM must start from an operating-system image that matches the required platform and software baseline.
Answer C is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. This would not resolve the stated requirement for Fabrikam: the VM must start from an operating-system image that matches the required platform and software baseline.
Answer D is incorrect because In the Fabrikam case, the required result is: the VM must start from an operating-system image that matches the required platform and software baseline. Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. Selecting this would solve a neighboring problem instead.
Question 3
Northwind Traders wants every new VM to begin from an approved custom golden operating-system build. Which VM input should point to that baseline? Choose ONE.
- Choose an Azure VM size that meets the workload requirements
- Use Azure managed disks for the VM disks
- Choose the required VM image
- Deploy separate VM instances across availability zones
Correct Answer: C
Correct Answer
Answer C is correct because A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. This aligns with The Northwind Traders scenario, whose requirement is: the VM must start from an operating-system image that matches the required platform and software baseline.
Incorrect Answers
Answer A is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. That feature is valid Azure functionality, but The requirement for Northwind Traders is: the VM must start from an operating-system image that matches the required platform and software baseline.
Answer B is incorrect because For Northwind Traders, the required behavior is: the VM must start from an operating-system image that matches the required platform and software baseline. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. That is not the behavior this scenario calls for.
Answer D is incorrect because Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. That does not line up with the stated constraint for Northwind Traders: the VM must start from an operating-system image that matches the required platform and software baseline.
Question 4
Adventure Works is provisioning a VM and first needs to choose between supported marketplace operating-system offerings. Which configuration decision is it making? Choose ONE.
- Choose an Azure VM size that meets the workload requirements
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
- Choose the required VM image
Correct Answer: D
Correct Answer
Answer D is correct because For Adventure Works, the technical constraint is: the VM must start from an operating-system image that matches the required platform and software baseline. A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements.
Incorrect Answers
Answer A is incorrect because For Adventure Works, the deciding constraint is: the VM must start from an operating-system image that matches the required platform and software baseline. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This solves a different operational need.
Answer B is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. Even though the feature can be useful, it does not provide The required outcome for Adventure Works: the VM must start from an operating-system image that matches the required platform and software baseline.
Answer C is incorrect because The Adventure Works scenario is testing this requirement: the VM must start from an operating-system image that matches the required platform and software baseline. Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. This option does not provide that result.
Question 5
Tailspin Toys needs a VM with more memory and vCPUs for a database workload. Which VM configuration should the administrator change? Choose ONE.
- Choose an Azure VM size that meets the workload requirements
- Choose the required VM image
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
Correct Answer: A
Correct Answer
Answer A is correct because The Tailspin Toys scenario turns on this requirement: the VM SKU must provide the required compute and supported hardware capabilities in the target region. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. That makes this the appropriate choice.
Incorrect Answers
Answer B is incorrect because A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. It misses the key condition in the Tailspin Toys case: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Answer C is incorrect because Tailspin Toys must satisfy this condition: the VM SKU must provide the required compute and supported hardware capabilities in the target region. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. This option is aimed at another design goal.
Answer D is incorrect because Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. Tailspin Toys needs a different capability; the required result is: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Question 6
Woodgrove Bank requires a VM SKU that supports a specific accelerator and enough network bandwidth in the selected region. What should it select? Choose ONE.
- Choose the required VM image
- Choose an Azure VM size that meets the workload requirements
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
Correct Answer: B
Correct Answer
Answer B is correct because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. The capability is relevant to Woodgrove Bank because the required outcome is: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Incorrect Answers
Answer A is incorrect because The requirement for Woodgrove Bank is: the VM SKU must provide the required compute and supported hardware capabilities in the target region. A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. The option therefore targets a different Azure capability.
Answer C is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. The mismatch for Woodgrove Bank is the stated requirement: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Answer D is incorrect because The Woodgrove Bank design calls for this outcome: the VM SKU must provide the required compute and supported hardware capabilities in the target region. Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. This choice addresses another concern.
Question 7
Proseware is sizing a new application VM and must choose the number of vCPUs and amount of RAM. Which Azure VM setting controls these resources? Choose ONE.
- Choose the required VM image
- Use Azure managed disks for the VM disks
- Choose an Azure VM size that meets the workload requirements
- Deploy separate VM instances across availability zones
Correct Answer: C
Correct Answer
Answer C is correct because The scenario for Proseware requires this result: the VM SKU must provide the required compute and supported hardware capabilities in the target region. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This directly addresses it.
Incorrect Answers
Answer A is incorrect because A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. This would not resolve the stated requirement for Proseware: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Answer B is incorrect because In the Proseware case, the required result is: the VM SKU must provide the required compute and supported hardware capabilities in the target region. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. Selecting this would solve a neighboring problem instead.
Answer D is incorrect because Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. It is not the appropriate selection for Proseware; the scenario requires: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Question 8
Litware has a compute workload whose hardware profile must meet CPU, memory, disk, and networking limits. Which deployment choice determines those limits? Choose ONE.
- Choose the required VM image
- Use Azure managed disks for the VM disks
- Deploy separate VM instances across availability zones
- Choose an Azure VM size that meets the workload requirements
Correct Answer: D
Correct Answer
Answer D is correct because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. It is the suitable choice for Litware; the deciding requirement is: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Incorrect Answers
Answer A is incorrect because For Litware, the required behavior is: the VM SKU must provide the required compute and supported hardware capabilities in the target region. A VM image supplies the operating system and base software state from which the virtual machine OS disk is created, so it must match the workload and licensing requirements. That is not the behavior this scenario calls for.
Answer B is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. That does not line up with the stated constraint for Litware: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Answer C is incorrect because Availability zones are physically separate datacenter zones with independent power, cooling, and networking, so distributing instances across zones protects against a datacenter-level failure. For Litware, however, that does not meet the stated requirement: the VM SKU must provide the required compute and supported hardware capabilities in the target region.
Question 9
Wingtip Toys wants Azure to handle the storage account complexity for a new VM OS disk. Which disk model should it use? Choose ONE.
- Use Azure managed disks for the VM disks
- Create or select a managed data disk and attach it to the VM
- Create a managed disk snapshot before the risky disk change
- Choose an Azure VM size that meets the workload requirements
Correct Answer: A
Correct Answer
Answer A is correct because For Wingtip Toys, the required behavior is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. That is why this option fits.
Incorrect Answers
Answer B is incorrect because A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. Even though the feature can be useful, it does not provide The required outcome for Wingtip Toys: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Answer C is incorrect because The Wingtip Toys scenario is testing this requirement: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. This option does not provide that result.
Answer D is incorrect because The required outcome for Wingtip Toys is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This capability does not satisfy that condition.
Question 10
- Datum is standardizing VM disks on Azure-managed block storage resources with independent disk lifecycle. What should it choose? Choose ONE.
- Create or select a managed data disk and attach it to the VM
- Use Azure managed disks for the VM disks
- Create a managed disk snapshot before the risky disk change
- Choose an Azure VM size that meets the workload requirements
Correct Answer: B
Correct Answer
Answer B is correct because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. The technical fit for A. Datum is direct because the requirement is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Incorrect Answers
Answer A is incorrect because A. Datum must satisfy this condition: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. This option is aimed at another design goal.
Answer C is incorrect because A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. A. Datum needs a different capability; the required result is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Answer D is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. The A. Datum scenario instead calls for this outcome: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Question 11
Fourth Coffee needs an OS disk that appears as a first-class Azure resource and does not require a manually managed storage account. Which storage option fits? Choose ONE.
- Create or select a managed data disk and attach it to the VM
- Create a managed disk snapshot before the risky disk change
- Use Azure managed disks for the VM disks
- Choose an Azure VM size that meets the workload requirements
Correct Answer: C
Correct Answer
Answer C is correct because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. For Fourth Coffee, that directly matches the stated requirement: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Incorrect Answers
Answer A is incorrect because A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. The mismatch for Fourth Coffee is the stated requirement: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Answer B is incorrect because The Fourth Coffee design calls for this outcome: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. This choice addresses another concern.
Answer D is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. That feature is valid Azure functionality, but The requirement for Fourth Coffee is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Question 12
Lucerne Publishing is creating data disks for VMs and wants Azure-managed availability and lifecycle for those disk resources. What should it use? Choose ONE.
- Create or select a managed data disk and attach it to the VM
- Create a managed disk snapshot before the risky disk change
- Choose an Azure VM size that meets the workload requirements
- Use Azure managed disks for the VM disks
Correct Answer: D
Correct Answer
Answer D is correct because The required outcome for Lucerne Publishing is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. This option provides that capability.
Incorrect Answers
Answer A is incorrect because In the Lucerne Publishing case, the required result is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. Selecting this would solve a neighboring problem instead.
Answer B is incorrect because A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. It is not the appropriate selection for Lucerne Publishing; the scenario requires: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs.
Answer C is incorrect because For Lucerne Publishing, the deciding constraint is: Azure should manage the storage resource backing the VM OS or data disk instead of the administrator managing storage accounts for VHDs. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This solves a different operational need.
Question 13
Contoso has an existing VM and needs a new 512-GB persistent volume for application data. What should the administrator do? Choose ONE.
- Create or select a managed data disk and attach it to the VM
- Use Azure managed disks for the VM disks
- Create a managed disk snapshot before the risky disk change
- Resize the VM while it is running, accepting the required reboot
Correct Answer: A
Correct Answer
Answer A is correct because A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. The deciding condition in The Contoso scenario is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. This option fits that condition.
Incorrect Answers
Answer B is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. That does not line up with the stated constraint for Contoso: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Answer C is incorrect because A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. For Contoso, however, that does not meet the stated requirement: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Answer D is incorrect because If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. It misses the key condition in the Contoso case: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Question 14
Fabrikam needs to add a separate managed data volume to a running VM without replacing the OS disk. Which action is appropriate? Choose ONE.
- Use Azure managed disks for the VM disks
- Create or select a managed data disk and attach it to the VM
- Create a managed disk snapshot before the risky disk change
- Resize the VM while it is running, accepting the required reboot
Correct Answer: B
Correct Answer
Answer B is correct because The key requirement for Fabrikam is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed.
Incorrect Answers
Answer A is incorrect because The Fabrikam scenario is testing this requirement: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. This option does not provide that result.
Answer C is incorrect because The required outcome for Fabrikam is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. This capability does not satisfy that condition.
Answer D is incorrect because The requirement for Fabrikam is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. The option therefore targets a different Azure capability.
Question 15
Northwind Traders created an empty managed disk for database files and now needs the VM to use it. What should happen next? Choose ONE.
- Use Azure managed disks for the VM disks
- Create a managed disk snapshot before the risky disk change
- Create or select a managed data disk and attach it to the VM
- Resize the VM while it is running, accepting the required reboot
Correct Answer: C
Correct Answer
Answer C is correct because A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed. This aligns with The Northwind Traders scenario, whose requirement is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Incorrect Answers
Answer A is incorrect because Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. Northwind Traders needs a different capability; the required result is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Answer B is incorrect because A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. The Northwind Traders scenario instead calls for this outcome: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Answer D is incorrect because If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. This would not resolve the stated requirement for Northwind Traders: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Question 16
Adventure Works wants to expand storage by adding another managed data disk rather than resizing the OS disk. Which VM operation should it perform? Choose ONE.
- Use Azure managed disks for the VM disks
- Create a managed disk snapshot before the risky disk change
- Resize the VM while it is running, accepting the required reboot
- Create or select a managed data disk and attach it to the VM
Correct Answer: D
Correct Answer
Answer D is correct because For Adventure Works, the technical constraint is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. A VM can use additional managed data disks for application data; the disk is attached to the VM and then initialized or mounted inside the guest operating system as needed.
Incorrect Answers
Answer A is incorrect because The Adventure Works design calls for this outcome: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. Managed disks are Azure-managed block-level storage volumes for virtual machines and remove the need to manage storage accounts for individual VM OS and data disks. This choice addresses another concern.
Answer B is incorrect because A managed disk snapshot captures a point-in-time copy of a managed disk and provides a recovery source that can be used to create another managed disk if a later change fails. That feature is valid Azure functionality, but The requirement for Adventure Works is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS.
Answer C is incorrect because For Adventure Works, the required behavior is: an additional persistent data volume must be made available to the existing VM and then initialized in the guest OS. If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. That is not the behavior this scenario calls for.
Question 17
Tailspin Toys verifies that Standard_D4s_v5 is available as a resize option for a running VM on its current cluster. What is the least disruptive resize approach? Choose ONE.
- Resize the VM while it is running, accepting the required reboot
- Deallocate the VM, resize it, and then start it again
- Choose an Azure VM size that meets the workload requirements
- Deploy the workload with an Azure Virtual Machine Scale Set
Correct Answer: A
Correct Answer
Answer A is correct because The Tailspin Toys scenario turns on this requirement: the requested VM size is available on the current cluster and only the resize restart is acceptable. If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. That makes this the appropriate choice.
Incorrect Answers
Answer B is incorrect because When the requested VM size is not available on the current cluster, the VM must be deallocated so Azure can place it on hardware that supports the new size before restart. It is not the appropriate selection for Tailspin Toys; the scenario requires: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Answer C is incorrect because For Tailspin Toys, the deciding constraint is: the requested VM size is available on the current cluster and only the resize restart is acceptable. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This solves a different operational need.
Answer D is incorrect because Virtual Machine Scale Sets centrally create and manage groups of VM instances and support high availability, consistent configuration, and horizontal scaling across demand changes. Even though the feature can be useful, it does not provide The required outcome for Tailspin Toys: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Question 18
Woodgrove Bank needs to resize a VM and the desired SKU appears in the VM current resize options. What can the administrator do? Choose ONE.
- Deallocate the VM, resize it, and then start it again
- Resize the VM while it is running, accepting the required reboot
- Choose an Azure VM size that meets the workload requirements
- Deploy the workload with an Azure Virtual Machine Scale Set
Correct Answer: B
Correct Answer
Answer B is correct because If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. The capability is relevant to Woodgrove Bank because the required outcome is: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Incorrect Answers
Answer A is incorrect because When the requested VM size is not available on the current cluster, the VM must be deallocated so Azure can place it on hardware that supports the new size before restart. For Woodgrove Bank, however, that does not meet the stated requirement: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Answer C is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. It misses the key condition in the Woodgrove Bank case: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Answer D is incorrect because Woodgrove Bank must satisfy this condition: the requested VM size is available on the current cluster and only the resize restart is acceptable. Virtual Machine Scale Sets centrally create and manage groups of VM instances and support high availability, consistent configuration, and horizontal scaling across demand changes. This option is aimed at another design goal.
Question 19
Proseware is increasing a VM size and confirms Azure can satisfy the new size on the current hardware cluster. Which process is sufficient? Choose ONE.
- Deallocate the VM, resize it, and then start it again
- Choose an Azure VM size that meets the workload requirements
- Resize the VM while it is running, accepting the required reboot
- Deploy the workload with an Azure Virtual Machine Scale Set
Correct Answer: C
Correct Answer
Answer C is correct because The scenario for Proseware requires this result: the requested VM size is available on the current cluster and only the resize restart is acceptable. If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. This directly addresses it.
Incorrect Answers
Answer A is incorrect because The required outcome for Proseware is: the requested VM size is available on the current cluster and only the resize restart is acceptable. When the requested VM size is not available on the current cluster, the VM must be deallocated so Azure can place it on hardware that supports the new size before restart. This capability does not satisfy that condition.
Answer B is incorrect because The requirement for Proseware is: the requested VM size is available on the current cluster and only the resize restart is acceptable. The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. The option therefore targets a different Azure capability.
Answer D is incorrect because Virtual Machine Scale Sets centrally create and manage groups of VM instances and support high availability, consistent configuration, and horizontal scaling across demand changes. The mismatch for Proseware is the stated requirement: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Question 20
Litware wants to change a VM SKU; the target size is available without moving the VM to another cluster. What should it expect to do? Choose ONE.
- Deallocate the VM, resize it, and then start it again
- Choose an Azure VM size that meets the workload requirements
- Deploy the workload with an Azure Virtual Machine Scale Set
- Resize the VM while it is running, accepting the required reboot
Correct Answer: D
Correct Answer
Answer D is correct because If the requested size is available on the current hardware cluster, Azure can resize the VM without first deallocating it, although the operation restarts the VM. It is the suitable choice for Litware; the deciding requirement is: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Incorrect Answers
Answer A is incorrect because When the requested VM size is not available on the current cluster, the VM must be deallocated so Azure can place it on hardware that supports the new size before restart. The Litware scenario instead calls for this outcome: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Answer B is incorrect because The VM size determines compute resources and supported capabilities such as vCPU count, memory, disk and network limits, so the selected SKU must satisfy workload and regional availability needs. This would not resolve the stated requirement for Litware: the requested VM size is available on the current cluster and only the resize restart is acceptable.
Answer C is incorrect because In the Litware case, the required result is: the requested VM size is available on the current cluster and only the resize restart is acceptable. Virtual Machine Scale Sets centrally create and manage groups of VM instances and support high availability, consistent configuration, and horizontal scaling across demand changes. Selecting this would solve a neighboring problem instead.
