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 78

Question 770

For a multi-tenant data transport provider, operators addressed: 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. What is the strongest acceptance evidence?

  1. Policy state selects the highest eligible preference candidate and traffic follows its listed segments.
  2. A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.
  3. The PCC installs only approved delegated candidates and reports their active state back to the PCE.
  4. RSVP PATH and RESV state establish across the intended nodes and the LSP forwards test traffic.

Explanation

Correct Answer

B:

A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments. This confirms the approved response: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics. It is relevant because: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

Incorrect Answers

A:

Policy state selects the highest eligible preference candidate and traffic follows its listed segments. This would validate ANOTHER scenario: A carrier configures multiple SR policy candidate paths and expects the smallest latency metric to always win, but an explicitly higher-preference candidate overrides it. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

C:

The PCC installs only approved delegated candidates and reports their active state back to the PCE. This would validate 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. The specific correction here is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

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: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

Question 771

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

  1. SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet.
  2. An SR policy defines an engineered path but requires steering to affect user traffic.
  3. Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.
  4. MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

Explanation

Correct Answer

C:

Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding. This explains the investigated 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. The approved corrective response is: Identify segment types from the advertised IGP/BGP SID attributes and construct the policy with the correct Prefix-SID and adjacency-SID semantics.

Incorrect Answers

A:

SRv6 forwarding requires ordinary IPv6 reachability to the locator before a local SID behavior can process a packet. That explains a DIFFERENT scenario: An SRv6 service router creates a locator inside an IPv6 prefix not advertised in the core, and remote PEs drop encapsulated packets despite matching the local SID function. The mechanism to prioritize for this question is: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

B:

An SR policy defines an engineered path but requires steering to affect user traffic. That explains a DIFFERENT scenario: A Segment Routing policy is installed but no customer route is steered to its binding SID, so measured traffic still follows ordinary IGP shortest paths. The mechanism to prioritize for this question is: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

D:

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: Prefix and adjacency segments have different endpoint and scope semantics in SR-MPLS forwarding.

Question 772

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

  1. Monitor delegated LSP ownership and controller reachability.
  2. Test locator route advertisement whenever new SRv6 functions are provisioned.
  3. Verify LDP discovery, transport and authentication status during peer certification.
  4. Keep segment-type validation with path computation requests.

Explanation

Correct Answer

D:

Keep segment-type validation with path computation requests. This helps prevent recurrence of the 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. Acceptance evidence should be: A route trace follows the destination node for the prefix segment and only the intended local link for adjacency segments.

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: Keep segment-type validation with path computation requests.

B:

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: Keep segment-type validation with path computation requests.

C:

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: Keep segment-type validation with path computation requests.

Question 773

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

  1. Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.
  2. Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.
  3. Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration.
  4. Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path.

Explanation

Correct Answer

B:

Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design. This directly addresses the fictional service-provider network case: 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 technical mechanism is: MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress. Verify success by: Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.

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

C:

Enable supported LDP session protection with stable transport addresses and scoped targeted hello configuration. This would respond to a DIFFERENT fictional service-provider network issue: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. It does not directly address the current situation: A 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.

D:

Replace the strict path element with supported TE-capable nodes or adjust the explicit route to a valid engineered path. This would respond to a DIFFERENT fictional service-provider network issue: A provider changes an RSVP-TE tunnel to use an explicit path containing a router that lacks TE extensions, leaving the tunnel down despite IP reachability. It does not directly address the current situation: A 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.

Question 774

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

  1. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.
  2. The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
  3. Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.
  4. Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels.

Explanation

Correct Answer

C:

Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path. This confirms the approved response: Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design. It is relevant because: MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

Incorrect Answers

A:

During a single-link failure the session remains protected through the alternative route and bound FECs recover safely. This would validate ANOTHER scenario: An LDP transport session disappears whenever the direct router-to-router interface flaps, despite an alternate routed path existing between stable loopbacks. The specific correction here is: Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.

B:

The test isolates a healthy transport LSP from a missing inner VPN route or label binding. This would validate ANOTHER scenario: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. The specific correction here is: Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.

D:

Each router's label forwarding view leads to the same prefix destination despite different permitted local SRGB labels. This would validate ANOTHER scenario: An operator configures an SR-MPLS Prefix-SID for a PE loopback, but different routers assign inconsistent SID indexes relative to their SRGB ranges, causing label misinterpretation. The specific correction here is: Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.

Question 775

At an ISP route assurance team, an engineer examines: 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. Which technical principle is most applicable?

  1. MPLS forwarding hardware may limit the number of imposed or inspected labels per packet.
  2. MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.
  3. SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point.
  4. MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

Explanation

Correct Answer

D:

MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress. This explains the investigated issue: 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 approved corrective response is: Configure consistent MPLS TTL propagation behavior appropriate to the private or visible core design.

Incorrect Answers

A:

MPLS forwarding hardware may limit the number of imposed or inspected labels per packet. That explains a DIFFERENT scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The mechanism to prioritize for this question is: MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

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: MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

C:

SRv6 SIDs and MPLS labels represent different forwarding architectures requiring explicit conversion at an interworking point. That explains a DIFFERENT scenario: An ingress PE applies SRv6 encapsulation but an interworking gateway only supports MPLS label forwarding, so remote L3VPN traffic cannot cross the domain boundary. The mechanism to prioritize for this question is: MPLS TTL propagation settings control how IP and label TTL fields interact at ingress, transit and egress.

Question 776

For an ISP route assurance team, the change record describes: 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. What preventive validation should be standard?

  1. Document TTL transparency and troubleshooting expectations for each service class.
  2. Monitor protected-session status and route-to-transport-loopback reachability.
  3. Test route and label binding presence separately for every new backbone link.
  4. Monitor delegated LSP ownership and controller reachability.

Explanation

Correct Answer

A:

Document TTL transparency and troubleshooting expectations for each service class. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Test traceroutes and MPLS packet TTL values match the intended customer visibility policy across the path.

Incorrect Answers

B:

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: Document TTL transparency and troubleshooting expectations for each service class.

C:

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: Document TTL transparency and troubleshooting expectations for each service class.

D:

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: Document TTL transparency and troubleshooting expectations for each service class.

Question 777

For a converged broadband aggregation team, the failure is: 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 authorized correction best addresses it?

  1. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.
  2. Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.
  3. Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.
  4. Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

Explanation

Correct Answer

C:

Use a supported make-before-break signaling or switchover sequence when available and within resource constraints. This directly addresses the fictional service-provider network case: A provisioning system attempts to reoptimize an RSVP LSP using a new path but drops the existing path before the replacement is established, causing service interruption. The technical mechanism is: Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist. Verify success by: The replacement LSP becomes usable before the previous one is torn down in an acceptance test.

Incorrect Answers

A:

Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

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

D:

Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels. This would respond to a DIFFERENT fictional service-provider network issue: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. It does not directly address the current situation: A 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.

Question 778

After fixing the following network problem, what should the team verify: 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.

  1. FIB lookup for the test customer prefix resolves to the TE tunnel and measured packets follow its engineered path.
  2. Simulated loss of one shared optical component leaves the backup LSP on a truly independent facility.
  3. A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning.
  4. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.

Explanation

Correct Answer

D:

The replacement LSP becomes usable before the previous one is torn down in an acceptance test. This confirms the approved response: Use a supported make-before-break signaling or switchover sequence when available and within resource constraints. It is relevant because: Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.

Incorrect Answers

A:

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: Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.

B:

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: Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.

C:

A maximal permitted label-stack test forwards across the planned platform while an unsupported stack is rejected during provisioning. This would validate ANOTHER scenario: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. The specific correction here is: Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.

Question 779

A carrier root-cause review considers: 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. What underlying mechanism explains this?

  1. Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.
  2. Local protection for a link and local protection for a full node require different bypass topology constraints.
  3. DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls.
  4. SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone.

Explanation

Correct Answer

A:

Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist. This explains the investigated 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. The approved corrective response is: Use a supported make-before-break signaling or switchover sequence when available and within resource constraints.

Incorrect Answers

B:

Local protection for a link and local protection for a full node require different bypass topology constraints. That explains a DIFFERENT scenario: An MPLS TE bypass tunnel is administratively configured but the protected service shows no local protection because node protection was requested and only link protection is available. The mechanism to prioritize for this question is: Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.

C:

DS-TE extends traffic engineering reservation concepts with class-type-aware bandwidth controls. That explains a DIFFERENT scenario: Two DS-TE class types share one link, but one tunnel consumes the other class's reserved budget due to a misconfigured bandwidth constraint allocation. The mechanism to prioritize for this question is: Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.

D:

SR Flexible Algorithm computes paths using a shared algorithm definition and participant capability set, not ordinary best-effort SPF alone. That explains a DIFFERENT scenario: A Flexible Algorithm is activated only on a subset of routers and a service prefix uses a Flex-Algo SID that transit nodes cannot resolve. The mechanism to prioritize for this question is: Make-before-break can retain service continuity while TE paths are re-signaled, provided temporary bandwidth and state exist.

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.