Examkin

Question

Difficulty: HardConfigure Public and Private IP Addresses

An administrator is configuring a virtual machine named VM-Prod-01 in the East US region. The virtual machine has a single network interface named nic-prod-01. The primary IP configuration, ipconfig-primary, on nic-prod-01 is associated with a Basic SKU public IP address. You need to add a secondary IP configuration named ipconfig-secondary to nic-prod-01. The secondary configuration must include a public IP address that supports zone redundancy, which requires a Standard SKU public IP. Which of the following actions must you perform to allow the association of the Standard SKU public IP address with the secondary configuration?

  1. Dissociate the Basic SKU public IP address from the primary configuration, upgrade it to the Standard SKU, and then associate the Standard SKU public IP addresses.Answer
  2. B
    Associate the Standard SKU public IP address with the secondary configuration directly, as Azure supports mixing Basic and Standard SKU public IPs on different configurations of the same network interface.
  3. C
    Change the allocation method of the Standard SKU public IP address to Dynamic before associating it with the secondary configuration.
  4. D
    Create a second network interface, associate the Standard SKU public IP address with it, and attach it to the virtual machine while the first network interface retains the Basic SKU public IP address.

Answer

Dissociate the Basic SKU public IP address from the primary configuration, upgrade it to the Standard SKU, and then associate the Standard SKU public IP addresses.
The correct action is to dissociate the Basic SKU public IP from the primary configuration, upgrade it to the Standard SKU, and then associate the Standard SKU public IPs. Azure requires all public IP addresses associated with a virtual machine (whether on the same network interface or across multiple network interfaces) to use the same SKU. To upgrade a Basic SKU public IP to a Standard SKU, it must first be dissociated from the network interface. Once upgraded, both configurations can successfully use Standard SKU public IP addresses, which support the required zone redundancy.

Step-by-Step Solution

1
Identify the SKU mismatch constraint in Azure virtual machine network configurations.
Determine that all public IP addresses associated with a virtual machine's network interfaces must share the same SKU (either all Basic or all Standard).
Mixing Basic SKU and Standard SKU public IPs on a single virtual machine or a single network interface is not supported.
2
Formulate the upgrade path for the existing Basic SKU public IP address.
Determine that the Basic SKU public IP must be upgraded to Standard SKU, and that this upgrade requires the public IP to be in a dissociated state.
Azure requires a public IP address to be dissociated from any resource before its SKU can be upgraded from Basic to Standard.
3
Execute the dissociation, upgrade, and reassociation steps.
Dissociate the primary public IP, perform the SKU upgrade to Standard, and then associate the Standard SKU public IPs to both configurations.
This aligns the SKUs of all public IPs on the network interface to Standard, satisfying both the SKU consistency requirement and the zone-redundancy requirement.

Key Concept

Public IP SKU alignment and configuration constraints on Azure network interfaces
Rate this question

Topics

Configure Public and Private IP Addresses

More questions from this topic