220-1202 Exam Dumps - CompTIA A+ Core 2 2025 Exam

The completed configuration:

1. Wireless AP (LAN side)

1. LAN IP: 192.168.10.1

2. Encryption: WPA2 PSK

2. Router (port-forward rule)

1. Allow TCP Any 3389

This forwards inbound RDP traffic (TCP/3389) from the Internet to the Windows PC, enabling Remote Desktop access.

3. Firewall (screened subnet side)

1. LAN IP: 10.100.0.1

4. Device placement

1. PC: place behind the router (where the port-forward rule points).

2. Game console: place on the Wireless AP (so it can use chat and extra services over WPA2 PSK).

3. Firewall: place in front of the screened subnet (with its 10.100.0.1 IP facing that subnet).

The Windows PC is placed in the screened subnet (behind the firewall) for enhanced security. Remote access to this PC requires port forwarding of TCP port 3389 (RDP), which is correctly configured through the router.

The Game Console is placed on the Wireless AP LAN, using WPA2 PSK for a secure wireless connection. Game consoles typically use peer-to-peer chat and online services that require open access without firewall restrictions, which is why the console is not placed behind the firewall.

CompTIA A+ 220-1102 Reference Points:

Objective 3.4: Given a scenario, implement best practices associated with data and device security.

Objective 2.4: Given a scenario, use appropriate tools to support and configure network settings.

Study Guide Reference: CompTIA A+ Core 2 guides recommend using screened subnets (a type of DMZ) for systems needing controlled external access, such as remote desktops, while placing gaming and media devices on less restricted networks for full functionality.

Issue: Limited network connectivity

Resolution: Refresh DHCP

Verify/Resolve: ipconfig

Issue (drop-down)

Limited network connectivity

Why this matches:

“Internet Down” most commonly indicates the workstation has lost valid Layer 3 connectivity (bad/expired DHCP lease, APIPA address, wrong gateway, etc.). In CompTIA A+ terms, this aligns best with limited connectivity symptoms (can’t reach internet resources).

Resolution (drop-down)

Refresh DHCP

Why this is the most efficient fix:

If the client has:

an expired lease

an APIPA address (169.254.x.x) because DHCP failed

an incorrect IP/gateway from a bad lease

…then the fastest first remediation is to renew DHCP to obtain a correct IP address, default gateway, and DNS servers. This is a standard CompTIA A+ troubleshooting action (quick, low-risk, high-success).

Verify/Resolve (drop-down)

ipconfig

Why this is the correct verification tool:

ipconfig is the primary Windows CLI tool to:

check current IP settings (ipconfig /all)

release/renew DHCP (ipconfig /release and ipconfig /renew)

confirm you received a valid IP + gateway + DNS , which is required for internet access.

What you would do (mapped to those choices)

Using ipconfig to complete “Refresh DHCP” and confirm the fix:

Check current addressing

ipconfig /all

Look for:

Valid IPv4 (not 169.254.x.x )

Valid Default Gateway

DNS servers present

Refresh the DHCP lease

ipconfig /release

ipconfig /renew

Verify outcome

Run ipconfig again to confirm:

You now have a correct IP for the network

Default gateway is populated

If the gateway/DNS populate correctly, internet access typically returns.

Ticket #8675310

Issue: Limited network connectivity

Resolution: Refresh DHCP

Verify/Resolve: ipconfig /renew

For the Low priority ticket #8675310 (“ A small yellow triangle appeared in the taskbar. I am no longer able to access network resources. ”), the Windows yellow triangle on the network icon is the classic indicator of limited connectivity (often caused by a bad/expired DHCP lease, APIPA address, missing default gateway, or DNS info not being assigned).

Correct PBQ Selections (Ticket #8675310)

Issue

Limited network connectivity

Why (CompTIA logic):

That yellow warning triangle means the NIC is connected at Layer 2 (link is up), but the system likely doesn’t have valid Layer 3 config (IP/gateway/DNS), so it can’t reach network resources.

Resolution

Refresh DHCP

Why this is the most efficient fix:

When a Windows PC can’t access network resources and shows “limited connectivity,” the fastest, lowest-risk fix is to renew DHCP so the PC can pull:

a valid IP address

default gateway

DNS servers

This directly resolves the most common root cause behind that icon.

Verify / Resolve

ipconfig /renew

Why this is the correct verification/remediation command:

ipconfig /renew is the direct command to request a fresh DHCP lease . After renewal, the user should regain access to network resources if DHCP was the issue.

What this fixes (what you’d expect to see)

Before the fix, the attachment ( Output.txt ) in these PBQs typically shows symptoms like:

169.254.x.x (APIPA) → DHCP failed

Missing/blank Default Gateway

DNS not present or incorrect

After ipconfig /renew, you should see a normal private IP (like 192.168.x.x / 10.x.x.x / 172.16-31.x.x ) and a valid gateway/DNS.

The question asks where to find ownership and business criticality details for a server. That type of “who owns it, what does it support, and how important is it” data is maintained in a Configuration Management Database (CMDB) as part of configuration/asset management. Quentin Docter discusses asset management as lifecycle tracking and emphasizes accountability, including assigning responsibility and tracking who is associated with assets.

The All-in-One guide similarly describes asset management databases as tracking details such as “who has the asset,” “what type of asset,” and “where this asset is located,” which supports the idea that ownership and operational relevance are stored in such systems.

An SLA defines service expectations, an SOP defines procedures, and an EULA covers licensing—none are intended to be the authoritative inventory/ownership record for a specific server. Therefore, CMDB is the correct answer.

If the PC can ping the domain controller by IP , basic connectivity exists. Domain join, however, depends heavily on name resolution (finding the domain and locating domain services), so incorrect DNS is the most likely cause. Mike Meyers explains a key diagnostic pattern: when you ping a URL/name and get “could not find host,” the system “can’t get an IP address for that Web site,” which “points to a DNS failure.” This same logic applies to domains: if the client can reach the DC by IP but can’t properly resolve domain names/services, the join fails.

Quentin Docter reinforces that one of the “key things” for TCP/IP to work effectively is that “a hostname must resolve to an IP address—an action usually performed by a DNS server,” and he highlights nslookup as a tool to verify DNS server entries.

Firewall issues could block some traffic, but the clue “ping by IP works” points away from total network blockage. IPv6 enabled is normal, and “not connected” contradicts successful ping. Therefore, DNS settings are incorrect (A) .

“No OS found” commonly indicates the firmware can’t locate boot instructions for the installed OS. If the drive isn’t obviously failing (no unusual noises) and BIOS/UEFI settings are reasonable, a classic cause is a corrupt Master Boot Record (MBR) (on MBR-partitioned disks). Mike Meyers’ Lab Manual explains that when BIOS can’t find an OS, causes may include configuration issues or drive problems, but also states: “If the correct drive is already first in the boot sequence, the master boot record… may be corrupt and need to be rebuilt.”

The Lab Manual also explains what the MBR does: the first sector contains boot code that informs the system about installed operating systems, and “without this bit of code, your OS will never load.” The All-in-One guide describes the same: BIOS looks at the first sector for instructions, and without the MBR code, the OS won’t load.

NTFS corruption wouldn’t typically present as “no OS found” at the firmware stage, and TPM issues usually create different security/boot errors. Therefore, MBR (D) is most likely.

Comprehensive and Detailed Explanation From Exact Extract:

The recurring print issue suggests theprint spooler service is not set to start automatically, causing it to stop between sessions. Ensuring it is set tostart automaticallyand manuallystarting the servicewill resolve the issue.

FromMark Soper – Mike Meyers ' Lab Manual:

“The print spooler is essential for print services. If it isn’t configured to start automatically, users may experience recurring failures.”

“Manually starting the service or setting it to ' Automatic ' in the Services panel resolves persistent print availability problems.”

The correct answer is D. Enabling HTTPS-Only Mode , because HTTPS ensures that all communication between the browser and websites is encrypted using TLS (Transport Layer Security) . This protects sensitive information such as usernames, passwords, and payment details from interception.

According to the Quentin Docter – CompTIA A+ Complete Study Guide , HTTPS encrypts data in transit, preventing attackers from eavesdropping or modifying communications. HTTPS-only modes in modern browsers block or warn users when a site does not support secure connections.

The Travis Everett & Andrew Hutz – All-in-One Exam Guide emphasizes that HTTPS is essential for protecting authentication credentials and financial information, especially on public or untrusted networks. Enforcing HTTPS-only connections ensures users cannot accidentally submit data over unencrypted HTTP.

The Mike Meyers / Mark Soper Lab Manual clarifies that disabling cookies or JavaScript may break website functionality but does not guarantee encryption. Pop-up blockers address nuisance behavior, not data security.

Because the objective is to encrypt browser communications and protect sensitive data , enabling HTTPS-Only Mode is the most effective and direct solution, making D the correct answer.