Mobile Devices practice questions

The file server is powered off.

Why wrong: If the file server were powered off, no device on the network would be able to access its shares. The problem states that other devices *can* access the shares, which directly contradicts the idea of the server being offline. Furthermore, the laptop's ability to access the internet indicates that its basic network connectivity is functional, pointing away from a server-side issue affecting only one client.

The Wi-Fi router is overloaded.

Why wrong: An overloaded Wi-Fi router would typically manifest as widespread network performance issues, affecting *all* connected devices, not just a single laptop. Since other devices are working fine and the laptop itself can access the internet, the router is clearly capable of handling traffic and performing its routing functions. This scenario points to a client-specific configuration problem rather than a general network infrastructure bottleneck.

The laptop's firewall is blocking all traffic.

Why wrong: If the laptop's firewall were blocking all traffic, it would be unable to connect to *any* network resources, including the internet. The fact that the laptop can successfully access the internet directly contradicts the statement that its firewall is blocking all traffic. While a firewall *could* be configured to selectively block local network access while allowing internet access, the option specifically states "all traffic," making it incorrect.

The switch is a hub, not a switch.

Why wrong: A hub operates at Layer 1 of the OSI model, simply repeating all incoming electrical signals to every other port. While this creates a single collision domain and significantly reduces network performance due to frequent collisions, all devices connected to a hub remain within the same broadcast domain. Consequently, devices would still be able to send and receive broadcast frames, such as ARP requests, allowing them to discover and communicate with each other at Layer 2, even if internet access is slow.

The router is blocking multicast traffic.

Why wrong: Routers primarily operate at Layer 3 and are designed to segment networks, preventing broadcast and multicast traffic from traversing between different subnets by default. However, local network discovery protocols, like ARP or NetBIOS over TCP/IP, rely on broadcasts or link-local multicasts that occur *within* the same Layer 2 segment (e.g., a single switch or VLAN). Therefore, if the desktop computer and other local devices are on the same subnet and switch, the router's multicast blocking configuration would not impact their ability to discover each other locally.

The Ethernet cable is a crossover cable.

Why wrong: Historically, a crossover Ethernet cable was required to connect two similar devices directly (e.g., PC to PC, switch to switch) by swapping the transmit and receive wire pairs. However, virtually all modern network interface cards (NICs) and network switches are equipped with Auto-MDIX (Automatic Medium-Dependent Interface Crossover) technology. This feature automatically detects the cable type and adjusts the port's wiring configuration as needed, rendering crossover cables largely obsolete. If Auto-MDIX were not present or failed, a crossover cable would typically result in a complete link failure, preventing any network communication whatsoever, rather than just a loss of local visibility.

Port 22 and 23

Why wrong: Port 22 is exclusively reserved for Secure Shell (SSH), which provides a secure, encrypted channel for remote command-line access, file transfers, and tunneling services. Conversely, Port 23 is used by Telnet, an older, unencrypted protocol for remote terminal access. Neither of these protocols is designed for the collection of network device statistics or sending alerts, which are the primary functions of network monitoring tools utilizing SNMP.

Port 80 and 443

Why wrong: Port 80 is the standard port for Hypertext Transfer Protocol (HTTP), facilitating unencrypted communication for web browsing and accessing web-based services. Port 443 is used by HTTPS (HTTP Secure), which encrypts HTTP traffic using SSL/TLS for secure web communication. While network monitoring tools might have web interfaces accessible via these ports, HTTP/HTTPS are not the underlying protocols for gathering device metrics or receiving traps from network devices via SNMP.

Port 67 and 68

Why wrong: Port 67 is designated for the Dynamic Host Configuration Protocol (DHCP) server, which listens for incoming requests from clients seeking IP addresses and other network configuration parameters. Port 68 is used by DHCP clients to send their initial requests to the server and receive configuration offers. These ports are fundamental for IP address management within a network and have no functional role in the process of network monitoring or the operation of SNMP.

Use a crossover cable to connect the router directly to the WAP.

Why wrong: Using a crossover cable for a direct router-to-WAP connection would consume the router's single LAN port, leaving no direct connection point for the rest of the office network, which requires a switch. While modern devices often support auto-MDI/MDIX, eliminating the specific need for a crossover cable, the fundamental problem remains the router's limited port capacity. This setup fails to provide connectivity for additional devices beyond the WAP, making it an impractical solution for a small office network needing multiple connections.

Use a hub between the router and the switch.

Why wrong: Using a hub would create a single collision domain and half-duplex connections, failing the requirement to connect both the switch and WAP to the router’s single LAN port without an uplink port, as a hub cannot isolate traffic between devices. It is tempting because a hub provides additional ports to physically connect multiple devices, and it would be the correct choice in a scenario where all connected devices must share the same broadcast and collision domain, such as for legacy network traffic monitoring.

Configure the switch as a router to connect to the WAP.

Why wrong: A typical unmanaged network switch operates at Layer 2 of the OSI model, forwarding data frames based on MAC addresses, and lacks the necessary Layer 3 routing capabilities. Configuring such a switch to function as a router, which handles IP address-based packet forwarding and network address translation (NAT), is not possible. Even managed switches with some Layer 3 features are primarily designed for switching and would not typically replace a dedicated router for internet gateway functions in this context.

The DNS server is unreachable

Why wrong: An unreachable DNS server would prevent name resolution, meaning the laptop could not translate domain names to IP addresses for web browsing or accessing network resources by name. However, the device would still successfully obtain an IP address from a functioning DHCP server. The presence of a 169.254.x.x APIPA address indicates a failure in the fundamental IP address acquisition process itself, which occurs before any DNS resolution attempts.

The default gateway is misconfigured

Why wrong: A misconfigured default gateway would impact a device's ability to communicate with hosts outside its local subnet, preventing access to the internet or other networks. However, it would not prevent the device from obtaining a valid IP address, subnet mask, and DNS server information from a DHCP server. The client would still receive a proper IP, only failing when attempting to route traffic beyond its immediate network segment.

The network cable is faulty

Why wrong: While a faulty network cable can certainly prevent network connectivity, the assignment of an APIPA address implies that a physical link has been established and the network adapter is active. If the cable were completely faulty, disconnected, or the network interface card (NIC) was disabled, the operating system would typically report no link status, and the device would not even attempt DHCP or subsequently assign an APIPA address.

The iPhone's DNS settings are misconfigured.

Why wrong: If the iPhone's DNS settings were misconfigured, the device would likely connect to the Wi-Fi network but fail to resolve domain names for *any* internet resource, not just after connecting to a public hotspot. While the captive portal page itself might load via IP redirection, subsequent attempts to browse the web would result in "server not found" errors. This issue typically affects all internet access uniformly, rather than being specific to the initial public Wi-Fi authentication phase.

The iPhone's Wi-Fi antenna is faulty.

Why wrong: A faulty Wi-Fi antenna on the iPhone would primarily manifest as an inability to detect available networks, extremely weak signal strength even when in close proximity to an access point, or persistent connection drops. Since the iPhone successfully connects to the public Wi-Fi hotspot, it indicates that the device's antenna and radio components are functioning adequately to establish a physical and data link layer connection. Therefore, a faulty antenna is inconsistent with the described scenario.

The public Wi-Fi network is using an incompatible security protocol.

Why wrong: If the public Wi-Fi network were employing a security protocol incompatible with the iPhone's capabilities, the device would be unable to establish a connection to the access point at all. The iPhone would either fail to authenticate, display an error message during the connection attempt, or simply be unable to join the network. The fact that the iPhone *connects* to the hotspot rules out an incompatible security protocol as the root cause of the lack of internet access.

Enable Bluetooth on the printer and pair it with each phone

Why wrong: Bluetooth printing is typically designed for direct, short-range, one-to-one connections, making it impractical for multiple users in a shared office setting due to the constant need for re-pairing and its limited operational range (typically 10-30 meters). Furthermore, many multifunction printers, especially those without Wi-Fi Direct, do not natively support Bluetooth for printing, requiring a separate adapter or specific model features not commonly found in standard office printers.

Use a USB cable to connect each phone to the printer

Why wrong: While some Android devices support USB On-The-Go (OTG) for connecting peripherals, direct USB printing from a smartphone to a multifunction printer is generally not supported without specific drivers or apps, which are often unavailable or cumbersome to install. This method is highly impractical for multiple users as it would require physically connecting and disconnecting each phone individually, creating significant workflow disruptions and cable management issues in a shared environment.

Install Google Cloud Print on the printer

Why wrong: Google Cloud Print was a service that allowed printing from any web-connected device to a registered printer, but it was officially deprecated by Google on December 31, 2020. Consequently, attempting to install or rely on Google Cloud Print for new printer setups is futile as the service is no longer operational or supported, rendering it an invalid and non-functional solution for modern printing needs.

Internal virtual switch

Why wrong: An internal virtual switch facilitates communication exclusively between virtual machines (VMs) and the host operating system. While VMs can communicate with each other and the host, this configuration intentionally prevents any direct access to the physical network or external internet. This isolation makes it unsuitable for a test environment that requires VMs to interact with external network resources or the internet.

Private virtual switch

Why wrong: A private virtual switch creates a completely isolated network segment where virtual machines (VMs) can communicate only with each other. This configuration strictly prevents any communication between the VMs and the host operating system, as well as any access to the physical network or the internet. Such extreme isolation is inappropriate for a test environment that likely needs to simulate real-world network interactions, including external connectivity.

NAT virtual switch

Why wrong: A NAT (Network Address Translation) virtual switch allows virtual machines (VMs) to access external networks by sharing the host's IP address. VMs are placed on a private internal network, and the host performs NAT to translate their private IP addresses for outbound traffic. While VMs can initiate connections to the internet, direct inbound connections from the external network to the VMs are generally blocked or require complex port forwarding, which limits the flexibility needed for a comprehensive test environment.

The earbuds have a low battery.

Why wrong: A low battery in the earbuds typically manifests as reduced range, intermittent audio dropouts, or complete disconnections due to insufficient power for stable signal transmission. However, if the earbuds function perfectly with a different smartphone, it indicates their battery is adequately charged and capable of maintaining a connection. Therefore, the problem is not inherent to the earbuds' power level but rather specific to the current smartphone or its environment.

The smartphone's Bluetooth driver is outdated.

Why wrong: An outdated Bluetooth driver on the smartphone would likely cause consistent issues across all environments, such as failure to pair, corrupted audio, or general instability, rather than problems localized specifically to a conference room. Driver issues usually result in persistent malfunctions or complete non-functionality, not intermittent disconnections tied to a particular physical location. The environmental specificity points away from a fundamental software problem.

The earbuds are not compatible with the smartphone's Bluetooth version.

Why wrong: Bluetooth technology is designed with strong backward compatibility, meaning newer devices can typically connect and communicate with older ones, albeit potentially without the latest features or speeds. If the earbuds and smartphone had a fundamental Bluetooth version incompatibility, they would most likely fail to pair or establish any connection whatsoever. Intermittent disconnections after a successful initial connection indicate an external, dynamic factor rather than a static compatibility barrier.

NFC

Why wrong: NFC operates over extremely short distances (typically 4 cm or less) and is designed for quick, secure, peer-to-peer data exchange or device pairing. Its low data transfer rate and inherent range limitations make it impractical for continuously streaming print job data from a mobile POS system to a printer. While useful for initial connection setup, it lacks the sustained bandwidth and range required for reliable printing.

Infrared

Why wrong: Infrared (IR) communication requires a direct, unobstructed line-of-sight between the transmitting and receiving devices, making it highly impractical for a dynamic retail environment. Furthermore, IR technology offers very low data transfer rates compared to modern wireless standards and is highly susceptible to interference from ambient light sources. It is an outdated technology rarely found in contemporary POS or general-purpose printers due to these significant limitations.

Wi-Fi Direct

Why wrong: Wi-Fi Direct creates a peer-to-peer network between devices, but it requires manual pairing and connection setup, introducing latency and potential interference in a crowded retail environment where the tablet must maintain a separate internet connection for transaction processing. This option is tempting because Wi-Fi Direct is often used for high-speed file transfers or media streaming between devices without a router, making it a correct choice for bulk data synchronisation between two tablets.

Enable airplane mode and then turn on Wi-Fi.

Why wrong: Enabling airplane mode disconnects the cellular radio, preventing any mobile-network roaming charges, but the user still needs mobile data when away from Wi-Fi. This fails the scenario because the user requires data connectivity outside Wi-Fi zones, and airplane mode blocks all cellular data. It is tempting because it is the correct method to eliminate roaming charges entirely when the user can rely solely on Wi-Fi, such as in a hotel or office with consistent coverage.

Enable data roaming.

Why wrong: Enabling data roaming explicitly permits the smartphone to connect to cellular networks operated by partner carriers in foreign regions, which is precisely where high roaming charges are incurred. This setting is designed to provide cellular data connectivity when outside the home network, but it comes with significant per-megabyte costs that the user is trying to avoid. Therefore, activating this feature would directly contradict the objective of preventing unexpected mobile expenses.

Set the device to 2G only.

Why wrong: Setting the device to 2G only merely restricts the cellular radio to the slowest available generation of mobile network technology, such as GPRS or EDGE. While this might reduce the *amount* of data consumed due to slower speeds, it does not disable cellular data connectivity altogether. Consequently, the device would still actively use the cellular network for data, making it susceptible to incurring roaming charges, albeit potentially at a slower rate, which fails to meet the user's primary goal of preventing such fees.

The corporate network is blocking the smartphone's MAC address.

Why wrong: MAC address filtering operates at Layer 2 (Data Link Layer) of the OSI model. If the corporate network were blocking the smartphone's MAC address, the device would be completely unable to associate with the access point or join the Wi-Fi network in the first place. The user would experience an inability to connect to the Wi-Fi network at all, rather than successfully connecting but lacking internet access.

The smartphone's Wi-Fi adapter is faulty.

Why wrong: A malfunctioning Wi-Fi adapter typically manifests as an inability to detect wireless networks, frequent disconnections, extremely slow speeds, or complete failure to connect to any network. Since the smartphone successfully connects to the corporate Wi-Fi, its adapter is likely functional enough to establish a Layer 2 connection. A faulty adapter would prevent the initial connection or cause instability, not a stable connection that simply lacks internet access.

The corporate proxy server is down.

Why wrong: A corporate proxy server acts as an intermediary for all outbound internet requests from devices configured to use it. If the proxy server were down, any device on the network attempting to access external websites through that proxy would experience connection failures. The problem statement implies this issue is specific to "a user's smartphone," making a system-wide failure like a downed proxy server an unlikely cause for an isolated incident.

Bluetooth interference

Why wrong: Bluetooth devices operate in the 2.4 GHz band, similar to Wi-Fi. However, Bluetooth typically uses frequency hopping spread spectrum (FHSS) and lower power outputs, making its interference more transient and localized. While it can cause minor, intermittent disruptions, it is less likely to be the source of sustained, significant performance degradation across an entire 2.4 GHz Wi-Fi network compared to other continuous emitters.

Microwave oven interference

Why wrong: Microwave ovens also operate within the 2.4 GHz Industrial, Scientific, and Medical (ISM) band, which can cause significant electromagnetic interference with Wi-Fi signals. However, this interference is typically intermittent, occurring only when the microwave oven is actively in use for heating food. Since the problem described is persistent, a microwave oven is an unlikely cause for continuous poor network performance.

Co-channel interference from a neighboring Wi-Fi network

Why wrong: Co-channel interference from a neighboring Wi-Fi network occurs when multiple access points use the same or overlapping channels, leading to contention and reduced throughput. While this is a common issue in crowded 2.4 GHz environments, the problem statement indicates that the 5 GHz band is performing normally. This distinction suggests the interference is specific to the 2.4 GHz band and not a general network congestion issue affecting both frequency ranges.

The laptop's Wi-Fi antenna is damaged.

Why wrong: If the laptop's Wi-Fi antenna were damaged, the device would likely be unable to detect or connect to *any* wireless network, regardless of the 802.11 standard (ac, n, g, b). Since the problem is specific to the 802.11ac laptop and implies other devices *can* connect, a general antenna failure on the laptop is not the most plausible cause. This issue points to a specific incompatibility or configuration problem rather than a complete hardware failure affecting all Wi-Fi functionality.

The laptop's drivers are not compatible with 802.11n.

Why wrong: An 802.11ac-capable laptop's wireless adapter drivers are inherently designed to support backward compatibility with previous Wi-Fi standards, including 802.11n, 802.11g, and 802.11b. Therefore, a driver incompatibility specifically preventing connection to an 802.11n network, while still being an 802.11ac device, is highly improbable. The issue described is that the *new 802.11ac laptop* cannot connect, implying it should be able to utilize its advanced capabilities or fall back to older ones.

The access point is set to 802.11b-only mode.

Why wrong: If the access point were configured for 802.11b-only mode, it would exclusively broadcast on the 2.4 GHz band using the 802.11b protocol. This setting would prevent *all* newer devices, including both 802.11ac and 802.11n laptops, from connecting, as they require at least 802.11g or 802.11n for optimal performance and often cannot connect to a pure 802.11b network. This contradicts the problem statement, which implies that other (likely 802.11n) devices *can* connect.

The smartphone's battery saver mode is turning off the hotspot.

Why wrong: The smartphone's battery saver mode is designed to extend battery life by reducing background app activity, limiting CPU performance, and dimming the screen. While it might slightly reduce the hotspot's maximum throughput or efficiency, it is highly improbable for battery saver mode to completely disable the mobile hotspot functionality after just a few minutes of operation. Hotspot disabling is typically a manual user action or a carrier-imposed restriction, not an automatic function of battery saver.

The connected device is out of Bluetooth range.

Why wrong: Mobile hotspots utilize Wi-Fi technology to broadcast a network, allowing other devices to connect and access the internet. Bluetooth, on the other hand, is a separate, short-range wireless communication standard primarily used for connecting peripherals like headphones or for file transfers between nearby devices. Therefore, the range of a Bluetooth connection is entirely irrelevant to the operation or performance of a smartphone's mobile hotspot, which relies solely on Wi-Fi signals.

The smartphone's Wi-Fi antenna is overheating.

Why wrong: While prolonged, intensive use can cause a smartphone to generate heat, a Wi-Fi antenna overheating to the point of failure or shutdown is an extremely rare occurrence and typically indicates a significant hardware malfunction. If the Wi-Fi antenna were truly overheating, it would likely affect all Wi-Fi functions (both client mode and hotspot mode) and would not typically manifest as a quick, intermittent failure solely for the hotspot feature after a short period of use.

10.0.1.50

Why wrong: This IP address, 10.0.1.50, belongs to a different subnet (10.0.1.0/24) than the router's interface, which is implied to be on the 10.0.0.0/24 network. Assigning a host an IP from a different subnet would prevent it from communicating directly with the router and other devices on the intended local network without a Layer 3 device to route between them. This configuration would isolate the host from the rest of the office network.

10.0.0.0

Why wrong: The IP address 10.0.0.0 represents the network address for the 10.0.0.0/24 subnet. This address is reserved for identifying the entire network segment itself, not for individual hosts within it. Assigning 10.0.0.0 to a device would cause severe network communication issues, as it is used by routing protocols and network management tools to refer to the network as a whole.

10.0.0.255

Why wrong: The IP address 10.0.0.255 is the dedicated broadcast address for the 10.0.0.0/24 subnet. This address is used to send data to all devices simultaneously within that specific network segment, rather than to a single host. Assigning the broadcast address to a host would prevent proper network communication, as it would interfere with the network's ability to send broadcast messages effectively.

Ad hoc network; the laptop is trying to connect directly to other devices.

Why wrong: An ad hoc network establishes direct peer-to-peer connections between devices without a central access point (AP). The scenario describes a laptop disconnecting from '3', implying a connection to a central Wi-Fi network managed by an AP, which is characteristic of infrastructure mode, not an ad hoc setup.

Mesh network; the laptop is roaming between mesh nodes.

Why wrong: A mesh network consists of multiple interconnected wireless nodes that cooperate to extend coverage and provide redundant paths. The problem statement refers to a single point of connection ('3'), not a distributed system of multiple nodes that the laptop would roam between, making a mesh network an incorrect assumption.

PAN network; the laptop is using Bluetooth, which has limited range.

Why wrong: A Personal Area Network (PAN) typically involves short-range wireless technologies like Bluetooth, designed for connecting devices within a very close proximity, usually around 10 meters. The user's complaint about Wi-Fi disconnections, rather than Bluetooth, and the implied longer distance rule out a PAN as the primary issue.

The smartphone's Wi-Fi antenna is damaged.

Why wrong: A damaged Wi-Fi antenna would universally impair the smartphone's ability to send and receive wireless signals, affecting connectivity across all networks, not just the office Wi-Fi. If the device connects successfully at home, the antenna is likely functional, indicating a problem specific to the office network configuration or the device's settings for that network.

The office Wi-Fi router is out of range.

Why wrong: If the office Wi-Fi router were truly out of range, other devices in the same location would also experience connection difficulties or complete signal loss. Since other devices connect without issue, the signal strength is adequate for the area, ruling out range as the primary cause for this specific smartphone's inability to connect.

The smartphone's IP address is static and conflicting.

Why wrong: A static IP address conflict typically manifests as intermittent network connectivity issues or an inability to access network resources *after* successfully connecting to the Wi-Fi network, rather than preventing the initial Wi-Fi association and authentication entirely. Furthermore, modern networks with DHCP are designed to prevent such conflicts, and if one occurred, it wouldn't necessarily stop the device from associating with the access point.

Reduce the 2.4 GHz channel width to 20 MHz.

Why wrong: Reducing the 2.4 GHz channel width to 20 MHz primarily aims to minimize co-channel or adjacent-channel interference from other Wi-Fi networks. While it can improve stability in congested Wi-Fi environments by using narrower frequency bands, it does not mitigate interference originating from non-Wi-Fi sources like microwaves, cordless phones, or Bluetooth devices, which operate across broader portions of the 2.4 GHz spectrum. Furthermore, this reduction in channel width inherently limits the maximum achievable data throughput for connected devices.

Implement DFS channels on the 5 GHz band.

Why wrong: Dynamic Frequency Selection (DFS) channels are a regulatory requirement for certain 5 GHz Wi-Fi frequencies to prevent interference with radar systems, such as weather or military radar. While implementing DFS channels on the 5 GHz band helps avoid radar detection and ensures compliance, it has absolutely no impact on troubleshooting interference issues occurring within the 2.4 GHz band. The problem statement implies a 2.4 GHz issue, making this solution irrelevant to the core problem.

Increase the transmit power on the 2.4 GHz radio.

Why wrong: Increasing the transmit power on the 2.4 GHz radio might seem like a way to "shout over" existing interference, potentially improving signal strength for distant devices. However, this approach often exacerbates the problem by increasing co-channel interference for other Wi-Fi networks in the vicinity and can lead to client devices "sticking" to a weaker, distant access point. Crucially, it does not eliminate the underlying source of non-Wi-Fi noise, merely attempting to overpower it, which is an inefficient and often counterproductive strategy.

Check if the SATA controller is set to AHCI mode.

Why wrong: AHCI (Advanced Host Controller Interface) is a specification designed for SATA host bus adapters to enable advanced features like hot-plugging and Native Command Queuing. NVMe (Non-Volatile Memory Express) drives, however, communicate directly over the PCIe bus using their own highly optimized protocol. Therefore, checking or changing SATA controller settings, including AHCI mode, has no bearing on the functionality or bootability of an NVMe drive.

Check if the M.2 slot is configured to use SATA or PCIe lanes in the BIOS.

Why wrong: If the NVMe drive is detected by the system, it indicates that the M.2 slot is already correctly configured for PCIe lanes, as NVMe drives operate exclusively over PCIe. Motherboard BIOS settings to switch M.2 slots between SATA and PCIe modes are only relevant if the drive is not detected at all. Since the drive is present but not booting, the physical configuration of the slot is not the root cause.

Check if the drive has been initialized with a Master Boot Record (MBR).

Why wrong: NVMe drives, particularly when used as boot devices, require the system to be in UEFI boot mode, which necessitates a GUID Partition Table (GPT) for the boot drive. A Master Boot Record (MBR) is an older partitioning scheme primarily associated with legacy BIOS booting and has limitations in drive size and partition count. Therefore, checking if the drive is MBR is counterproductive; the correct troubleshooting step would be to ensure it is partitioned with GPT.