Free Networking Foundations practice questions

A missing default gateway is a Network-layer problem because the Network layer handles logical IP addressing and routing between networks. Without a configured gateway, the device can communicate with other systems on its own subnet but does not know where to send traffic destined for remote networks, which prevents internet access. Adding the correct default gateway restores connectivity. The Physical layer is incorrect because the strong Wi-Fi signal confirms that radio transmission and the physical connection are working. The Data Link layer is incorrect because the laptop successfully associated with the access point and can communicate locally using frames and MAC addresses. The Transport layer is incorrect because Transport-layer issues involve ports, TCP/UDP sessions, and service availability rather than routing between networks. Since the device already has a valid IP address and can reach local devices but has no gateway, the failure is specifically in Layer 3 routing configuration.

A successful ping confirms that basic IP communication (the Network layer) is working, since packets reach the server and return. When IP connectivity works but one specific service fails, the problem is usually at the Transport layer, where port numbers identify services and firewalls may block them. A recently changed firewall rule blocking the application's required TCP port would allow ping and web traffic to succeed while preventing the accounting application from connecting. A missing default gateway is incorrect because the technician can already ping the server's IP, proving routing is functional. A damaged Ethernet cable is incorrect because a Physical-layer failure would break all connectivity, including web browsing and email, and would likely prevent a successful ping. A disabled network adapter is incorrect because the adapter must be enabled and communicating for the ping, websites, and email to function. The key clue is that everything works except one service, which points to ports, firewall rules, or service availability at the Transport layer.

When a site loads by IP address but not by hostname, the problem is DNS name resolution, an Application-layer function that translates human-readable names into IP addresses. Because the page opens using the raw IP, the physical connection, local network, IP routing, and web service are all confirmed working; only the name-to-address translation is failing. An incorrect subnet mask is incorrect because a subnetting error would break local and remote IP connectivity, yet the site loads fine by IP. A blocked TCP port 443 is incorrect because if the HTTPS port were blocked, the site would fail to load by both hostname and IP address. An expired website certificate is incorrect because a certificate problem would display a certificate warning rather than a name-resolution failure, and it would appear regardless of whether the user typed the hostname or the IP. The distinguishing evidence is that connectivity succeeds by IP but fails by name, which isolates the fault to DNS at the Application layer.

This is primarily a Data Link-layer problem because VLAN assignment and switch-port configuration operate at Layer 2, where frames, MAC addresses, and local delivery are managed. Placing the port in the wrong VLAN isolates the device onto a different logical network segment, so even with a working cable and link light, it cannot reach the intended employee network. The Physical layer is incorrect because the active link light and functioning cable confirm the physical connection and switch-port hardware are operational. The Network layer answer citing an unreachable gateway is incorrect because the actual root cause is the VLAN assignment; the device is on the wrong segment entirely rather than simply lacking gateway reachability. The Transport layer is incorrect because no specific service or port is involved; the device cannot access the network segment at all, which is a local delivery issue rather than a port or service problem. Recognizing that the physical connection works while local segmentation fails points the technician toward switch and VLAN configuration at Layer 2.

When a packet moves through a router, the router removes the existing frame, examines the destination IP address, and places the packet inside a new frame for the next network segment. Because a new frame is built for each hop, the source and destination MAC addresses change as the packet crosses each local network. The source and destination IP addresses normally remain associated with the original sending and receiving devices, so they do not change on a typical routed path. The destination IP address only is incorrect because IP addressing generally stays the same end to end (barring technologies such as Network Address Translation), and the router uses that destination IP to decide where to forward the packet. The source port and destination port are transport-layer values used to identify applications and services; they are not rewritten by standard routing between segments. Understanding that MAC addresses are local and IP addresses are end-to-end helps a technician trace where communication succeeds or fails as data travels across multiple networks.

Throughput is the actual amount of data successfully transferred through a network during a specific period, and it is usually lower than the maximum available bandwidth because of overhead, congestion, and equipment limitations. In this case the 1 Gbps rating is the bandwidth (the maximum theoretical capacity), while the measured 800 Mbps transfer rate is the throughput. Bandwidth is incorrect because it describes the connection's maximum capacity, not the real-world data rate the user achieves. Latency is incorrect because it measures the time delay for data to travel between two points, expressed in milliseconds, not a data transfer rate. Jitter is incorrect because it measures the variation in latency between packets and is most relevant to real-time communication rather than file transfers. Remembering that bandwidth describes capacity while throughput describes actual performance is essential when diagnosing whether a slow transfer is a hardware limitation, congestion, or a normal amount of protocol overhead.

Real-time communication such as voice and video is highly sensitive to jitter and packet loss. A weak, unstable wireless signal causes packets to arrive at inconsistent intervals (jitter) and some packets to fail to arrive at all (packet loss), producing broken audio and frozen video even when plenty of bandwidth is available. Insufficient bandwidth and high throughput is incorrect because the connection has 300 Mbps and the call uses only a small portion of it, so capacity is not the limitation. High latency and low bandwidth is incorrect for the same reason; bandwidth is not the problem, and while latency can affect calls, the described unstable signal points specifically to variation and loss rather than a consistent delay. Low throughput and low latency is incorrect because low latency would actually be beneficial, and low throughput alone would not create the choppy, out-of-order behavior described. The key lesson is that a network can have ample bandwidth yet still perform poorly for real-time applications when jitter and packet loss are present, so moving closer to the access point or adding another access point would likely resolve the issue.

The ping utility sends a test message to a destination and measures how long it takes to receive a response, which represents the round-trip time. A low ping time generally indicates low latency, while a high or inconsistent ping time may indicate congestion, a distant server, or a poor connection. ipconfig is incorrect because it displays and manages the local device's IP configuration, such as its address, subnet mask, and default gateway, rather than measuring reachability or delay. nslookup is incorrect because it queries DNS to resolve hostnames to IP addresses and troubleshoot name resolution, not to measure response time. netstat is incorrect because it displays active connections, listening ports, and network statistics on the local host rather than testing round-trip time to a remote destination. It is worth remembering that ping measures latency and reachability but does not directly measure available bandwidth, since a connection can have low latency yet limited bandwidth, or high bandwidth yet high latency.

Encapsulation is the process of adding addressing and control information to data as it moves through the networking process. An application creates data, transport information is added, source and destination IP addresses are added to create a packet, and source and destination MAC addresses are added to create a frame before the frame is transmitted as signals. De-encapsulation is incorrect because it is the reverse process performed by the receiving device, which removes the frame, processes the packet, and passes the original data up to the correct application. Fragmentation is incorrect because it refers specifically to dividing data into smaller units for transmission, not the layered addition of addressing and control information. Retransmission is incorrect because it describes resending packets that were lost or corrupted during transmission, which helps maintain reliability but can reduce throughput and increase delay. Understanding encapsulation and de-encapsulation helps a technician visualize how a single piece of data is wrapped with the information needed to travel across both local segments and remote networks.

When a destination is on a different network, the sending device forwards its frames to the default gateway, which is usually a router that determines where to send the packet next. If a workstation can communicate locally but cannot reach any remote or internet resources, a missing or incorrect default gateway is the most likely cause, so it should be verified first. The subnet mask on the local switch is incorrect because switches forward frames based on MAC addresses and do not require an IP subnet mask to move local traffic; the relevant subnet mask would be on the workstation, not the switch. The MAC address table on the switch is incorrect because that table is used to forward frames within the local network, and local communication is already working correctly in this scenario. The DNS suffix on the workstation is incorrect because DNS affects name resolution rather than raw connectivity; even with DNS issues, a device with a valid gateway could still reach remote hosts by IP address. Because local traffic succeeds and only inter-network traffic fails, the gateway that hands off packets to other networks is the logical starting point for troubleshooting.