Examkin

Question

Difficulty: HardConfigure Public and Private IP Addresses

An organization is deploying a multi-tenant web application on a single Azure Virtual Machine. The network architecture requires a single network interface to receive traffic on two distinct private IP addresses, each mapped to a dedicated public IP address for external access. The virtual network uses the address space 10.0.0.0/1610.0.0.0/16 and the subnet uses 10.0.1.0/2410.0.1.0/24. The network interface currently has a single IP configuration named `ipconfig-primary` with a dynamic private IP address of 10.0.1.410.0.1.4 and a Standard SKU public IP address. Which of the following configuration steps must be performed to implement the secondary IP configuration? (Select TWO).

  1. Add a secondary IP configuration named `ipconfig-secondary` to the network interface and assign it a private IP address within the 10.0.1.0/2410.0.1.0/24 range.Answer
  2. Associate a Standard SKU public IP address configured with static allocation to the secondary IP configuration.Answer
  3. C
    Associate a Basic SKU public IP address configured with dynamic allocation to the secondary IP configuration.
  4. D
    Associate a Standard SKU public IP address configured with dynamic allocation to the secondary IP configuration.
  5. E
    Configure the secondary IP configuration to use a different subnet within the virtual network than the primary IP configuration.

Answer

To implement the secondary IP configuration, you must add a secondary IP configuration to the network interface with a private IP in the same subnet range, and associate it with a Standard SKU public IP address configured with static allocation.
To successfully configure a secondary IP configuration for internet access on an existing network interface, you must first add a secondary IP configuration and assign it a private IP address within the same subnet (10.0.1.0/2410.0.1.0/24). Then, because the primary configuration already uses a Standard SKU public IP, any secondary public IP associated with the same network interface must also be a Standard SKU public IP. Standard SKU public IP addresses in Azure require static allocation, so you must create and associate a Standard SKU public IP with static allocation.

Step-by-Step Solution

1
Add a secondary IP configuration on the network interface.
The secondary configuration is created but requires a valid private IP address in the same subnet as the primary configuration.
All IP configurations on a single network interface must belong to the same subnet.
2
Create a new Standard SKU Public IP address with static allocation.
A new Standard SKU public IP is provisioned.
Azure requires all public IP addresses on a single network interface to share the same SKU. Since the primary is Standard, the secondary must also be Standard. Standard public IPs only support static allocation.
3
Associate the Standard SKU public IP address with the secondary IP configuration.
The secondary IP configuration is successfully mapped to the new public IP address, allowing external traffic to reach the secondary private IP.
This completes the binding of the public IP to the secondary private IP configuration.

Key Concept

Configuring multiple IP configurations on a single network interface and aligning Public IP SKUs and allocation methods.
Rate this question

Topics

Configure Public and Private IP Addresses

More questions from this topic