Examkin

Soru

Zorluk: ZorIP Addressing and Network Configuration

A network technician is diagnosing several network connectivity issues across different client workstations. Match each diagnostic symptom or command output on the left with its primary underlying network configuration cause on the right.

  • A workstation receives an IPv4 address of 169.254.43.88 with a subnet mask of 255.255.0.0 upon startup, resulting in loss of connectivity to corporate servers.Automatic Private IP Addressing (APIPA) self-assignment caused by an unreachable or unresponsive DHCP server.
  • A host can successfully ping other devices on its local subnet (10.10.4.0/24), but all traffic destined for remote subnets or the internet fails immediately.Missing or improperly configured Default Gateway IP address on the host network interface.
  • A user can reach external resources using direct IPv4 addresses (e.g., pinging 1.1.1.1 works), but browser requests using domain names fail to load.Incorrect, missing, or unreachable Domain Name System (DNS) server address setting.
  • A dual-stack interface automatically generates an address starting with fe80::/10 and can only communicate with devices on the local link without manual setup.Standard IPv6 Link-Local auto-configuration using SLAAC or EUI-64 interface identifier generation.

Cevap

1. 169.254.x.x assignment correlates with APIPA self-assignment due to DHCP server unreachability.
2. Local-only subnet communication failures correlate with a missing or misconfigured default gateway.
3. IP ping success with FQDN failure correlates with a DNS server misconfiguration.
4. fe80::/10 address generation correlates with IPv6 Link-Local auto-configuration.
Each symptom precisely maps to a standard TCP/IP configuration component: APIPA (169.254.0.0/16) results from failed DHCP acquisition; Default Gateway failure restricts traffic exclusively to the local broadcast domain; DNS failures prevent resolving domain names despite working IP routing; and fe80::/10 represents non-routable IPv6 link-local auto-addressing.

Adım Adım Çözüm

1
Analyze the 169.254.43.88 IP address symptom.
Identify 169.254.0.0/16 as the APIPA address block.
When a DHCP client fails to obtain a lease, operating systems auto-assign an APIPA address.
2
Analyze local vs. remote connectivity symptoms.
Determine that local ARP and switching work, but routing fails.
Traffic bound for foreign subnets must be forwarded to the default gateway; missing this entry breaks cross-subnet communication.
3
Analyze direct IP success versus domain name failure.
Isolate the issue to name resolution.
DNS translates human-readable hostnames into IP addresses; if IP connectivity works, layer 3 routing is intact while name resolution is faulty.
4
Analyze the fe80:: IPv6 prefix.
Identify the standard IPv6 Link-Local scope.
IPv6 interfaces automatically generate link-local addresses within fe80::/10 for immediate local segment operation.

Anahtar Kavram

Network configuration parameter diagnostics including APIPA, Default Gateway routing, DNS resolution, and IPv6 Link-Local addressing.
Bu soruyu puanla

Konular

IP Addressing and Network Configuration

Bu konudan daha fazla soru