Examkin

Question

Difficulty: HardConfigure Public and Private IP Addresses

An administrator is configuring a virtual machine named VM-Prod1 in the West US 2 region. VM-Prod1 has a single network interface named nic-prod1. The primary IP configuration on nic-prod1 (ipconfig-primary) uses the static private IP address 10.0.0.410.0.0.4 and is associated with a Standard SKU public IP address named pip-primary. The administrator needs to configure a secondary IP configuration named ipconfig-secondary on nic-prod1. The secondary configuration must be accessible from the internet. The administrator plans to deploy a new public IP address named pip-secondary for this purpose. Which configuration must the administrator use for pip-secondary and the private IP address of ipconfig-secondary?

  1. pip-secondary must use the Standard SKU and Static allocation. The private IP address of ipconfig-secondary can use either Dynamic or Static allocation.Answer
  2. B
    pip-secondary must use the Basic SKU and Dynamic allocation. The private IP address of ipconfig-secondary must use Static allocation.
  3. C
    pip-secondary must use the Standard SKU and Dynamic allocation. The private IP address of ipconfig-secondary can use either Dynamic or Static allocation.
  4. D
    pip-secondary must use the Standard SKU and Static allocation. The private IP address of ipconfig-secondary must use Static allocation.

Answer

pip-secondary must use the Standard SKU and Static allocation. The private IP address of ipconfig-secondary can use either Dynamic or Static allocation.
The correct option correctly identifies that pip-secondary must use the Standard SKU to match the existing Standard SKU public IP on the virtual machine, and it must use Static allocation because Standard SKU public IPs do not support Dynamic allocation. Additionally, it correctly states that the private IP address for a secondary IP configuration can use either Dynamic or Static allocation.

Step-by-Step Solution

1
Determine the required SKU for the new public IP address (pip-secondary).
Standard SKU is required.
Azure does not support mixing Basic and Standard SKU public IP addresses on the same virtual machine instance. Since the primary IP configuration already uses a Standard SKU public IP (pip-primary), any additional public IP addresses associated with VM-Prod1 must also use the Standard SKU.
2
Determine the allocation method for the Standard SKU public IP address.
Static allocation is required.
In Azure, Standard SKU public IP addresses only support Static allocation. Dynamic allocation is not supported for Standard SKU public IPs.
3
Determine the private IP address allocation rules for the secondary IP configuration.
Either Dynamic or Static allocation is supported.
Azure virtual network interfaces support both Dynamic and Static private IP allocation methods for both primary and secondary IP configurations.

Key Concept

Azure Public IP SKU compatibility rules and private IP allocation capabilities on multi-IP network interfaces.
Estimated Time:2m 0s
Rate this question

Topics

Configure Public and Private IP Addresses

More questions from this topic