An administrator is configuring a secondary IP configuration for an Azure virtual machine named VM-Db1. VM-Db1 has a single network interface named nic-db1. VM-Db1 is currently part of the backend pool of a Standard Load Balancer named LB-Prod. The administrator needs to configure a new IP configuration named ipconfig2 on nic-db1 to meet the following requirements:
- The private IP address of ipconfig2 must be set to .
- The public IP address of ipconfig2 must be accessible from the internet.
- VM-Db1 must remain in the backend pool of LB-Prod.
Which configuration must the administrator apply to ipconfig2 and the associated public IP address?
- Set the private IP allocation of ipconfig2 to Static, and associate a Standard SKU public IP address with Static allocation.Answer
- BSet the private IP allocation of ipconfig2 to Static, and associate a Basic SKU public IP address with Dynamic allocation.
- CSet the private IP allocation of ipconfig2 to Dynamic, and associate a Standard SKU public IP address with Static allocation.
- DSet the private IP allocation of ipconfig2 to Dynamic, and associate a Basic SKU public IP address with Static allocation.
Answer
Set the private IP allocation of ipconfig2 to Static, and associate a Standard SKU public IP address with Static allocation.
To satisfy the requirements, the private IP allocation must be set to Static to guarantee the assignment of . Furthermore, because the virtual machine is in the backend pool of a Standard Load Balancer, any public IP address associated with the network interface must be of the Standard SKU. Standard SKU public IP addresses require Static allocation.
Step-by-Step Solution
Key Concept
SKU alignment and IP allocation rules for Azure Virtual Machine NICs integrated with Standard Load Balancers.