Configuring Point-to-Site VPN for Remote Azure VM Access
Your company has virtual machines (VMs) hosted in Microsoft Azure. The VMs are located in a single Azure virtual network named VNet1. The company has users that work remotely. The remote workers require access to the VMs on VNet1. You need to provide access for the remote workers. What should you do?
Community Insight
The exam tests the distinction between site-based and point-based connectivity; the common trap is selecting Site-to-Site (S2S) when only individual users, not entire branch networks, need access.
This question addresses the correct method for granting individual remote workers secure access to an Azure Virtual Network (VNet). It establishes that a Point-to-Site (P2S) VPN is the standard solution for connecting individual client devices directly to a VNet over the internet.
Candidates often choose Option A (Site-to-Site VPN) because they associate 'remote access' with corporate branches. However, S2S requires a physical gateway at the remote end, which is unnecessary and incorrect for individual telecommuters.
Community Discussion (50 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option C is the correct answer because a Point-to-Site (P2S) VPN connection allows individual client computers to connect securely to an Azure Virtual Network. This architecture is specifically designed for scenarios where remote workers (points) need to access resources within a central network (site) without requiring a dedicated on-premises hardware gateway at each user's location.Why the Other Options Are Wrong
Option A (Site-to-Site VPN) connects an entire on-premises network to Azure via a gateway, which is inefficient for individual users. Option B (VNet-to-VNet) connects two Azure VNets, not external clients. Option D (DirectAccess) is a legacy Windows Server feature that is complex to deploy and generally superseded by modern cloud-native solutions like P2S or Azure AD Join/Entra ID. Option E (Multi-Site) is used when connecting multiple on-premises sites to a single Azure gateway, irrelevant for individual remote workers.Community Comment Notes
The community consensus strongly supports Option C. As BinuRaj noted, "A Point-to-Site (P2S) VPN gateway connection lets you create a secure connection to your virtual network from an individual client computer." Multiple users confirmed that P2S is the ideal solution for telecommuters accessing a VNet from home or conference locations, distinguishing it from site-based connections.Official Reference
Exam Strategy
Always identify the 'endpoint' type in the scenario: if it is a single device/user, think Point-to-Site; if it is a whole office/network, think Site-to-Site. Avoid getting distracted by legacy technologies like DirectAccess unless the question explicitly mentions Windows Server infrastructure constraints.
Frequently Asked Questions
Why not use DirectAccess for remote workers?
DirectAccess is a legacy Windows Server technology requiring complex deployment and specific infrastructure. P2S VPN is simpler, cloud-native, and supported by Azure Gateway natively.
Is P2S VPN suitable for large numbers of users?
Yes, but for very large scale, consider Azure Firewall or application-level authentication. P2S is optimal for typical remote worker scenarios up to several thousand concurrent connections.
Related Analysis
Practice All AZ-900 Questions
Access 90 questions with complete answers and detailed explanations.
View Full AZ-900 Practice Test →