McAfee Secure

Cisco 350-501 Bundle

Exam Code: 350-501

Exam Name Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR)

Certification Provider: Cisco

Corresponding Certifications: CCIE Service Provider , CCNP Service Provider

Cisco 350-501 Bundle $28.79

100% Cisco 350-501 Guaranteed Success With Testking Training Materials

Get Real 350-501 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    350-501 Questions & Answers

    528 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual 350-501 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • 350-501 Video Course

    350-501 Training Course

    253 Video Lectures

    350-501 Video Course is developed by Cisco Professionals to help you pass the 350-501 exam.

    Description

    This course will improve your knowledge and skills required to pass Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) exam.
  • Study Guide

    350-501 Study Guide

    1160 PDF Pages

    Developed by industry experts, this 1160-page guide spells out in painstaking detail all of the information you need to ace 350-501 exam.

Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) (350-501) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $189.97
Bundle Price: $161.18

Purchase Individually

  • Questions & Answers

    Questions & Answers

    528 Questions

    $124.99
  • 350-501 Video Course

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 53

Question 520

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A provider PE has the customer's IPv4 routes but another VRF with overlapping prefixes also imports them unexpectedly. Which continuing control best reduces recurrence of this problem?

  1. Exercise link failover with multicast counters and packet duplication checks.
  2. Audit customer edge marking behavior when service contracts change.
  3. Test flooding limits and MAC learning across all endpoints.
  4. Audit per-VRF RT tables against the customer service registry.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A provider PE has the customer's IPv4 routes but another VRF with overlapping prefixes also imports them unexpectedly. The most directly supported response is: Correct import/export route targets and VRF binding while retaining unique route distinguishers. Technical basis: L3VPN membership is controlled by route targets rather than IP prefix uniqueness alone. Evidence of success: Only the authorized customer VRF receives the matching VPNv4 routes. Ongoing protection: Audit per-VRF RT tables against the customer service registry.

Incorrect Answers

A:

The alternative guards against: Multicast replication follows distribution trees and requires consistent RPF and listener state. The root condition for this case is: L3VPN membership is controlled by route targets rather than IP prefix uniqueness alone. The focused prevention check is: Audit per-VRF RT tables against the customer service registry.

B:

The alternative guards against: Carrier MPLS EXP/TC treatment must follow approved classification rather than arbitrary customer marking. The root condition for this case is: L3VPN membership is controlled by route targets rather than IP prefix uniqueness alone. The focused prevention check is: Audit per-VRF RT tables against the customer service registry.

C:

The alternative guards against: E-LAN provides multipoint Ethernet membership whereas E-Line has two service endpoints. The root condition for this case is: L3VPN membership is controlled by route targets rather than IP prefix uniqueness alone. The focused prevention check is: Audit per-VRF RT tables against the customer service registry.

Question 521

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Restore underlay labeled reachability to the remote PE loopback before using the VPN path.
  2. Apply hierarchical QoS to the correct service instance and physical egress as supported.
  3. Design EVPN control-plane advertisement with tenant-specific bridge domains and approved MAC reachability.
  4. Apply explicit ingress and egress VLAN tag translation rules on the correct service instance.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. The most directly supported response is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path. Technical basis: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Evidence of success: VPN packets use the expected transport and service labels and reach the remote PE. Ongoing protection: Check layered transport and VPN label state during PE provisioning.

Incorrect Answers

B:

The option fits a control for: Hierarchical QoS can combine aggregate shaping with per-class scheduling for shared access links. The present failure is caused by a different mechanism: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The targeted implementation is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path.

C:

EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. That principle governs the alternative intervention. The issue described here is different: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The case-matched corrective action is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path.

D:

VLAN tag manipulation determines which customer frames map to each Ethernet service. That principle governs the alternative intervention. The issue described here is different: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The case-matched corrective action is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path.

Question 522

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. Which observable result most directly verifies that this network issue was resolved?

  1. Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.
  2. Participating sources and receivers use the intended bidirectional shared distribution structure.
  3. VPN packets use the expected transport and service labels and reach the remote PE.
  4. A simulated single-link failure reestablishes traffic on the ring without sustained Layer 2 looping.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. The most directly supported response is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path. Technical basis: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Evidence of success: VPN packets use the expected transport and service labels and reach the remote PE. Ongoing protection: Check layered transport and VPN label state during PE provisioning.

Incorrect Answers

A:

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: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Instead, verify: VPN packets use the expected transport and service labels and reach the remote PE.

B:

That observation tests a different mechanism: PIM-BIDIR supports a bidirectional shared-tree multicast model suited to appropriate many-to-many scenarios. It cannot establish this case, whose mechanism is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The needed verification is: VPN packets use the expected transport and service labels and reach the remote PE.

D:

That observation tests a different mechanism: G.8032 coordinates ring protection switching to maintain connectivity while preventing Ethernet loops. It cannot establish this case, whose mechanism is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The needed verification is: VPN packets use the expected transport and service labels and reach the remote PE.

Question 523

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. Which underlying network infrastructure principle best explains the situation?

  1. MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution.
  2. Ethernet OAM can measure service connectivity independently of customer Layer 3 routing.
  3. Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery.
  4. Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. The most directly supported response is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path. Technical basis: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Evidence of success: VPN packets use the expected transport and service labels and reach the remote PE. Ongoing protection: Check layered transport and VPN label state during PE provisioning.

Incorrect Answers

B:

The alternative principle describes: Ethernet OAM can measure service connectivity independently of customer Layer 3 routing. In this question, the decisive mechanism is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. In this question, the decisive mechanism is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. These are distinct technical causes, even when they share a platform.

D:

The alternative principle describes: Inter-AS VPN designs extend customer VPN transport across separate service provider administrative domains. In this question, the decisive mechanism is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. These are distinct technical causes, even when they share a platform.

Question 524

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. Which continuing control best reduces recurrence of this problem?

  1. Monitor MLD membership expiry and snooping behavior on access switches.
  2. Check layered transport and VPN label state during PE provisioning.
  3. Validate route-target separation and transport label continuity at interprovider handoffs.
  4. Validate every UNI and EVC membership during order fulfillment.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A remote VPNv4 prefix appears in BGP but forwarding fails because the labeled BGP next hop is not reachable through the MPLS backbone. The most directly supported response is: Restore underlay labeled reachability to the remote PE loopback before using the VPN path. Technical basis: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Evidence of success: VPN packets use the expected transport and service labels and reach the remote PE. Ongoing protection: Check layered transport and VPN label state during PE provisioning.

Incorrect Answers

A:

That recurring practice manages a separate exposure: MLD manages IPv6 multicast listener subscriptions, playing a role analogous to IGMP for IPv4. The present case instead depends on: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The suitable ongoing safeguard is: Check layered transport and VPN label state during PE provisioning.

C:

That recurring practice manages a separate exposure: Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. The present case instead depends on: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The suitable ongoing safeguard is: Check layered transport and VPN label state during PE provisioning.

D:

E-Line services are point-to-point Carrier Ethernet constructs rather than arbitrary LAN segments. Maintaining that control would not track the failure described here. The relevant risk is: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. Review this instead: Check layered transport and VPN label state during PE provisioning.

Question 525

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use a carrier-supporting-carrier VPN architecture with isolated downstream carrier reachability.
  2. Deploy IGMPv3 when the service requires explicit include/exclude source membership.
  3. Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy.
  4. Configure supported ITU-T G.8032 Ethernet Ring Protection with the intended blocked ring link.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. The most directly supported response is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy. Technical basis: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Evidence of success: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes. Ongoing protection: Validate route-leak exceptions and default-route scope at every service change.

Incorrect Answers

A:

Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. That principle governs the alternative intervention. The issue described here is different: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. The case-matched corrective action is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy.

B:

IGMPv3 extends group membership to source-specific reception; older IGMP versions differ. That principle governs the alternative intervention. The issue described here is different: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. The case-matched corrective action is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy.

D:

The proposed option addresses this separate mechanism: G.8032 coordinates ring protection switching to maintain connectivity while preventing Ethernet loops. The stated problem instead depends on: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. The required response is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy.

Question 526

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. Which observable result most directly verifies that this network issue was resolved?

  1. RPF state points toward the selected source path and expected packets forward downstream.
  2. Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes.
  3. A simulated single-link failure reestablishes traffic on the ring without sustained Layer 2 looping.
  4. Measured traffic conforms to agreed rate and burst limits without unnecessary application loss.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. The most directly supported response is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy. Technical basis: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Evidence of success: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes. Ongoing protection: Validate route-leak exceptions and default-route scope at every service change.

Incorrect Answers

A:

That observation tests a different mechanism: Multicast reverse-path forwarding prevents looping traffic by checking upstream source reachability. It cannot establish this case, whose mechanism is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. The needed verification is: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes.

C:

G.8032 coordinates ring protection switching to maintain connectivity while preventing Ethernet loops. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. A passing check should show: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes.

D:

Traffic shaping buffers and paces excess traffic while policing typically drops or remarks nonconforming packets. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. A passing check should show: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes.

Question 527

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. Which underlying network infrastructure principle best explains the situation?

  1. E-Tree service semantics restrict leaf connectivity while allowing designated roots.
  2. Multicast reverse-path forwarding prevents looping traffic by checking upstream source reachability.
  3. Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation.
  4. Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. The most directly supported response is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy. Technical basis: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Evidence of success: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes. Ongoing protection: Validate route-leak exceptions and default-route scope at every service change.

Incorrect Answers

A:

E-Tree service semantics restrict leaf connectivity while allowing designated roots. That is not the causal relationship tested by the current facts. The relevant principle is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation.

B:

Multicast reverse-path forwarding prevents looping traffic by checking upstream source reachability. That is not the causal relationship tested by the current facts. The relevant principle is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation.

D:

Carrier-supporting-carrier separates wholesale transport from the subordinate carrier's own VPN routing. That is not the causal relationship tested by the current facts. The relevant principle is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation.

Question 528

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. Which continuing control best reduces recurrence of this problem?

  1. Monitor MLD membership expiry and snooping behavior on access switches.
  2. Validate route-leak exceptions and default-route scope at every service change.
  3. Audit customer edge marking behavior when service contracts change.
  4. Monitor MAC mobility and route-target imports after adding remote sites.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A service provider offers customer VPN Internet breakout but the shared Internet VRF mistakenly receives private VPN routes from every tenant. The most directly supported response is: Use controlled route leaking or a shared-services VRF with narrow authorized import/export policy. Technical basis: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Evidence of success: Tenant traffic reaches the permitted Internet gateway without exposing unrelated private tenant prefixes. Ongoing protection: Validate route-leak exceptions and default-route scope at every service change.

Incorrect Answers

A:

MLD manages IPv6 multicast listener subscriptions, playing a role analogous to IGMP for IPv4. Maintaining that control would not track the failure described here. The relevant risk is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Review this instead: Validate route-leak exceptions and default-route scope at every service change.

C:

Carrier MPLS EXP/TC treatment must follow approved classification rather than arbitrary customer marking. Maintaining that control would not track the failure described here. The relevant risk is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. Review this instead: Validate route-leak exceptions and default-route scope at every service change.

D:

The alternative guards against: EVPN distributes Ethernet reachability through BGP control-plane information and service-specific isolation. The root condition for this case is: Shared services require explicit VRF route exchange boundaries to preserve multi-tenant isolation. The focused prevention check is: Validate route-leak exceptions and default-route scope at every service change.

Question 529

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. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Publish only necessary service prefixes and return reachability through controlled extranet VRF policies.
  2. Use PIM-SSM with an appropriate source-specific membership protocol.
  3. Use Ethernet OAM continuity and fault-management measurements for the specified EVC.
  4. Combine marking with validated scheduling, capacity planning, and traffic admission controls.

Explanation

Correct Answer

A:

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

B:

The proposed option addresses this separate mechanism: Source-Specific Multicast explicitly binds receivers to a source and group, typically avoiding RP-based discovery. The stated problem instead depends on: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. The required response is: Publish only necessary service prefixes and return reachability through controlled extranet VRF policies.

C:

The option fits a control for: Ethernet OAM can measure service connectivity independently of customer Layer 3 routing. The present failure is caused by a different mechanism: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. The targeted implementation is: Publish only necessary service prefixes and return reachability through controlled extranet VRF policies.

D:

The option fits a control for: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. The present failure is caused by a different mechanism: An MPLS L3VPN extranet selectively shares service routes while retaining tenant separation. The targeted implementation is: Publish only necessary service prefixes and return reachability through controlled extranet VRF policies.

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?

  1. Leaf-to-root traffic succeeds and unauthorized leaf-to-leaf traffic is denied.
  2. Downstream carrier VPN traffic crosses the wholesale backbone while unrelated customer routes remain isolated.
  3. Each tenant reaches the DNS service without receiving another tenant's private routes.
  4. Under full load, traffic receives the planned queue share and premium latency stays within SLA.

Explanation

Correct Answer

C:

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

A:

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.

B:

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.

D:

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.