Examkin

Question

Difficulty: HardWindows Client Networking Configuration

A systems administrator is configuring a multihomed Windows client workstation connected to both a general office subnet (192.168.1.0/24192.168.1.0/24) and a dedicated technician subnet (192.168.20.0/24192.168.20.0/24). The administrator must ensure that all traffic destined for a remote server network (10.250.0.0/1610.250.0.0/16) is persistently routed through the gateway at 192.168.20.50192.168.20.50, and that single-label hostname queries automatically append the internal corporate domain suffix. Which TWO of the following actions should the administrator perform on the Windows workstation to fulfill these requirements?

  1. Execute `route add 10.250.0.0 mask 255.255.0.0 192.168.20.50 -p` in an elevated Command Prompt.Answer
  2. Add the corporate domain name to the 'Append these DNS suffixes (in order)' list within the Advanced TCP/IP Settings window.Answer
  3. C
    Run `ipconfig /setdns 10.250.0.0` in an elevated Command Prompt to bind the target subnet routing mask.
  4. D
    Assign 192.168.20.50192.168.20.50 as the Default Gateway on both active network adapters in IPv4 properties.

Answer

To achieve persistent selective network routing and automatic domain suffix resolution, the administrator must add a persistent static route using `route add -p` and append the domain name under the Advanced TCP/IP DNS properties.
The combination of creating a persistent static route using `route add -p` and defining specific DNS search suffixes in the Advanced TCP/IP Settings properly isolates local subnet traffic routing while guaranteeing automatic FQDN resolution for internal hosts.

Step-by-Step Solution

1
Configure persistent static route for the target management network.
Running `route add 10.250.0.0 mask 255.255.0.0 192.168.20.50 -p` adds an entry to the IPv4 routing table that persists across system reboots, ensuring traffic for 10.250.0.0/1610.250.0.0/16 is directed via 192.168.20.50192.168.20.50.
Default gateways only handle non-local traffic without a specific route. Specific subnet routing requires explicit static routes.
2
Configure DNS suffix search list in Advanced IPv4 Properties.
Adding the corporate domain suffix to the DNS search order ensures single-label names (e.g., 'fileserver') resolve fully as FQDNs (e.g., 'fileserver.corp.domain').
Windows uses the DNS suffix search list to resolve short names across multi-domain enterprise environments.

Key Concept

Windows Client Routing Table and Advanced IPv4 DNS Settings
Rate this question

Topics

Windows Client Networking Configuration

More questions from this topic