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 65

Question 640

To prevent recurrence of this provider network issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Which control should be retained?

  1. Require boundary-prefix tests whenever prefix sets are edited.
  2. Include tagged and untagged candidate routes in route-map test suites.
  3. Archive policy diffs and route-acceptance fixtures with change approvals.
  4. Baseline BFD jitter and loss before setting aggressive detection timers.

Explanation

Correct Answer

C:

Archive policy diffs and route-acceptance fixtures with change approvals. This helps prevent recurrence of the issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. Acceptance evidence should be: A sandbox change shows the aggregate retained and the desired new filter applied before production approval.

Incorrect Answers

A:

Require boundary-prefix tests whenever prefix sets are edited. That is a sensible control for ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.

B:

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: Archive policy diffs and route-acceptance fixtures with change approvals.

D:

Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Archive policy diffs and route-acceptance fixtures with change approvals.

Question 641

At a managed VPN service carrier, an engineering review finds: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. Which change most directly corrects the service problem?

  1. Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.
  2. Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.
  3. Align approved IS-IS authentication parameters and keys on all intended peer interfaces.
  4. Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

Explanation

Correct Answer

A:

Align supported BFD session parameters and measure them against the actual transport latency and loss envelope. This directly addresses the fictional service-provider network case: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The technical mechanism is: BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures. Verify success by: In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.

Incorrect Answers

B:

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 router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection.

C:

Align approved IS-IS authentication parameters and keys on all intended peer interfaces. This would respond to a DIFFERENT fictional service-provider network issue: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. It does not directly address the current situation: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection.

D:

Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection. This would respond to a DIFFERENT fictional service-provider network issue: A carrier's inbound customer route has local preference 200 but another exit's route has a shorter AS_PATH, and the team incorrectly expects the short path to win. It does not directly address the current situation: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection.

Question 642

For a managed VPN service carrier, operators addressed: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. What is the strongest acceptance evidence?

  1. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.
  2. In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.
  3. A test prefix is visible across the area boundary before the dependent BGP route recovers.
  4. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.

Explanation

Correct Answer

B:

In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target. This confirms the approved response: Align supported BFD session parameters and measure them against the actual transport latency and loss envelope. It is relevant because: BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.

Incorrect Answers

A:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This would validate ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The specific correction here is: Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.

C:

A test prefix is visible across the area boundary before the dependent BGP route recovers. This would validate ANOTHER scenario: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. The specific correction here is: Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.

D:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This would validate ANOTHER scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The specific correction here is: Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.

Question 643

Which network protocol or forwarding behavior explains the following issue: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection.

  1. Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.
  2. BGP path usability depends on resolution through the underlying routing table.
  3. BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.
  4. Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.

Explanation

Correct Answer

C:

BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures. This explains the investigated issue: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The approved corrective response is: Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.

Incorrect Answers

A:

Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization. That explains a DIFFERENT scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The mechanism to prioritize for this question is: BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.

B:

BGP path usability depends on resolution through the underlying routing table. That explains a DIFFERENT scenario: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. The mechanism to prioritize for this question is: BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.

D:

Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix. That explains a DIFFERENT scenario: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. The mechanism to prioritize for this question is: BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.

Question 644

A core network change board wants to avoid: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. Which ongoing safeguard fits best?

  1. Trend prefix counts and alert before capacity thresholds are reached.
  2. Include protocol-specific reachability and adjacency checks after ACL changes.
  3. Teach neighbor-state expectations per OSPF network type in runbooks.
  4. Tune BFD to observed transport behavior and test at peak utilization.

Explanation

Correct Answer

D:

Tune BFD to observed transport behavior and test at peak utilization. This helps prevent recurrence of the issue: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. Acceptance evidence should be: In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.

Incorrect Answers

A:

Trend prefix counts and alert before capacity thresholds are reached. That is a sensible control for ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It is less targeted to this issue than: Tune BFD to observed transport behavior and test at peak utilization.

B:

Include protocol-specific reachability and adjacency checks after ACL changes. That is a sensible control for ANOTHER scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. It is less targeted to this issue than: Tune BFD to observed transport behavior and test at peak utilization.

C:

Teach neighbor-state expectations per OSPF network type in runbooks. That is a sensible control for ANOTHER scenario: A multiaccess OSPF network forms neighbor relationships but routes stay stuck at 2-Way between two DROTHER peers, and the operator repeatedly resets them. It is less targeted to this issue than: Tune BFD to observed transport behavior and test at peak utilization.

Question 645

A carrier service activation check discovers: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. Which action best restores the intended behavior?

  1. Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform.
  2. Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.
  3. Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.
  4. Set the intended IS-IS wide metric on the optical link based on approved transport cost.

Explanation

Correct Answer

B:

Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology. This directly addresses the fictional service-provider network case: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. The technical mechanism is: Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap. Verify success by: Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.

Incorrect Answers

A:

Validate compatible NSF/graceful-restart capability and forwarding-state retention behavior on the platform. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. It does not directly address the current situation: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy.

C:

Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies. This would respond to a DIFFERENT fictional service-provider network issue: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. It does not directly address the current situation: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy.

D:

Set the intended IS-IS wide metric on the optical link based on approved transport cost. This would respond to a DIFFERENT fictional service-provider network issue: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. It does not directly address the current situation: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy.

Question 646

Following a supported configuration correction, the original issue was: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. Which observation verifies success?

  1. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.
  2. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.
  3. Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.
  4. In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.

Explanation

Correct Answer

C:

Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic. This confirms the approved response: Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology. It is relevant because: Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

Incorrect Answers

A:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This would validate ANOTHER scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The specific correction here is: Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

B:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This would validate ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The specific correction here is: Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

D:

In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target. This would validate ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The specific correction here is: Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

Question 647

At a regional peering-exchange operator, an engineer examines: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. Which technical principle is most applicable?

  1. High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.
  2. Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.
  3. BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.
  4. Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

Explanation

Correct Answer

D:

Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap. This explains the investigated issue: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. The approved corrective response is: Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

Incorrect Answers

A:

High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario. That explains a DIFFERENT scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The mechanism to prioritize for this question is: Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

B:

Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts. That explains a DIFFERENT scenario: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The mechanism to prioritize for this question is: Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

C:

BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. That explains a DIFFERENT scenario: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. The mechanism to prioritize for this question is: Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.

Question 648

For a regional peering-exchange operator, the change record describes: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. What preventive validation should be standard?

  1. Audit FIB recursive adjacency groups as part of resiliency tests.
  2. Verify port-channel membership and individual-link counters after physical changes.
  3. Map provider optical shared-risk groups in high-availability path review.
  4. Tune BFD to observed transport behavior and test at peak utilization.

Explanation

Correct Answer

A:

Audit FIB recursive adjacency groups as part of resiliency tests. This helps prevent recurrence of the issue: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. Acceptance evidence should be: Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.

Incorrect Answers

B:

Verify port-channel membership and individual-link counters after physical changes. That is a sensible control for ANOTHER scenario: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. It is less targeted to this issue than: Audit FIB recursive adjacency groups as part of resiliency tests.

C:

Map provider optical shared-risk groups in high-availability path review. That is a sensible control for 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. It is less targeted to this issue than: Audit FIB recursive adjacency groups as part of resiliency tests.

D:

Tune BFD to observed transport behavior and test at peak utilization. That is a sensible control for ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It is less targeted to this issue than: Audit FIB recursive adjacency groups as part of resiliency tests.

Question 649

For an optical transport engineering team, the failure is: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. Which authorized correction best addresses it?

  1. Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.
  2. Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.
  3. Align authorized LDP session authentication and transport addresses on the intended peers.
  4. Set explicit TE priority and bandwidth allocation policies for the intended service classes.

Explanation

Correct Answer

C:

Align authorized LDP session authentication and transport addresses on the intended peers. This directly addresses the fictional service-provider network case: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. The technical mechanism is: LDP discovery and its subsequent transport session are separate stages with independent failure conditions. Verify success by: LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs.

Incorrect Answers

A:

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: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive.

B:

Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive.

D:

Set explicit TE priority and bandwidth allocation policies for the intended service classes. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. It does not directly address the current situation: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive.

Question 650

After fixing the following network problem, what should the team verify: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive.

  1. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.
  2. The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
  3. A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table.
  4. LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs.

Explanation

Correct Answer

D:

LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs. This confirms the approved response: Align authorized LDP session authentication and transport addresses on the intended peers. It is relevant because: LDP discovery and its subsequent transport session are separate stages with independent failure conditions.

Incorrect Answers

A:

The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This would validate ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.

B:

The test isolates a healthy transport LSP from a missing inner VPN route or label binding. This would validate ANOTHER scenario: 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 specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.

C:

A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table. This would validate ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. The specific correction here is: Align authorized LDP session authentication and transport addresses on the intended peers.