nerdexam
Cisco

300-420 · Question #291

What is the easiest way to enable SD-Access for all your remote sites after you have your campus SD-Access fabric up and running?

The correct answer is A. Treat all the sites as one fabric domain and use the traditional physical network as the underlay. The easiest way to extend a campus SD-Access fabric to remote sites is by treating all sites as part of a single fabric domain, leveraging the existing traditional physical network as the underlay for fabric transport.

Advanced Enterprise Campus Networks

Question

What is the easiest way to enable SD-Access for all your remote sites after you have your campus SD-Access fabric up and running?

Options

  • ATreat all the sites as one fabric domain and use the traditional physical network as the underlay.
  • BUse a separate fabric domain for each site and use the traditional physical network as the
  • CUse a separate fabric domain for each site and use SD-WAN as the underlay
  • DTreat all the sites as one fabric domain and use SD-WAN as the underlay

How the community answered

(63 responses)
  • A
    94% (59)
  • B
    2% (1)
  • C
    2% (1)
  • D
    3% (2)

Why each option

The easiest way to extend a campus SD-Access fabric to remote sites is by treating all sites as part of a single fabric domain, leveraging the existing traditional physical network as the underlay for fabric transport.

ATreat all the sites as one fabric domain and use the traditional physical network as the underlay.Correct

Extending the campus SD-Access fabric as a single logical domain over the existing traditional physical network (such as a routed WAN or MPLS) minimizes new infrastructure deployment and configuration overhead, making it the simplest integration path. This approach allows the LISP control plane and VXLAN data plane of the fabric to span across the existing WAN infrastructure, simplifying overall management.

BUse a separate fabric domain for each site and use the traditional physical network as the

Managing separate fabric domains for each remote site increases administrative complexity and operational overhead compared to a single unified fabric domain.

CUse a separate fabric domain for each site and use SD-WAN as the underlay

Deploying a separate SD-WAN solution as an underlay for each remote site's separate fabric domain introduces significant additional complexity and management burden, making it far from the easiest approach.

DTreat all the sites as one fabric domain and use SD-WAN as the underlay

While a single fabric domain simplifies management, introducing a new SD-WAN solution specifically to act as the underlay for the SD-Access fabric adds a new layer of technology and deployment effort that may not be simpler than leveraging an existing traditional physical underlay.

Concept tested: SD-Access remote site integration

Source: https://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/sda-design-guide/sda_remote_sites.html

Topics

#SD-Access Extension#Multi-site Fabric#Fabric Underlay#WAN Integration

Community Discussion

No community discussion yet for this question.

Full 300-420 Practice