An airport authority is designing the civic data-center handoff from SD-Access and must distinguish border responsibilities. Which statement correctly contrasts internal and external border roles at a conceptual level?
Select an answer to reveal the explanation.
Short Explanation
Picture doors on a terminal: one opens to the secure ops wing you already trust, another opens to the wild outside world. Internal borders face known internal networks like a civic DC or shared services. External borders face outside/WAN/Internet-style realms with tougher trust and routing assumptions—names that actually change design choices.
Full Explanation
In SD-Access design language, internal borders interconnect the fabric to known enterprise-internal domains (data center, shared services, other internal routing domains), while external borders interconnect toward external or less-trusted domains such as Internet or certain WAN exteriors. The distinction drives fusion, default-route, security, and reciprocity expectations. It is not merely a labeling convenience, nor is it defined as “L2-only versus WLC-only.”