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.
Question 631
Two hosts can ping each other, but the application fails only on UDP 5000. Which test should focus on the correct transport?
- Application backend availability and proxy health
- Host and upstream firewall source rules
- UDP-specific reachability and filtering test
- Packet loss and link errors on the affected path
Explanation
Correct Answer
C:ICMP success does not establish UDP port reachability. Capture traffic and inspect UDP listeners and firewall protocol selection.
Incorrect Answers
A:HTTP 503 indicates that the request reached an HTTP-speaking server which cannot currently serve it; it answers a neighboring question rather than distinguishing UDP filtering from ICMP reachability.
B:Source-based filtering can permit one network and silently drop other clients; that changes a different part of the system; the requested outcome is distinguishing UDP filtering from ICMP reachability.
D:Retransmissions often reflect loss, congestion or reordering rather than application parsing; it will not provide distinguishing UDP filtering from ICMP reachability under these conditions.
Question 632
An SSH client reports no matching host key type after a server hardening change. What should be reviewed?
- Host and upstream firewall source rules
- TLS endpoint authentication
- Overlap of allowed SSH host-key algorithms
- No service bound to the requested port
Explanation
Correct Answer
C:The client and server must negotiate a mutually supported acceptable host-key algorithm. Enabling obsolete algorithms indiscriminately is unsafe.
Incorrect Answers
A:Source-based filtering can permit one network and silently drop other clients; the requirement is resolving SSH algorithm negotiation failure, outside the effect of this choice.
B:TCP reachability exists, but certificate validation rejects the server identity; it does not deliver resolving SSH algorithm negotiation failure, which is decisive in this scenario.
D:A refused connection commonly indicates the destination stack rejected the attempt because no listener exists; the task involves resolving SSH algorithm negotiation failure, whereas this addresses another subsystem.
Question 633
An IPv6 host can reach local link-local peers but no global IPv6 destinations. Which configuration needs inspection?
- Service bind address
- Persistent network-manager profile
- IPv6 default route and router advertisements
- IPv4 default gateway route
Explanation
Correct Answer
C:Link-local scope functions without global routing. Missing RA-derived or static default routes can prevent off-link IPv6 traffic.
Incorrect Answers
A:A listener on loopback cannot accept connections to the machine's external IP; that is not equivalent to finding missing IPv6 off-link routing.
B:Transient ip address commands modify current kernel state but do not necessarily persist across boot; the administrator instead needs finding missing IPv6 off-link routing; this option serves a different purpose.
D:Local subnet traffic uses connected routes, while off-subnet destinations need a gateway or other suitable route; that changes a different part of the system; the requested outcome is finding missing IPv6 off-link routing.
Question 634
Both interfaces on a bonded connection lose carrier when one cable is removed, despite active-backup expectations. Which configuration area is suspect?
- End-to-end effective MTU across the VLAN path
- Bonding mode and slave attachment
- Ethernet autonegotiation and cabling quality
- Physical-layer corruption or faulty link components
Explanation
Correct Answer
B:Active-backup bonding should retain connectivity when a functioning alternate link takes over. Verify bond members and switch connections.
Incorrect Answers
A:Encapsulation overhead and lower-device limits determine usable payload size; it will not provide diagnosing broken link-failover behavior under these conditions.
C:Poor cable pairs or mismatched negotiation can limit link speed; the requirement is diagnosing broken link-failover behavior, outside the effect of this choice.
D:Frame check sequence errors are consistent with corrupted link-layer traffic; it does not deliver diagnosing broken link-failover behavior, which is decisive in this scenario.
Question 635
ethtool shows no link detected even though the interface is administratively UP. What is the most direct physical suspicion?
- Cable, transceiver or switch-port fault
- VLAN ID and switch trunk tagging agreement
- End-to-end effective MTU across the VLAN path
- Physical-layer corruption or faulty link components
- ARP or neighbor-discovery cache
Explanation
Correct Answer
A:Administrative UP does not guarantee electrical or optical carrier. Check cabling and switch state before DNS configuration.
Incorrect Answers
B:Tagged frames must use matching VLAN IDs across the host, bridge and switch trunk; its scope differs from investigating loss of physical carrier, so it cannot meet the stated requirement.
C:Encapsulation overhead and lower-device limits determine usable payload size; that is not equivalent to investigating loss of physical carrier.
D:Frame check sequence errors are consistent with corrupted link-layer traffic; the administrator instead needs investigating loss of physical carrier; this option serves a different purpose.
E:Neighbor tables map IP addresses to link-layer addresses; it answers a neighboring question rather than investigating loss of physical carrier.
Question 636
A laptop's default route is correct but no packets leave after interface renaming from eth0 to enp3s0. Which configuration should be reviewed?
- Bonding mode and slave attachment
- Cable, transceiver or switch-port fault
- Physical-layer corruption or faulty link components
- Stale interface-name references
Explanation
Correct Answer
D:Network profiles and services may still reference an interface name that no longer exists. Update them to the current predictable name.
Incorrect Answers
A:Active-backup bonding should retain connectivity when a functioning alternate link takes over; that changes a different part of the system; the requested outcome is correcting configuration after network interface rename.
B:Administrative UP does not guarantee electrical or optical carrier; this does not achieve correcting configuration after network interface rename on the system described.
C:Frame check sequence errors are consistent with corrupted link-layer traffic; it will not provide correcting configuration after network interface rename under these conditions.
Question 637
A server has two default routes of equal priority and replies leave through a different interface than requests. Which mechanism should be reviewed?
- Failed DHCP lease acquisition
- IPv6 default route and router advertisements
- Unreachable next-hop gateway
- Routing metrics and policy routing
- Service bind address
- Incorrect connected subnet calculation
Explanation
Correct Answer
D:Route selection and source rules determine egress paths, which may become asymmetric. Adjusting metrics or source-specific routes can restore symmetry.
Incorrect Answers
A:Link-local IPv4 addressing often indicates no usable DHCP lease; it does not deliver diagnosing asymmetric multi-homed routing, which is decisive in this scenario.
B:Link-local scope functions without global routing; the evidence calls for diagnosing asymmetric multi-homed routing, not merely this separate operation.
C:A gateway normally must be reachable through an on-link route or explicit next-hop configuration; the task involves diagnosing asymmetric multi-homed routing, whereas this addresses another subsystem.
E:A listener on loopback cannot accept connections to the machine's external IP; that is not equivalent to diagnosing asymmetric multi-homed routing.
F:A /25 prefix splits a /24 into two separate subnets; the administrator instead needs diagnosing asymmetric multi-homed routing; this option serves a different purpose.
Question 638
A local resolver times out when using 127.0.0.53, but upstream DNS responds when queried directly. Which local component should be checked?
- AAAA resolution versus listener address family
- PTR record in the reverse zone
- systemd-resolved stub listener
- Incomplete DNS resolution due to blocked TCP fallback
Explanation
Correct Answer
C:On distributions using the stub resolver, 127.0.0.53 forwards local DNS requests to configured upstream servers. A stopped or misconfigured local resolver breaks ordinary lookup.
Incorrect Answers
A:A client may prefer an IPv6 address when a name has AAAA records; the administrator instead needs repairing the local DNS stub resolution service; this option serves a different purpose.
B:Reverse DNS resolves addresses through PTR records under in-addr.arpa or ip6.arpa; it answers a neighboring question rather than repairing the local DNS stub resolution service.
D:DNS can use TCP for truncated or larger responses; this does not achieve repairing the local DNS stub resolution service on the system described.
Question 639
An interface's configured subnet mask is /25 but the peer is on the other half of a /24. Why might direct connectivity fail?
- Duplicate IP address assignment
- Incorrect connected subnet calculation
- IPv4 default gateway route
- Routing metrics and policy routing
Explanation
Correct Answer
B:A /25 prefix splits a /24 into two separate subnets. Hosts disagreeing about on-link neighbors can attempt the wrong ARP or gateway path.
Incorrect Answers
A:Two devices claiming one address can cause unstable ARP resolution and traffic delivery; using it would leave diagnosing mismatched address prefixes unresolved.
C:Local subnet traffic uses connected routes, while off-subnet destinations need a gateway or other suitable route; it does not deliver diagnosing mismatched address prefixes, which is decisive in this scenario.
D:Route selection and source rules determine egress paths, which may become asymmetric; the evidence calls for diagnosing mismatched address prefixes, not merely this separate operation.
Question 640
An interface receives 169.254.x.x but should get a DHCP address on a private subnet. What is the likely issue?
- Persistent network-manager profile
- Duplicate IP address assignment
- Routing metrics and policy routing
- Failed DHCP lease acquisition
Explanation
Correct Answer
D:Link-local IPv4 addressing often indicates no usable DHCP lease. Verify broadcast reachability, client logs and server availability.
Incorrect Answers
A:Transient ip address commands modify current kernel state but do not necessarily persist across boot; its scope differs from diagnosing an unexpected IPv4 link-local address, so it cannot meet the stated requirement.
B:Two devices claiming one address can cause unstable ARP resolution and traffic delivery; that is not equivalent to diagnosing an unexpected IPv4 link-local address.
C:Route selection and source rules determine egress paths, which may become asymmetric; the administrator instead needs diagnosing an unexpected IPv4 link-local address; this option serves a different purpose.