Examkin

Question

Difficulty: MediumComparing Traditional Networks with Controller-Based Networking

When contrasting traditional distributed networking with a centralized controller-based architecture, which of the following statements accurately highlight key operational and architectural differences? (Select two.)

  1. Control plane intelligence in controller-based networks is centralized or orchestrated, communicating instructions down to edge devices via Southbound APIs such as NETCONF or RESTCONF.Answer
  2. B
    Controller-based automation relies on Ansible software agents persistently running on all managed switches to execute control plane routing decisions locally.
  3. Traditional networks require individual box-by-box configuration via CLI or SNMP on distributed nodes, whereas controller-based networks enable central policy management across the fabric.Answer
  4. D
    Centralized controllers utilize HTTP GET requests as the primary Northbound API verb to create new configuration objects and modify running operational states on edge switches.

Answer

In controller-based networking, control plane intelligence is centralized or policy-driven, relaying forwarding rules to devices via Southbound APIs (such as NETCONF or RESTCONF). Additionally, traditional networks depend on individual box-by-box management via CLI or SNMP, while controller-based networks allow network-wide policy provisioning from a single management plane.
Controller-based architectures decouple or centralize control logic, allowing network-wide policies to be deployed across devices using Southbound APIs (such as NETCONF/RESTCONF). Furthermore, while traditional networking depends on distributed control planes managed through individual CLI or SNMP sessions per device, controller-based networking provides centralized abstraction and management across the entire network fabric.

Step-by-Step Solution

1
Analyze control plane deployment and API roles in traditional vs. controller-based environments
Controller-based architectures centralize or abstract control plane logic and use Southbound APIs (NETCONF, RESTCONF, OpenFlow) to program data plane devices.
This contrasts with traditional devices where each node independently computes routes and updates local forwarding tables.
2
Compare configuration and management approaches
Traditional network management requires manual, distributed box-by-box CLI or SNMP interactions, whereas controller-based networks utilize centralized management and Northbound APIs to streamline policy deployment.
Centralized controllers provide abstraction, reducing configuration drift and operational overhead across enterprise fabrics.
3
Evaluate distractor statements for technical accuracy
Statements claiming Ansible requires resident agent daemons or that HTTP GET modifies configuration state are false.
Ansible is inherently agentless, and HTTP GET is strictly a read-only operation in RESTful architecture.

Key Concept

Comparing Traditional Networks with Controller-Based Networking
Rate this question

Topics

Comparing Traditional Networks with Controller-Based Networking

More questions from this topic