CompTIA N10-009 - CompTIA Network+ Certification Exam

The correct answer is Integrity because a hashing algorithm ensures that data has not been altered. According to CompTIA Network+ (N10-009) security objectives, hashing is a cryptographic process that takes input data of any size and produces a fixed-length output known as a hash value or digest. If even a single bit of the original data changes, the resulting hash value will be significantly different.

Hashing is commonly used to verify file integrity, validate message authenticity, and securely store passwords. For example, when downloading software, the vendor may publish a hash value so users can calculate the hash of the downloaded file and confirm it matches, ensuring the file was not tampered with.

Non-repudiation (Option A) typically requires digital signatures that combine hashing with asymmetric encryption to verify the sender’s identity. Confidentiality (Option C) is achieved through encryption, which protects data from unauthorized access. Availability (Option D) refers to ensuring systems and data are accessible when needed and is not related to hashing functions.

Therefore, hashing primarily provides data integrity verification.

RTO stands for Recovery Time Objective, which defines the maximum acceptable amount of time that a system, application, or function can be down after a failure or disaster. It helps prioritize which systems need to be recovered first based on their importance to business operations.

SLA (Service Level Agreement) refers to an agreement between a service provider and a customer regarding expected performance and availability, but it does not dictate recovery order.

MTBF (Mean Time Between Failures) is a measure of reliability and time between hardware or system failures.

SIEM (Security Information and Event Management) is a centralized tool for logging and alerting but not relevant to DR recovery prioritization.

📘 Reference:

CompTIA Network+ N10-009 Official Objectives: 4.4 – Summarize business continuity and disaster recovery concepts.

===========

Definition of RPO:

Recovery Point Objective (RPO) is a disaster recovery metric that describes the maximum acceptable amount of data loss measured in time. It indicates the point in time to which data must be recovered to resume normal operations after a disaster.

For example, if the RPO is set to 24 hours, then the business could tolerate losing up to 24 hours ' worth of data in the event of a disruption.

Why RPO is Important:

RPO is critical for determining backup frequency and helps businesses decide how often they need to back up their data. A lower RPO means more frequent backups and less potential data loss.

Comparison with Other Metrics:

MTTR (Mean Time to Repair): Refers to the average time required to repair a system or component and return it to normal operation.

RTO (Recovery Time Objective): The maximum acceptable length of time that a computer, system, network, or application can be down after a failure or disaster occurs.

MTBF (Mean Time Between Failures): The predicted elapsed time between inherent failures of a system during operation.

How RPO is Used in Disaster Recovery:

Organizations establish RPOs to ensure that they can recover data within a timeframe that is acceptable to business operations. This involves creating a backup plan that meets the RPO requirements.

A SIEM (Security Information and Event Management) platform is built to collect, correlate, and alert on security-relevant events across many sources, which is exactly what’s needed to identify patterns such as brute force attempts, port scanning, and DDoS indicators. In Network+ (N10-009) security operations concepts, correlation is key: a SIEM can ingest logs from firewalls, IDS/IPS, servers, authentication systems, endpoint agents, and network devices, then apply rules/analytics to detect suspicious behavior that might not be obvious from a single log source. It can also generate real-time alerts, dashboards, and incident timelines—helping the engineer respond quickly and prioritize threats.

Packet capture provides deep visibility into traffic but is not inherently designed for enterprise-wide correlation and alerting without significant additional tooling and expertise. SNMPv3 is used for secure device monitoring (status, counters, performance) rather than detecting coordinated attack patterns. A syslog collector centralizes logs but generally does not provide the same level of correlation, enrichment, and automated alerting capabilities as a SIEM. Therefore, SIEM is the best answer.

===========

Branchingallows developers and administrators tocreate an isolated copyof the main configuration so they can test changes independently. This avoids impacting the primary environment and allows for safer testing and development.

A misaligned parabolic antenna can cause a significant increase in input errors because the signal is not properly focused or directed towards the receiving antenna, resulting in poor reception and data corruption. The document confirms:

“Misalignment of parabolic microwave antennas can lead to weak or incorrect signal reception, causing an increase in input errors and connectivity issues on the link.”

The correct solution is to configure the connecting ports as trunk ports. When connecting switches, the uplink ports must be configured to carry traffic for multiple VLANs (trunking), not just a single access VLAN. Without trunking, VLAN tags may be dropped, and traffic from hosts will not reach the rest of the network or internet.

B. STP cables is a misnomer — STP refers to Spanning Tree Protocol or Shielded Twisted Pair cables, neither of which solves this logical configuration issue.

C. PoE budget is irrelevant because switches and hosts in this context don’t require PoE.

D. Link aggregation (LACP, EtherChannel) is for increasing bandwidth/redundancy across multiple links, not required with a single cable.

By enabling trunking on the uplink ports, the switches can pass VLAN-tagged traffic, ensuring hosts connected to the new switch have access to the same resources as those on the existing switch.

References (CompTIA Network+ N10-009):

Domain: Network Troubleshooting — VLAN trunking, inter-switch connectivity.

Private VLANs (PVLANs) are used to segment devices on the same subnet and switch so they cannot communicate with each other, while still accessing a shared resource like a router or gateway. This is often used in shared hosting or DMZ environments.

A. ACLs (Access Control Lists) control traffic between networks, not within the same VLAN.

B. Trunking carries multiple VLANs between switches but does not isolate devices.

C. Port security limits MAC addresses per port but doesn’t isolate communication between ports.

📘 Reference:

CompTIA Network+ N10-009 Official Objectives: 3.4 – Compare and contrast access control methods.

Introduction to Security Zones:

Security zones are logical segments within a network designed to enforce security policies and control access. They help in segregating and securing different parts of the network.

Types of Security Zones:

Trusted Zone: This is the most secure zone, typically used for internal corporate networks where only trusted users have access.

Extranet: This zone allows controlled access to external partners, vendors, or customers.

VPN (Virtual Private Network): While VPNs are used to create secure connections over the internet, they are not a security zone themselves.

Public Zone: This zone is the least secure and is typically used for public-facing services accessible by anyone.

Trusted Zone Implementation:

The trusted zone is configured to include internal corporate users and resources. Access controls, firewalls, and other security measures ensure that only authorized personnel can access this zone.

Internal network segments, such as the finance department, HR, and other critical functions, are usually placed in the trusted zone.

Example Configuration:

Firewall Rules: Set up rules to allow traffic only from internal IP addresses.

Access Control Lists (ACLs): Implement ACLs on routers and switches to restrict access based on IP addresses and other criteria.

Segmentation: Use VLANs and subnetting to segment and isolate the trusted zone from other zones.

Explanation of the Options:

A. Extranet: Suitable for external partners, not for internal-only access.

B. Trusted: The correct answer, as it provides controlled access to internal corporate users.

C. VPN: A method for secure remote access, not a security zone itself.

D. Public: Suitable for public access, not for internal corporate users.

Conclusion:

Implementing a trusted zone is the best solution for controlling access within a corporate network. It ensures that only trusted internal users can access sensitive resources, enhancing network security.

When traffic moves laterally between VMs within the same network or subnet, it is known as east-west traffic. This contrasts with north-south traffic, which refers to communication between internal and external networks.

Breakdown of Options:

A. East-west – Correct answer. This refers to traffic between internal servers or VMs, which is a common security concern.

B. Point-to-point – Point-to-point describes a direct connection between two devices, but does not specifically define lateral movement.

C. Horizontal-scaling – This refers to adding more instances or nodes in cloud computing, unrelated to traffic flow.

D. Hub-and-spoke – This network topology describes a centralized design, not lateral traffic.

Asymmetrical routing occurs when packets take different paths to and from the destination, leading to instability in network communication. The use of two different MPLS providers with OSPF can lead to this type of routing issue, especially if the paths aren ' t carefully configured and managed. This can cause unexpected routing behaviors and instability in a dual-WAN setup. (Reference: CompTIA Network+ Study Guide, Chapter on Network Routing)

A split-tunnel VPN allows a device to route some traffic through the VPN (typically corporate traffic) while sending other traffic (like general internet browsing) directly over the local internet connection. This reduces the load on the corporate network because not all traffic is routed through the VPN tunnel.

Site-to-site VPNs are for permanent links between locations.

Full-tunnel VPNs route all traffic through the VPN, increasing the bandwidth usage on the corporate network.

GRE (Generic Routing Encapsulation) is a tunneling protocol that doesn’t encrypt and doesn ' t reduce bandwidth usage by itself.

📘 Reference:

CompTIA Network+ N10-009 Official Objectives: 3.3 – Given a scenario, configure and deploy common VPN technologies.

If the IP phone works but the workstation doesn ' t, it indicates that the Voice VLAN is functioning correctly, but the Data VLAN (C) is either misconfigured or missing. The workstation typically connects through the phone, which tags voice and data traffic separately using VLANs.

A. Voice VLAN is for the IP phone, which is already working.

B. Native VLAN is for untagged traffic on trunk ports, but doesn’t control access directly.

D. Trunk port is more relevant to switch interconnections than individual workstation ports.

📘 Reference:

CompTIA Network+ N10-009 Official Objectives: 2.3 – Given a scenario, configure and verify VLANs.

Adding more access points can improve coverage, but it also increases the risk of co-channel interference if APs are configured on the same or overlapping channels. Channel overlap causes contention and interference, leading to retries, unstable performance, and symptoms that feel like frequent disconnect/reconnect events—especially in dense deployments. Network+ (N10-009) wireless troubleshooting objectives highlight proper channel planning (non-overlapping channels, appropriate channel width) as critical when increasing AP density. If adjacent APs are competing on the same channel (or overlapping channels in 2.4 GHz), clients may experience poor signal-to-noise ratios and repeated reassociations as they struggle to maintain a stable link.

Roaming misconfiguration can cause sticky clients or poor handoffs, but the classic problem introduced immediately after “adding more APs” is interference from bad channel design. Throughput capacity is about available bandwidth and airtime efficiency; it can make things slow, but it doesn’t inherently cause repeated disconnect/reconnect loops like interference does. Packet loss is a symptom that may occur due to interference, but the root cause in the options that best fits the scenario is channel overlap.

Recovery Point Objective (RPO) defines the maximum acceptable amount of data loss measured in time. If leadership states “no more than eight hours of data loss,” they are describing how far back the organization is willing to roll data after an outage or disaster—meaning backups, replication, snapshots, or journaling must ensure recoverable data is no older than eight hours. In Network+ terms, this is a core availability and resiliency planning concept: you choose an RPO based on business impact, then implement backup frequency/replication strategy to meet it. By contrast, Recovery Time Objective (RTO) is about how quickly services must be restored (downtime duration), not how much data can be lost. MTTR (Mean Time to Repair/Recover) is an operational reliability metric describing typical time to restore a system, and MTBF (Mean Time Between Failures) indicates expected time between failures—neither directly states acceptable data loss. Therefore, the metric matching “eight hours of data loss” is RPO.