SaveMyCert
Log in
5 of 5 free questions left today·for 10 a day
AZ-104 · Domain 4

Implement and manage virtual networking practice questions

Implement and manage virtual networking is worth 19% of the AZ-104 exam — the 3rd-heaviest of the 5 domains. Virtual networks and subnets, secure network access, name resolution, and load balancing. Official weighting 15–20%. 6 fully worked examples are further down this page, answers included.

Exam weight
19%
the 3rd-heaviest of the 5 domains
Questions
114
across 3 topics
Free, no account
5/day
a free account allows 10 a day
Explanations
Every option
right and wrong

Build a practice session

5 free questions left today.

Domains

How many?

5 free questions left today.

Mode

Ready when you are

10 fresh questions drawn across 1 of 5 domains, in Learn mode.

Review what you missed

Every question you answer incorrectly, and every question you flag while practising, is saved here automatically. Finish a session and you can come back to re-drill just those.

6 sample Implement and manage virtual networking questions, fully explained

Questions from the AZ-104 bank mapped to domain 4, with the answer key and the reasoning behind every option. None of them repeat the examples on the main AZ-104 practice page.

Question 1Implement and manage virtual networking

You create a subnet with the address range 10.1.1.0/24 in an Azure virtual network. How many IP addresses in that subnet are available for you to assign to resources?

Choose one.

  • a
    254

    254 is the classic on-premises answer (256 minus network and broadcast), but Azure reserves 5 addresses per subnet, not 2.

  • b
    256

    256 is the raw size of a /24 with nothing reserved; no network — Azure included — hands you every address in the block.

  • c
    251 Correct

    A /24 has 256 addresses, and Azure reserves 5 in every subnet (network address, default gateway, two for Azure DNS, and broadcast), leaving 251 usable.

  • d
    250

    250 would imply Azure reserves 6 addresses; the actual number reserved in every Azure subnet is 5.

The concept

Azure reserves 5 IP addresses in every subnet: x.x.x.0 (network), x.x.x.1 (default gateway), x.x.x.2 and x.x.x.3 (mapped for Azure DNS), and the last address (broadcast).

Why that’s the answer

A /24 contains 256 addresses. Subtracting Azure's 5 reserved addresses leaves 251 assignable. The 254 distractor is the traditional networking answer that only subtracts network and broadcast — the most common wrong answer on this question. 256 ignores reservations entirely, and 250 over-counts the reservation.

How to reason it out
  1. Compute the raw subnet size: 2^(32 - prefix length); for /24 that is 256.
  2. Subtract Azure's 5 reserved addresses (first four addresses plus the last one).
  3. Size subnets with this overhead in mind — this is also why Azure's smallest supported subnet is a /29, which yields only 3 usable addresses.

Exam tip: Azure reserves 5 IPs in every subnet, so a /24 gives you 251 usable addresses, not 254.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

Question 2Implement and manage virtual networking

You need to create a small subnet for exactly three network interfaces used by a management appliance. To conserve address space, you want the smallest subnet size Azure supports. Which prefix should you use?

Choose one.

  • a
    /30

    A /30 has only 4 addresses; after Azure's 5 reserved addresses nothing would remain, so Azure does not permit subnets smaller than /29.

  • b
    /28

    A /28 works (11 usable addresses) but it is not the smallest supported size, so it wastes address space against the stated requirement.

  • c
    /32

    A /32 is a single host address; it cannot be a subnet at all in Azure since there would be no room for the 5 reserved addresses.

  • d
    /29 Correct

    /29 is the smallest subnet Azure allows; it has 8 addresses, and after Azure's 5 reservations exactly 3 remain assignable — a perfect fit here.

The concept

Because Azure reserves 5 addresses in every subnet, the smallest subnet prefix Azure supports is /29, which leaves 3 usable addresses out of 8.

Why that’s the answer

/29 is both the minimum Azure allows and exactly sufficient for three NICs (8 total minus 5 reserved = 3 usable). /30 and /32 fail because their raw size cannot even cover Azure's 5 reservations, so Azure rejects them. /28 is valid but larger than necessary, so it does not satisfy the smallest-size constraint in the question.

How to reason it out
  1. Recall the Azure subnet limits: smallest is /29, largest is /2.
  2. Work out usable addresses as (2^(32 - prefix)) minus 5 reserved.
  3. Match the usable count to the number of NICs you must place, and leave growth headroom when the workload might scale.

Exam tip: The smallest Azure subnet is /29 — 8 addresses minus 5 reserved leaves 3 usable.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

Question 3Implement and manage virtual networking

VNet-Hub is peered with VNet-Spoke1 and with VNet-Spoke2. The spokes are not peered with each other, and the hub contains no network virtual appliance or gateway. A VM in VNet-Spoke1 can reach VMs in the hub, but connections to a VM's private IP in VNet-Spoke2 time out. What is the cause?

Choose one.

  • a
    The default NSG rules deny inbound traffic that arrives from a peered network

    The default AllowVnetInBound rule admits traffic from peered networks, because the VirtualNetwork service tag includes peered address space. Spoke1 already reaches the hub, which proves peered traffic is allowed.

  • b
    Gateway transit isn't enabled on the hub's peerings to the two spoke networks

    Gateway transit shares a VPN or ExpressRoute gateway with peers. The hub has no gateway, and gateway transit never turns a hub into a router between spokes.

  • c
    Peering is non-transitive, so the hub's two peerings don't link the spokes Correct

    Peerings do not chain: Spoke1-Hub plus Hub-Spoke2 gives Spoke1 no route to Spoke2. A direct spoke peering or routing through a hub appliance is needed.

  • d
    IP forwarding isn't enabled on the network interfaces of the hub's VMs

    IP forwarding matters only on a VM that relays traffic, such as an NVA that UDRs point at. No route sends spoke traffic to any hub VM, so the setting changes nothing here.

The concept

VNet peering is non-transitive: if A is peered with B and B with C, A cannot reach C through B. Spoke-to-spoke traffic in a hub-spoke design needs a direct peering or user-defined routes through an NVA or Azure Firewall in the hub.

Why that’s the answer

The spokes have no peering and no route to each other, and the two hub peerings do not combine into one path, so the packets have nowhere to go. The NSG option fails because the default rules allow peered traffic, and Spoke1-to-hub already works. Gateway transit only shares a gateway the hub does not have. IP forwarding is needed on a relaying appliance, but nothing routes spoke traffic to one.

How to reason it out
  1. List the peerings that exist: Spoke1-Hub and Hub-Spoke2, with no Spoke1-Spoke2 link.
  2. Apply the rule that a peering never carries traffic on to a third network.
  3. Rule out NSGs: Spoke1 reaching the hub shows peered traffic is allowed.
  4. Fix it with a direct spoke peering, or UDRs through a hub NVA or firewall.

Exam tip: Peering is non-transitive: two spokes peered to one hub cannot talk until you peer them or route them through a hub appliance.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

Question 4Implement and manage virtual networking

VNet-Hub has a VPN gateway connected to the on-premises network, and its peering to VNet-Spoke already has "Allow gateway transit" enabled. VNet-Spoke has no gateway of its own. The effective routes of a spoke VM show no on-premises prefixes. You must give the spoke on-premises connectivity with the least administrative effort. What should you do?

Choose one.

  • a
    Enable "Use remote gateways" on the spoke's peering to the hub Correct

    This is the consuming half of gateway transit: the spoke starts using the hub's gateway and learns the on-premises routes through it.

  • b
    Deploy a second VPN gateway in VNet-Spoke and connect it on-premises

    A spoke gateway would work, but it costs money, takes time to deploy and needs its own on-premises connection, so it fails the least-effort requirement.

  • c
    Enable "Allow gateway transit" on the spoke's peering to the hub

    Allow gateway transit is set by the VNet that owns the gateway. The spoke has no gateway to offer, so this setting does not make it consume the hub's gateway.

  • d
    Enable "Allow forwarded traffic" on the spoke's peering to the hub

    Allow forwarded traffic accepts packets relayed by an appliance from a third network. It does not attach the spoke to the hub's gateway or bring in on-premises routes.

The concept

Gateway transit lets peered VNets share one VPN or ExpressRoute gateway. The VNet that owns the gateway enables "Allow gateway transit" on its peering, and each consuming VNet enables "Use remote gateways" on its own peering. Both regional and global peering support it.

Why that’s the answer

The hub side is already done, so the missing half is "Use remote gateways" on the spoke's peering, after which the spoke learns the on-premises prefixes. A spoke gateway would also work but adds cost and effort, failing the constraint. "Allow gateway transit" on the spoke inverts the roles. "Allow forwarded traffic" concerns relayed traffic, not gateway sharing.

How to reason it out
  1. Identify which VNet owns the gateway: the hub.
  2. Confirm the owner's half: "Allow gateway transit" on the hub's peering is already set.
  3. Set the consumer's half: "Use remote gateways" on the spoke's peering (possible because the spoke has no gateway of its own).
  4. Check a spoke NIC's effective routes for on-premises prefixes with next hop Virtual network gateway.

Exam tip: Gateway owner sets "Allow gateway transit"; each consumer sets "Use remote gateways" on its own peering.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

Question 5Implement and manage virtual networking

You try to peer VNet-A (10.0.0.0/16) in one subscription with VNet-B (10.0.0.0/16) in another subscription of the same Microsoft Entra tenant. You hold the Network Contributor role on both virtual networks, but Azure rejects the peering. What must you do before the peering can be created?

Choose one.

  • a
    Move both virtual networks into the same subscription and resource group

    Peering works across resource groups, subscriptions and even tenants, so moving the networks does not remove the real blocker.

  • b
    Change the address space of one VNet so the two ranges don't overlap Correct

    Peered address spaces must not overlap. With identical 10.0.0.0/16 ranges Azure cannot route between them, so one VNet must be re-addressed first.

  • c
    Deploy a VPN gateway in each VNet and connect them with BGP enabled

    A VNet-to-VNet VPN is a different connection method; it does not fix the peering, and identical prefixes still could not be routed between the networks.

  • d
    Enable "Allow forwarded traffic" on both sides of the new peering

    Allow forwarded traffic is an option on a peering that already exists and concerns relayed traffic; it has nothing to do with overlapping ranges.

The concept

VNet peering requires the address spaces being peered to be non-overlapping, because Azure must build unambiguous routes between them. Peering otherwise works across resource groups, subscriptions and Microsoft Entra tenants when you have the needed permissions.

Why that’s the answer

Overlap is the hard blocker, so re-addressing one VNet (for example VNet-B to 10.1.0.0/16) is the fix. The subscription option is wrong because peering spans subscriptions and tenants, and the stem confirms permissions are in place. A VPN connection does not repair a peering and cannot route identical prefixes either. Allow forwarded traffic is an unrelated setting on an existing peering.

How to reason it out
  1. Compare the two address spaces: both are 10.0.0.0/16.
  2. Recall that peered ranges must not overlap; subscriptions and resource groups do not matter.
  3. Re-address one VNet from your IP plan (move or delete resources in the conflicting range first).
  4. Create the peering again once the ranges are disjoint.

Exam tip: Overlapping address space blocks VNet peering; subscription, resource group and tenant boundaries do not.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

Question 6Implement and manage virtual networking

You peer VNet-East in East US with VNet-West in West Europe. Before approving the design, the security team asks how traffic between VMs in the two virtual networks travels. Which statement is accurate?

Choose one.

  • a
    It stays on the Microsoft backbone between private IPs, with no gateway Correct

    Global peering keeps traffic on Microsoft's private backbone between private addresses; no gateway, tunnel or internet hop is involved.

  • b
    It crosses the internet inside an IPsec tunnel that Azure creates for it

    That describes a VNet-to-VNet VPN connection between gateways. Peering creates no tunnel and does not use the public internet.

  • c
    It passes through a VPN gateway that each VNet deploys for the peering

    Peering needs no gateway at all; avoiding gateways is one of its main advantages over VNet-to-VNet VPN.

  • d
    It leaves through each VM's public IP and is filtered by the NSG rules

    Peered traffic uses private IPs end to end; public IPs are not involved, although NSGs can still filter it.

The concept

VNet peering is regional (same region) or global (different regions). Both keep traffic private on the Microsoft backbone between private IP addresses, with no gateway, tunnel or public internet hop.

Why that’s the answer

Global peering differs from regional peering only in region scope; the data path is the same private backbone. The IPsec option describes VNet-to-VNet VPN. The gateway option inverts the point of peering. The public-IP option confuses peering with internet connectivity. One global-only constraint worth knowing: resources cannot reach the front-end IP of a Basic load balancer (a retired SKU) in a globally peered VNet.

How to reason it out
  1. Recognise the setup as global peering because the regions differ.
  2. Recall that peering of either kind uses the Microsoft backbone and private IPs.
  3. Eliminate options that need gateways, tunnels or public IPs; those belong to VPN or internet designs.

Exam tip: Global VNet peering connects regions privately over Microsoft's backbone, with no gateway, tunnel or internet hop.

Azure Virtual Networks, Subnets, Peering & User-Defined Routes — the lesson that teaches this.

What AZ-104 domain 4 tests, topic by topic

The official exam guide breaks Implement and manage virtual networking into 3 topics. The question bank follows the same split, so a weak topic shows up as a cluster of misses you can go back and read.

Published AZ-104 practice questions per topic in Implement and manage virtual networking
TopicWhat it coversQuestions
Configure and manage virtual networks in AzureSkills outline section (AZ-104, as of April 17, 2026). Creating and configuring virtual networks and subnets; creating and configuring virtual network peering; configuring public IP addresses; configuring user-defined routes; troubleshooting network connectivity.38
Configure secure access to virtual networksSkills outline section (AZ-104, as of April 17, 2026). Creating and configuring network security groups (NSGs) and application security groups; evaluating effective security rules in NSGs; implementing Azure Bastion; configuring service endpoints and private endpoints for Azure platform as a service (PaaS).38
Configure name resolution and load balancingSkills outline section (AZ-104, as of April 17, 2026). Configuring Azure DNS; configuring an internal or public load balancer; troubleshooting load balancing.38
Total114

Revise Implement and manage virtual networking before you drill it

Other AZ-104 domains

Implement and manage virtual networking: your questions

Implement and manage virtual networking is domain 4 of the AZ-104 exam guide and carries 19% of the scored content — the 3rd-heaviest of the 5 domains. On a 50-question paper that works out to roughly 10 questions, though Microsoft Azure does not publish an exact per-domain count and individual exam forms vary.

Source

The domain weight and topic list on this page come from the official AZ-104 exam guide.