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 80

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.

Question 791

At a wholesale transit provider, an engineer examines: 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 technical principle is most applicable?

  1. SR policy candidate selection can prioritize administrative preference over metric optimization.
  2. SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.
  3. Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.
  4. SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.

Explanation

Correct Answer

D:

SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context. This explains the investigated 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. The approved corrective response is: Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

Incorrect Answers

A:

SR policy candidate selection can prioritize administrative preference over metric optimization. That explains a DIFFERENT 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 mechanism to prioritize for this question is: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.

B:

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: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.

C:

Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. That explains a DIFFERENT 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 mechanism to prioritize for this question is: SRv6 End.DT4 behavior couples decapsulation to an IPv4 table lookup and must be associated with the right service routing context.

Question 792

For a wholesale transit provider, the change record describes: 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. What preventive validation should be standard?

  1. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  2. Include MSD capability checks in every SR policy computation.
  3. Keep segment-type validation with path computation requests.
  4. Maintain optical SRLG metadata with core IGP-TE inventory.

Explanation

Correct Answer

A:

Verify local SID behaviors and VRF bindings during VPN service provisioning. This helps prevent recurrence of the 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. Acceptance evidence should be: A test IPv4 customer route decapsulates into the correct VRF without appearing in another tenant's table.

Incorrect Answers

B:

Include MSD capability checks in every SR policy computation. That is a sensible control for ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It is less targeted to this issue than: Verify local SID behaviors and VRF bindings during VPN service provisioning.

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: Verify local SID behaviors and VRF bindings during VPN service provisioning.

D:

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: Verify local SID behaviors and VRF bindings during VPN service provisioning.

Question 793

For a multi-region fiber backbone operator, the failure is: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. Which authorized correction best addresses it?

  1. Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.
  2. Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.
  3. Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.
  4. Bind the service SID's decapsulation and table lookup behavior to the intended customer VRF.

Explanation

Correct Answer

C:

Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route. This directly addresses the fictional service-provider network case: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The technical mechanism is: A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP. Verify success by: The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.

Incorrect Answers

A:

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 remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved.

B:

Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved.

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 remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved.

Question 794

After fixing the following network problem, what should the team verify: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved.

  1. LDP neighbor tables and LIB/LFIB show the desired transport label and test VPN packets arrive correctly.
  2. Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.
  3. A test packet traverses the intended interface sequence and no longer visits the retired link.
  4. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.

Explanation

Correct Answer

D:

The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This confirms the approved response: Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route. It is relevant because: A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.

Incorrect Answers

A:

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: Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

B:

Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly. This would validate ANOTHER scenario: 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 specific correction here is: Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

C:

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: Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

Question 795

A carrier root-cause review considers: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. What underlying mechanism explains this?

  1. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.
  2. MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.
  3. MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.
  4. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

Explanation

Correct Answer

A:

A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP. This explains the investigated issue: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The approved corrective response is: Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

Incorrect Answers

B:

MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.

C:

MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress. That explains a DIFFERENT scenario: A router's MPLS TTL propagation policy differs from its neighboring core nodes, and traceroute unexpectedly exposes or hides provider hops relative to the service contract. The mechanism to prioritize for this question is: A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.

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: A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.

Question 796

After addressing: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. Which recurring service assurance check is most useful?

  1. Measure end-to-end label-stack MTU at every new pseudowire deployment.
  2. Check IGP and LDP FEC consistency at every interregion boundary.
  3. Monitor protected-session status and route-to-transport-loopback reachability.
  4. Record candidate preferences and validity tests in TE change control.

Explanation

Correct Answer

B:

Check IGP and LDP FEC consistency at every interregion boundary. This helps prevent recurrence of the issue: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. Acceptance evidence should be: The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.

Incorrect Answers

A:

Measure end-to-end label-stack MTU at every new pseudowire deployment. That is a sensible control for ANOTHER scenario: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It is less targeted to this issue than: Check IGP and LDP FEC consistency at every interregion boundary.

C:

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: Check IGP and LDP FEC consistency at every interregion boundary.

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: Check IGP and LDP FEC consistency at every interregion boundary.

Question 797

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

  1. Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination.
  2. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  3. Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.
  4. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

Explanation

Correct Answer

D:

Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state. Verify success by: A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.

Incorrect Answers

A:

Validate TI-LFA eligibility, link/node protection constraints and the repair path toward the intended destination. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

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

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

Question 798

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

  1. A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.
  2. A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end.
  3. FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.
  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

A:

A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state. This confirms the approved response: Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state. It is relevant because: Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.

Incorrect Answers

B:

A worst-case policy passes a documented Maximum SID Depth check and forwards test packets end-to-end. This would validate ANOTHER scenario: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. The specific correction here is: Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

C:

FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF. This would validate 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. The specific correction here is: Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

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: Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

Question 799

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

  1. Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments.
  2. Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.
  3. PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.
  4. RSVP-TE supports priority-based reservation and preemption to allocate scarce transport resources.

Explanation

Correct Answer

B:

Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state. This explains the investigated 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. The approved corrective response is: Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.

Incorrect Answers

A:

Adjacency segments steer traffic over specific local links, unlike more abstract prefix segments. That explains a DIFFERENT scenario: A headend constructs an SR policy from adjacency SIDs but one adjacency SID identifies the wrong outbound interface after topology maintenance. The mechanism to prioritize for this question is: Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.

C:

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: Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.

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: Segment Routing can encode forwarding instructions in the packet and reduce dependency on per-tunnel transit RSVP state.

Question 800

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

  1. Monitor delegated LSP ownership and controller reachability.
  2. Verify local SID behaviors and VRF bindings during VPN service provisioning.
  3. Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks.
  4. Synchronize TE bandwidth advertisement with actual circuit inventory.

Explanation

Correct Answer

C:

Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks. This helps prevent recurrence of the 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. Acceptance evidence should be: A policy forwards using the expected label stack while transit nodes only maintain their advertised segment forwarding state.

Incorrect Answers

A:

Monitor delegated LSP ownership and controller reachability. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks.

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: Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks.

D:

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: Distinguish SR policy state from RSVP-TE tunnel state in operational runbooks.