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 70

Question 690

For a global tier-one IP transit carrier, operators addressed: 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. What is the strongest acceptance evidence?

  1. The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
  2. Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.
  3. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.
  4. CSPF selects an eligible path whose measured reserved capacity meets the service constraint.

Explanation

Correct Answer

B:

Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly. This confirms the approved response: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels. It is relevant because: MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

Incorrect Answers

A:

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: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

C:

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: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

D:

CSPF selects an eligible path whose measured reserved capacity meets the service constraint. This would validate ANOTHER 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 specific correction here is: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

Question 691

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

  1. MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.
  2. LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.
  3. MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.
  4. SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.

Explanation

Correct Answer

C:

MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress. This explains the investigated issue: 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 approved corrective response is: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

Incorrect Answers

A:

MPLS OAM for one FEC or layer does not independently verify every overlaid customer service. That explains a DIFFERENT 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 mechanism to prioritize for this question is: MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

B:

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: MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

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 implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

Question 692

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

  1. Track per-platform maximum label-stack depth in service design inventory.
  2. Review FEC label policy and routing context boundaries at PE-P handoffs.
  3. Include TE database completeness checks during IGP maintenance.
  4. Train operators to differentiate implicit-null, explicit-null and real transport labels.

Explanation

Correct Answer

D:

Train operators to differentiate implicit-null, explicit-null and real transport labels. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.

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: Train operators to differentiate implicit-null, explicit-null and real transport labels.

B:

Review FEC label policy and routing context boundaries at PE-P handoffs. That is a sensible control for 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. It is less targeted to this issue than: Train operators to differentiate implicit-null, explicit-null and real transport labels.

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: Train operators to differentiate implicit-null, explicit-null and real transport labels.

Question 693

A carrier service activation check discovers: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. Which action best restores the intended behavior?

  1. Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.
  2. Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.
  3. Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation.
  4. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

Explanation

Correct Answer

B:

Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives. This directly addresses the fictional service-provider network case: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The technical mechanism is: Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes. Verify success by: Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.

Incorrect Answers

A:

Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. It does not directly address the current situation: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation.

C:

Inspect RSVP reservation state and remove stale or excess allocations through supported teardown and reconciliation. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation.

D:

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: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation.

Question 694

Following a supported configuration correction, the original issue was: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. Which observation verifies success?

  1. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  2. A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.
  3. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  4. An MPLS capture shows the egress PE still receives the necessary inner VPN service label for correct VRF lookup.

Explanation

Correct Answer

C:

Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed. This confirms the approved response: Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives. It is relevant because: Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

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: Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.

B:

A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth. This would validate ANOTHER 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 specific correction here is: Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.

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: Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.

Question 695

At a mobile packet-core transport operator, an engineer examines: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. Which technical principle is most applicable?

  1. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.
  2. Local protection for a link and local protection for a full node require different bypass topology constraints.
  3. MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.
  4. Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

Explanation

Correct Answer

D:

Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes. This explains the investigated issue: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The approved corrective response is: Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.

Incorrect Answers

A:

Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

B:

Local protection for a link and local protection for a full node require different bypass topology constraints. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

C:

MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU. That explains a DIFFERENT scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. The mechanism to prioritize for this question is: Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

Question 696

For a mobile packet-core transport operator, the change record describes: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. What preventive validation should be standard?

  1. Record reoptimization stability and path-change rate in monitoring.
  2. Synchronize TE bandwidth advertisement with actual circuit inventory.
  3. Test preemption conditions and impact warnings before new tunnel activation.
  4. Keep segment-type validation with path computation requests.

Explanation

Correct Answer

A:

Record reoptimization stability and path-change rate in monitoring. This helps prevent recurrence of the issue: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. Acceptance evidence should be: Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.

Incorrect Answers

B:

Synchronize TE bandwidth advertisement with actual circuit inventory. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Record reoptimization stability and path-change rate in monitoring.

C:

Test preemption conditions and impact warnings before new tunnel activation. That is a sensible control for ANOTHER scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. It is less targeted to this issue than: Record reoptimization stability and path-change rate in monitoring.

D:

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: Record reoptimization stability and path-change rate in monitoring.

Question 697

For a managed VPN service carrier, the failure is: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Which authorized correction best addresses it?

  1. Review SR policy candidate preference and validation rules before comparing metric objectives.
  2. Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility.
  3. Align micro-segment block, locator and local function behavior on every participating SRv6 node.
  4. Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.

Explanation

Correct Answer

C:

Align micro-segment block, locator and local function behavior on every participating SRv6 node. This directly addresses the fictional service-provider network case: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. The technical mechanism is: SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path. Verify success by: A test packet advances through the micro-segment sequence and exits at the intended service SID.

Incorrect Answers

A:

Review SR policy candidate preference and validation rules before comparing metric objectives. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup.

B:

Advertise the reachable SRv6 locator with the appropriate IGP/BGP reachability and check IPv6 forwarding compatibility. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup.

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 compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup.

Question 698

After fixing the following network problem, what should the team verify: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup.

  1. Flex-Algo route and SID tables show a consistent constraint topology across the intended service path.
  2. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  3. A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.
  4. A test packet advances through the micro-segment sequence and exits at the intended service SID.

Explanation

Correct Answer

D:

A test packet advances through the micro-segment sequence and exits at the intended service SID. This confirms the approved response: Align micro-segment block, locator and local function behavior on every participating SRv6 node. It is relevant because: SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path.

Incorrect Answers

A:

Flex-Algo route and SID tables show a consistent constraint topology across the intended service path. This would validate ANOTHER scenario: 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. The specific correction here is: Align micro-segment block, locator and local function behavior on every participating SRv6 node.

B:

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: Align micro-segment block, locator and local function behavior on every participating SRv6 node.

C:

A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth. This would validate ANOTHER 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 specific correction here is: Align micro-segment block, locator and local function behavior on every participating SRv6 node.

Question 699

A carrier root-cause review considers: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. What underlying mechanism explains this?

  1. SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path.
  2. PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.
  3. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.
  4. Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.

Explanation

Correct Answer

A:

SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path. This explains the investigated issue: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. The approved corrective response is: Align micro-segment block, locator and local function behavior on every participating SRv6 node.

Incorrect Answers

B:

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: SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path.

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: SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path.

D:

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: SRv6 uSID compression relies on a shared locator and micro-segment encoding model along the path.

Question 700

After addressing: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Which recurring service assurance check is most useful?

  1. Test locator route advertisement whenever new SRv6 functions are provisioned.
  2. Maintain validated micro-segment encoding templates per software release.
  3. Check SR policy candidate selection and actual prefix steering in acceptance.
  4. Test the exact failure class named in each protection service objective.

Explanation

Correct Answer

B:

Maintain validated micro-segment encoding templates per software release. This helps prevent recurrence of the issue: A provider compresses SRv6 micro-segments into a uSID container but configures an incompatible locator block structure on one endpoint, breaking the final function lookup. Acceptance evidence should be: A test packet advances through the micro-segment sequence and exits at the intended service SID.

Incorrect Answers

A:

Test locator route advertisement whenever new SRv6 functions are provisioned. That is a sensible control for 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. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.

C:

Check SR policy candidate selection and actual prefix steering in acceptance. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.

D:

Test the exact failure class named in each protection service objective. That is a sensible control for 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. It is less targeted to this issue than: Maintain validated micro-segment encoding templates per software release.