Examkin

Question

Difficulty: Very hardConfigure Public and Private IP Addresses

An administrator is upgrading a legacy Azure virtual machine named VM1 to comply with modern Azure security and SKU support standards. VM1 is configured with a single network interface named nic1. The primary IP configuration of nic1 (ipconfig1) is associated with a legacy Basic SKU public IP address (PubIP1) that uses Dynamic allocation.

The administrator needs to assign a second public IP address to VM1 to support a new secure web service. They create a new Standard SKU public IP address named PubIP2. However, when attempting to associate PubIP2 with a new secondary IP configuration (ipconfig2) on nic1, the association fails with a SKU mismatch error.

Which configuration change should the administrator perform to resolve this error and successfully associate both public IP addresses with VM1?

  1. Change the allocation method of PubIP1 to Static, upgrade PubIP1 to the Standard SKU, and then associate PubIP2 with ipconfig2.Answer
  2. B
    Create a second network interface named nic2, attach nic2 to VM1, and associate PubIP2 with the primary IP configuration of nic2.
  3. C
    Modify the configuration of PubIP2 to use Dynamic allocation, and then associate it with ipconfig2.
  4. D
    Disassociate PubIP1 from ipconfig1, change the SKU of PubIP2 from Standard to Basic in the Azure portal, and then reassociate both IPs.

Answer

Change the allocation method of PubIP1 to Static, upgrade PubIP1 to the Standard SKU, and then associate PubIP2 with ipconfig2.
To resolve the SKU mismatch, all public IP addresses associated with a single virtual machine (regardless of whether they are on the same network interface or different network interfaces) must use the same SKU. Since the new public IP (PubIP2) is a Standard SKU, the legacy public IP (PubIP1) must be upgraded to the Standard SKU. To upgrade a Basic SKU public IP to Standard SKU, its allocation method must first be changed from Dynamic to Static. Once both public IPs are of the Standard SKU, they can be successfully associated with VM1.

Step-by-Step Solution

1
Change the allocation method of the legacy Basic SKU public IP (PubIP1) from Dynamic to Static.
PubIP1 is now configured with Static allocation, which is a prerequisite for upgrading to the Standard SKU.
Standard SKU public IP addresses only support Static allocation; you cannot upgrade a Dynamic Basic SKU IP directly.
2
Upgrade PubIP1 from the Basic SKU to the Standard SKU.
PubIP1 becomes a Standard SKU public IP address.
All public IP addresses associated with a single virtual machine instance must share the same SKU. Since the second IP (PubIP2) is Standard, PubIP1 must also be Standard.
3
Associate the new Standard SKU public IP (PubIP2) with the secondary IP configuration (ipconfig2) on nic1.
Both PubIP1 and PubIP2 are successfully associated with VM1 without causing a SKU mismatch error.
Both public IP addresses now use the Standard SKU, complying with Azure's SKU alignment constraints for virtual machines.

Key Concept

SKU alignment and upgrade requirements for Public IP addresses associated with a single Virtual Machine
Rate this question

Topics

Configure Public and Private IP Addresses

More questions from this topic