A company is deploying a set of Azure resources that need public IP addresses. They want to ensure that all IPs are from a contiguous block to simplify firewall rules. They also want to be able to assign IPs to resources as they are created. Which approach should they use?

Create individual public IP addresses for each resource

Create a Public IP Prefix and assign IPs from the prefix to resources

Use Azure Firewall to manage public IPs

Create a Custom IP address prefix

You have a standard public IP address that you need to use with an Azure Load Balancer's frontend. What is the correct way to associate it?

Create a NAT rule on the load balancer and use the public IP as the source.

Assign the public IP to the load balancer's backend pool.

Create the load balancer and assign the public IP to its frontend IP configuration.

Associate the public IP directly with the backend pool VMs.

A company is deploying an Azure SQL Managed Instance. They need to ensure that the service can automatically manage the subnet, including scaling and high availability. Which configuration should they implement?

Place the SQL Managed Instance in a subnet with no delegation

Use a subnet that is already delegated to another service

Delegate the subnet to Microsoft.Sql/managedInstances

Assign a route table to the subnet

A startup is creating a VNet for a new application. They expect to grow to 500 VMs across multiple tiers. They want to avoid renumbering later. What address space should you choose for the VNet?

Use a /24 address space, such as 10.0.0.0/24.

Use a /8 address space, such as 10.0.0.0/8.

Use a /28 address space, such as 10.0.0.0/28.

Use a /16 address space, such as 10.0.0.0/16.

What is the primary purpose of creating a Public IP Prefix in Azure?

To provide a static public IP address for a single virtual machine

To reserve a contiguous block of public IP addresses that can be assigned to multiple resources

To enable a resource to use a custom domain name

To create a private IP address range for a virtual network

Microsoft Certified:Azure Network Engineer Associate

Domain 1Objective 1

Design and Implement IP Addressing for Azure Resources AZ-700 Practice Questions (Page 7)

Part of the Design and implement core networking infrastructure domain, which accounts for 25–30% of the AZ-700 exam. Microsoft does not publish an official question count, but from its 100-minute exam (~40–65 total, ~10–20 in this domain), expect 3–5 from this objective — we provide 39 practice questions to prepare you well beyond it. (estimate)

39questions here

8free pages

10concepts

25–30%of the exam

Questions 31–35

31application · medium
A company is deploying a set of Azure resources that need public IP addresses. They want to ensure that all IPs are from a contiguous block to simplify firewall rules. They also want to be able to assign IPs to resources as they are created. Which approach should they use?
Select an answer first
32application · medium
You have a standard public IP address that you need to use with an Azure Load Balancer's frontend. What is the correct way to associate it?
Select an answer first
33application · medium
A company is deploying an Azure SQL Managed Instance. They need to ensure that the service can automatically manage the subnet, including scaling and high availability. Which configuration should they implement?
Select an answer first
34application · medium
A startup is creating a VNet for a new application. They expect to grow to 500 VMs across multiple tiers. They want to avoid renumbering later. What address space should you choose for the VNet?
Select an answer first
35foundation · easy
What is the primary purpose of creating a Public IP Prefix in Azure?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to AZ-700

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Microsoft. “AZ-700” is a trademark of its owner, used for identification only.