Question 760
A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Which shortcut would be most likely to undermine this objective?
Explanation
Correct Answer
This is the unsafe shortcut to avoid: enable unrestricted route redistribution for every tenant to make a single external peering session work. It violates the principle that connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. An appropriate alternative is to create or correct a scoped connectivity template and routing policy for the authorized VRF.
Incorrect Answers
The option “Announce every local routing-zone prefix to all external peers instead of reviewing policy” is useful in a different setting: A route export template applied to a border device advertises all tenant prefixes beyond the data center. The case being tested is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.
“Configure every virtual network as a tagged VLAN on the server trunk for convenience” is relevant to a different condition: A hypervisor's trunk must carry two allowed application VLANs while leaving unrelated tenant segments inaccessible. The stated question instead concerns: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.
“Create an unrelated VRF for each VLAN without validating the tenant's routing requirements” is associated with a distinct issue: A multirack tenant needs two segmented application subnets while sharing a common VRF routing domain. By contrast, the actual problem is: A tenant needs a dedicated external BGP peering connection without advertising every other tenant's prefixes. Connectivity templates can describe supported external routing sessions and attach them to the intended routing zone. The directly relevant unsafe shortcut is “Enable unrestricted route redistribution for every tenant to make a single external peering session work”.