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 79

Question 780

After addressing: 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. Which recurring service assurance check is most useful?

  1. Maintain optical SRLG metadata with core IGP-TE inventory.
  2. Include intermediate capacity and sequencing validation in path migration scripts.
  3. Audit RSVP reservation lifetimes and headend ownership regularly.
  4. Test route and label binding presence separately for every new backbone link.

Explanation

Correct Answer

B:

Include intermediate capacity and sequencing validation in path migration scripts. This helps prevent recurrence of the issue: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. Acceptance evidence should be: The replacement LSP becomes usable before the previous one is torn down in an acceptance test.

Incorrect Answers

A:

Maintain optical SRLG metadata with core IGP-TE inventory. That is a sensible control for ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It is less targeted to this issue than: Include intermediate capacity and sequencing validation in path migration scripts.

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: Include intermediate capacity and sequencing validation in path migration scripts.

D:

Test route and label binding presence separately for every new backbone link. That is a sensible control for ANOTHER scenario: Two P routers forward IPv4 internet traffic but no MPLS labels appear for PE loopbacks because one interface has LDP disabled. It is less targeted to this issue than: Include intermediate capacity and sequencing validation in path migration scripts.

Question 781

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  2. Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy.
  3. Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.
  4. Review SR policy candidate preference and validation rules before comparing metric objectives.

Explanation

Correct Answer

D:

Review SR policy candidate preference and validation rules before comparing metric objectives. This directly addresses the fictional service-provider network case: 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 technical mechanism is: SR policy candidate selection can prioritize administrative preference over metric optimization. Verify success by: Policy state selects the highest eligible preference candidate and traffic follows its listed segments.

Incorrect Answers

A:

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 carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it.

B:

Configure an explicit color/endpoint or route-policy steering association that maps the service flow to the intended SR policy. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

C:

Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

Question 782

A service-provider operations test targets: 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. Which result is required?

  1. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  2. A controlled transit-node failure uses the precomputed repair path within the stated local restoration target.
  3. A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint.
  4. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Explanation

Correct Answer

A:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This confirms the approved response: Review SR policy candidate preference and validation rules before comparing metric objectives. It is relevant because: SR policy candidate selection can prioritize administrative preference over metric optimization.

Incorrect Answers

B:

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: Review SR policy candidate preference and validation rules before comparing metric objectives.

C:

A remote PE reaches the locator and the SRv6 behavior executes at the intended endpoint. This would validate ANOTHER scenario: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. The specific correction here is: Review SR policy candidate preference and validation rules before comparing metric objectives.

D:

RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic. This would validate ANOTHER 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 specific correction here is: Review SR policy candidate preference and validation rules before comparing metric objectives.

Question 783

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information.
  2. SR policy candidate selection can prioritize administrative preference over metric optimization.
  3. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.
  4. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

Explanation

Correct Answer

B:

SR policy candidate selection can prioritize administrative preference over metric optimization. This explains the investigated 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. The approved corrective response is: Review SR policy candidate preference and validation rules before comparing metric objectives.

Incorrect Answers

A:

Topology-Independent Loop-Free Alternate mechanisms depend on available SID repair paths and correct topological information. That explains a DIFFERENT 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 mechanism to prioritize for this question is: SR policy candidate selection can prioritize administrative preference over metric optimization.

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: SR policy candidate selection can prioritize administrative preference over metric optimization.

D:

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: SR policy candidate selection can prioritize administrative preference over metric optimization.

Question 784

To prevent recurrence of this 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. Which control should be retained?

  1. Check SR policy candidate selection and actual prefix steering in acceptance.
  2. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  3. Record candidate preferences and validity tests in TE change control.
  4. Document TTL transparency and troubleshooting expectations for each service class.

Explanation

Correct Answer

C:

Record candidate preferences and validity tests in TE change control. This helps prevent recurrence of the 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. Acceptance evidence should be: Policy state selects the highest eligible preference candidate and traffic follows its listed segments.

Incorrect Answers

A:

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: Record candidate preferences and validity tests in TE change control.

B:

Verify local SID behaviors and VRF bindings during VPN service provisioning. That is a sensible control for ANOTHER scenario: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. It is less targeted to this issue than: Record candidate preferences and validity tests in TE change control.

D:

Document TTL transparency and troubleshooting expectations for each service class. That is a sensible control for 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. It is less targeted to this issue than: Record candidate preferences and validity tests in TE change control.

Question 785

At a regional service-provider operations center, an engineering review finds: 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. Which change most directly corrects the service problem?

  1. Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.
  2. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.
  3. Design the supported unified MPLS hierarchy with transport label continuity and controlled route exchange at the ABR or AS border.
  4. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

Explanation

Correct Answer

A:

Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately. This directly addresses the fictional service-provider network case: 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 technical mechanism is: MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations. Verify success by: A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state.

Incorrect Answers

B:

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 P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context.

C:

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 P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context.

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

Question 786

For a regional service-provider operations center, operators addressed: 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. 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 P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state.
  3. A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed.
  4. The TE database contains capacity and administrative-group information for all selected links and the constraint solver returns a valid route.

Explanation

Correct Answer

B:

A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state. This confirms the approved response: Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately. It is relevant because: MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.

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: Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.

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: Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.

D:

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: Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.

Question 787

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

  1. Unified MPLS connects labeled forwarding domains through compatible hierarchical transport and route policies rather than universal direct LDP peering.
  2. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.
  3. MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.
  4. Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

Explanation

Correct Answer

C:

MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations. This explains the investigated issue: 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 approved corrective response is: Separate provider transport label distribution from customer VPN service-label signaling and restrict advertised FECs appropriately.

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 transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.

B:

A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP. That explains a DIFFERENT scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The mechanism to prioritize for this question is: MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.

D:

Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding. That explains a DIFFERENT scenario: A router advertises a Prefix-SID for a loopback but another node's policy interprets the index as an adjacency segment and sends traffic out an unrelated interface. The mechanism to prioritize for this question is: MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.

Question 788

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

  1. Monitor protected-session status and route-to-transport-loopback reachability.
  2. Verify LDP discovery, transport and authentication status during peer certification.
  3. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.
  4. Review FEC label policy and routing context boundaries at PE-P handoffs.

Explanation

Correct Answer

D:

Review FEC label policy and routing context boundaries at PE-P handoffs. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A P router's LFIB contains approved core transport FECs and no unintended VRF-specific customer forwarding state.

Incorrect Answers

A:

Monitor protected-session status and route-to-transport-loopback reachability. That is a sensible control for ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It is less targeted to this issue than: Review FEC label policy and routing context boundaries at PE-P handoffs.

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: Review FEC label policy and routing context boundaries at PE-P handoffs.

C:

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: Review FEC label policy and routing context boundaries at PE-P handoffs.

Question 789

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

  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. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.
  3. Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
  4. Align authorized LDP session authentication and transport addresses on the intended peers.

Explanation

Correct Answer

B:

Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. This directly addresses the fictional service-provider network case: An SRv6 egress router discards traffic because a local End.DT4 service SID is placed in the wrong VRF context, even though the locator is reachable. The technical mechanism is: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context. Verify success by: A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table.

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

C:

Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

D:

Align authorized LDP session authentication and transport addresses on the intended peers. This would respond to a DIFFERENT fictional service-provider network issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It does not directly address the current situation: 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.

Question 790

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

  1. A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.
  2. An isolated service-prefix test traverses the gateway with the expected service context preserved.
  3. A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table.
  4. FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.

Explanation

Correct Answer

C:

A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table. This confirms the approved response: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF. It is relevant because: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.

Incorrect Answers

A:

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: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

B:

An isolated service-prefix test traverses the gateway with the expected service context preserved. This would validate 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. The specific correction here is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

D:

FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path. This would validate ANOTHER scenario: The route processor shows an RSVP-TE tunnel Up, but a live traffic test still traverses native IGP forwarding because the tunnel is not selected for the destination. The specific correction here is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.