A city asks whether EVPN-VXLAN DCI requires purchasing a special DCI-only switch product SKU. What should the architecture answer emphasize?
Select an answer to reveal the explanation.
Short Explanation
DCI is a role and architecture story—border or DCI gateways on supported platforms—not a scavenger hunt for a mythical "DCI-only" SKU. Buy the right box class; do not invent a product code.
Full Explanation
EVPN-VXLAN DCI uses supported border or DCI gateway roles on appropriate Juniper platforms; it does not depend on a mythical mandatory DCI-only switch product SKU invented for exams. Architecture answers should emphasize roles and capabilities—border leaf, DCI gateway, stretch model—not a unique SKU name that appears only on Design-track marketing. A leaf without a fictional DCI SKU license can still terminate VXLAN VTEPs when the platform and software support it. DCI is not restricted to SRX firewalls; QFX-class DC switches commonly fill border roles. Exam caveat: platform capability matrices still matter—some features need specific systems and software—but that is capability fit, not a single mandatory DCI SKU. Operational check: pick supported border platforms in the municipal BOM, enable EVPN-VXLAN DCI features required by the stretch model, and verify interoperability between DC borders without waiting for a nonexistent DCI-only SKU. Source border platforms from the supported EVPN-VXLAN DCI hardware list rather than from a fictional DCI-only SKU rumor. Source border platforms from the supported EVPN-VXLAN DCI hardware list rather than from a fictional DCI-only SKU rumor. Source border platforms from the supported EVPN-VXLAN DCI hardware list rather than from a fictional DCI-only SKU rumor.