CompTIA Updated CNX-001 Exam Questions and Answers by izabella

Comprehensive and Detailed Explanation From Exact Extract:

Network flow logging (e.g., AWS VPC Flow Logs, Azure NSG Flow Logs, or GCP VPC Flow Logs) is a cloud-native feature that records metadata about network conversations, including source and destination IPs, ports, and traffic volume. It does not capture payloads but provides detailed flow-level insight without requiring agents or intrusive configuration changes, making it the most efficient and least effort solution.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Cloud-native Network Monitoring”:

“Network flow logging provides metadata about traffic within cloud VPCs and is used for visibility, troubleshooting, and security auditing without packet inspection.”

Other options:

B. SNMP traps monitor device health, not traffic flows.

C. QoS tagging controls traffic priority but doesn’t log flows.

D. Monitoring agents collect system-level metrics and logs, but require installation and configuration.

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

Comprehensive and Detailed Explanation From Exact Extract:

SD-WAN (Software-Defined Wide Area Networking) is ideal for enterprises that want to simplify WAN management, reduce operational overhead, and optimize connectivity to cloudservices. SD-WAN provides intelligent traffic routing, dynamic path selection, and direct-to-cloud access without backhauling traffic through a central data center.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “SD-WAN and Cloud Connectivity”:

“SD-WAN enables efficient cloud access from branch offices and simplifies management through centralized policy control. It is cost-effective and reduces the need for complex hardware configurations and manual routing.”

Other options:

B. Adds latency and overhead by backhauling through headquarters.

C. MPLS is expensive and less flexible than SD-WAN.

D. Dark fiber is high-cost and not scalable for cloud-first architectures.

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

Comprehensive and Detailed Explanation From Exact Extract:

Round-robin DNS is a simplistic form of load balancing that does not perform health checks. If one of the four servers is down, DNS will still resolve its IP to 25% of users, resulting in failed connections. This matches the symptom of 25% failure rate — 1 out of 4.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Load Balancing Techniques and Availability”:

“Round-robin DNS distributes requests without regard for health status. Without external health checks, failed servers will continue to receive traffic, leading to partial service disruptions.”

Other options:

B. The percentages do not align with a 25% failure rate.

C. Least-connection algorithms usually have integrated health checks.

D. If health checks are active, the load balancer would not forward requests to a failed server.

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

Comprehensive and Detailed Explanation From Exact Extract:

With GitOps, all infrastructure changes are tracked as code and committed to version-controlled repositories. When the main branch is protected, changes should not be committed directly. Instead, best practices require that a new feature or change branch be created, followed by a pull request (PR) for peer review and approval before merging into the protected branch.

Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide — under “Infrastructure as Code and GitOps”:

“In GitOps workflows, changes are made in feature branches, reviewed via pull requests, and merged into protected branches only after validation, ensuring auditability and control over infrastructure deployments.”

Other options:

A. Direct commits to protected branches are restricted and violate GitOps practices.

C. The development branch may exist, but the question specifies main is the default, and the correct process requires a PR.

D. Rebase is for integrating histories, not submitting approved changes.