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 20

Question 190

A service-provider operations test targets: 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. Which result is required?

  1. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.
  2. Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.
  3. Both links join one stable operational bundle and sampled customer flows traverse valid active members.
  4. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Explanation

Correct Answer

A:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This confirms the approved response: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. It is relevant because: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

Incorrect Answers

B:

Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic. This would validate ANOTHER scenario: 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 specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

C:

Both links join one stable operational bundle and sampled customer flows traverse valid active members. This would validate 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. The specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

D:

Parallel test sessions resolve to unique external tuples and return to the correct subscriber. This would validate ANOTHER scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. The specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

Question 191

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap.
  2. NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.
  3. Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.
  4. IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

Explanation

Correct Answer

B:

NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior. This explains the investigated issue: 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 approved corrective response is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

Incorrect Answers

A:

Equal-cost routes can conceal a common downstream failure when their recursive forwarding dependencies overlap. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

C:

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: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

D:

IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

Question 192

To prevent recurrence of this provider network issue: 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. Which control should be retained?

  1. Baseline BFD jitter and loss before setting aggressive detection timers.
  2. Verify port-channel membership and individual-link counters after physical changes.
  3. Check protocol-specific NSR readiness before planned route-processor switchover.
  4. Validate area-type consistency before enabling stub policy.

Explanation

Correct Answer

C:

Check protocol-specific NSR readiness before planned route-processor switchover. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.

Incorrect Answers

A:

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: Check protocol-specific NSR readiness before planned route-processor switchover.

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: Check protocol-specific NSR readiness before planned route-processor switchover.

D:

Validate area-type consistency before enabling stub policy. That is a sensible control for ANOTHER scenario: An OSPF stub area loses its expected default route when an engineer configures stub mode on the access router but not consistently on the area border router. It is less targeted to this issue than: Check protocol-specific NSR readiness before planned route-processor switchover.

Question 193

At a managed VPN service carrier, an engineering review finds: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. Which change most directly corrects the service problem?

  1. Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.
  2. Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.
  3. Align authorized LDP session authentication and transport addresses on the intended peers.
  4. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.

Explanation

Correct Answer

A:

Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration. This directly addresses the fictional service-provider network case: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The technical mechanism is: LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures. Verify success by: During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.

Incorrect Answers

B:

Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route. This would respond to a DIFFERENT fictional service-provider network issue: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It does not directly address the current situation: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks.

C:

Align authorized LDP session authentication and transport addresses on the intended peers. This would respond to a DIFFERENT fictional service-provider network issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It does not directly address the current situation: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks.

D:

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: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks.

Question 194

For a managed VPN service carrier, operators addressed: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. What is the strongest acceptance evidence?

  1. Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.
  2. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.
  3. A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.
  4. A test packet traverses the intended interface sequence and no longer visits the retired link.

Explanation

Correct Answer

B:

During a single-link failure the session remains protected through the alternative route and bound FECs recover safely. This confirms the approved response: Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration. It is relevant because: LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.

Incorrect Answers

A:

Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly. This would validate ANOTHER scenario: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. The specific correction here is: Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.

C:

A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning. This would validate ANOTHER 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 specific correction here is: Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.

D:

A test packet traverses the intended interface sequence and no longer visits the retired link. This would validate ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The specific correction here is: Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.

Question 195

Which network protocol or forwarding behavior explains the following issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks.

  1. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.
  2. IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.
  3. LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.
  4. Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

Explanation

Correct Answer

C:

LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures. This explains the investigated issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The approved corrective response is: Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.

Incorrect Answers

A:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. That explains a DIFFERENT scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The mechanism to prioritize for this question is: LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.

B:

IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core. That explains a DIFFERENT scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. The mechanism to prioritize for this question is: LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.

D:

Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values. That explains a DIFFERENT scenario: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. The mechanism to prioritize for this question is: LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.

Question 196

A core network change board wants to avoid: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. Which ongoing safeguard fits best?

  1. Test link startup ordering with IGP and LDP state counters.
  2. Document TTL transparency and troubleshooting expectations for each service class.
  3. Verify control-plane service route labels and locator reachability across interdomain handoffs.
  4. Monitor protected-session status and route-to-transport-loopback reachability.

Explanation

Correct Answer

D:

Monitor protected-session status and route-to-transport-loopback reachability. This helps prevent recurrence of the issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. Acceptance evidence should be: During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.

Incorrect Answers

A:

Test link startup ordering with IGP and LDP state counters. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Monitor protected-session status and route-to-transport-loopback reachability.

B:

Document TTL transparency and troubleshooting expectations for each service class. That is a sensible control for ANOTHER scenario: A router's MPLS TTL propagation policy differs from its neighboring core nodes, and traceroute unexpectedly exposes or hides provider hops relative to the service contract. It is less targeted to this issue than: Monitor protected-session status and route-to-transport-loopback reachability.

C:

Verify control-plane service route labels and locator reachability across interdomain handoffs. That is a sensible control for ANOTHER scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. It is less targeted to this issue than: Monitor protected-session status and route-to-transport-loopback reachability.

Question 197

A carrier service activation check discovers: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Which action best restores the intended behavior?

  1. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.
  2. Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.
  3. Include available shared-risk link group constraints or explicit path diversity in TE computation.
  4. Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

Explanation

Correct Answer

B:

Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path. This directly addresses the fictional service-provider network case: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The technical mechanism is: RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology. Verify success by: RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Incorrect Answers

A:

Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability.

C:

Include available shared-risk link group constraints or explicit path diversity in TE computation. This would respond to a DIFFERENT fictional service-provider network issue: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It does not directly address the current situation: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability.

D:

Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border. This would respond to a DIFFERENT fictional service-provider network issue: A service provider exports VPNv4 labels across multiple autonomous regions but assumes LDP sessions must directly span every access network and interregion core. It does not directly address the current situation: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability.

Question 198

Following a supported configuration correction, the original issue was: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Which observation verifies success?

  1. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.
  2. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  3. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.
  4. The PCC installs only approved delegated candidates and reports their active state back to the PCE.

Explanation

Correct Answer

C:

RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This confirms the approved response: Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path. It is relevant because: RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.

Incorrect Answers

A:

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: Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

B:

The replacement LSP becomes usable before the previous one is torn down in an acceptance test. This would validate ANOTHER scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The specific correction here is: Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

D:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate ANOTHER scenario: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. The specific correction here is: Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

Question 199

At a regional peering-exchange operator, an engineer examines: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Which technical principle is most applicable?

  1. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.
  2. Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.
  3. Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.
  4. RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.

Explanation

Correct Answer

D:

RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology. This explains the investigated issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. The approved corrective response is: Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

Incorrect Answers

A:

RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources. That explains a DIFFERENT scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. The mechanism to prioritize for this question is: RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.

B:

Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist. That explains a DIFFERENT scenario: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The mechanism to prioritize for this question is: RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.

C:

Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information. That explains a DIFFERENT scenario: During a P-router failure, Ti-LFA repair is expected but no backup next hop is installed because one adjacent link is excluded from the repair topology. The mechanism to prioritize for this question is: RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.

Question 200

For a regional peering-exchange operator, the change record describes: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. What preventive validation should be standard?

  1. Validate explicit-route hops against TE capability data before committing.
  2. Maintain optical SRLG metadata with core IGP-TE inventory.
  3. Include TE database completeness checks during IGP maintenance.
  4. Check IGP and LDP FEC consistency at every interregion boundary.

Explanation

Correct Answer

A:

Validate explicit-route hops against TE capability data before committing. This helps prevent recurrence of the issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. Acceptance evidence should be: RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Incorrect Answers

B:

Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.

C:

Include TE database completeness checks during IGP maintenance. That is a sensible control for ANOTHER scenario: A backbone planner expects constrained TE to calculate alternate paths while the IGP advertises only basic reachability and no extended TE link attributes. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.

D:

Check IGP and LDP FEC consistency at every interregion boundary. That is a sensible control for ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It is less targeted to this issue than: Validate explicit-route hops against TE capability data before committing.