Public IP addresses in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Understanding Azure Public IP Address Allocation

In Azure, when you create a Public IP address resource, what is the difference between Static and Dynamic allocation methods?

A Static allocation means the IP address is only available during business hours, Dynamic allocation is available 24/7.

B Static allocation assigns an IP address from a pool shared by all users, while Dynamic allocation assigns a unique IP address permanently.

C Static allocation automatically changes the IP address daily, Dynamic allocation keeps the same IP address forever.

D Static allocation assigns a fixed IP address that does not change, while Dynamic allocation assigns an IP address that can change when the resource is stopped and started.

💡 Hint

Think about whether the IP address stays the same or can change over time.

Static Public IP addresses in Azure remain the same throughout the resource lifecycle, while Dynamic Public IP addresses can change when the resource is deallocated and restarted.

❓ Architecture

intermediate

Choosing Public IP SKU for High Availability

You want to assign a Public IP address to a virtual machine scale set in Azure that requires zone redundancy and protection against IP address loss during maintenance. Which Public IP SKU should you choose?

A Dynamic Basic Public IP

B Basic SKU Public IP

C Standard SKU Public IP

D Classic Public IP

💡 Hint

Consider which SKU supports zone redundancy and SLA guarantees.

The Standard SKU Public IP supports zone redundancy and higher availability SLAs, making it suitable for production workloads requiring high availability.

❓ security

advanced

Securing Access to Azure Public IP Addresses

You have a Public IP address assigned to a virtual machine in Azure. You want to restrict inbound traffic so only specific IP addresses can connect. Which Azure service should you configure?

A Azure Network Security Group (NSG) with inbound rules

B Azure Application Gateway with WAF

C Azure Traffic Manager with geographic routing

D Azure Load Balancer with NAT rules

💡 Hint

Think about controlling network traffic at the subnet or NIC level.

Network Security Groups allow you to create inbound and outbound rules to restrict traffic to specific IP addresses or ranges.

❓ Configuration

advanced

Assigning a Public IP to an Azure Load Balancer

Which of the following JSON snippets correctly defines a Standard SKU Public IP resource in an Azure Resource Manager (ARM) template with static allocation?

A

{
  "type": "Microsoft.Network/publicIPAddresses",
  "apiVersion": "2022-05-01",
  "name": "myPublicIP",
  "location": "eastus",
  "sku": { "name": "Basic" },
  "properties": {
    "publicIPAllocationMethod": "Dynamic"
  }
}

B

{
  "type": "Microsoft.Network/publicIPAddresses",
  "apiVersion": "2022-05-01",
  "name": "myPublicIP",
  "location": "eastus",
  "sku": { "name": "Standard" },
  "properties": {
    "publicIPAllocationMethod": "Static",
    "idleTimeoutInMinutes": 10
  }
}

C

{
  "type": "Microsoft.Network/publicIPAddresses",
  "apiVersion": "2022-05-01",
  "name": "myPublicIP",
  "location": "eastus",
  "sku": { "name": "Standard" },
  "properties": {
    "publicIPAllocationMethod": "Static"
  }
}

D

{
  "type": "Microsoft.Network/publicIPAddresses",
  "apiVersion": "2022-05-01",
  "name": "myPublicIP",
  "location": "eastus",
  "sku": { "name": "Standard" },
  "properties": {
    "allocationMethod": "Static"
  }
}

💡 Hint

Check the property names and SKU values carefully.

Option B correctly uses the publicIPAllocationMethod property with value Static and specifies Standard SKU. It also includes an optional idleTimeoutInMinutes property which is valid.

✅ Best Practice

expert

Designing Public IP Usage for Cost and Security Optimization

You manage multiple Azure virtual machines that require internet access but do not need inbound connections from the internet. What is the best practice regarding Public IP address assignment to optimize cost and security?

A Use a NAT gateway with a single Public IP address for outbound internet access and no Public IPs on individual VMs.

B Assign a Public IP address to each virtual machine to allow outbound internet access.

C Assign dynamic Public IP addresses to each VM to reduce cost and allow inbound access when needed.

D Use Azure Firewall with Public IPs assigned to each VM for outbound and inbound traffic control.

💡 Hint

Consider how to provide outbound internet access without exposing VMs to inbound traffic.

Using a NAT gateway with a single Public IP address allows all VMs in a subnet to access the internet outbound without assigning Public IPs to each VM, reducing cost and improving security by preventing inbound internet connections.