The CompTIA Troubleshooting Methodology states that after testing the theory, the next step is to establish a plan of action to resolve the issue.

Troubleshooting Steps:

Identify the problem.

Establish a theory of probable cause.

Test the theory to determine the cause.

Establish a plan of action and implement the solution. ✅ (Correct step)

Verify full system functionality.

Document findings, actions, and outcomes.

Breakdown of Options:

A. Verify full system functionality – Happens after implementing the solution.

B. Document the findings and outcomes – Final step, happens after resolving the issue.

C. Establish a plan of action – ✅ Correct answer. Comes immediately after confirming the cause.

D. Identify the problem – First step, already completed.

MTTR (Mean Time to Repair) is the average time it takes to repair a system or service after a failure. It helps in measuring the downtime and planning recovery processes.

=================

Devices in both buildings should be able to access the Internet.

Security insists that all Internet traffic be inspected before entering the network.

Desktops should not see traffic destined for other devices.

Here is the corrected layout with explanation:

Building A:

Switch: Correctly placed to connect all desktops.

Firewall: Correctly placed to inspect all incoming and outgoing traffic.

Building B:

Switch: Not needed. Instead, place a Wireless Access Point (WAP) to provide wireless connectivity for laptops and mobile devices.

Between Buildings:

Wireless Range Extender: Correctly placed to provide connectivity between the buildings wirelessly.

Connection to the Internet:

Router: Correctly placed to connect to the Internet and route traffic between the buildings and the Internet.

Firewall: The firewall should be placed between the router and the internal network to inspect all traffic before it enters the network.

Corrected Setup:

Top-left (Building A): Switch

Bottom-left (Building A): Firewall (inspect traffic before it enters the network)

Top-middle (Internet connection): Router

Bottom-middle (between buildings): Wireless Range Extender

Top-right (Building B): Wireless Access Point (WAP)

In this corrected setup, the WAP in Building B will connect wirelessly to the Wireless Range Extender, which is connected to the Router. The Router is connected to the Firewall to ensure all traffic is inspected before it enters the network.

Configuration for Wireless Range Extender:

SSID: CORP

Security Settings: WPA2 or WPA2 - Enterprise

Key or Passphrase: [Enter a strong passphrase]

Mode: [Set based on your network plan]

Channel: [Set based on your network plan]

Speed: Auto

Duplex: Auto

With these settings, both buildings will have secure access to the Internet, and all traffic will be inspected by the firewall before entering the network. Desktops and other devices will not see traffic intended for others, maintaining the required security and privacy.

To configure the wireless range extender for security, follow these steps:

SSID (Service Set Identifier):

Ensure the SSID is set to " CORP " as shown in the exhibit.

Security Settings:

WPA2 or WPA2 - Enterprise: Choose one of these options for stronger security. WPA2-Enterprise provides more robust security with centralized authentication, which is ideal for a corporate environment.

Key or Passphrase:

If you select WPA2, enter a strong passphrase in the " Key or Passphrase " field.

If you select WPA2 - Enterprise, you will need to configure additional settings for authentication servers, such as RADIUS, which is not shown in the exhibit.

Wireless Mode and Channel:

Set the appropriate mode and channel based on your network design and the environment to avoid interference. These settings are not specified in the exhibit, so set them according to your network plan.

Wired Speed and Duplex:

Set the speed to " Auto " unless you have specific requirements for 100 or 1000 Mbps.

Set the duplex to " Auto " unless you need to specify half or full duplex based on your network equipment.

Save Configuration:

After making the necessary changes, click the " Save " button to apply the settings.

Here is how the configuration should look after adjustments:

SSID: CORP

Security Settings: WPA2 or WPA2 - Enterprise

Key or Passphrase: [Enter a strong passphrase]

Mode: [Set based on your network plan]

Channel: [Set based on your network plan]

Speed: Auto

Duplex: Auto

Once these settings are configured, your wireless range extender will provide secure connectivity for devices in both buildings.

Firewall setting to to ensure complete compliance with the requirements and best security practices, consider the following adjustments and additions:

DNS Rule: This rule allows DNS traffic from the internal network to any destination, which is fine.

HTTPS Outbound: This rule allows HTTPS traffic from the internal network (assuming 192.169.0.1/24 is a typo and should be 192.168.0.1/24) to any destination, which is also good for secure web browsing.

Management: This rule allows SSH access to the firewall for management purposes, which is necessary for administrative tasks.

HTTPS Inbound: This rule denies inbound HTTPS traffic to the internal network, which is good unless you have a web server that needs to be accessible from the internet.

HTTP Inbound: This rule denies inbound HTTP traffic to the internal network, which is correct for security purposes.

Suggested Additional Settings:

Permit General Outbound Traffic: Allow general outbound traffic for web access, email, etc.

Block All Other Traffic: Ensure that all other traffic is blocked to prevent unauthorized access.

Firewall Configuration Adjustments:

Correct the Network Typo:

Ensure that the subnet 192.169.0.1/24 is corrected to 192.168.0.1/24.

Permit General Outbound Traffic:

Rule Name: General Outbound

Source: 192.168.0.1/24

Destination: ANY

Service: ANY

Action: PERMIT

Deny All Other Traffic:

Rule Name: Block All

Source: ANY

Destination: ANY

Service: ANY

Action: DENY

Here is how your updated firewall settings should look:

Rule Name

Source

Destination

Service

Action

DNS Rule

192.168.0.1/24

ANY

DNS

PERMIT

HTTPS Outbound

192.168.0.1/24

ANY

HTTPS

PERMIT

Management

ANY

192.168.0.1/24

SSH

PERMIT

HTTPS Inbound

ANY

192.168.0.1/24

HTTPS

DENY

HTTP Inbound

ANY

192.168.0.1/24

HTTP

DENY

General Outbound

192.168.0.1/24

ANY

ANY

PERMIT

Block All

ANY

ANY

ANY

DENY

These settings ensure that:

Internal devices can access DNS and HTTPS services externally.

Management access via SSH is permitted.

Inbound HTTP and HTTPS traffic is denied unless otherwise specified.

General outbound traffic is allowed.

All other traffic is blocked by default, ensuring a secure environment.

Make sure to save the settings after making these adjustments.

Link aggregation (also known as port trunking or EtherChannel) combines multiple network connections in parallel to increase throughput and provide redundancy. When two switches are connected with multiple links without any additional configuration, a Layer 2 loop may occur. Link aggregation prevents these loops by treating the multiple connections as a single logical link, using a protocol such as LACP (Link Aggregation Control Protocol).

From Andrew Ramdayal’s guide:

“Link aggregation allows you to combine multiple network connections to increase the bandwidth and provide redundancy. It helps prevent Layer 2 loops when connecting switches with multiple links by making them operate as a single logical interface.”

The correct choice is D. netstat because the display shown is a classic list of active TCP sessions, including the protocol, local address, remote address, and the connection state such as ESTABLISHED and TIME_WAIT. That is exactly the kind of information a technician checks when trying to see what connections a workstation currently has open.

The distractors do different jobs. nslookup and dig are DNS utilities. They help query name resolution records, but they do not list active client sessions. nmap is mainly used to scan hosts and ports across the network, usually to discover services or assess exposure on target systems. It does not normally produce a local session table in this format.

For Network+ purposes, this falls under troubleshooting with command-line tools. When the goal is to inspect current sessions on the local device and confirm whether a port is open, listening, or already connected, netstat is the expected command. The wording “currently established from a client device” is the clue that matters most. The question is not asking what ports exist on a remote server; it is asking what active connections are present on the machine itself. That makes netstat the best fit.

A large number of collisions and input errors typically indicates a duplex mismatch, such as when one device is set to full duplex and the other to half duplex. This leads to communication issues and poor performance. The document explains:

“Collisions and input errors are clear signs of duplex mismatches… typically caused when one device operates in half duplex while the other is in full duplex, causing performance and connectivity issues.”

The correct answer is B. PAT. Port Address Translation allows many internal devices that use private IP addresses to share a small number of public IP addresses when accessing the internet. In this case, the question says all users can access the internet using only two public IPs, which is exactly the kind of situation PAT is designed for. The device performing PAT keeps track of each connection by using source port numbers, so multiple internal sessions can be translated and maintained at the same time without requiring a unique public IP for every user.

The other options do not match this function. EIGRP and BGP are routing protocols used to exchange routing information, not to translate addresses for outbound internet traffic. VIP refers to a virtual IP address, commonly used in high availability or load-balancing scenarios, but it does not provide the many-to-one address translation behavior described in the question.

For Network+ exam purposes, when the scenario talks about conserving public IPv4 addresses and allowing many users to reach external networks through a very small number of public IPs, the expected answer is PAT. This is one of the most common real-world uses of NAT technology at the network edge.

If the three new employees can communicate with each other’s devices, that strongly suggests their local Layer 2/Layer 3 connectivity is working (same VLAN/subnet, switching is fine, and they have IP addressing that allows local communication). The fact that they cannot access company resources (often on other subnets, servers, or the internet via internal routing) points to a problem with how these new endpoints are being addressed or routed beyond their local segment.

The most likely shared root cause affecting only “new employees” is DHCP scope/pool configuration. If the DHCP pool is exhausted, mis-scoped, or handing out incorrect options (such as an incorrect default gateway, wrong subnet mask, or an address range tied to an isolated VLAN), users could still talk locally but fail to reach resources outside their subnet. Modifying the DHCP server pool (expanding the scope, correcting the scope network, or ensuring the correct options are assigned) would resolve this with minimal changes.

A gateway routing table issue would typically affect many users, not just three new ones. DNS misconfiguration on the router would more commonly cause name-resolution problems, not block all resource access (and wouldn’t be isolated to only new employees). A workstation firewall would not usually prevent access to “company resources” in a way that consistently affects three new devices while still allowing peer connectivity.

When configuring a firewall, the first step is identifying which ports, protocols, and services are required for normal business operations. This ensures only legitimate traffic is allowed. After establishing the required rules, a default deny rule is added for security.

B. Deny all rule is important, but it should come after defining required rules.

C. VPN access is a service to configure, but only after determining baseline needs.

D. Outbound traffic policies are part of refinement, not the first consideration.

References (CompTIA Network+ N10-009):

Domain: Network Security — Firewall configuration, rule order, least privilege.

224.0.0.1 is a multicast address that allows packets to be sent to all hosts within a multicast group. Since video streaming often uses multicast to efficiently distribute data to multiple clients without unnecessary duplication, this is the correct answer.

•Why not the other options?

•127.0.0.1 (A) – This is the loopback address used for internal device testing, not for multicast traffic.

•172.17.1.1 (B) – This is a private unicast address, meaning it can only send packets to one specific host.

•240.0.0.1 (D) – This falls within the reserved experimental IP address range and is not used for multicast.

A DDoS (Distributed Denial of Service) attack is often launched from botnets — networks of compromised systems (bots or zombies) under the control of an attacker. These devices flood the target with traffic to disrupt services.

A. Evil twin attack is a wireless spoofing method.

C. XML injection targets web applications.

D. Brute-force attacks repeatedly guess passwords but don ' t involve a botnet by default.

???? Reference:

CompTIA Network+ N10-009 Official Objectives: 4.2 – Identify common security threats and vulnerabilities.

EIGRP (Enhanced Interior Gateway Routing Protocol) is a Cisco proprietary advanced distance-vector routing protocol. While it operates within an Autonomous System (AS), it requires the AS number to be configured for routers to recognize each other as EIGRP neighbors.

OSPF (Open Shortest Path First) uses areas and routers must be in the same area to form adjacencies, but it doesn ' t require AS numbers in the same way.

FHRP (First Hop Redundancy Protocol) is not a routing protocol but a group of protocols (e.g., HSRP, VRRP) to ensure high availability at the default gateway level.

RIP (Routing Information Protocol) does not use autonomous system numbers.

???? Reference:

CompTIA Network+ N10-009 Official Objectives: 3.1 – Compare and contrast various routing technologies.

===========

For a secure 802.1X design that includes BYOD access to a trusted wireless network, the engineer should implement NAC (Network Access Control). In the Network+ (N10-009) objectives, 802.1X provides authentication (commonly via EAP to a RADIUS server), but NAC expands this by enforcing policy-based access decisions—such as device posture checks, user/device identity validation, and dynamic assignment to the appropriate VLAN/role. With BYOD, the organization often needs to confirm whether devices meet requirements (OS version, encryption, security software) and then grant the correct level of access (full, limited, or quarantine/remediation). NAC is the architecture that ties these controls together in a scalable way for wireless networks.

An ACL can restrict traffic after a device connects, but it doesn’t perform authentication/posture assessment. MAC filtering is weak because MAC addresses can be spoofed and it does not provide strong identity assurance. Port security is mainly a wired switch control (limiting MAC addresses per port) and is not the right control set for secure BYOD wireless access. NAC best matches the requirement of secure, policy-driven 802.1X BYOD access.

===========

A central repository describes a single location where critical network infrastructure configurations are stored and managed. This can include switch configurations, router configurations, firewall rules, wireless controller settings, diagrams, templates, backup files, and standard operating procedures. A central repository helps administrators maintain consistency, improve recovery time, simplify audits, and reduce the risk of losing important configuration data.

The CompTIA Network+ N10-009 objectives include network documentation, configuration management, change management, and operational best practices. Storing configurations in a central repository supports backup and recovery because administrators can quickly retrieve known-good configurations if a device fails or a change causes an outage. It also helps teams collaborate by giving authorized personnel access to the same current documentation and configuration files.

Version control is related but refers specifically to tracking changes, revisions, and rollback history over time. Conflict mitigation involves reducing conflicts when multiple people work on the same files or configurations. Branching is a version-control feature that allows separate lines of development or change testing. Since the question focuses on housing all configurations in one location, the best answer is central repository.

Top of Form

Bottom of Form