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 60

Question 590

A service-provider operations test targets: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. Which result is required?

  1. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.
  2. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.
  3. A failure drill on one shelf leaves at least one approved end-to-end route available.
  4. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.

Explanation

Correct Answer

A:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This confirms the approved response: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan. It is relevant because: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

Incorrect Answers

B:

During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget. This would validate ANOTHER 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 specific correction here is: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

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 supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

D:

The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged. This would validate ANOTHER scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The specific correction here is: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

Question 591

A provider troubleshooting note states: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. Which mechanism is central?

  1. NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.
  2. High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.
  3. BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.
  4. The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.

Explanation

Correct Answer

B:

High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario. This explains the investigated issue: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The approved corrective response is: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

Incorrect Answers

A:

NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior. That explains a DIFFERENT 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 mechanism to prioritize for this question is: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

C:

BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures. That explains a DIFFERENT scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. The mechanism to prioritize for this question is: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

D:

The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance. That explains a DIFFERENT scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. The mechanism to prioritize for this question is: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

Question 592

To prevent recurrence of this provider network issue: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. Which control should be retained?

  1. Map provider optical shared-risk groups in high-availability path review.
  2. Baseline BFD jitter and loss before setting aggressive detection timers.
  3. Maintain release-specific ISSU qualification and rollback documentation.
  4. Validate next-hop recursion for every new iBGP export policy.

Explanation

Correct Answer

C:

Maintain release-specific ISSU qualification and rollback documentation. This helps prevent recurrence of the issue: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. Acceptance evidence should be: The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.

Incorrect Answers

A:

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: Maintain release-specific ISSU qualification and rollback documentation.

B:

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: Maintain release-specific ISSU qualification and rollback documentation.

D:

Validate next-hop recursion for every new iBGP export policy. That is a sensible control for 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. It is less targeted to this issue than: Maintain release-specific ISSU qualification and rollback documentation.

Question 593

At an optical transport engineering team, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.
  2. Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.
  3. Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.
  4. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

Explanation

Correct Answer

A:

Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label. This directly addresses the fictional service-provider network case: 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 technical mechanism is: MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. Verify success by: An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.

Incorrect Answers

B:

Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It does not directly address the current situation: 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.

C:

Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

D:

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: 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.

Question 594

For an optical transport engineering team, operators addressed: 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. What is the strongest acceptance evidence?

  1. Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.
  2. An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.
  3. A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed.
  4. The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.

Explanation

Correct Answer

B:

An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup. This confirms the approved response: Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label. It is relevant because: MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

Incorrect Answers

A:

Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This would validate 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. The specific correction here is: Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.

C:

A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed. This would validate 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. The specific correction here is: Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.

D:

The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass. This would validate ANOTHER 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 specific correction here is: Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.

Question 595

Which network protocol or forwarding behavior explains the following 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.

  1. Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.
  2. IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.
  3. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.
  4. SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

Explanation

Correct Answer

C:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. This explains the investigated 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. The approved corrective response is: Validate transport versus service label stacking and make sure penultimate-hop popping applies only to the intended outer transport label.

Incorrect Answers

A:

Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering. That explains a DIFFERENT 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 mechanism to prioritize for this question is: MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

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: MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

D:

SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet. That explains a DIFFERENT 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 mechanism to prioritize for this question is: MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

Question 596

A core network change board wants to avoid: 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. Which ongoing safeguard fits best?

  1. Track per-platform maximum label-stack depth in service design inventory.
  2. Verify LDP discovery, transport and authentication status during peer certification.
  3. Keep segment-type validation with path computation requests.
  4. Inspect label-stack depth and disposition at each egress after LDP or BGP changes.

Explanation

Correct Answer

D:

Inspect label-stack depth and disposition at each egress after LDP or BGP changes. This helps prevent recurrence of the 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. Acceptance evidence should be: An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.

Incorrect Answers

A:

Track per-platform maximum label-stack depth in service design inventory. That is a sensible control for 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. It is less targeted to this issue than: Inspect label-stack depth and disposition at each egress after LDP or BGP changes.

B:

Verify LDP discovery, transport and authentication status during peer certification. That is a sensible control for ANOTHER scenario: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It is less targeted to this issue than: Inspect label-stack depth and disposition at each egress after LDP or BGP changes.

C:

Keep segment-type validation with path computation requests. That is a sensible control for 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. It is less targeted to this issue than: Inspect label-stack depth and disposition at each egress after LDP or BGP changes.

Question 597

A carrier service activation check discovers: 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. Which action best restores the intended behavior?

  1. Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.
  2. Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.
  3. Configure and verify compatible facility or one-to-one local repair for the critical protected link.
  4. Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy.

Explanation

Correct Answer

B:

Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it. Verify success by: FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.

Incorrect Answers

A:

Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

C:

Configure and verify compatible facility or one-to-one local repair for the critical protected link. This would respond to a DIFFERENT fictional service-provider network issue: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It does not directly address the current situation: 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.

D:

Recalculate the segment list using the current topology and correct adjacency SID advertisements before enabling the policy. This would respond to a DIFFERENT fictional service-provider network issue: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. It does not directly address the current situation: 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.

Question 598

Following a supported configuration correction, the original issue was: 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. Which observation verifies success?

  1. Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.
  2. Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity.
  3. FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.
  4. A controlled transit-node failure uses the precomputed repair path within the stated local restoration target.

Explanation

Correct Answer

C:

FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path. This confirms the approved response: Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes. It is relevant because: An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

Incorrect Answers

A:

Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility. This would validate ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. The specific correction here is: Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.

B:

Available TE reservable bandwidth rises in line with released legitimate reservations without changing the physical capacity. This would validate ANOTHER scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The specific correction here is: Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.

D:

A controlled transit-node failure uses the precomputed repair path within the stated local restoration target. This would validate ANOTHER 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 specific correction here is: Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.

Question 599

At a carrier automation platform team, an engineer examines: 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. Which technical principle is most applicable?

  1. Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.
  2. RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.
  3. Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.
  4. An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

Explanation

Correct Answer

D:

An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it. This explains the investigated issue: 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. The approved corrective response is: Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.

Incorrect Answers

A:

Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes. That explains a DIFFERENT scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The mechanism to prioritize for this question is: An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

B:

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: An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

C:

Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. That explains a DIFFERENT scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The mechanism to prioritize for this question is: An established TE LSP does not attract user traffic unless routing or policy intentionally steers packets into it.

Question 600

For a carrier automation platform team, the change record describes: 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. What preventive validation should be standard?

  1. Verify data-plane steering separately from RSVP session state.
  2. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.
  3. Record reoptimization stability and path-change rate in monitoring.
  4. Include crossregion label-stack tracing in service acceptance.

Explanation

Correct Answer

A:

Verify data-plane steering separately from RSVP session state. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.

Incorrect Answers

B:

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 data-plane steering separately from RSVP session state.

C:

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: Verify data-plane steering separately from RSVP session state.

D:

Include crossregion label-stack tracing in service acceptance. That is a sensible control for 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. It is less targeted to this issue than: Verify data-plane steering separately from RSVP session state.