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 54

Question 530

For a managed VPN service carrier, operators addressed: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. What is the strongest acceptance evidence?

  1. A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.
  2. A test at the required maximum service size passes without fragmentation-dependent loss or interface MTU errors.
  3. A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.
  4. A stress test admits or rejects reservations according to the per-class budget without starving the protected class.

Explanation

Correct Answer

B:

A test at the required maximum service size passes without fragmentation-dependent loss or interface MTU errors. This confirms the approved response: Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract. It is relevant because: MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.

Incorrect Answers

A:

A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE. This would validate 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. The specific correction here is: Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.

C:

A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning. This would validate ANOTHER scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The specific correction here is: Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.

D:

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: Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.

Question 531

Which network protocol or forwarding behavior explains the following issue: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget.

  1. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.
  2. MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.
  3. MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.
  4. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

Explanation

Correct Answer

C:

MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU. This explains the investigated issue: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. The approved corrective response is: Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.

Incorrect Answers

A:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. That explains a DIFFERENT scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The mechanism to prioritize for this question is: MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.

B:

MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.

D:

RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources. That explains a DIFFERENT scenario: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. The mechanism to prioritize for this question is: MPLS labels and service tags add encapsulation overhead that must fit within the backbone's effective MTU.

Question 532

A core network change board wants to avoid: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. Which ongoing safeguard fits best?

  1. Alert on mismatched IGP FEC and LFIB installation counters.
  2. Track per-platform maximum label-stack depth in service design inventory.
  3. Include TE database completeness checks during IGP maintenance.
  4. Measure end-to-end label-stack MTU at every new pseudowire deployment.

Explanation

Correct Answer

D:

Measure end-to-end label-stack MTU at every new pseudowire deployment. This helps prevent recurrence of the issue: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. Acceptance evidence should be: A test at the required maximum service size passes without fragmentation-dependent loss or interface MTU errors.

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: Measure end-to-end label-stack MTU at every new pseudowire deployment.

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: Measure end-to-end label-stack MTU at every new pseudowire deployment.

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: Measure end-to-end label-stack MTU at every new pseudowire deployment.

Question 533

A carrier service activation check discovers: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. 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. Set explicit TE priority and bandwidth allocation policies for the intended service classes.
  3. Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes.
  4. Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

Explanation

Correct Answer

B:

Set explicit TE priority and bandwidth allocation policies for the intended service classes. This directly addresses the fictional service-provider network case: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. The technical mechanism is: RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources. Verify success by: A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.

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: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable.

C:

Install the intended route or autoroute steering policy into the established TE tunnel without affecting unrelated prefixes. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable.

D:

Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable.

Question 534

Following a supported configuration correction, the original issue was: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. Which observation verifies success?

  1. The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.
  2. CSPF selects an eligible path whose measured reserved capacity meets the service constraint.
  3. A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.
  4. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.

Explanation

Correct Answer

C:

A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth. This confirms the approved response: Set explicit TE priority and bandwidth allocation policies for the intended service classes. It is relevant because: RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

Incorrect Answers

A:

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: Set explicit TE priority and bandwidth allocation policies for the intended service classes.

B:

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: Set explicit TE priority and bandwidth allocation policies for the intended service classes.

D:

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: Set explicit TE priority and bandwidth allocation policies for the intended service classes.

Question 535

At a regional peering-exchange operator, an engineer examines: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. Which technical principle is most applicable?

  1. Unbounded TE path reoptimization can create control-plane churn and traffic disruption without improving service outcomes.
  2. DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.
  3. MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.
  4. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

Explanation

Correct Answer

D:

RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources. This explains the investigated issue: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. The approved corrective response is: Set explicit TE priority and bandwidth allocation policies for the intended service classes.

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: RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

B:

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: RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

C:

MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

Question 536

For a regional peering-exchange operator, the change record describes: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. What preventive validation should be standard?

  1. Test preemption conditions and impact warnings before new tunnel activation.
  2. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.
  3. Audit RSVP reservation lifetimes and headend ownership regularly.
  4. Keep segment-type validation with path computation requests.

Explanation

Correct Answer

A:

Test preemption conditions and impact warnings before new tunnel activation. This helps prevent recurrence of the issue: A provider enables RSVP bandwidth reservation but leaves all tunnels with one identical setup and holding priority, making critical voice LSP preemption unpredictable. Acceptance evidence should be: A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.

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: Test preemption conditions and impact warnings before new tunnel activation.

C:

Audit RSVP reservation lifetimes and headend ownership regularly. That is a sensible control for 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. It is less targeted to this issue than: Test preemption conditions and impact warnings before new tunnel activation.

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: Test preemption conditions and impact warnings before new tunnel activation.

Question 537

For an optical transport engineering team, the failure is: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Which authorized correction best addresses it?

  1. Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.
  2. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  3. Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.
  4. Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.

Explanation

Correct Answer

C:

Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules. This directly addresses the fictional service-provider network case: 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 technical mechanism is: PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority. Verify success by: The PCC installs only approved delegated candidates and reports their active state back to the PCE.

Incorrect Answers

A:

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 PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control.

B:

Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains. This would respond to a DIFFERENT fictional service-provider network issue: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. It does not directly address the current situation: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control.

D:

Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration. This would respond to a DIFFERENT fictional service-provider network issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It does not directly address the current situation: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control.

Question 538

After fixing the following network problem, what should the team verify: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control.

  1. Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.
  2. A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.
  3. LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly.
  4. The PCC installs only approved delegated candidates and reports their active state back to the PCE.

Explanation

Correct Answer

D:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This confirms the approved response: Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules. It is relevant because: PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

Incorrect Answers

A:

Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This would validate ANOTHER 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 specific correction here is: Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.

B:

A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state. This would validate ANOTHER 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 specific correction here is: Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.

C:

LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly. This would validate ANOTHER scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. The specific correction here is: Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.

Question 539

A carrier root-cause review considers: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. What underlying mechanism explains this?

  1. PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.
  2. An SR policy defines an engineered path but requires steering to affect user traffic.
  3. SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.
  4. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.

Explanation

Correct Answer

A:

PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority. This explains the investigated issue: 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 approved corrective response is: Align PCE-PCC session capabilities and authenticated delegated SR policy configuration with the provider's control rules.

Incorrect Answers

B:

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: PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

C:

SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point. That explains a DIFFERENT scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The mechanism to prioritize for this question is: PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

D:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. That explains a DIFFERENT scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The mechanism to prioritize for this question is: PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

Question 540

After addressing: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Which recurring service assurance check is most useful?

  1. Verify control-plane service route labels and locator reachability across interdomain handoffs.
  2. Monitor delegated LSP ownership and controller reachability.
  3. Keep segment-type validation with path computation requests.
  4. Include TE database completeness checks during IGP maintenance.

Explanation

Correct Answer

B:

Monitor delegated LSP ownership and controller reachability. This helps prevent recurrence of the issue: A PCE computes a low-latency SR-TE candidate, but the PCC ignores it because the PCEP session lacks authorization for delegated policy control. Acceptance evidence should be: The PCC installs only approved delegated candidates and reports their active state back to the PCE.

Incorrect Answers

A:

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

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: Monitor delegated LSP ownership and controller reachability.

D:

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: Monitor delegated LSP ownership and controller reachability.