Examkin

Question

Difficulty: HardIP Addressing and Network Configuration

A desktop workstation in an office environment is configured with a static IPv4 address of 10.0.12.45 and a subnet mask of 255.255.255.0. The user reports that while they can successfully ping and share files with adjacent devices on the local 10.0.12.0/24 subnet, they cannot access corporate web services on remote subnets or resolve hostnames to IP addresses. An inspection of the network configuration reveals that the Default Gateway field is empty and the Primary DNS Server is set to an invalid loopback address. Which TWO of the following actions should the technician take to resolve these connectivity issues?

  1. Configure the local interface with the correct router address on the subnet to act as the default gateway.Answer
  2. Update the primary DNS server entry to point to a valid, reachable domain name server.Answer
  3. C
    Change the workstation's IP address assignment to an APIPA address in the 169.254.0.0/16 range to automatically discover external gateways.
  4. D
    Reconfigure the primary DNS server settings on the host to lease dynamic IPv4 network parameters.

Answer

To restore complete network communication, the technician must set a valid default gateway IP address on the workstation interface so traffic can be routed to external subnets, and configure a reachable DNS server IP address to allow hostname resolution.
Configuring the correct default gateway address enables the host network interface to pass packets intended for remote subnets to the local router. Setting a valid primary DNS server address allows the host to send domain name resolution requests, enabling access to web services by hostname.

Step-by-Step Solution

1
Analyze local vs. remote communication symptoms.
Local communication works because the host has a valid IPv4 address and subnet mask on 10.0.12.0/24. Remote communication fails due to a missing default gateway entry.
Without a default gateway specified, traffic targeted outside the local IP subnet cannot be routed.
2
Analyze hostname resolution failure symptoms.
Hostname queries fail because the configured DNS server is set to an invalid loopback address.
Host computers must point to an operational DNS server capable of resolving names to IP addresses.
3
Identify the required remediation actions.
Assigning a valid default gateway address on the local subnet restores routing, and pointing to a valid corporate DNS server restores name resolution.
Both settings are necessary to address the user's specific reported symptoms of remote subnet access failure and hostname lookup failure.

Key Concept

IP Addressing Parameter Responsibilities (Default Gateway & DNS)
Rate this question

Topics

IP Addressing and Network Configuration

More questions from this topic