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 66

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.

Question 651

A carrier root-cause review considers: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. What underlying mechanism explains this?

  1. LDP discovery and its subsequent transport session are separate stages with independent failure conditions.
  2. MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.
  3. IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.
  4. PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

Explanation

Correct Answer

A:

LDP discovery and its subsequent transport session are separate stages with independent failure conditions. This explains the investigated issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. The approved corrective response is: Align authorized LDP session authentication and transport addresses on the intended peers.

Incorrect Answers

B:

MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress. That explains a DIFFERENT 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 mechanism to prioritize for this question is: LDP discovery and its subsequent transport session are separate stages with independent failure conditions.

C:

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 discovery and its subsequent transport session are separate stages with independent failure conditions.

D:

PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority. That explains a DIFFERENT 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 mechanism to prioritize for this question is: LDP discovery and its subsequent transport session are separate stages with independent failure conditions.

Question 652

After addressing: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. Which recurring service assurance check is most useful?

  1. Alert on mismatched IGP FEC and LFIB installation counters.
  2. Verify LDP discovery, transport and authentication status during peer certification.
  3. Monitor protected-session status and route-to-transport-loopback reachability.
  4. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.

Explanation

Correct Answer

B:

Verify LDP discovery, transport and authentication status during peer certification. This helps prevent recurrence of the issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. Acceptance evidence should be: LDP TCP session establishes and advertises expected label mappings without including unapproved neighbor IDs.

Incorrect Answers

A:

Alert on mismatched IGP FEC and LFIB installation counters. That is a sensible control for ANOTHER scenario: Label advertisement remains present for a withdrawn IGP FEC due to a stale forwarding cache, producing a short-lived blackhole after a route-policy rollback. It is less targeted to this issue than: Verify LDP discovery, transport and authentication status during peer certification.

C:

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: Verify LDP discovery, transport and authentication status during peer certification.

D:

Inspect protection flags and test actual repair behavior instead of assuming FRR is armed. That is a sensible control for ANOTHER scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It is less targeted to this issue than: Verify LDP discovery, transport and authentication status during peer certification.

Question 653

A provider backbone escalation identifies: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. What should the network team implement?

  1. Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.
  2. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.
  3. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.
  4. Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.

Explanation

Correct Answer

D:

Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation. This directly addresses the fictional service-provider network case: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The technical mechanism is: Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand. Verify success by: Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.

Incorrect Answers

A:

Use a supported make-before-break signaling or switchover sequence when available and within resource constraints. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations.

B:

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: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations.

C:

Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables SR-MPLS forwarding but assumes each SR-TE path requires RSVP-TE state on every transit router, blocking deployment when RSVP is disabled. It does not directly address the current situation: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations.

Question 654

A service-provider operations test targets: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. Which result is required?

  1. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.
  2. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  3. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.
  4. A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.

Explanation

Correct Answer

A:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This confirms the approved response: Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation. It is relevant because: Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

Incorrect Answers

B:

Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed. This would validate ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The specific correction here is: Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.

C:

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: Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.

D:

A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint. This would validate ANOTHER scenario: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. The specific correction here is: Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.

Question 655

A provider troubleshooting note states: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. Which mechanism is central?

  1. RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.
  2. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.
  3. DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.
  4. LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.

Explanation

Correct Answer

B:

Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand. This explains the investigated issue: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The approved corrective response is: Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.

Incorrect Answers

A:

RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

C:

DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

D:

LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures. That explains a DIFFERENT scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The mechanism to prioritize for this question is: Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

Question 656

To prevent recurrence of this provider network issue: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. Which control should be retained?

  1. Verify data-plane steering separately from RSVP session state.
  2. Track class-type utilization and validate reservation boundaries after QoS changes.
  3. Audit RSVP reservation lifetimes and headend ownership regularly.
  4. Test route and label binding presence separately for every new backbone link.

Explanation

Correct Answer

C:

Audit RSVP reservation lifetimes and headend ownership regularly. This helps prevent recurrence of the issue: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. Acceptance evidence should be: Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.

Incorrect Answers

A:

Verify data-plane steering separately from RSVP session state. That is a sensible control for ANOTHER scenario: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. It is less targeted to this issue than: Audit RSVP reservation lifetimes and headend ownership regularly.

B:

Track class-type utilization and validate reservation boundaries after QoS changes. That is a sensible control for 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. It is less targeted to this issue than: Audit RSVP reservation lifetimes and headend ownership regularly.

D:

Test route and label binding presence separately for every new backbone link. That is a sensible control for ANOTHER scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. It is less targeted to this issue than: Audit RSVP reservation lifetimes and headend ownership regularly.

Question 657

At a multi-tenant data transport provider, an engineering review finds: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. Which change most directly corrects the service problem?

  1. Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.
  2. Enable the agreed algorithm definition and participation on all required forwarding nodes or avoid steering through unsupported paths.
  3. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
  4. Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.

Explanation

Correct Answer

A:

Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility. This directly addresses the fictional service-provider network case: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. The technical mechanism is: SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet. Verify success by: A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.

Incorrect Answers

B:

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 SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function.

C:

Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. This would respond to a DIFFERENT fictional service-provider network issue: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. It does not directly address the current situation: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function.

D:

Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function.

Question 658

For a multi-tenant data transport provider, operators addressed: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. What is the strongest acceptance evidence?

  1. A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.
  2. A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.
  3. A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.
  4. An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.

Explanation

Correct Answer

B:

A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint. This confirms the approved response: Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility. It is relevant because: SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

Incorrect Answers

A:

A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This would validate ANOTHER scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The specific correction here is: Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.

C:

A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end. This would validate ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The specific correction here is: Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.

D:

An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup. This would validate ANOTHER 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 specific correction here is: Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.

Question 659

Which network protocol or forwarding behavior explains the following issue: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function.

  1. An SR policy defines an engineered path but requires steering to affect user traffic.
  2. Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.
  3. SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.
  4. Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.

Explanation

Correct Answer

C:

SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet. This explains the investigated issue: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. The approved corrective response is: Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.

Incorrect Answers

A:

An SR policy defines an engineered path but requires steering to affect user traffic. That explains a DIFFERENT scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The mechanism to prioritize for this question is: SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

B:

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: SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

D:

Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. That explains a DIFFERENT scenario: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. The mechanism to prioritize for this question is: SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

Question 660

A core network change board wants to avoid: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. Which ongoing safeguard fits best?

  1. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  2. Monitor adjacency SID changes and invalidate stale policy segment lists.
  3. Inspect label-stack depth and disposition at each egress after LDP or BGP changes.
  4. Test locator route advertisement whenever new SRv6 functions are provisioned.

Explanation

Correct Answer

D:

Test locator route advertisement whenever new SRv6 functions are provisioned. This helps prevent recurrence of the issue: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. Acceptance evidence should be: A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.

Incorrect Answers

A:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for 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. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.

B:

Monitor adjacency SID changes and invalidate stale policy segment lists. That is a sensible control for ANOTHER scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.

C:

Inspect label-stack depth and disposition at each egress after LDP or BGP changes. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Test locator route advertisement whenever new SRv6 functions are provisioned.