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
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
Architectural plane separation and interface distinction between traditional and controller-based networks
Tahmini Süre:1m 0s