AZ-500 Secure networking Practice Question
You need to secure traffic between an on-premises network and Azure using a VPN connection. Which TWO configurations are required?
⚠ Common exam trap
Watch out — candidates often confuse the local network gateway (a configuration object) with needing a public IP assigned to it, or think Azure Firewall can serve as a VPN endpoint, when in fact it is a separate security service.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a virtual network gateway (VPN)
Option A is correct because a virtual network gateway of type VPN is the Azure-side endpoint that terminates the IPsec/IKE tunnel and is mandatory for any site-to-site VPN connection. Option E is correct because the local network gateway is the Azure resource that represents the on-premises VPN device, holding its public IP address and address spaces so Azure knows how to route traffic to the remote network. Together, the virtual network gateway and local network gateway form the two required endpoints for a site-to-site VPN. Option B is not required because Azure Firewall provides traffic filtering and security policies, not the VPN tunnel itself. Option C is not required because the public IP is assigned to the on-premises VPN device (or referenced in the local network gateway), not to the local network gateway resource itself. Option D is not required because ExpressRoute is a separate dedicated private connectivity service, not a VPN solution.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create a virtual network gateway (VPN)
Why this is correct
The virtual network gateway is the Azure-side endpoint of a site-to-site VPN tunnel. It must be deployed in a dedicated GatewaySubnet and receives a public IP address to terminate the encrypted IPsec/IKE connection originating from the on-premises VPN device. Without this gateway, Azure has no component to establish the secure tunnel, so it is essential for securing traffic between the on-premises network and the virtual network.
- ✗
Deploy Azure Firewall
Why it's wrong here
Azure Firewall is a stateful, cloud-native firewall that filters and logs traffic, but it does not create a VPN tunnel or provide encrypted connectivity between the on-premises network and Azure. While you can route VPN traffic through an Azure Firewall for inspection, deploying a firewall alone leaves no IPsec endpoint on the Azure side. It is an optional security control, not the foundational connectivity resource the scenario requires.
- ✗
Assign a public IP to the local network gateway
Why it's wrong here
A local network gateway is a representation of the on-premises VPN device; it contains the device's public IP address and the on-premises address prefixes as configuration data, but it is not a resource that requires its own public IP assignment. The public IP for incoming connections is attached to the virtual network gateway, not to the local network gateway. Assigning a public IP to the local network gateway object is both unnecessary and invalid, so this action does not help establish the secure tunnel.
- ✗
Provision an ExpressRoute circuit
Why it's wrong here
ExpressRoute creates a private, dedicated connection from an on-premises network to Azure through a telecom provider, bypassing the public internet and using BGP rather than IPsec/IKE. It is a valid alternative for private connectivity, but it is not a VPN gateway and does not satisfy a requirement to create a VPN-based secure tunnel between the two sites. ExpressRoute also involves different prerequisites, provider partnerships, and longer provisioning times than a standard site-to-site VPN.
- ✓
Create a local network gateway
Why this is correct
The local network gateway is the Azure object that defines the on-premises VPN device's public IP address and the specific IP address ranges that Azure should route to the on-premises site. It is a required half of a site-to-site VPN configuration because it gives the virtual network gateway the destination information needed to build and route the encrypted tunnel. Without it, Azure would not know how to reach the on-premises network, so creating it is a necessary step for securing the connection.
Visual reference
Quick reference
VPN Protocol Comparison
| Protocol | Port | Encryption | Authentication | Use Case |
|---|---|---|---|---|
| IKEv2 / IPsec | UDP 500 / 4500 | AES-256 | Certificates / PSK | Site-to-site & remote access |
| SSL / TLS VPN | TCP 443 | TLS 1.3 | Certificates / MFA | Clientless remote access |
| L2TP / IPsec | UDP 1701 | AES (IPsec) | PSK / Certificates | Legacy remote access |
| WireGuard | UDP 51820 | ChaCha20 | Public keys | Modern high-performance VPN |
| PPTP | TCP 1723 | MPPE (weak) | MS-CHAPv2 | Legacy — avoid in production |
PPTP is considered insecure. IKEv2/IPsec and SSL VPN are the current recommended options.
Go deeper
Related to this question
About these practice questions
One of 617 original AZ-500 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-500 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-500 exam.