You have an Azure virtual machine named VM-Legacy deployed in the East US region. The virtual machine has a network interface named nic-legacy, which is associated with a public IP address named pip-legacy. The public IP address uses the Basic SKU and Dynamic allocation. You plan to deploy a Standard Load Balancer named LB-Prod in the East US region and associate nic-legacy with the load balancer's backend pool. You need to upgrade pip-legacy to the Standard SKU to support the new configuration. Which sequence of actions should you perform?
- AChange the allocation method of pip-legacy to Static, upgrade the SKU to Standard, and perform the upgrade while the public IP remains associated with nic-legacy.
- BUpgrade the SKU of pip-legacy directly to Standard, and keep the allocation method as Dynamic.
- Disassociate pip-legacy from nic-legacy, change the allocation method of pip-legacy to Static, and then upgrade the SKU to Standard.Answer
- DChange the allocation method of pip-legacy to Dynamic, and then upgrade the SKU to Standard while it remains associated with nic-legacy.
Answer
Disassociate pip-legacy from nic-legacy, change the allocation method of pip-legacy to Static, and then upgrade the SKU to Standard.
The correct sequence requires disassociating the public IP address from the network interface first because Azure does not allow SKU modifications on associated public IPs. Additionally, because Standard SKU public IP addresses only support Static allocation, the allocation method must be set to Static before performing the SKU upgrade.
Step-by-Step Solution
Key Concept
Upgrading a Basic SKU public IP to a Standard SKU public IP requires disassociating the resource and ensuring the allocation method is Static, as Standard SKU public IPs do not support Dynamic allocation.