Courseiva
Implement and Manage Virtual NetworkingmediumMultiple ChoiceObjective-mapped

AZ-104 Implement and Manage Virtual Networking Practice Question

A branch office uses an on-premises firewall that supports IPsec/IKE and has a stable public IP. The office needs always-on private connectivity to an Azure VNet over the internet. Which Azure component should the administrator deploy?

⚠ Common exam trap

Test-takers frequently confuse VNet peering (which only works between Azure VNets) with site-to-site VPN connectivity, or they mistakenly think Azure Bastion or private endpoints can provide network-level connectivity to on-premises networks.

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

A site-to-site connection using Azure VPN Gateway.

A site-to-site VPN connection using Azure VPN Gateway is the correct choice because it provides always-on, encrypted connectivity over the internet between an on-premises network with a stable public IP and an Azure VNet. Azure VPN Gateway supports IPsec/IKE protocols, which are compatible with the branch office's firewall, enabling a secure tunnel that meets the requirement for private connectivity.

Answer analysis

Option-by-option breakdown

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

  • A site-to-site connection using Azure VPN Gateway.

    Why this is correct

    A site-to-site VPN with Azure VPN Gateway is designed for permanent encrypted connectivity between an on-premises network and an Azure VNet. The branch firewall can establish an IPsec/IKE tunnel to the gateway using its public IP, which matches the scenario. This approach provides private connectivity across the internet without exposing the workload directly to public endpoints. It is the standard choice for hybrid network connectivity when ExpressRoute is not required.

  • VNet peering between the branch office and the Azure VNet.

    Why it's wrong here

    VNet peering connects two Azure virtual networks, enabling private IP traffic between them without any VPN tunnel. The branch office's on-premises firewall is not a virtual network and cannot participate in peering, nor does peering create any encrypted link across the internet. Peering is also non-transitive for indirect connectivity, so you still need a gateway to reach on-premises resources. Thus it is purely a cloud-to-cloud networking mechanism, not a hybrid connectivity option.

    When this WOULD be correct

    When connecting two Azure VNets in the same region or across regions for private, low-latency communication, VNet peering is the correct solution. For example, linking a hub VNet to a spoke VNet.

  • Azure Bastion in the target VNet.

    Why it's wrong here

    Azure Bastion is a fully managed PaaS service that provides secure, browser-based RDP and SSH sessions to individual virtual machines in a VNet, eliminating public IP exposure on those VMs. It does not create any IPsec tunnel, route traffic from the office's entire network, or connect the on-premises firewall to Azure. Bastion only carries interactive management sessions and requires the VNet to already have some network path from the client; it cannot establish a permanent site-to-site connection.

    When this WOULD be correct

    An administrator needs to provide secure, browser-based RDP/SSH access to Azure VMs in a VNet without exposing them to the public internet. The on-premises users must connect through Azure Bastion, not via a VPN tunnel.

  • A private endpoint for the Azure VNet.

    Why it's wrong here

    A private endpoint is a network interface with a private IP assigned from your Azure VNet that provides connectivity to a specific Azure PaaS service (such as storage or SQL) over Microsoft's backbone. It does not offer a generic IPsec/IKE tunnel or route for an entire branch office network, nor does it terminate on-premises firewall traffic. Without an existing VPN/ExpressRoute path, the office cannot even reach the endpoint, so it is not a site-to-site solution.

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.

A site-to-site connection using Azure VPN Gateway.Correct answer

Why this is correct

A site-to-site VPN with Azure VPN Gateway is designed for permanent encrypted connectivity between an on-premises network and an Azure VNet. The branch firewall can establish an IPsec/IKE tunnel to the gateway using its public IP, which matches the scenario. This approach provides private connectivity across the internet without exposing the workload directly to public endpoints. It is the standard choice for hybrid network connectivity when ExpressRoute is not required.

VNet peering between the branch office and the Azure VNet.Wrong answer — click to see why

Why this is wrong here

VNet peering connects two Azure VNets within Azure, not an on-premises network to Azure. It cannot connect a branch office's on-premises firewall to an Azure VNet over the internet.

★ When this WOULD be the correct answer

When connecting two Azure VNets in the same region or across regions for private, low-latency communication, VNet peering is the correct solution. For example, linking a hub VNet to a spoke VNet.

Why candidates choose this

Candidates may confuse VNet peering with site-to-site VPN, thinking it can extend on-premises connectivity, but peering is limited to Azure-internal networks only.

Azure Bastion in the target VNet.Wrong answer — click to see why

Why this is wrong here

Azure Bastion provides secure RDP/SSH access to VMs inside a VNet without public IPs, but it does not establish site-to-site IPsec/IKE connectivity from an on-premises network to Azure.

★ When this WOULD be the correct answer

An administrator needs to provide secure, browser-based RDP/SSH access to Azure VMs in a VNet without exposing them to the public internet. The on-premises users must connect through Azure Bastion, not via a VPN tunnel.

Why candidates choose this

Candidates may confuse Bastion's secure connectivity feature with VPN capabilities, assuming it can also serve as a gateway for site-to-site connections.

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.

About these practice questions

This AZ-104 question is part of Courseiva's 1,049-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.