Topics

Next:Microsoft Entra ID100AZ-104Account…Loading progress
Show in graph
Virtual NetworkingNot studiedBlocked by 1

Subnets & IP Planning

Where resources actually land, and where delegation, service endpoints and reserved names change what a subnet can host.

Readiness

0%

Importance

2h baseline

Exam memorization points

  • Five addresses per subnet are reserved by the platform, so the usable host count is 2^(32-prefix) - 5.
  • Reserved subnet names matter: GatewaySubnet for VPN and ExpressRoute gateways, AzureBastionSubnet for Azure Bastion, AzureFirewallSubnet for Azure Firewall.
  • AzureBastionSubnet must be at least /26, while GatewaySubnet is commonly recommended as /27 or larger.
  • Subnet delegation hands a subnet to a PaaS service, for example Microsoft.Web/serverFarms for App Service VNet integration.
  • Service endpoints extend the VNet identity of a subnet to a PaaS public endpoint; private endpoints instead place a NIC with a private IP in the subnet.
  • Route tables and network security groups are associated with subnets, not with individual VMs.

Traps & distractors

  • Naming the gateway subnet anything other than GatewaySubnet, which makes the gateway deployment fail.
  • Sizing AzureBastionSubnet smaller than /26 - a frequent exam distractor.
  • Assuming a subnet CIDR can be edited while resources exist. It generally cannot; plan address space up front.
  • Delegating a subnet and then trying to deploy a VM there - delegated subnets are reserved for the delegated service.
  • Confusing service endpoints (public endpoint plus firewall) with private endpoints (private IP plus private DNS).

Suggested lab

Build the standard landing subnet set

50mcost medium

Practise the naming and sizing rules that the exam tests directly.

  1. 1In your VNet, create AzureBastionSubnet as /26 and GatewaySubnet as /27.
  2. 2Add a NAT Gateway and associate it with the workload subnet, then check the outbound public IP.
  3. 3Create a second VNet and a subnet delegated to Microsoft.Web/serverFarms.
  4. 4Try to deploy a VM into the delegated subnet and record the failure.
  5. 5Convert a service endpoint on the workload subnet for Microsoft.Storage into a private endpoint and compare addresses.

Cleanup / cost guard

Use a dedicated throwaway resource group whenever possible. At the end, delete disposable lab resources and verify in Cost Management/resource lists that no billable VM, gateway, public IP, private endpoint, disk, database or other paid resource remains.

Microsoft Learn

Direct Microsoft Learn links are also used by the live AI tutor retrieval layer when available. Search links remain a discovery fallback and are not presented as retrieved evidence.

Status

No time invested yet. Baseline assumptions only.

Self-assessed mastery

0%

0%50%100%
Computed readiness0%
Logged study time0 min
Last studiednever
Last updatedtoday
89/ 100

Critical priority

High-yield and still weak. Study this next.

  • Exam importance100% × 30% = 30.0

    Learner-agnostic frequency on the real exam (5/5).

  • Blueprint weight78% × 25% = 19.4

    This topic's domain carries 17.5% of the exam objectives.

  • Dependency leverage72% × 20% = 14.5

    11 later topics depend on it.

  • Current gap100% × 25% = 25.0

    Readiness is 0%, so 100% of the topic is still uncovered.

Exam Priority Score = 30% importance + 25% blueprint + 20% dependency + 25% gap. Importance is exam frequency, blueprint is the domain's official exam weight, dependency is how many later topics this one unlocks, and gap is how far you currently are from ready.

Prerequisites

Locked until prerequisites reach 50% readiness.

Unlocks next

11 topics downstream in total.

Baseline study time

2h

Complexity

3 / 5

Remaining to target

1h 42m

Status weight

0%

Topics: subnet, cidr, delegation, service endpoint, gateway subnet, bastion subnet

AI tutor · Microsoft Learn grounded

Live DeepSeek tutor using the official Microsoft Learn links attached to this topic. It can explain and test you; it does not mark mastery or claim that a lab was completed.

Weak neighbours in Networking