Courseiva
Implement and Manage Virtual NetworkingmediumMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Virtual Networking Practice Question

Your company has an on-premises office network that needs encrypted connectivity to an Azure virtual network. In addition, traveling users need secure access from their laptops when they are away from the office. Which Azure design best meets both requirements?

⚠ Common exam trap

Watch out — candidates often confuse VNet peering (which only works between Azure VNets) with hybrid connectivity, or assume a single-purpose service like NAT gateway or service endpoint can replace a VPN gateway for encrypted remote access.

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

Deploy a VPN gateway and configure both site-to-site and point-to-site connections.

A VPN gateway supports both site-to-site (S2S) connections for the on-premises office network and point-to-site (P2S) connections for individual traveling users. The S2S connection uses IPsec/IKE to establish encrypted tunnels between the on-premises VPN device and the Azure VPN gateway, while the P2S connection uses SSTP, OpenVPN, or IKEv2 to allow remote laptops to connect securely from anywhere. This single gateway resource can handle both connection types simultaneously, meeting both requirements efficiently.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Deploy a VPN gateway and configure both site-to-site and point-to-site connections.

    Why this is correct

    A VPN gateway supports both site-to-site tunnels for the office network and point-to-site access for individual users. This single design meets the hybrid branch requirement and the remote-user requirement without exposing the VNet directly to the internet. It is the standard Azure networking choice when you need encrypted connectivity from both networks and individual clients.

  • Use VNet peering between the office network and Azure, then share the same connection with remote users.

    Why it's wrong here

    VNet peering is a Layer 3 connection between Azure virtual networks, not between on-premises and Azure. It relies on the Microsoft backbone and does not create an encrypted tunnel, nor does it provide any client VPN capability for traveling users. You would still need a VPN gateway to connect the office network, and a separate point-to-site configuration for remote laptops—so this option fails both requirements.

    When this WOULD be correct

    A question asks: 'You need to connect two Azure virtual networks in different regions with low-latency, private IP communication. Which solution should you use?' In that case, VNet peering is the correct answer.

  • Create a service endpoint to the virtual network and enable private access for laptops.

    Why it's wrong here

    Service endpoints are designed to secure access to Azure PaaS services (like Storage or SQL Database) from a virtual network, not to extend network connectivity to on-premises or remote users. They do not establish any encrypted tunnel for the office network, nor do they authenticate individual laptops. Simply enabling a service endpoint gives no path for a traveling user's laptop to reach Azure VMs or other private resources.

    When this WOULD be correct

    A question requiring secure access from an on-premises network to Azure PaaS services (e.g., Azure Storage or SQL Database) without traversing the public internet, while also needing private access for laptops. For example: 'Your company needs to connect its on-premises network to Azure Storage and also allow remote employees to access the storage privately. Which solution should you use?'

  • Deploy a NAT gateway and use it for secure office and laptop connectivity.

    Why it's wrong here

    A NAT gateway is an outbound-only connectivity tool that translates private source IP addresses from VMs to a public IP address. It provides no inbound site-to-site VPN capability, no point-to-site remote access, and no encryption or user authentication. Deploying a NAT gateway would not connect the office network to Azure and would not give laptops secure access—it is irrelevant for hybrid connectivity and remote-user connectivity.

    When this WOULD be correct

    A question requiring outbound internet access for Azure resources with source network address translation (SNAT) to a single public IP, while minimizing the number of public IPs used. For example: 'You need to enable outbound internet connectivity for multiple VMs in a subnet using a single public IP address.'

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The AZ-104 exam frequently reuses these exact scenarios with slightly different constraints.

Deploy a VPN gateway and configure both site-to-site and point-to-site connections.Correct answer

Why this is correct

A VPN gateway supports both site-to-site tunnels for the office network and point-to-site access for individual users. This single design meets the hybrid branch requirement and the remote-user requirement without exposing the VNet directly to the internet. It is the standard Azure networking choice when you need encrypted connectivity from both networks and individual clients.

Use VNet peering between the office network and Azure, then share the same connection with remote users.Wrong answer — click to see why

Why this is wrong here

VNet peering connects two Azure virtual networks, not an on-premises network to Azure. It does not provide encrypted site-to-site or point-to-site connectivity, so it fails to meet both requirements.

★ When this WOULD be the correct answer

A question asks: 'You need to connect two Azure virtual networks in different regions with low-latency, private IP communication. Which solution should you use?' In that case, VNet peering is the correct answer.

Why candidates choose this

Candidates may confuse VNet peering with VPN connectivity, thinking it can extend on-premises networks, or they might believe that once a connection is established, it can be shared with remote users without additional configuration.

Create a service endpoint to the virtual network and enable private access for laptops.Wrong answer — click to see why

Why this is wrong here

Service endpoints provide private connectivity from a virtual network to Azure PaaS services, not from on-premises or remote laptops to the virtual network. They do not support site-to-site or point-to-site VPN connectivity.

★ When this WOULD be the correct answer

A question requiring secure access from an on-premises network to Azure PaaS services (e.g., Azure Storage or SQL Database) without traversing the public internet, while also needing private access for laptops. For example: 'Your company needs to connect its on-premises network to Azure Storage and also allow remote employees to access the storage privately. Which solution should you use?'

Why candidates choose this

Candidates may confuse service endpoints with VPN connectivity, thinking they provide general private access to the virtual network, or they may assume 'private access for laptops' means using a service endpoint, not understanding that service endpoints apply only to Azure services.

Deploy a NAT gateway and use it for secure office and laptop connectivity.Wrong answer — click to see why

Why this is wrong here

A NAT gateway provides outbound internet connectivity for virtual networks but does not support encrypted site-to-site or point-to-site VPN connections. It cannot establish encrypted tunnels from on-premises offices or remote laptops to Azure.

★ When this WOULD be the correct answer

A question requiring outbound internet access for Azure resources with source network address translation (SNAT) to a single public IP, while minimizing the number of public IPs used. For example: 'You need to enable outbound internet connectivity for multiple VMs in a subnet using a single public IP address.'

Why candidates choose this

Candidates may confuse NAT (Network Address Translation) with VPN (Virtual Private Network) because both involve network connectivity and security, leading them to think a NAT gateway can provide secure remote access.

Analysis generated from the official AZ-104blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Quick reference

VPN Protocol Comparison

ProtocolPortEncryptionAuthenticationUse Case
IKEv2 / IPsecUDP 500 / 4500AES-256Certificates / PSKSite-to-site & remote access
SSL / TLS VPNTCP 443TLS 1.3Certificates / MFAClientless remote access
L2TP / IPsecUDP 1701AES (IPsec)PSK / CertificatesLegacy remote access
WireGuardUDP 51820ChaCha20Public keysModern high-performance VPN
PPTPTCP 1723MPPE (weak)MS-CHAPv2Legacy — 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

Courseiva writes every AZ-104 question from scratch — 1,049 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This AZ-104 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-104 exam.