McAfee-Secured Website

Exam 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 Video 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

    Video Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 72

Question 710

Following a supported configuration correction, the original issue was: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. Which observation verifies success?

  1. A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change.
  2. Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding.
  3. A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.
  4. An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree.

Explanation

Correct Answer

C:

A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes. This confirms the approved response: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation. It is relevant because: VPN routing can preserve stale more-specific or static routes that override newly learned paths.

Incorrect Answers

A:

A remote VRF installs the approved CE prefix and unrelated customer VRFs show no route change. This would validate ANOTHER scenario: A CE-PE BGP session successfully exchanges routes but a newly provisioned customer VRF has no route targets and none of its routes propagate to distant PEs. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

B:

Label disposition places the test prefix into the intended customer VRF with no cross-tenant forwarding. This would validate ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

D:

An IPTV test stream reaches all authorized receivers while transit replication follows the intended efficient tree. This would validate ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. The specific correction here is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

Question 711

At a carrier automation platform team, an engineer examines: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. Which technical principle is most applicable?

  1. L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels.
  2. Shared Internet or extranet services require symmetric routing or supported translation for the return path.
  3. Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters.
  4. VPN routing can preserve stale more-specific or static routes that override newly learned paths.

Explanation

Correct Answer

D:

VPN routing can preserve stale more-specific or static routes that override newly learned paths. This explains the investigated issue: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. The approved corrective response is: Update the PE-CE routing and VPNv4 advertisement then withdraw obsolete routes after reachability validation.

Incorrect Answers

A:

L3VPN path choice is influenced by per-service routing policy in addition to reachability and transport labels. That explains a DIFFERENT scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. The mechanism to prioritize for this question is: VPN routing can preserve stale more-specific or static routes that override newly learned paths.

B:

Shared Internet or extranet services require symmetric routing or supported translation for the return path. That explains a DIFFERENT scenario: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. The mechanism to prioritize for this question is: VPN routing can preserve stale more-specific or static routes that override newly learned paths.

C:

Traffic shaping delays excess traffic to conform to a rate, with behavior shaped by token and queue parameters. That explains a DIFFERENT scenario: A traffic shaper is configured with a committed rate lower than the contracted customer rate and drops bursts even though physical uplink capacity is idle. The mechanism to prioritize for this question is: VPN routing can preserve stale more-specific or static routes that override newly learned paths.

Question 712

For a carrier automation platform team, the change record describes: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. What preventive validation should be standard?

  1. Include stale route and next-hop cleanup in VPN site migrations.
  2. Audit bidirectional prefix scope and service ACLs on extranet changes.
  3. Inspect per-VRF service-label mapping after platform or route-policy changes.
  4. Audit tenant RT policies for EVPN IP prefix advertisements.

Explanation

Correct Answer

A:

Include stale route and next-hop cleanup in VPN site migrations. This helps prevent recurrence of the issue: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. Acceptance evidence should be: A packet trace to the moved prefix follows the new PE while the retired next hop disappears from service routes.

Incorrect Answers

B:

Audit bidirectional prefix scope and service ACLs on extranet changes. That is a sensible control for ANOTHER scenario: A shared-services DNS VRF must serve three customer VRFs, but engineers import full customer route tables into the DNS VRF and unintentionally create broad extranet connectivity. It is less targeted to this issue than: Include stale route and next-hop cleanup in VPN site migrations.

C:

Inspect per-VRF service-label mapping after platform or route-policy changes. That is a sensible control for ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. It is less targeted to this issue than: Include stale route and next-hop cleanup in VPN site migrations.

D:

Audit tenant RT policies for EVPN IP prefix advertisements. That is a sensible control for ANOTHER scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. It is less targeted to this issue than: Include stale route and next-hop cleanup in VPN site migrations.

Question 713

For a multi-tenant data transport provider, the failure is: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. Which authorized correction best addresses it?

  1. Activate the IPv6 unicast address family and required export policies on both intended peers.
  2. Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.
  3. Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.
  4. Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.

Explanation

Correct Answer

C:

Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported. This directly addresses the fictional service-provider network case: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The technical mechanism is: BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution. Verify success by: A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.

Incorrect Answers

A:

Activate the IPv6 unicast address family and required export policies on both intended peers. This would respond to a DIFFERENT fictional service-provider network issue: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. It does not directly address the current situation: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes.

B:

Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border. This would respond to a DIFFERENT fictional service-provider network issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. It does not directly address the current situation: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes.

D:

Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment. This would respond to a DIFFERENT fictional service-provider network issue: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. It does not directly address the current situation: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes.

Question 714

After fixing the following network problem, what should the team verify: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes.

  1. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.
  2. The prefix becomes usable with a resolved next hop while the IGP remains stable.
  3. A failure drill on one shelf leaves at least one approved end-to-end route available.
  4. A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.

Explanation

Correct Answer

D:

A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target. This confirms the approved response: Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported. It is relevant because: BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.

Incorrect Answers

A:

Customer route queries show approved aggregate service routes but no internal infrastructure prefixes. This would validate ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The specific correction here is: Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.

B:

The prefix becomes usable with a resolved next hop while the IGP remains stable. This would validate ANOTHER scenario: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The specific correction here is: Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.

C:

A failure drill on one shelf leaves at least one approved end-to-end route available. This would validate ANOTHER scenario: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. The specific correction here is: Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.

Question 715

A carrier root-cause review considers: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. What underlying mechanism explains this?

  1. BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.
  2. AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.
  3. BGP session establishment is distinct from activation of a specific MP-BGP address family.
  4. NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers.

Explanation

Correct Answer

A:

BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution. This explains the investigated issue: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The approved corrective response is: Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.

Incorrect Answers

B:

AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection. That explains a DIFFERENT scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. The mechanism to prioritize for this question is: BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.

C:

BGP session establishment is distinct from activation of a specific MP-BGP address family. That explains a DIFFERENT scenario: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. The mechanism to prioritize for this question is: BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.

D:

NAT44 translates IPv4 addresses within one family and cannot by itself connect IPv6-only clients to IPv4-only servers. That explains a DIFFERENT scenario: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. The mechanism to prioritize for this question is: BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.

Question 716

After addressing: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. Which recurring service assurance check is most useful?

  1. Record upstream acceptance of traffic-engineering communities and MED policy.
  2. Measure PIC behavior for each platform and address family before claiming fast failover.
  3. Track Add-Path capabilities and route scale in peering acceptance tests.
  4. Include tagged and untagged candidate routes in route-map test suites.

Explanation

Correct Answer

B:

Measure PIC behavior for each platform and address family before claiming fast failover. This helps prevent recurrence of the issue: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. Acceptance evidence should be: A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.

Incorrect Answers

A:

Record upstream acceptance of traffic-engineering communities and MED policy. That is a sensible control for ANOTHER scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. It is less targeted to this issue than: Measure PIC behavior for each platform and address family before claiming fast failover.

C:

Track Add-Path capabilities and route scale in peering acceptance tests. That is a sensible control for ANOTHER scenario: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. It is less targeted to this issue than: Measure PIC behavior for each platform and address family before claiming fast failover.

D:

Include tagged and untagged candidate routes in route-map test suites. That is a sensible control for ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. It is less targeted to this issue than: Measure PIC behavior for each platform and address family before claiming fast failover.

Question 717

A provider backbone escalation identifies: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. What should the network team implement?

  1. Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.
  2. Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.
  3. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.
  4. Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.

Explanation

Correct Answer

D:

Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF. This directly addresses the fictional service-provider network case: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. The technical mechanism is: MPLS OAM for one FEC or layer does not independently verify every overlaid customer service. Verify success by: The test isolates a healthy transport LSP from a missing inner VPN route or label binding.

Incorrect Answers

A:

Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready. This would respond to a DIFFERENT fictional service-provider network issue: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets. It does not directly address the current situation: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven.

B:

Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration. This would respond to a DIFFERENT fictional service-provider network issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It does not directly address the current situation: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven.

C:

Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths. This would respond to a DIFFERENT fictional service-provider network issue: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. It does not directly address the current situation: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven.

Question 718

A service-provider operations test targets: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Which result is required?

  1. The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
  2. A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.
  3. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.
  4. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.

Explanation

Correct Answer

A:

The test isolates a healthy transport LSP from a missing inner VPN route or label binding. This confirms the approved response: Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF. It is relevant because: MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.

Incorrect Answers

B:

A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE. This would validate ANOTHER scenario: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. The specific correction here is: Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.

C:

During a single-link failure the session remains protected through the alternative route and bound FECs recover safely. This would validate ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The specific correction here is: Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.

D:

A stress test admits or rejects reservations according to the per-class budget without starving the protected class. This would validate ANOTHER scenario: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. The specific correction here is: Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.

Question 719

A provider troubleshooting note states: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Which mechanism is central?

  1. MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.
  2. MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.
  3. MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.
  4. Local protection for a link and local protection for a full node require different bypass topology constraints.

Explanation

Correct Answer

B:

MPLS OAM for one FEC or layer does not independently verify every overlaid customer service. This explains the investigated issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. The approved corrective response is: Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.

Incorrect Answers

A:

MPLS forwarding hardware may limit the number of imposed or inspected labels per packet. That explains a DIFFERENT scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The mechanism to prioritize for this question is: MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.

C:

MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations. That explains a DIFFERENT scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. The mechanism to prioritize for this question is: MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.

D:

Local protection for a link and local protection for a full node require different bypass topology constraints. That explains a DIFFERENT scenario: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. The mechanism to prioritize for this question is: MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.

Question 720

To prevent recurrence of this provider network issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Which control should be retained?

  1. Measure end-to-end label-stack MTU at every new pseudowire deployment.
  2. Monitor protected-session status and route-to-transport-loopback reachability.
  3. Include transport and service-layer OAM in VPN fault playbooks.
  4. Record reoptimization stability and path-change rate in monitoring.

Explanation

Correct Answer

C:

Include transport and service-layer OAM in VPN fault playbooks. This helps prevent recurrence of the issue: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. Acceptance evidence should be: The test isolates a healthy transport LSP from a missing inner VPN route or label binding.

Incorrect Answers

A:

Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.

B:

Monitor protected-session status and route-to-transport-loopback reachability. That is a sensible control for ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.

D:

Record reoptimization stability and path-change rate in monitoring. That is a sensible control for ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It is less targeted to this issue than: Include transport and service-layer OAM in VPN fault playbooks.