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?
- Change the private IP address allocation method of the secondary configuration (ipconfig2) to Static.Answer
- BConfigure a User-Defined Route in the subnet route table with a next hop type of Virtual Network Gateway.
- CAssociate a Private DNS Zone virtual network link to the virtual network of VM-Mgmt.
- DChange 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
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