70-695 · Question #86
Your network contains three subnets named Subnet1, Subnet2, and Subnet3. A DHCP server named DHCP1 is on Subnet1. All of the client computers on all of the subnets receive an IP address from DHCP1…
The correct answer is D. From the properties of the DHCP scope, configure DHCP options 66 and 67. When the DHCP server and WDS server are on different subnets, DHCP options 66 and 67 must be configured on the DHCP scope to provide PXE clients with the WDS server's IP address and the boot file name.
Question
Your network contains three subnets named Subnet1, Subnet2, and Subnet3. A DHCP server named DHCP1 is on Subnet1. All of the client computers on all of the subnets receive an IP address from DHCP1. Your company deploys a Windows Deployment Services (WDS) infrastructure to Subnet1. You attempt to deploy Windows 8.1 Enterprise to new client computers in Subnet2 by using PXE boot, but the computers fail to start from PXE. You verify that all of the TCP and UDP ports required for WDS PXE boot are allowed on the routers between the subnets. You need to ensure that you can perform PXE boot installations of Windows 8.1 Enterprise successfully on the new client computers on all of the subnets. What should you do?
Options
- AAdd a remote access server to Subnet2 and Subnet3.
- BAdd a DHCP server to each subnet.
- CFrom the WDS server, configure network address translation (NAT).
- DFrom the properties of the DHCP scope, configure DHCP options 66 and 67.
How the community answered
(39 responses)- A5% (2)
- B3% (1)
- C13% (5)
- D79% (31)
Why each option
When the DHCP server and WDS server are on different subnets, DHCP options 66 and 67 must be configured on the DHCP scope to provide PXE clients with the WDS server's IP address and the boot file name.
Adding a remote access server is unrelated to enabling PXE boot functionality across subnets.
Adding a DHCP server to each subnet would solve the problem but is a less efficient solution than configuring DHCP options on a centralized DHCP server, especially if IP helpers are already present.
Configuring Network Address Translation (NAT) on the WDS server is not the correct approach to enable PXE boot across subnets; NAT is for translating IP addresses, not directing PXE clients.
DHCP options 66 (Boot Server Host Name) and 67 (Bootfile Name) are essential for PXE booting across subnets. These options instruct the client on where to find the WDS server and the specific boot image file, enabling successful PXE initiation.
Concept tested: WDS PXE boot across subnets
Source: https://learn.microsoft.com/en-us/windows-server/get-started/whats-new-in-windows-server-2016#windows-deployment-services
Topics
Community Discussion
No community discussion yet for this question.