Recording and monitoring all activity at the cabinet greatly strengthens security by providing a real-time deterrent, an audit trail of who accessed it and when, and forensic evidence if an incident ever occurs.

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.

Comprehensive and Detailed Explanation From Exact Extract:
A data lake is ideal for aggregating structured and unstructured data at scale. It supports storage and analysis of logs, performance metrics, and other telemetry data from various sources. Data lakes enable advanced analytics and machine learning for decision support.
Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide - under "Data Aggregation and Analytics":
"Data lakes allow storage and analysis of high-volume, diverse data types, including logs and monitoring data. They support enterprise-wide visibility and strategic decision-making." Other options:
* A. Relational databases are optimized for structured data and are less scalable for log aggregation.
* B. CDNs deliver content, not used for data aggregation.
* C. CIEM (Cloud Infrastructure Entitlement Management) governs cloud permissions, not logging.

Comprehensive and Detailed Explanation From Exact Extract:
Layer 2 client isolation ensures that devices connected to the same wireless network (such as a guest SSID) cannot communicate with each other or other VLANs. This prevents guest users from scanning or attacking internal devices. It's a fundamental security control for guest Wi-Fi access.
Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide - under "Wireless Network Segmentation and Security":
"Client isolation prevents peer-to-peer attacks over Wi-Fi by ensuring wireless clients cannot communicate with one another, a necessary control on shared guest networks." Other options:
* B. MAC filtering is easy to spoof and hard to manage at scale.
* C. Strong passwords improve access control but don't isolate guest traffic.
* D. Captive portals add a registration layer but don't address VLAN or broadcast isolation.

Comprehensive and Detailed Explanation From Exact Extract:
A collapsed core design combines the core and distribution layers into a single tier, making it ideal for small- scale networks such as satellite campuses or branch offices. It reduces complexity, cost, and footprint while still supporting redundancy and scalability where needed.
Relevant Extract from CompTIA CloudNetX CNX-001 Study Guide - under "Network Design Models":
"For small to medium-sized deployments, a collapsed core topology reduces hardware and configuration complexity while maintaining essential functionality." Other options:
* A. Hybrid refers to cloud/physical blends, not network topology.
* B. Dual-layer isn't a standard enterprise architecture reference.
* C. Three-tier is overkill for small networks and adds unnecessary complexity.