Question

Difficulty: MediumConfigure Public and Private IP Addresses

An administrator is configuring a virtual machine named VM-Mgmt. The virtual machine has a single network interface named nic-mgmt. The primary IP configuration (ipconfig1) of nic-mgmt is configured with a dynamic private IP address. The administrator adds a secondary IP configuration named ipconfig2 to nic-mgmt. The administrator needs to associate a public IP address with ipconfig2 to allow direct management access. However, when configuring ipconfig2 in the Azure portal, the option to associate a public IP address is unavailable. What is the primary configuration change required to resolve this issue and allow the association of the public IP address?

  1. Change the private IP address allocation method of the secondary configuration (ipconfig2) to Static.Answer
  2. B
    Configure a User-Defined Route in the subnet route table with a next hop type of Virtual Network Gateway.
  3. C
    Associate a Private DNS Zone virtual network link to the virtual network of VM-Mgmt.
  4. D
    Change the priority of the default inbound Network Security Group (NSG) rules to allow traffic on port 3389.

Answer

Change the private IP address allocation method of the secondary configuration (ipconfig2) to Static.
The correct answer is to change the private IP address allocation method of the secondary configuration (ipconfig2) to Static. Azure enforces a rule that a public IP address can only be associated with a secondary IP configuration of a network interface if that secondary configuration uses a Static private IP address. If it is set to Dynamic, the public IP association option is disabled in the portal.

Step-by-Step Solution

1
Navigate to the network interface nic-mgmt in the Azure portal and select IP configurations.
The list of IP configurations (ipconfig1 and ipconfig2) is displayed.
To modify the settings of the secondary IP configuration where the public IP needs to be associated.
2
Select the secondary configuration ipconfig2, change the Private IP address settings allocation from Dynamic to Static, and specify a valid private IP address within the subnet range.
The private IP allocation is updated to Static, and the option to associate a public IP address becomes active and configurable.
Azure requires that any secondary IP configuration on a network interface must have a static private IP address before a public IP address can be associated with it.
3
Associate the desired public IP address to ipconfig2 and save the configuration.
The public IP address is successfully associated with the secondary IP configuration.
To complete the requirement of enabling public access on the secondary IP configuration.

Key Concept

In Azure, associating a public IP address with a secondary IP configuration on a network interface (NIC) requires that the private IP address allocation method for that specific configuration be set to Static.
Estimated Time:1m 30s
Rate this question