Question 620
A port negotiates 100 Mb/s instead of its expected 1 Gb/s, without an intentional cap. Which detail should be checked?
- Bonding mode and slave attachment
- Ethernet autonegotiation and cabling quality
- VLAN ID and switch trunk tagging agreement
- Cable, transceiver or switch-port fault
Explanation
Correct Answer
B:Poor cable pairs or mismatched negotiation can limit link speed. Inspect both endpoints' capabilities and physical media.
Incorrect Answers
A:Active-backup bonding should retain connectivity when a functioning alternate link takes over; the requirement is diagnosing lower-than-expected Ethernet link rate, outside the effect of this choice.
C:Tagged frames must use matching VLAN IDs across the host, bridge and switch trunk; the evidence calls for diagnosing lower-than-expected Ethernet link rate, not merely this separate operation.
D:Administrative UP does not guarantee electrical or optical carrier; the task involves diagnosing lower-than-expected Ethernet link rate, whereas this addresses another subsystem.
Question 621
TCP establishes but HTTPS immediately fails with a certificate hostname error. Which layer has failed?
- TLS endpoint authentication
- Local TCP filtering or listen-path failure
- Application backend availability and proxy health
- Destination explicitly rejecting the connection
Explanation
Correct Answer
A:TCP reachability exists, but certificate validation rejects the server identity. Correct the certificate names or the requested host.
Incorrect Answers
B:Arriving SYNs without responses suggest host-side filtering or failure to service the target socket; the administrator instead needs isolating TLS identity failure from network transport; this option serves a different purpose.
C:HTTP 503 indicates that the request reached an HTTP-speaking server which cannot currently serve it; it answers a neighboring question rather than isolating TLS identity failure from network transport.
D:TCP RST often indicates a closed port or intentional rejection policy; that changes a different part of the system; the requested outcome is isolating TLS identity failure from network transport.
Question 622
A reverse lookup of 192.0.2.10 fails although forward A lookup works. Which DNS record type is missing or incorrect?
- systemd-resolved stub listener
- AAAA resolution versus listener address family
- DNS caching or zone propagation differences
- PTR record in the reverse zone
- Incomplete DNS resolution due to blocked TCP fallback
Explanation
Correct Answer
D:Reverse DNS resolves addresses through PTR records under in-addr.arpa or ip6.arpa. It is configured separately from forward A and AAAA records.
Incorrect Answers
A:On distributions using the stub resolver, 127.0.0.53 forwards local DNS requests to configured upstream servers; it will not provide fixing reverse DNS without altering forward mapping under these conditions.
B:A client may prefer an IPv6 address when a name has AAAA records; using it would leave fixing reverse DNS without altering forward mapping unresolved.
C:Recursive caches can retain records until TTL expiration, and different authoritative sources may disagree; the requirement is fixing reverse DNS without altering forward mapping, outside the effect of this choice.
E:DNS can use TCP for truncated or larger responses; the evidence calls for fixing reverse DNS without altering forward mapping, not merely this separate operation.
Question 623
A host reaches a peer only after clearing stale neighbor cache entries following a MAC replacement. Which cache caused the problem?
- Cable, transceiver or switch-port fault
- ARP or neighbor-discovery cache
- Ethernet autonegotiation and cabling quality
- Bonding mode and slave attachment
Explanation
Correct Answer
B:Neighbor tables map IP addresses to link-layer addresses. Stale entries can direct packets toward an old MAC until refreshed.
Incorrect Answers
A:Administrative UP does not guarantee electrical or optical carrier; the task involves diagnosing outdated IP-to-MAC neighbor mappings, whereas this addresses another subsystem.
C:Poor cable pairs or mismatched negotiation can limit link speed; that is not equivalent to diagnosing outdated IP-to-MAC neighbor mappings.
D:Active-backup bonding should retain connectivity when a functioning alternate link takes over; the administrator instead needs diagnosing outdated IP-to-MAC neighbor mappings; this option serves a different purpose.
Question 624
Two DNS resolvers give different A records for one hostname after a migration. Which likely factor deserves attention?
- DNS caching or zone propagation differences
- systemd-resolved stub listener
- Cached DNS answers still within TTL
- PTR record in the reverse zone
- AAAA resolution versus listener address family
- Incomplete DNS resolution due to blocked TCP fallback
Explanation
Correct Answer
A:Recursive caches can retain records until TTL expiration, and different authoritative sources may disagree. Compare answers against the authoritative zone.
Incorrect Answers
B:On distributions using the stub resolver, 127.0.0.53 forwards local DNS requests to configured upstream servers; this does not achieve explaining inconsistent resolver answers on the system described.
C:Resolvers can cache records for their time-to-live, delaying observation of changes; it will not provide explaining inconsistent resolver answers under these conditions.
D:Reverse DNS resolves addresses through PTR records under in-addr.arpa or ip6.arpa; using it would leave explaining inconsistent resolver answers unresolved.
E:A client may prefer an IPv6 address when a name has AAAA records; the requirement is explaining inconsistent resolver answers, outside the effect of this choice.
F:DNS can use TCP for truncated or larger responses; it does not deliver explaining inconsistent resolver answers, which is decisive in this scenario.
Question 625
A host's IP address is correct but its default gateway is outside the configured connected subnet without special routing. What is the likely failure?
- IPv6 default route and router advertisements
- Unreachable next-hop gateway
- Failed DHCP lease acquisition
- Service bind address
Explanation
Correct Answer
B:A gateway normally must be reachable through an on-link route or explicit next-hop configuration. Otherwise the host cannot resolve the next hop.
Incorrect Answers
A:Link-local scope functions without global routing; it does not deliver checking whether a default gateway is reachable, which is decisive in this scenario.
C:Link-local IPv4 addressing often indicates no usable DHCP lease; the task involves checking whether a default gateway is reachable, whereas this addresses another subsystem.
D:A listener on loopback cannot accept connections to the machine's external IP; its scope differs from checking whether a default gateway is reachable, so it cannot meet the stated requirement.
Question 626
An interface reports many CRC errors and a high retry rate after a cabling change. Which cause is plausible?
- Ethernet autonegotiation and cabling quality
- End-to-end effective MTU across the VLAN path
- ARP or neighbor-discovery cache
- Physical-layer corruption or faulty link components
Explanation
Correct Answer
D:Frame check sequence errors are consistent with corrupted link-layer traffic. Inspect optics, cables, negotiated parameters and switch counters.
Incorrect Answers
A:Poor cable pairs or mismatched negotiation can limit link speed; the administrator instead needs explaining frame errors following hardware changes; this option serves a different purpose.
B:Encapsulation overhead and lower-device limits determine usable payload size; it answers a neighboring question rather than explaining frame errors following hardware changes.
C:Neighbor tables map IP addresses to link-layer addresses; that changes a different part of the system; the requested outcome is explaining frame errors following hardware changes.
Question 627
A remote HTTP request negotiates TCP and TLS but returns 503 consistently. Where should investigation shift?
- Overlap of allowed SSH host-key algorithms
- Application backend availability and proxy health
- UDP-specific reachability and filtering test
- Destination explicitly rejecting the connection
Explanation
Correct Answer
B:HTTP 503 indicates that the request reached an HTTP-speaking server which cannot currently serve it. Check upstream pools and service logs.
Incorrect Answers
A:The client and server must negotiate a mutually supported acceptable host-key algorithm; using it would leave diagnosing an application-layer availability error unresolved.
C:ICMP success does not establish UDP port reachability; it does not deliver diagnosing an application-layer availability error, which is decisive in this scenario.
D:TCP RST often indicates a closed port or intentional rejection policy; the evidence calls for diagnosing an application-layer availability error, not merely this separate operation.
Question 628
TCP retransmission spikes on one path but not another while utilization is moderate. What should be investigated?
- Application backend availability and proxy health
- Overlap of allowed SSH host-key algorithms
- Host and upstream firewall source rules
- Packet loss and link errors on the affected path
Explanation
Correct Answer
D:Retransmissions often reflect loss, congestion or reordering rather than application parsing. Interface counters and captures help localize the problem.
Incorrect Answers
A:HTTP 503 indicates that the request reached an HTTP-speaking server which cannot currently serve it; its scope differs from correlating retransmissions with packet loss, so it cannot meet the stated requirement.
B:The client and server must negotiate a mutually supported acceptable host-key algorithm; that is not equivalent to correlating retransmissions with packet loss.
C:Source-based filtering can permit one network and silently drop other clients; the administrator instead needs correlating retransmissions with packet loss; this option serves a different purpose.
Question 629
A technician queries DNS over UDP but large responses are truncated and TCP fallback is blocked. Which symptom is expected?
- Cached DNS answers still within TTL
- AAAA resolution versus listener address family
- Incomplete DNS resolution due to blocked TCP fallback
- DNS caching or zone propagation differences
- NSS hosts source precedence
Explanation
Correct Answer
C:DNS can use TCP for truncated or larger responses. Firewall rules blocking TCP 53 may cause intermittent failures despite normal UDP queries.
Incorrect Answers
A:Resolvers can cache records for their time-to-live, delaying observation of changes; this does not achieve allowing required DNS transport fallback on the system described.
B:A client may prefer an IPv6 address when a name has AAAA records; it will not provide allowing required DNS transport fallback under these conditions.
D:Recursive caches can retain records until TTL expiration, and different authoritative sources may disagree; the requirement is allowing required DNS transport fallback, outside the effect of this choice.
E:/etc/nsswitch.conf can prefer DNS over local files or omit them; it does not deliver allowing required DNS transport fallback, which is decisive in this scenario.
Question 630
A static IP survives network interface reset but disappears after reboot. What configuration layer is likely incomplete?
- Incorrect connected subnet calculation
- IPv6 default route and router advertisements
- Failed DHCP lease acquisition
- Persistent network-manager profile
Explanation
Correct Answer
D:Transient ip address commands modify current kernel state but do not necessarily persist across boot. Save addressing in NetworkManager or Netplan as appropriate.
Incorrect Answers
A:A /25 prefix splits a /24 into two separate subnets; the evidence calls for persisting an IP address across reboots, not merely this separate operation.
B:Link-local scope functions without global routing; the task involves persisting an IP address across reboots, whereas this addresses another subsystem.
C:Link-local IPv4 addressing often indicates no usable DHCP lease; its scope differs from persisting an IP address across reboots, so it cannot meet the stated requirement.