When Windows Server is used as a DHCP Relay Agent, the feature is delivered through Routing and Remote Access Service (RRAS). The AZ-800 content explains: “The DHCP Relay Agent is a component of RRAS and is installed by adding the Remote Access role and enabling the Routing role service.” After installation, admins configure the relay interface(s) and specify the IP addresses of one or more DHCP servers to which broadcast DHCPDISCOVER messages are forwarded. The documentation further notes: “Network Policy and Access Services (NPS) provides RADIUS and policy evaluation, not DHCP relay; the DHCP Server role offers DHCP lease services, not relay.” Thus, to prepare the server that sits on the new subnet to forward DHCP requests, you must install the Remote Access role (and within it, the Routing role service), then add the DHCP Relay Agent in the RRAS console or via PowerShell. QUESTION NO: 162
You have an on-premises server named Server! that runs Windows Server.
You have an Azure subscription that contains a virt ual network named VNet1.
You need to connect Server1 to VNet1 by using Azure Network Adapter.
What should you use?
A. Azure AD Connect
B. Device Manager
C. the Azure portal
D. Windows Admin Center
Answer: D
The Administering Windows Server H ybrid Core Infrastructure study guides describe Azure Network Adapter (ANA) as “a Windows Admin Center (WAC) workflow that creates a point-to-site VPN from an on-premises Windows Server to an Azure virtual network.” The guidance emphasizes: “ANA is initiated and configured exclusively from Windows Admin Center; it automates creation of the Azure VPN gateway side and the client configuration on the server.” The Azure portal does not expose an “ANA” button for a standalone server, Device Manager has no role, and Azure AD Connect is for directory synchronization, not networking. The steps include registering WAC with Azure, selecting Add > Azure Network Adapter on the target server, choosing the subscription/resource group/VNet (e.g., VNet1), and letting WAC provision the P2S configuration and Windows VPN client profile. Therefore, to connect Server1 to VNet1 using Azure Network Adapter, you must use Windows Admin Center.
Submit