Examkin

Question

Difficulty: EasyComparing Traditional Networks with Controller-Based Networking

Match each operational feature or interface component to its correct classification when comparing traditional network architectures with controller-based software-defined networks (SDN).

  • Routing protocols run locally on each device to compute paths independentlyTraditional Network Distributed Control Plane
  • RESTful APIs used by management applications to communicate policy intent to the network controllerController-Based Northbound Interface (NBI)
  • Protocols such as NETCONF or OpenFlow used by the controller to program network device forwarding tablesController-Based Southbound Interface (SBI)
  • Manual node-by-node configuration applied directly via SSH or console command-line interfaceTraditional Network Decentralized Management Plane

Answer

Independent protocol path computation matches Traditional Network Distributed Control Plane; RESTful APIs for application-to-controller policy intent match Controller-Based Northbound Interface (NBI); NETCONF/OpenFlow for controller-to-device programming matches Controller-Based Southbound Interface (SBI); Node-by-node CLI configuration matches Traditional Network Decentralized Management Plane.
In traditional networking, control plane processing and management operations are decentralized across every network node. Conversely, controller-based SDN centralizes the control plane into a single logical controller, using Northbound APIs (REST) to expose network services to applications and Southbound APIs (NETCONF, RESTCONF, OpenFlow) to program policy onto hardware devices.

Step-by-Step Solution

1
Analyze how control plane decisions are processed in traditional networks.
Identify that traditional networks distribute control plane processing across every individual device.
Each switch and router maintains its own control plane intelligence and routing protocols.
2
Identify the API direction connecting applications to the central controller.
Recognize that interfaces facing upward toward applications are Northbound Interfaces (NBIs).
Northbound APIs allow software applications to programmatically convey network requirements to the SDN controller.
3
Identify the API direction connecting the central controller to forwarding hardware.
Recognize that interfaces facing downward toward network nodes are Southbound Interfaces (SBIs).
Southbound protocols like NETCONF, RESTCONF, and OpenFlow carry instructions from the controller to network switches and routers.
4
Evaluate traditional device management practices.
Identify manual box-by-box CLI access as a characteristic of traditional management planes.
Unlike controller-driven centralized policy pushing, traditional management relies on individual device CLI interaction.

Key Concept

Architectural plane separation and interface distinction between traditional and controller-based networks
Estimated Time:1m 0s
Rate this question

Topics

Comparing Traditional Networks with Controller-Based Networking

More questions from this topic