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 7

Question 60

After addressing: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. Which recurring service assurance check is most useful?

  1. Baseline BFD jitter and loss before setting aggressive detection timers.
  2. Exercise planned supervisor failovers with forwarding and GR timer telemetry.
  3. Maintain release-specific ISSU qualification and rollback documentation.
  4. Test component-prefix ownership before exporting aggregates.

Explanation

Correct Answer

B:

Exercise planned supervisor failovers with forwarding and GR timer telemetry. This helps prevent recurrence of the issue: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. Acceptance evidence should be: During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.

Incorrect Answers

A:

Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.

C:

Maintain release-specific ISSU qualification and rollback documentation. That is a sensible control for ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.

D:

Test component-prefix ownership before exporting aggregates. That is a sensible control for ANOTHER scenario: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It is less targeted to this issue than: Exercise planned supervisor failovers with forwarding and GR timer telemetry.

Question 61

A provider backbone escalation identifies: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets. What should the network team implement?

  1. Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.
  2. Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract.
  3. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  4. Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.

Explanation

Correct Answer

D:

Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready. This directly addresses the fictional service-provider network case: 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 technical mechanism is: LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges. Verify success by: A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed.

Incorrect Answers

A:

Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets.

B:

Align MPLS payload MTU and transport frame size, or adjust effective service MTU with the customer handoff contract. This would respond to a DIFFERENT fictional service-provider network issue: An MPLS pseudowire intermittently drops large customer frames after VLAN tagging increases payload size beyond a transit link's supported frame budget. It does not directly address the current situation: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets.

C:

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 upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets.

Question 62

A service-provider operations test targets: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets. Which result is required?

  1. A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed.
  2. A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.
  3. The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution.
  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 lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed. This confirms the approved response: Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready. It is relevant because: LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.

Incorrect Answers

B:

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: Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.

C:

The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution. This would validate 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. The specific correction here is: Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.

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: Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.

Question 63

A provider troubleshooting note states: A provider upgrades an MPLS core and OSPF sends traffic over a new link before LDP has exchanged transport labels there, blackholing VPN packets. Which mechanism is central?

  1. A label binding without reachable next-hop context is insufficient to deliver a usable MPLS transport LSP.
  2. LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.
  3. LDP session protection uses extended hello/discovery behavior to retain a TCP session across some direct-link failures.
  4. PCEP path computation and policy delegation are distinct capabilities with explicit controller-to-headend authority.

Explanation

Correct Answer

B:

LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges. This explains the investigated 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. The approved corrective response is: Apply supported LDP-IGP synchronization so the IGP does not prefer the link for label-switched traffic until LDP is ready.

Incorrect Answers

A:

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: LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.

C:

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: LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.

D:

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: LDP-IGP synchronization prevents a transit path from carrying labeled traffic before the label distribution plane converges.

Question 64

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

  1. Include transport and service-layer OAM in VPN fault playbooks.
  2. Document TTL transparency and troubleshooting expectations for each service class.
  3. Test link startup ordering with IGP and LDP state counters.
  4. Test locator route advertisement whenever new SRv6 functions are provisioned.

Explanation

Correct Answer

C:

Test link startup ordering with IGP and LDP state counters. This helps prevent recurrence of the 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. Acceptance evidence should be: A lab link turn-up shows the route only becomes preferred for MPLS service after the necessary label bindings are installed.

Incorrect Answers

A:

Include transport and service-layer OAM in VPN fault playbooks. That is a sensible control for 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. It is less targeted to this issue than: Test link startup ordering with IGP and LDP state counters.

B:

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: Test link startup ordering with IGP and LDP state counters.

D:

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: Test link startup ordering with IGP and LDP state counters.

Question 65

At a multi-region fiber backbone operator, an engineering review finds: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. Which change most directly corrects the service problem?

  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. Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy.
  4. Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

Explanation

Correct Answer

A:

Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. Verify success by: CSPF selects an eligible path whose measured reserved capacity meets the service constraint.

Incorrect Answers

B:

Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives. This would respond to a DIFFERENT fictional service-provider network issue: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. It does not directly address the current situation: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale.

C:

Correct class-type bandwidth model and bandwidth constraints to match the provider's differentiated service policy. This would respond to a DIFFERENT fictional service-provider network issue: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. It does not directly address the current situation: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale.

D:

Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth. This would respond to a DIFFERENT fictional service-provider network issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It does not directly address the current situation: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale.

Question 66

For a multi-region fiber backbone operator, operators addressed: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. What is the strongest acceptance evidence?

  1. A capacity test shows lower-priority reservations yield to approved higher-priority needs under constrained bandwidth.
  2. CSPF selects an eligible path whose measured reserved capacity meets the service constraint.
  3. Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.
  4. An isolated service-prefix test traverses the gateway with the expected service context preserved.

Explanation

Correct Answer

B:

CSPF selects an eligible path whose measured reserved capacity meets the service constraint. This confirms the approved response: Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route. It is relevant because: Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.

Incorrect Answers

A:

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: Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.

C:

Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility. This would validate ANOTHER scenario: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. The specific correction here is: Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.

D:

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: Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.

Question 67

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

  1. RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology.
  2. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.
  3. Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.
  4. MPLS OAM for one FEC or layer does not independently verify every overlaid customer service.

Explanation

Correct Answer

C:

Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale. This explains the investigated 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. The approved corrective response is: Correct IGP-TE link capacity and reservable bandwidth attributes and recompute the constrained route.

Incorrect Answers

A:

RSVP-TE explicit routing requires nodes along the selected path to support the signaling and advertised TE topology. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.

B:

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: Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.

D:

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: Constrained Shortest Path First relies on advertised TE attributes and can make incorrect admission decisions if topology data is stale.

Question 68

A core network change board wants to avoid: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. Which ongoing safeguard fits best?

  1. Test the exact failure class named in each protection service objective.
  2. Track class-type utilization and validate reservation boundaries after QoS changes.
  3. Test locator route advertisement whenever new SRv6 functions are provisioned.
  4. Synchronize TE bandwidth advertisement with actual circuit inventory.

Explanation

Correct Answer

D:

Synchronize TE bandwidth advertisement with actual circuit inventory. This helps prevent recurrence of the 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. Acceptance evidence should be: CSPF selects an eligible path whose measured reserved capacity meets the service constraint.

Incorrect Answers

A:

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: Synchronize TE bandwidth advertisement with actual circuit inventory.

B:

Track class-type utilization and validate reservation boundaries after QoS changes. That is a sensible control for 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. It is less targeted to this issue than: Synchronize TE bandwidth advertisement with actual circuit inventory.

C:

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: Synchronize TE bandwidth advertisement with actual circuit inventory.

Question 69

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

  1. Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.
  2. Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.
  3. Use IGP-distributed SIDs and supported SR policy steering without imposing unnecessary per-LSP RSVP signaling state.
  4. Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route.

Explanation

Correct Answer

B:

Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values. Verify success by: Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.

Incorrect Answers

A:

Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth. This would respond to a DIFFERENT fictional service-provider network issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It does not directly address the current situation: 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.

C:

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

D:

Restore loopback reachability and confirm the label's mapped FEC belongs to an installed valid route. This would respond to a DIFFERENT fictional service-provider network issue: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. It does not directly address the current situation: 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.

Question 70

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

  1. A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.
  2. FIB and label-stack readback show the selected traffic enters the SR policy while unrelated flows remain on normal SPF.
  3. Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.
  4. Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.

Explanation

Correct Answer

C:

Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This confirms the approved response: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. It is relevant because: Prefix-SID indexes are interpreted through each node's advertised Segment Routing Global Block, not as universally identical label values.

Incorrect Answers

A:

A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This would validate 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. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

B:

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: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

D:

Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This would validate 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. The specific correction here is: Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.