Free Practice Questions for CompTIA CNX-001 Exam

Comprehensive and Detailed Explanation From Exact Extract:

An Allow List (also known as Whitelisting) is the most restrictive firewall rule approach. It blocks all traffic by default and only permits explicitly defined trusted IPs, URLs, or applications. This minimizes the attack surface and ensures that only known, safe traffic is allowed into the network.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Firewall and Security Rule Configuration”:

“Whitelisting or Allow Listing enforces a default-deny security posture by permitting only specified trusted sources. This approach offers the highest level of control and reduces exposure to unknown threats.”

Other options:

A. URL filtering restricts content access but is not as strict as allow lists.

B. File blocking targets malicious payloads but doesn’t limit traffic sources.

C. Network Security Groups (NSGs) are effective but broader in scope; they use allow/deny rules but may not be as tightly controlled as explicit allow lists.

Comprehensive and Detailed Explanation From Exact Extract:

SD-WAN (Software-Defined Wide Area Network) enables private, encrypted connections over public internet links and supports policy-based routing for application-aware traffic steering. It offers centralized management, redundancy, and automatic path selection — all aligned with the stated requirements.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Software-Defined Networking and WAN Optimization”:

“SD-WAN uses secure tunnels over the public internet, supports dynamic path selection, and provides application-aware routing, making it ideal for multi-site enterprise connectivity without dedicated links.”

Other options:

A. MPLS requires dedicated circuits and is costly.

C. Site-to-site VPN provides security but lacks intelligent traffic steering.

D. ExpressRoute is a private connection to Azure, not suited for general internet-based multi-site connectivity.

Comprehensive and Detailed Explanation From Exact Extract:

The WBS (Work Breakdown Structure) is the document that outlines all project tasks, associated timelines, and deliverables. Since the project timeline has significantly deviated from its original estimates, updating the WBS will allow for accurate tracking, reallocation of resources, and setting new expectations. It directly reflects the phase durations and current project status.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Project and Lifecycle Documentation”:

“A Work Breakdown Structure provides a detailed timeline and scope of project tasks. Revisions to WBS are essential when milestones or phase durations change significantly.”

Other options:

A. BIA (Business Impact Analysis) deals with criticality, not project scheduling.

B. SLA (Service Level Agreement) defines performance guarantees, not project phases.

C. SOW (Statement of Work) outlines scope and deliverables but doesn't track current status or time spent.

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

Comprehensive and Detailed Explanation From Exact Extract:

Using an active-active deployment across two regions with at least two Availability Zones (AZs) each provides the highest level of fault tolerance and geographic redundancy. This ensures continuity even if an entire region or multiple zones become unavailable. In regulated sectors such as healthcare, this meets strict availability and disaster recovery requirements.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “High Availability and Multi-Region Design”:

“Active-active configurations across multiple regions and availability zones maximize uptime and ensure failover in the event of localized or regional failures.”

Other options:

B. Active-passive introduces delays in failover.

C. Active-active in one region offers no geographic redundancy.

D. Active-passive in two regions is slower and less efficient during failover.

Comprehensive and Detailed Explanation From Exact Extract:

The traceroute shows that the traffic successfully passes through the application development network (192.168.2.1), to the server segment gateway (192.168.1.1), and reaches the serversegment firewall (192.168.4.1). However, it times out immediately after hitting 192.168.4.1, indicating that the traffic is being dropped or filtered at that firewall.

Because other users (outside of the application development segment) are able to SSH into the database server (192.168.1.9), the issue is not with the database server itself or the core network. This points to the server segment firewall blocking traffic originating from the application development subnet (192.168.2.0/24), which is a common practice in segmented network designs unless proper access rules are defined.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Network Segmentation and Firewall Rules”:

“Firewalls between network segments may enforce security policies that restrict access based on source/destination IP and port. Lack of proper allow rules can result in blocked traffic even if routing is successful.”

Other options:

A. The core firewall is not in the traceroute path; it is irrelevant to this specific flow.

B. NSGs (Network Security Groups) apply to cloud workloads, but the behavior and hop-by-hop flow suggest it is a firewall-level issue, not NSG misconfiguration.

D. Bandwidth issues would typically show packet loss or high latency, not consistent timeouts at a specific hop.