200-301 - Automation and Programmability - Section 6.1

Explain how automation impacts network management, compare traditional networks with controller-based and software-defined architectures (overlay, underlay, fabric, control/data plane separation, northbound/southbound APIs), and compare traditional with cloud-based and Cisco Catalyst Center management.

Explain how automation reduces manual, error-prone CLI work and improves consistency, then contrast a traditional distributed control plane with a controller-based model where the control plane is centralised and separated from the data plane. Map the overlay, underlay, and fabric of an SDN architecture, and the northbound (controller-to-application) and southbound (controller-to-device) APIs, and recognise where v1.1 cloud network management fits versus on-box CLI and Catalyst Center.

Network automationController-based networkingControl plane vs data planeNorthbound and southbound APIsCloud network management

Practice question for this objective

Free sampleAutomation and Programmabilitymedium

A network engineer is documenting how a traditional distributed network differs from an SDN architecture that separates the control plane from the data plane. In the SDN model, which function does the centralised controller take over from the individual forwarding devices?

  • APhysically rewriting frames and pushing packets out of egress interfaces at line rate
  • BStoring the MAC address table and performing per-frame hardware lookups inside the ASIC
  • CGenerating link-state hello packets on every interface to keep neighbour adjacencies alive
  • DBuilding the forwarding logic and reachability decisions, then programming the resulting state down to the switches Correct
In SDN, the centralised controller owns the control plane and programs forwarding state into devices that retain only the data plane. Control and data plane separation means the controller centralises the intelligence that decides how traffic should be forwarded and installs that state into the network elements, while each device still performs the local job of moving packets out of its interfaces.

Why A is wrong: Tempting because the controller manages forwarding, but actually moving frames out of interfaces at line rate is the data plane function that stays on each switch, not the controller.

Why B is wrong: Per-frame ASIC lookups against the MAC table are data plane operations performed locally on the switch hardware, so this is not what the controller centralises.

Why C is wrong: This describes a traditional distributed control protocol running independently on each device, which is exactly the per-device behaviour an SDN controller replaces rather than performs on their behalf.

Why D is correct: Separating the control plane means the controller computes routing and forwarding intelligence centrally and pushes the resulting forwarding state to the devices, which keep only the data plane.

See more 200-301 practice questions, answers explained.

More in this domain

Back to all Automation and Programmability objectives, or the 200-301 cert hub.

Examworthy is not affiliated with or endorsed by Cisco. Original, blueprint-aligned practice material only.