Skip to main content

Technical Lab: Create a public IP address

Questions​

Question 1 — Multiple Choice​

An infrastructure team needs to ensure that a public IP address remains the same even after rebooting a virtual machine in Azure. During planning, a question arose about which SKU and allocation method to use.

Which combination correctly meets this requirement?

A) Basic SKU with Static allocation

B) Standard SKU with Dynamic allocation

C) Standard SKU with Static allocation

D) Basic SKU with Dynamic allocation, as Azure preserves the IP between reboots of the same resource

Question 2 — Technical Scenario​

An engineer creates a public IP address with the following command:

az network public-ip create \
  --resource-group rg-producao \
  --name pip-frontend \
  --sku Basic \
  --allocation-method Dynamic \
  --zone 1

After executing the command, Azure returns an error. What is the most likely cause?

A) The name pip-frontend contains a hyphen, which is not allowed in public IP addresses

B) Basic SKU does not support availability zone assignment

C) The --zone parameter can only be used with Static allocation, regardless of SKU

D) The resource group rg-producao needs to be in the same zone specified before creating the resource

Question 3 — True or False​

A Standard SKU public IP address created without zone specification is globally redundant and zone fault-tolerant by default, without requiring additional configuration.

Question 4 — Technical Scenario​

An organization operates a critical application exposed via Azure Load Balancer. The networking team receives instructions to migrate the public IP associated with the Load Balancer from Basic SKU to Standard, without changing the IP address. The responsible engineer plans to simply change the SKU directly in the Azure portal.

What problem does this approach present?

A) The SKU of a public IP address can be updated directly, but only via CLI, not through the portal

B) The SKU change requires the public IP to be disassociated from any resource before being recreated, as the SKU cannot be changed on an existing resource

C) Basic Load Balancer accepts Standard public IPs without any restrictions, so migration is unnecessary

D) SKU changes are only allowed within the same resource creation session, before saving

Question 5 — Multiple Choice​

When creating a public IP address in Azure, the Routing Preference field offers options that affect how traffic is routed between the end user and Azure resources.

Which statement correctly describes the behavior of the Internet option in Routing Preference?

A) Traffic is routed through Microsoft's global network from the edge closest to the user to the destination resource

B) Traffic travels through internet providers' public network for longer before entering Microsoft's network, prioritizing cost over latency

C) Traffic is always routed through Microsoft's private backbone, ensuring minimum latency regardless of origin

D) The Internet option is equivalent to the Microsoft Network option, differing only in the nomenclature displayed in the portal

Answer Key and Explanations​

Answer Key — Question 1​

Answer: C

Explanation:

  • Standard SKU with Static allocation is the only combination that ensures the IP address remains fixed and predictable throughout the resource lifecycle, including VM reboots and reassociations.
  • Alternative A is partially plausible because Basic SKU does support Static allocation, and this IP indeed doesn't change. However, Basic SKU is being deprecated by Microsoft and is not recommended for production environments. In AZ-700 exam contexts, the defensible and correct answer for a production stability requirement is always Standard SKU with Static allocation.
  • Alternative D represents a common misconception: in Basic SKU with Dynamic allocation, the IP can change when the resource is deallocated, which violates the requirement.
  • Standard SKU does not offer Dynamic allocation, making alternative B technically invalid.

Answer Key — Question 2​

Answer: B

Explanation:

  • Basic SKU does not support availability zones. The --zone parameter is exclusive to Standard SKU, which was designed for integration with Azure Availability Zones.
  • Attempting to associate a zone with a Basic public IP results in a validation error by Azure Resource Manager, as this resource lacks the necessary architecture for zonal redundancy.
  • Alternative C is a plausible distractor because it mixes two real concepts (zone and allocation), but the problem isn't in the combination with Dynamic allocation, but rather in the incompatibility of Basic SKU with the zone parameter.
  • Hyphens are allowed in Azure resource names, and the resource group doesn't need to be "in the same zone" as a public IP, making A and D incorrect.

Answer Key — Question 3​

Answer: False

Explanation:

  • A Standard public IP created without zone specification is classified as non-zonal, not as zone-redundant. It is provisioned in a specific zone automatically chosen by Microsoft, but without guarantee of survival to zonal failures.
  • For a Standard public IP to be zone-redundant, it's necessary to explicitly specify multiple zones or select the "Zone-redundant" option during creation.
  • This distinction is critical in high-availability design: assuming automatic redundancy can lead to architectures with single points of failure at the zone level, even when using the correct SKU.

Answer Key — Question 4​

Answer: B

Explanation:

  • The SKU of a public IP address in Azure is immutable after creation. It's not possible to change the SKU from Basic to Standard on an existing resource, whether through portal, CLI, or API.
  • The correct approach is to disassociate the public IP from the Load Balancer, delete the resource, create a new public IP with Standard SKU (which will assign a new address, different from the original) and reassociate.
  • If the organization needs to preserve the specific IP address, this is not directly possible: Microsoft doesn't offer IP portability between resources of different SKUs with preservation of the same address.
  • This limitation also implies that the associated Load Balancer needs to be of the same SKU as the public IP. Mixing SKUs between IP and Load Balancer results in a validation error.

Answer Key — Question 5​

Answer: B

Explanation:

  • The Internet option in Routing Preference means that traffic travels through ISPs' public network for a longer stretch before entering Microsoft's infrastructure. This results in lower data transfer egress costs, but with potentially higher latency and less control over the path.
  • The Microsoft Network option (the default) does the opposite: traffic enters Microsoft's global network as early as possible and travels through the private backbone to the destination, prioritizing performance.
  • Alternative A describes the behavior of the Microsoft Network option, not the Internet option.
  • Alternatives C and D are incorrect because they confuse the two modes or treat them as equivalent, when in practice they represent opposite routing philosophies with real cost and performance implications.