McAfee Secure

Cisco 350-501 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 Training 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

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 35

Question 340

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS data path shows a valid local label while the downstream label lookup points to a missing outgoing interface. Which continuing control best reduces recurrence of this problem?

  1. Revalidate SR policy end-to-end paths after IGP metric revisions.
  2. Calibrate delay telemetry and revalidate stale path information.
  3. Verify LFIB consistency after routing reconvergence and line-card restart.
  4. Review affinity assignments in link build checklists.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An MPLS data path shows a valid local label while the downstream label lookup points to a missing outgoing interface. The most directly supported response is: Trace the LFIB and IGP next-hop mapping to repair the underlying transport path. Technical basis: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. Evidence of success: Each hop has an eligible outgoing label operation and egress reachability. Ongoing protection: Verify LFIB consistency after routing reconvergence and line-card restart.

Incorrect Answers

A:

The alternative guards against: SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. The root condition for this case is: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The focused prevention check is: Verify LFIB consistency after routing reconvergence and line-card restart.

B:

The alternative guards against: Path computation depends on the attributes advertised or otherwise provided to its topology database. The root condition for this case is: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The focused prevention check is: Verify LFIB consistency after routing reconvergence and line-card restart.

D:

That recurring practice manages a separate exposure: TE affinity constraints select links according to defined administrative groups. The present case instead depends on: An MPLS forwarding entry includes a label action and a next-hop path that must both be valid. The suitable ongoing safeguard is: Verify LFIB consistency after routing reconvergence and line-card restart.

Question 341

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Design local repair paths with actual shared-risk link groups and diversity constraints.
  2. Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls.
  3. Check whether node SID paths are recalculated by SPF and use adjacency SIDs for fixed link requirements.
  4. Use traffic engineering path constraints with measured link attributes and an explicitly defined headend policy.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. The most directly supported response is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls. Technical basis: LDP distributes FEC labels without inherently reserving traffic engineering resources. Evidence of success: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels. Ongoing protection: Document distinct capacity, label, and TE control-plane acceptance criteria.

Incorrect Answers

A:

The option fits a control for: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The present failure is caused by a different mechanism: LDP distributes FEC labels without inherently reserving traffic engineering resources. The targeted implementation is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls.

C:

SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. That principle governs the alternative intervention. The issue described here is different: LDP distributes FEC labels without inherently reserving traffic engineering resources. The case-matched corrective action is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls.

D:

Traffic engineering selects paths based on constraints beyond default shortest-path cost. That principle governs the alternative intervention. The issue described here is different: LDP distributes FEC labels without inherently reserving traffic engineering resources. The case-matched corrective action is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls.

Question 342

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. Which observable result most directly verifies that this network issue was resolved?

  1. A cross-domain service packet traverses the gateway and retains correct customer isolation.
  2. The computed flex-algo path contains only participating nodes and satisfies the defined constraints.
  3. The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels.
  4. A controlled protected-link failure reroutes the tunnel inside the engineered repair target.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. The most directly supported response is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls. Technical basis: LDP distributes FEC labels without inherently reserving traffic engineering resources. Evidence of success: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels. Ongoing protection: Document distinct capacity, label, and TE control-plane acceptance criteria.

Incorrect Answers

A:

The proposed test would be relevant to: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The reported problem follows from: LDP distributes FEC labels without inherently reserving traffic engineering resources. Instead, verify: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels.

B:

That observation tests a different mechanism: SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. It cannot establish this case, whose mechanism is: LDP distributes FEC labels without inherently reserving traffic engineering resources. The needed verification is: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels.

D:

That observation tests a different mechanism: RSVP-TE FRR uses preplanned local bypass or detour paths for fast repair. It cannot establish this case, whose mechanism is: LDP distributes FEC labels without inherently reserving traffic engineering resources. The needed verification is: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels.

Question 343

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. Which underlying network infrastructure principle best explains the situation?

  1. SR policies can support candidate path preference and resilient local control independent of external PCE availability.
  2. RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route.
  3. An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link.
  4. LDP distributes FEC labels without inherently reserving traffic engineering resources.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. The most directly supported response is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls. Technical basis: LDP distributes FEC labels without inherently reserving traffic engineering resources. Evidence of success: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels. Ongoing protection: Document distinct capacity, label, and TE control-plane acceptance criteria.

Incorrect Answers

A:

The alternative principle describes: SR policies can support candidate path preference and resilient local control independent of external PCE availability. In this question, the decisive mechanism is: LDP distributes FEC labels without inherently reserving traffic engineering resources. These are distinct technical causes, even when they share a platform.

B:

The alternative principle describes: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. In this question, the decisive mechanism is: LDP distributes FEC labels without inherently reserving traffic engineering resources. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. In this question, the decisive mechanism is: LDP distributes FEC labels without inherently reserving traffic engineering resources. These are distinct technical causes, even when they share a platform.

Question 344

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. Which continuing control best reduces recurrence of this problem?

  1. Test protected-link and node failures with real traffic traces.
  2. Document distinct capacity, label, and TE control-plane acceptance criteria.
  3. Monitor unreserved bandwidth and tunnel admission rejections.
  4. Verify locator reachability and supported endpoint functions at every transit boundary.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A metro core uses LDP to signal transport labels but the operations team assumes it supplies per-flow bandwidth reservations. The most directly supported response is: Separate basic LDP label reachability from explicit traffic engineering and capacity reservation controls. Technical basis: LDP distributes FEC labels without inherently reserving traffic engineering resources. Evidence of success: The test distinguishes LDP transport LSP reachability from bandwidth-guaranteed engineered tunnels. Ongoing protection: Document distinct capacity, label, and TE control-plane acceptance criteria.

Incorrect Answers

A:

That recurring practice manages a separate exposure: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The present case instead depends on: LDP distributes FEC labels without inherently reserving traffic engineering resources. The suitable ongoing safeguard is: Document distinct capacity, label, and TE control-plane acceptance criteria.

C:

That recurring practice manages a separate exposure: RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable. The present case instead depends on: LDP distributes FEC labels without inherently reserving traffic engineering resources. The suitable ongoing safeguard is: Document distinct capacity, label, and TE control-plane acceptance criteria.

D:

SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. Maintaining that control would not track the failure described here. The relevant risk is: LDP distributes FEC labels without inherently reserving traffic engineering resources. Review this instead: Document distinct capacity, label, and TE control-plane acceptance criteria.

Question 345

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Design local repair paths with actual shared-risk link groups and diversity constraints.
  2. Assess RSVP-TE capability along every hop and choose a supported path or alternative technology.
  3. Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design.
  4. Use an appropriate adjacency SID or constrained SR policy segment list for explicit link steering.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. The most directly supported response is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design. Technical basis: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Evidence of success: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded. Ongoing protection: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

Incorrect Answers

A:

Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. That principle governs the alternative intervention. The issue described here is different: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. The case-matched corrective action is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design.

B:

RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. That principle governs the alternative intervention. The issue described here is different: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. The case-matched corrective action is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design.

D:

The proposed option addresses this separate mechanism: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. The stated problem instead depends on: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. The required response is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design.

Question 346

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. Which observable result most directly verifies that this network issue was resolved?

  1. Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded.
  2. The TE database receives the expected link resources while ordinary reachability remains intact.
  3. The ingress pushes valid segment labels and transit nodes forward to the intended PE.
  4. All selected path nodes accept signaling and the requested reservation appears.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. The most directly supported response is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design. Technical basis: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Evidence of success: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded. Ongoing protection: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

Incorrect Answers

B:

IGP traffic engineering extensions advertise resource attributes distinct from normal SPF reachability. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. A passing check should show: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded.

C:

SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. A passing check should show: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded.

D:

RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. A passing check should show: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded.

Question 347

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. Which underlying network infrastructure principle best explains the situation?

  1. Aggressive TE reoptimization can cause needless path churn even with valid alternate routes.
  2. An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link.
  3. Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques.
  4. TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. The most directly supported response is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design. Technical basis: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Evidence of success: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded. Ongoing protection: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

Incorrect Answers

A:

Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. That is not the causal relationship tested by the current facts. The relevant principle is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques.

B:

An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. That is not the causal relationship tested by the current facts. The relevant principle is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques.

D:

TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. That is not the causal relationship tested by the current facts. The relevant principle is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques.

Question 348

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. Which continuing control best reduces recurrence of this problem?

  1. Test protected-link and node failures with real traffic traces.
  2. Validate detour capacity and protection coverage after topology changes.
  3. Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.
  4. Test feature negotiation and service continuity before enabling compressed SID policies.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A regional provider must connect multiple metro access islands into a unified MPLS backbone without maintaining a single giant flat IGP area. The most directly supported response is: Plan transport segmentation and labeled next-hop reachability across areas under a unified MPLS design. Technical basis: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Evidence of success: Remote PE loopbacks resolve over the engineered interarea labeled transport while local IGP scale stays bounded. Ongoing protection: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

Incorrect Answers

A:

TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Maintaining that control would not track the failure described here. The relevant risk is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Review this instead: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

B:

RSVP-TE FRR uses preplanned local bypass or detour paths for fast repair. Maintaining that control would not track the failure described here. The relevant risk is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. Review this instead: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

D:

The alternative guards against: SRv6 micro-segment techniques compress functions but depend on interoperable network behavior. The root condition for this case is: Unified MPLS extends labeled reachability across routing domains using supported BGP and IGP transport techniques. The focused prevention check is: Audit labeled next-hop continuity and route-resolution dependencies at every area boundary.

Question 349

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: LSP ping succeeds to one PE but a customer VPN's forwarding fails, and operators confuse transport OAM with service OAM. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use platform-supported SRv6 locator and endpoint behavior with the required encapsulation mode.
  2. Test both the transport label-switched path and the VPN-specific service label disposition.
  3. Choose a compatible SRv6 micro-segment model or an explicit full-SID path for the mixed environment.
  4. Enable supported OSPF TE extensions and inspect the advertised link attributes.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: LSP ping succeeds to one PE but a customer VPN's forwarding fails, and operators confuse transport OAM with service OAM. The most directly supported response is: Test both the transport label-switched path and the VPN-specific service label disposition. Technical basis: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. Evidence of success: Transport LSP tests and end-to-end customer VRF forwarding are independently verified. Ongoing protection: Run layered transport and service validation before declaring turn-up complete.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. The stated problem instead depends on: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. The required response is: Test both the transport label-switched path and the VPN-specific service label disposition.

C:

The option fits a control for: SRv6 micro-segment techniques compress functions but depend on interoperable network behavior. The present failure is caused by a different mechanism: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. The targeted implementation is: Test both the transport label-switched path and the VPN-specific service label disposition.

D:

The option fits a control for: IGP traffic engineering extensions advertise resource attributes distinct from normal SPF reachability. The present failure is caused by a different mechanism: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. The targeted implementation is: Test both the transport label-switched path and the VPN-specific service label disposition.

Question 350

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: LSP ping succeeds to one PE but a customer VPN's forwarding fails, and operators confuse transport OAM with service OAM. Which observable result most directly verifies that this network issue was resolved?

  1. Traffic continues over the approved fallback after the tunnel is removed.
  2. Transport LSP tests and end-to-end customer VRF forwarding are independently verified.
  3. Mixed-domain traffic follows the intended route without unsupported SID decoding.
  4. Failure testing shows packets avoid microloops and recover through the planned repair within target.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: LSP ping succeeds to one PE but a customer VPN's forwarding fails, and operators confuse transport OAM with service OAM. The most directly supported response is: Test both the transport label-switched path and the VPN-specific service label disposition. Technical basis: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. Evidence of success: Transport LSP tests and end-to-end customer VRF forwarding are independently verified. Ongoing protection: Run layered transport and service validation before declaring turn-up complete.

Incorrect Answers

A:

TE tunnel control-plane teardown and service-level forwarding dependencies must be coordinated. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. A passing check should show: Transport LSP tests and end-to-end customer VRF forwarding are independently verified.

C:

The proposed test would be relevant to: SRv6 micro-segment techniques compress functions but depend on interoperable network behavior. The reported problem follows from: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. Instead, verify: Transport LSP tests and end-to-end customer VRF forwarding are independently verified.

D:

The proposed test would be relevant to: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The reported problem follows from: MPLS transport OAM proves a labeled path but does not automatically prove service VPN import and forwarding. Instead, verify: Transport LSP tests and end-to-end customer VRF forwarding are independently verified.