What is the function of a control-plane node in a Cisco SD-Access solution?

Question

Options

• Ato run a mapping system that manages endpoint to network device relationships
• Bto implement policies and commun cate with networks outside the fabric
• Cto connect external Layer 3 networks to the SD Access fabric.
• Dto connect APs and wireles endpoints to the SD-Access fabric

• A
  86% (49)
• B
  4% (2)
• C
  9% (5)
• D
  2% (1)

Explanation

SD-Access Control-Plane Node Explanation

In Cisco SD-Access, the control-plane node hosts the LISP (Locator/ID Separation Protocol) mapping system, which tracks and manages the relationships between endpoints (their identity/EID) and the network devices (RLOCs) they are connected to - essentially acting as a "directory service" for the fabric. This makes Option A correct, as it accurately describes this registration and lookup function.

Why the distractors are wrong:

• Option B describes the policy-plane node (Border + Policy Extended Node) or the SD-Access fabric's border node, which handles policy enforcement and external communications
• Option C describes the border node, which is specifically responsible for connecting external Layer 3 networks to the SD-Access fabric
• Option D describes the edge node, which is the point where APs, wired, and wireless endpoints physically connect to the fabric

Memory Tip: Think of the Control-Plane node as the "Phone Book" of the network - just like a phone book maps a name (endpoint identity) to a address (network location), the control-plane node maps endpoints to their network device locations using LISP. Control = Catalog of endpoints!

No community discussion yet for this question.