A newly installed desktop is unable to connect to networked resources. The systems administrator executes various commands and reviews the following output snippets: Which of the following should…

arp -s 20:ad:1f:ab:10:0f 192.168.1.10 adds a static ARP entry, which is irrelevant when the network interface itself is not in an UP state.

route add -net 192.168.1.0 netmask 255.255.255.0 adds a static route, but routing is non-functional when the underlying interface is down.

dig -x @127.0.0.1 192.168.1.10 performs a reverse DNS lookup against localhost and is a diagnostic tool that does not address a downed network interface.

ip link set wlo1 up activates the wireless interface wlo1, which based on the reviewed output is currently in a DOWN state and therefore cannot pass any network traffic. Without the physical interface being active, no routing, ARP, or DNS configuration will restore connectivity. Bringing the interface up is the foundational prerequisite before any higher-layer troubleshooting steps are applicable.

killall -HUP NetworkManager sends a reload signal to NetworkManager, which is a broader and less targeted action than directly activating the specific downed interface.