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 33

Question 320

To prevent recurrence of this provider network issue: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. Which control should be retained?

  1. Test deterministic mapping and log lookup as part of CGNAT capacity exercises.
  2. Audit port-block assignments and exhausted mapping pools.
  3. Validate B4 reachability and AFTR capacity at subscriber activation.
  4. Test component-prefix ownership before exporting aggregates.

Explanation

Correct Answer

C:

Validate B4 reachability and AFTR capacity at subscriber activation. This helps prevent recurrence of the issue: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. Acceptance evidence should be: A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address.

Incorrect Answers

A:

Test deterministic mapping and log lookup as part of CGNAT capacity exercises. That is a sensible control for ANOTHER scenario: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. It is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.

B:

Audit port-block assignments and exhausted mapping pools. That is a sensible control for 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. It is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.

D:

Test component-prefix ownership before exporting aggregates. That is a sensible control for ANOTHER scenario: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.

Question 321

At a multi-tenant data transport provider, an engineering review finds: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. Which change most directly corrects the service problem?

  1. Configure detection and multiplier values consistent with platform and WAN path characteristics.
  2. Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.
  3. Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing.
  4. Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.

Explanation

Correct Answer

A:

Configure detection and multiplier values consistent with platform and WAN path characteristics. This directly addresses the fictional service-provider network case: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. The technical mechanism is: BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures. Verify success by: Stability testing shows legitimate fault detection within budget without false down events under busy periods.

Incorrect Answers

B:

Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics.

C:

Align LACP partner/key and port-channel membership on both sides and confirm capacity and hashing. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics.

D:

Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised. This would respond to a DIFFERENT fictional service-provider network issue: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. It does not directly address the current situation: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics.

Question 322

For a multi-tenant data transport provider, operators addressed: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. What is the strongest acceptance evidence?

  1. During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.
  2. Stability testing shows legitimate fault detection within budget without false down events under busy periods.
  3. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.
  4. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.

Explanation

Correct Answer

B:

Stability testing shows legitimate fault detection within budget without false down events under busy periods. This confirms the approved response: Configure detection and multiplier values consistent with platform and WAN path characteristics. It is relevant because: BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.

Incorrect Answers

A:

During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load. This would validate ANOTHER scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The specific correction here is: Configure detection and multiplier values consistent with platform and WAN path characteristics.

C:

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: Configure detection and multiplier values consistent with platform and WAN path characteristics.

D:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This would validate ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The specific correction here is: Configure detection and multiplier values consistent with platform and WAN path characteristics.

Question 323

Which network protocol or forwarding behavior explains the following issue: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics.

  1. High availability must account for postfailure capacity, not merely the existence of an alternate topology path.
  2. Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly.
  3. BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.
  4. Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.

Explanation

Correct Answer

C:

BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures. This explains the investigated issue: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. The approved corrective response is: Configure detection and multiplier values consistent with platform and WAN path characteristics.

Incorrect Answers

A:

High availability must account for postfailure capacity, not merely the existence of an alternate topology path. That explains a DIFFERENT scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The mechanism to prioritize for this question is: BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.

B:

Link aggregation requires compatible control negotiation and consistent member roles to share forwarding correctly. That explains a DIFFERENT 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 mechanism to prioritize for this question is: BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.

D:

Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length. That explains a DIFFERENT scenario: A BGP router holds multiple valid paths yet chooses an unanticipated route because one path has a smaller origin code, not because of a mistaken community. The mechanism to prioritize for this question is: BFD liveness intervals must accommodate transport delay and scheduling to avoid spurious failures.

Question 324

A core network change board wants to avoid: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. Which ongoing safeguard fits best?

  1. Audit FIB recursive adjacency groups as part of resiliency tests.
  2. Include N-1 link capacity tests in planned-maintenance readiness checks.
  3. Test component-prefix ownership before exporting aggregates.
  4. Baseline BFD jitter and loss before setting aggressive detection timers.

Explanation

Correct Answer

D:

Baseline BFD jitter and loss before setting aggressive detection timers. This helps prevent recurrence of the issue: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. Acceptance evidence should be: Stability testing shows legitimate fault detection within budget without false down events under busy periods.

Incorrect Answers

A:

Audit FIB recursive adjacency groups as part of resiliency tests. That is a sensible control for 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. It is less targeted to this issue than: Baseline BFD jitter and loss before setting aggressive detection timers.

B:

Include N-1 link capacity tests in planned-maintenance readiness checks. That is a sensible control for ANOTHER scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. It is less targeted to this issue than: Baseline BFD jitter and loss before setting aggressive detection timers.

C:

Test component-prefix ownership before exporting aggregates. That is a sensible control for ANOTHER scenario: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It is less targeted to this issue than: Baseline BFD jitter and loss before setting aggressive detection timers.

Question 325

A carrier service activation check discovers: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. Which action best restores the intended behavior?

  1. Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.
  2. Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.
  3. Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.
  4. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

Explanation

Correct Answer

B:

Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC. This directly addresses the fictional service-provider network case: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. The technical mechanism is: IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core. Verify success by: LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly.

Incorrect Answers

A:

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: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled.

C:

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: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled.

D:

Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled.

Question 326

Following a supported configuration correction, the original issue was: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. Which observation verifies success?

  1. An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.
  2. A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state.
  3. LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly.
  4. A test packet traverses the intended interface sequence and no longer visits the retired link.

Explanation

Correct Answer

C:

LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly. This confirms the approved response: Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC. It is relevant because: IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.

Incorrect Answers

A:

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: Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.

B:

A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state. This would validate ANOTHER scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. The specific correction here is: Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.

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 LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.

Question 327

At an ISP route assurance team, an engineer examines: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. Which technical principle is most applicable?

  1. LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.
  2. Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.
  3. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.
  4. IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.

Explanation

Correct Answer

D:

IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core. This explains the investigated issue: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. The approved corrective response is: Enable LDP on the approved core interface and verify IGP reachability and label binding for the PE FEC.

Incorrect Answers

A:

LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges. That explains a DIFFERENT 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 mechanism to prioritize for this question is: IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.

B:

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: IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.

C:

Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: IP routing alone does not ensure MPLS forwarding entries are established for a label-switched core.

Question 328

For an ISP route assurance team, the change record describes: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. What preventive validation should be standard?

  1. Test route and label binding presence separately for every new backbone link.
  2. Track per-platform maximum label-stack depth in service design inventory.
  3. Test link startup ordering with IGP and LDP state counters.
  4. Record candidate preferences and validity tests in TE change control.

Explanation

Correct Answer

A:

Test route and label binding presence separately for every new backbone link. This helps prevent recurrence of the issue: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. Acceptance evidence should be: LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly.

Incorrect Answers

B:

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: Test route and label binding presence separately for every new backbone link.

C:

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: Test route and label binding presence separately for every new backbone link.

D:

Record candidate preferences and validity tests in TE change control. That is a sensible control for ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. It is less targeted to this issue than: Test route and label binding presence separately for every new backbone link.

Question 329

For a converged broadband aggregation team, the failure is: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. Which authorized correction best addresses it?

  1. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.
  2. Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.
  3. Configure and verify compatible facility or one-to-one local repair for the critical protected link.
  4. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.

Explanation

Correct Answer

C:

Configure and verify compatible facility or one-to-one local repair for the critical protected link. This directly addresses the fictional service-provider network case: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. The technical mechanism is: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected. Verify success by: Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target.

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 primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut.

B:

Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut.

D:

Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut.

Question 330

After fixing the following network problem, what should the team verify: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut.

  1. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  2. The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.
  3. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  4. Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target.

Explanation

Correct Answer

D:

Link-failure injection switches the intended LSP onto its pre-signaled detour within the acceptance target. This confirms the approved response: Configure and verify compatible facility or one-to-one local repair for the critical protected link. It is relevant because: MPLS TE Fast Reroute prepares local bypass forwarding before a failure is detected.

Incorrect Answers

A:

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: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

B:

The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route. This would validate 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. The specific correction here is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.

C:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Configure and verify compatible facility or one-to-one local repair for the critical protected link.