Question
Your network contains the segments shown in the following table.
You have servers that run Windows Server and are configured as shown in the following table.
You deploy a server named Server4 that runs Windows Server and has a static IP address of 172.16.1.1. You connect Server4 to Segment1.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point,
| Name | IPv4 address space | Gateway |
| --- | --- | --- |
| Segment1 | 172.16.1.0/24 | 172.16.1.1 |
| Segment2 | 172.16.2.0/24 | 172.16.2.1 |
| Name | IPv4 address | Connected to | Windows Defender Firewall configuration |
| --- | --- | --- | --- |
| Server1 | 172.16.1.10 | Segment1 | Allow ICMP traffic |
| Server2 | 172.16.2.2 | Segment1 | Allow ICMP traffic |
| Server3 | 172.16.2.20 | Segment2 | Allow ICMP traffic |
Explanation
Statement 1 (No): Server2 has the address 172.16.2.2, which belongs to Segment2's address space, but it is connected to Segment1. Server1 (172.16.1.10) sees 172.16.2.2 as a remote subnet and sends traffic for it to the gateway 172.16.1.1. The router forwards it to Segment2, where Server2 is not connected. Server2's replies to 172.16.1.10 would also have to go through its gateway 172.16.2.1, which it cannot reach from Segment1. Communication fails, so the ping by name fails too.
Statement 2 (No): With the address 172.16.2.2/24, Server2 treats Server3 (172.16.2.20) as being on its own link and sends an ARP request for it directly on Segment1. Server3 is on Segment2, a different broadcast domain, so the ARP request is never answered and the ping fails.
Statement 3 (Yes): Server4's static address 172.16.1.1 is already used by the Segment1 gateway. When the address is bound, Windows duplicate address detection finds the conflict, marks the static address as (Duplicate) and assigns an Automatic Private IP Addressing (APIPA) address. ipconfig /all then lists an Autoconfiguration IPv4 address from 169.254.0.0/16.
