350-401 · Question #600
How does the Cisco SD-Access control plane simplify traditional routing environments?
The correct answer is B. Separation of EID and RLOC reduces the size of routing tables.. Cisco SD-Access simplifies traditional routing by separating Endpoint Identifiers (EIDs) from Routing Locators (RLOCs), which effectively reduces the size of routing tables.
Question
How does the Cisco SD-Access control plane simplify traditional routing environments?
Options
- ARouting adjacencies are no longer required.
- BSeparation of EID and RLOC reduces the size of routing tables.
- CRouters query all routes to the map server.
- DFull routing tables are shared and ensure that all routers know all paths within the underlay fabric
How the community answered
(32 responses)- A6% (2)
- B88% (28)
- C3% (1)
- D3% (1)
Why each option
Cisco SD-Access simplifies traditional routing by separating Endpoint Identifiers (EIDs) from Routing Locators (RLOCs), which effectively reduces the size of routing tables.
Routing adjacencies are still required in the underlay network to establish connectivity between fabric devices, typically using interior gateway protocols like IS-IS or OSPF.
Cisco SD-Access leverages Locator/ID Separation Protocol (LISP) to decouple the Endpoint Identifier (EID) from the Routing Locator (RLOC), meaning fabric devices only need to know RLOCs for forwarding. This separation significantly reduces the size and complexity of routing tables across the network.
Routers in SD-Access do not query *all* routes to the map server; instead, they query the map server for the RLOC of a *specific* EID when they need to forward traffic to an unknown endpoint.
SD-Access aims to simplify routing by *avoiding* the sharing of full routing tables; instead, it uses a map-and-encapsulate system (LISP) to dynamically resolve endpoint locations, preventing every router from needing full knowledge of all paths.
Concept tested: Cisco SD-Access LISP architecture
Source: https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Campus/cisco-sda-design-guide.html
Topics
Community Discussion
No community discussion yet for this question.