In a Nexus Dashboard Orchestrator Multi-Site deployment, an engineer needs to configure a Layer 3 Out (L3Out) that is defined once and consumed consistently by multiple sites, while allowing each site to have site-specific parameters (e.g., different physical interfaces, IP addressing, or router IDs per site). Which NDO template concept supports this "define once, customize per site" pattern?
- A. VRF Route Leaking configured independently per site with no shared template
- B. Manually creating a fully separate, unrelated L3Out configuration on each site's local APIC with no NDO involvement
- C. A single fully Site-Local Template with no shared/global objects at all
- D. A Template object defined at the schema/global level (e.g., the L3Out logical definition) with site- specific properties supplied via each site's Site-Local Template values for that same object
Reveal Solution
Discussion