Free Practice Questions for CompTIA 220-1201 Exam

Bluetooth audio issues are typically related to distance and signal strength, not internet connectivity or Wi-Fi access points. Bluetooth devices—especially headsets—generally have a limited effective range of around 10 meters (33 feet) for Class 2 Bluetooth, which is common in consumer laptops and headsets. When the user leaves the room and walks into adjacent offices, they are likely moving beyond the optimal Bluetooth range or passing through walls that weaken the signal.

CompTIA A+ highlights that Bluetooth uses low-power radio frequencies easily disrupted by physical obstructions, distance, and interference. Since the laptop remains stationary and the user moves, the headset becomes progressively further from the laptop, causing intermittent audio dropouts, stuttering, or loss of connection.

The number of APs (A) is irrelevant because the headset is not using Wi-Fi. Mesh mode (C) applies only to wireless AP-to-AP communication. The internet connection (D) is high-quality fiber and conference calls work fine when stationary, so the issue is not bandwidth or WAN throughput.

Thus, the most likely cause is that the user is moving in and out of Bluetooth range.

CompTIA A+ explains that Secure Boot is a UEFI security feature that prevents unauthorized or malicious bootloaders, rootkits, and unsigned OS loaders from starting during the boot process. Secure Boot verifies digital signatures on the OS and critical boot files before allowing startup, ensuring the system has not been tampered with.

TPM (Option A) provides encryption key storage and is used for BitLocker, but alone does not block malicious bootloaders. HSMs (Option B) are enterprise cryptographic devices, not PC boot protection features. BIOS passwords (Option D) restrict access to configuration but do not protect against malicious boot-level malware.

Windows 11 specifically requires Secure Boot, making it the correct protection mechanism for preventing startup-level malware.

Thus, Secure Boot is the proper choice.

A CNAME (Canonical Name) record is used in DNS to create an alias that maps one domain name to another canonical domain name. According to CompTIA Core 1 (220-1201) DNS objectives, CNAME records allow multiple hostnames to reference the same IP address indirectly by pointing to a single authoritative domain name.

For example, www.example.com can be configured as a CNAME that points to example.com. When DNS queries are made, the resolver follows the alias until it reaches an A or AAAA record that contains the actual IP address.

An A record maps a hostname directly to an IPv4 address, while an AAAA record maps a hostname to an IPv6 address. A TXT record is used to store arbitrary text data, commonly for verification, email security (SPF, DKIM), or policy information, not for aliasing.

CompTIA stresses that CNAME records are specifically intended for aliasing and name redirection within DNS, making them the correct answer.

Adocking stationconnects to a laptop’sproprietary port or USB-C/Thunderbolt, providing access tomultiple additional ports(USB, Ethernet, video, audio, etc.). It allows users to transform a laptop into a full desktop workstation.

Option A (NFC adapter):Used for short-range communication, not port expansion.

Option C (Port replicator):Similar to a dock but usually less powerful and often lacks charging or video output.

Option D (USB dongle):Adds a single function (like Wi-Fi or storage), not full port expansion.

CompTIA A+ Core 1 Exam Objective Reference:

Objective 1.4: Given a scenario, configure settings and use cases for laptops and mobile devices.

===========

A valid public IP address must fall outside the private IP address ranges:

10.0.0.0 to 10.255.255.255

172.16.0.0 to 172.31.255.255

192.168.0.0 to 192.168.255.255

66.157.195.20 is outside these ranges, making it a public IP address.

Why Not A, C, D: These IPs fall within private IP address ranges.

CompTIA A+ Exam Reference: Core 1 (220-1201), Section 2.6, IP addressing​.

In CompTIA A+ Core 1 (220-1201) networking and troubleshooting, a common cause of “can’t reach internal resources” while docked is that the laptop is still using the wireless interface (or has a higher interface priority for Wi-Fi) instead of the docking station’s wired Ethernet connection. If the Wi-Fi network is a guest/isolated VLAN, uses different routing, or has stricter access controls, the user may be blocked from reaching department file servers even though an Ethernet cable is physically connected to the dock. Disabling Wi-Fi is a fast, low-risk step that forces the system to use the wired NIC path through the docking station, which typically provides the correct corporate network access, DHCP scope, and routing to internal servers.

Restarting the computer might help in some cases, but it’s less targeted and not the “best next step” when the likely issue is interface selection. Replacing the Ethernet cable is appropriate if link lights are off or the wired connection is clearly down, but the scenario highlights that the dock has a hardwired connection—suggesting the physical layer may be fine. Dock firmware updates are not a first-line fix for basic connectivity/access symptoms.

An IP address in the 169.254.x.x range indicates the device has assigned itself an APIPA address (Automatic Private IP Addressing). This happens when the device is configured to obtain an IP address automatically but cannot reach a DHCP server to receive a valid IP configuration for the local network. With an APIPA address, the device can sometimes communicate only with other devices in the same 169.254.x.x range on the local link, but it typically will not have a correct default gateway or DNS server settings. Without a valid gateway, the device cannot route traffic to the internet, which explains why it cannot access internet websites.

Option C is therefore the most likely cause: the DHCP assignment cannot be obtained due to issues such as a disconnected network cable, disabled Wi-Fi, DHCP server outage, VLAN misconfiguration, or a blocked DHCP request/response on the network.

Option B (DNS failure) could prevent name resolution, but it would not by itself cause an APIPA address. Option A suggests a static configuration problem, yet APIPA usually appears when the device is set to DHCP, not static. Option D could also break internet access, but it would not specifically result in a 169.254 address on the client.

An MX, or Mail Exchanger, record is a type of DNS resource record. It identifies the mail server responsible for accepting email for a particular domain. Consequently, an MX record is created or modified in the domain’s DNS zone , which is hosted on a DNS server.

Although the MX record points to a mail server, the record itself is configured through DNS. The mail server is the destination identified by the record, not the service in which the DNS record is stored.

A proxy server intermediates network requests, commonly for filtering, caching, or privacy.

A mail server sends, receives, and stores email, but DNS tells other systems how to locate it.

A print server manages printers and print jobs.

CompTIA objective 2.4 specifically includes DNS record types such as A, AAAA, CNAME, MX, and TXT. Microsoft also defines an MX record as a DNS resource record that identifies a domain’s mail server.

==========

For a main database server with high read/write activity, the best RAID choice must deliver strong performance while still providing fault tolerance. Per CompTIA A+ Core 1 (220-1201) storage/RAID objectives, RAID 10 (1+0) combines disk mirroring (RAID 1) and disk striping (RAID 0). Striping improves performance by distributing read/write operations across multiple disks, which is ideal for databases that perform frequent transactions. Mirroring provides redundancy by keeping an identical copy of data on a paired drive, allowing the system to tolerate drive failures (typically one drive per mirrored pair) without data loss.

RAID 0 is fast but offers no redundancy, making it inappropriate for critical servers. RAID 5 and RAID 6 use parity, which provides redundancy but introduces a write penalty because parity must be calculated and written during updates—often a poor fit for workloads with heavy random writes like databases. RAID 6 is even more write-intensive