How should C2 architecture handle networking and data sharing across echelons?

• A. Use scalable, interoperable networks; maintain COP and ensure secure data flows across levels.
• B. Use isolated, non-interoperable networks to protect secrets.
• C. Share all data with every level without restrictions.
• D. Centralize all data at HQ with no data flow to lower echelons.

Answer: (A)

Networking across echelons relies on scalable, interoperable networks that keep a shared picture of the battlespace and enable secure data exchange. The goal is for units from the front lines up through higher headquarters to connect using common formats and interfaces so information can flow quickly, be understood consistently, and support timely, coordinated decision-making. A centralized, accurate Common Operational Picture is built from this shared data, giving commanders at every level a true, up-to-date view of the situation and the ability to synchronize actions.

Security and governance matter as much as speed. Data must be protected by appropriate classification, need-to-know, and cyber protections so sensitive information reaches the right hands without leaking to unauthorized actors. The architecture should also be resilient and capable of handling contested or degraded networks, preserving access to essential information when conditions are tough.

Isolated networks, while protecting secrets in theory, hinder situational awareness and coordination because information cannot flow where it’s needed. Sharing all data with every level isn’t practical due to volume, relevance, and security constraints. Centralizing everything at HQ with no data flow to lower echelons destroys tempo and prevents lower echelons from acting with current visibility.