Question 530
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A managed DNS platform should be reachable by several VPN tenants, but the provider copies all tenant routes into one global table. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: A managed DNS platform should be reachable by several VPN tenants, but the provider copies all tenant routes into one global table. The most directly supported response is: Publish only necessary service prefixes and return reachability through controlled extranet VRF policies. Technical basis: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. Evidence of success: Each tenant reaches the DNS service without receiving another tenant's private routes. Ongoing protection: Test symmetric routing and deny-by-default route imports.
Incorrect Answers
E-Tree service semantics restrict leaf connectivity while allowing designated roots. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. A passing check should show: Each tenant reaches the DNS service without receiving another tenant's private routes.
The proposed test would be relevant to: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The reported problem follows from: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. Instead, verify: Each tenant reaches the DNS service without receiving another tenant's private routes.
The proposed test would be relevant to: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. The reported problem follows from: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. Instead, verify: Each tenant reaches the DNS service without receiving another tenant's private routes.