City fabric engineers map each agency to a Junos routing instance used as a tenant VRF on EVPN-VXLAN leaves. Which instance approach best matches common DC tenant separation at describe depth?
Select an answer to reveal the explanation.
Short Explanation
Pick the instance type that actually gives each agency its own routing brain—virtual-router/VRF-style patterns—not cosmetic renames on the master instance. If everything still lands in inet.0, you renamed the hallway signs but kept one hallway.
Full Explanation
Describe-level JN0-683 multitenancy expects suitable routing-instance types for tenant VRFs (commonly virtual-router or VRF-related patterns depending on feature set) so each agency has an independent routing context. Forwarding-only shells, master-instance reuse, or parking all IRBs in inet.0 fail to deliver tenant L3 separation. Match instance type to the overlay/VRF role the tenant requires.