CompTIA N10-009 Dumps for the CompTIA Network+ Certification Exam 2026

The correct answer is /25, which is the appropriate subnet mask for dividing an existing Class C network into two equal subnets. According to the CompTIA Network+ N10-009 objectives, subnetting is a core networking concept used to improve network segmentation, performance, and security.

A Class C network uses a default subnet mask of /24 (255.255.255.0), which provides 256 total addresses (254 usable). To split this network into two sections, the administrator must borrow one host bit from the last octet. Borrowing one bit results in a /25 subnet mask (255.255.255.128). This creates two subnets, each with 128 total addresses (126 usable)---an ideal solution for separating two departments such as finance and marketing.

A /24 would not create any segmentation, as it represents the original single network. A /26 would create four subnets, and a /27 would create eight subnets, both of which exceed the requirement of only two sections and unnecessarily reduce the number of available host addresses per subnet.

The Network+ objectives emphasize selecting subnet masks based on organizational requirements, balancing the number of subnets with sufficient host capacity. In this scenario, /25 is the most efficient and correct choice.

The correct answer is B. Spanning tree. At the distribution layer, switch redundancy is common because multiple paths are usually built into the design to avoid a single point of failure. The problem with redundant Layer 2 paths is that they can create switching loops, broadcast storms, and unstable MAC address tables if nothing controls them. Spanning Tree Protocol solves that problem by logically blocking one or more redundant paths while still keeping those paths available as backups.

That makes spanning tree the best fit for a feature that supports both redundancy and safe scaling. As the switched environment grows, STP helps maintain a stable topology and prevents loop-related failures. If the active path fails, a blocked redundant path can be brought into service.

The other options do not address the real need. VLAN assignment is used to segment broadcast domains, but it does not manage redundant Layer 2 paths. Port speed only affects throughput on an interface. Full duplex improves communication efficiency on a link, but it also does not provide redundancy control or loop prevention.

When a Network+ question mentions redundancy on switches and asks for the best switching feature, spanning tree is the strongest answer.

SSO (Single Sign-On) allows an organization to use an identity provider (IdP) to centrally manage authentication and access across multiple SaaS applications. In the Network+ (N10-009) objectives, identity and access management concepts include federated authentication, centralized account control, and reducing password sprawl. With SSO, users authenticate once to the IdP, and the IdP then provides assertions/tokens to SaaS services (commonly using federation standards such as SAML or OIDC in real environments). This improves security (fewer reused passwords, easier MFA enforcement), streamlines user experience, and simplifies administration (provisioning/deprovisioning from one place).

PKI supports certificates and encryption/signing, but it is not the core mechanism for managing access across many SaaS apps via an IdP. TACACS+ is typically used for device administration (AAA) on network equipment, and RADIUS commonly supports network access (802.1X, VPN) AAA---both are important AAA protocols but do not describe the SaaS-wide ''one login across many apps'' capability. Therefore, SSO is the best answer.

===========

Definition of GDPR:

General Data Protection Regulation (GDPR) is a regulation in EU law on data protection and privacy for all individuals within the European Union and the European Economic Area. It also addresses the transfer of personal data outside the EU and EEA areas.

Scope and Objectives:

GDPR aims to give individuals control over their personal data and to simplify the regulatory environment for international business by unifying the regulation within the EU.

It enforces rules about data protection, requiring companies to protect the personal data and privacy of EU citizens for transactions that occur within EU member states.

Comparison with Other Options:

SCADA (Supervisory Control and Data Acquisition): Refers to control systems used in industrial and infrastructure processes, not related to personal data protection.

SAML (Security Assertion Markup Language): A standard for exchanging authentication and authorization data between parties, not specifically for personal data protection.

PCI DSS (Payment Card Industry Data Security Standard): A set of security standards designed to ensure that all companies that accept, process, store or transmit credit card information maintain a secure environment, not specific to personal data protection in Europe.

Key Provisions:

GDPR includes provisions for data processing, data subject rights, obligations of data controllers and processors, and penalties for non-compliance.

CompTIA Network+ study materials on regulatory and compliance standards.

The problem is a subnet mismatch. The web server is using 255.255.255.0, which places it in the 192.168.1.0/24 network. The database server is using 255.255.255.128, which places 192.168.1.201 in the 192.168.1.128/25 network. So even though both addresses begin with 192.168.1, the two systems are not treating the network boundaries the same way.

That creates a Layer 3 communication issue because one host may believe the other device is local while the other host may treat traffic differently based on its smaller subnet. In a normal server segment like this, both systems should agree on the same mask if they are intended to be on the same network.

Changing the database server's subnet mask to 255.255.255.0 fixes that inconsistency immediately. Then both servers and the firewall interface are using the same local network definition, and traffic can be handled properly.

The other options do not solve the real issue. Changing the firewall to /25 would break consistency for the rest of the segment. Pointing the database server to 1.2.3.4 is incorrect because that is outside the local subnet and appears to be an upstream route. Changing the IP to 192.168.1.150 still leaves the wrong mask in place. The clean fix is A.