You have an Azure subscription that contains a virtual machine named VM-App1 in the East US region. VM-App1 has a single network interface named nic-app1, whose primary IP configuration is assigned to a subnet named Subnet1. VM-App1 is configured as a backend pool member of an East US Standard Load Balancer named LB1.
You need to configure nic-app1 to support a secondary web application. The configuration must allow the secondary application to be accessed from the internet using a dedicated public IP address.
Which two actions should you perform? (Select two.)
- Create a secondary IP configuration on nic-app1 within Subnet1.Answer
- Associate a Standard SKU public IP address in the East US region with the secondary IP configuration.Answer
- CAssociate a Basic SKU public IP address in the East US region with the secondary IP configuration.
- DCreate a secondary IP configuration on nic-app1 and assign it to a new subnet named Subnet2 in the same virtual network.
Answer
Create a secondary IP configuration on the network interface within the same subnet (Subnet1) and associate a Standard SKU public IP address in the same region with that secondary configuration.
To host a second website with its own public IP, you must configure a secondary IP configuration on the existing network interface. All IP configurations on a single network interface must be in the same subnet, meaning the secondary IP configuration must be assigned to Subnet1. Furthermore, because the virtual machine is in the backend pool of a Standard Load Balancer, any public IP address assigned to its network interface must use the Standard SKU to avoid a SKU mismatch.
Step-by-Step Solution
Key Concept
Configuring multiple IP configurations on a network interface and ensuring Public IP SKU alignment with a Standard Load Balancer.