What is the key design principle for the core layer when using a classic hierarchical network model?

The design sequence described is not a key design principle of the core layer itself; requirements-gathering typically starts at the access layer and the core is sized to accommodate aggregated traffic.

Controlling access to resources for security is the role of the distribution layer, which enforces policy boundaries between access and core.

Providing server access is a function of the access or distribution layer; the core layer connects distribution blocks and does not directly serve end devices or servers.

The core layer's sole purpose is high-speed, reliable switching of traffic between distribution layer devices, so any complexity such as ACLs, QoS policies, or packet manipulation adds latency and increases the risk of misconfiguration. Cisco's hierarchical design model explicitly recommends keeping the core free of feature-heavy configurations. Minimal complexity also improves stability and simplifies troubleshooting during outages.