Choosing the route by breadth or by order
The wrong answers pick the wider 10.0.0.0/16 route, send traffic down both routes, or let the earlier route win. Azure selects the longest matching prefix first, so 10.0.0.5 follows the 10.0.0.0/24 route. When two routes carry the identical prefix, such as 0.0.0.0/0, source priority decides: user-defined route, then BGP route, then system route. The user-defined route therefore overrides the default Internet route.
See it in a sample questionTreating all next hop types as settable in a route
The wrong answers treat next hop types as interchangeable. Virtual appliance, Virtual network gateway, None, Virtual network and Internet can be set in a user-defined route, and None drops the traffic. Virtual network peering and VirtualNetworkServiceEndpoint cannot be specified in a UDR. Azure adds them when a peering is configured or a service endpoint is enabled, so they are what effective routes show for those features. A gateway, appliance or Internet hop does not mark either one.
See it in a sample questionReading a higher priority number as higher priority
The wrong answers process the larger number first, or expect every matching rule to apply. Network security group rules are processed in priority order, lower numbers first, and processing stops at the first match. A priority 150 deny therefore beats a priority 200 allow, and an allow at 110 is reached before a deny at 120. Custom priorities run from 100 to 4096. Values such as 65000 belong to default rules, which carry the lowest priority.
See it in a sample questionConfusing load balancer rule, inbound NAT rule and probe
The wrong answers pick a component that sounds close. A health probe checks instance health, an outbound rule configures outbound NAT, and an inbound NAT rule forwards to one specific VM. A load balancer rule maps a frontend and port to every instance in the backend pool. To load balance all TCP and UDP flows on every port of an internal Standard Load Balancer, one rule with protocol all and port 0 replaces a rule per port.
See it in a sample questionSwapping the scope and region rules of service and private endpoints
The wrong answers blur service endpoints and private endpoints. A service endpoint secures a subnet to an Azure service, and for Azure SQL Database the virtual network must be in the same region as the resource. A private endpoint maps to a single PaaS resource instance, so other instances stay blocked. The private endpoint must sit in the same region and subscription as its virtual network, while the private-link resource can be in a different region.
See it in a sample question