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 33

Question 320

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS PE advertises VPN routes while its core LDP neighbors have not formed, so VPN packets are dropped inside the provider backbone. Which continuing control best reduces recurrence of this problem?

  1. Check LDP session state and outgoing-label resolution during PE activation.
  2. Audit flex-algo definition consistency and excluded-node handling.
  3. Validate per-hop feature support before allocating customer TE products.
  4. Revalidate SR policy end-to-end paths after IGP metric revisions.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An MPLS PE advertises VPN routes while its core LDP neighbors have not formed, so VPN packets are dropped inside the provider backbone. The most directly supported response is: Restore supported LDP neighbor discovery and label exchange across the transport path before enabling service traffic. Technical basis: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. Evidence of success: Hop-by-hop LFIB entries exist along the route and test VPN packets reach the remote PE. Ongoing protection: Check LDP session state and outgoing-label resolution during PE activation.

Incorrect Answers

B:

That recurring practice manages a separate exposure: SR Flexible Algorithm derives separate constraint-based IGP topologies from shared advertisements. The present case instead depends on: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The suitable ongoing safeguard is: Check LDP session state and outgoing-label resolution during PE activation.

C:

That recurring practice manages a separate exposure: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The present case instead depends on: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. The suitable ongoing safeguard is: Check LDP session state and outgoing-label resolution during PE activation.

D:

SR node SIDs represent destinations with shortest-path forwarding and do not pin every intermediate link. Maintaining that control would not track the failure described here. The relevant risk is: MPLS forwarding depends on an end-to-end usable label-switched transport path beneath service labels. Review this instead: Check LDP session state and outgoing-label resolution during PE activation.

Question 321

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Compute a supported topology-independent loop-free alternate repair path for the protected destination.
  2. Establish the supported PCEP PCC-PCE relationship and authorize the intended path control.
  3. Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational.
  4. Tune reoptimization triggers and hold timers with an acceptable path-quality threshold.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. The most directly supported response is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational. Technical basis: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Evidence of success: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link. Ongoing protection: Validate link-restoration timing for both IGP and LDP after planned interruptions.

Incorrect Answers

A:

TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. That principle governs the alternative intervention. The issue described here is different: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. The case-matched corrective action is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational.

B:

PCE computes paths while PCCs maintain local network forwarding and policy state. That principle governs the alternative intervention. The issue described here is different: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. The case-matched corrective action is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational.

D:

The proposed option addresses this separate mechanism: Aggressive TE reoptimization can cause needless path churn even with valid alternate routes. The stated problem instead depends on: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. The required response is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational.

Question 322

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. Which observable result most directly verifies that this network issue was resolved?

  1. IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.
  2. The engineered tunnel avoids excluded links and meets the required path constraints.
  3. The ingress pushes valid segment labels and transit nodes forward to the intended PE.
  4. Failure injection of the shared conduit no longer disables both primary and backup paths.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. The most directly supported response is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational. Technical basis: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Evidence of success: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link. Ongoing protection: Validate link-restoration timing for both IGP and LDP after planned interruptions.

Incorrect Answers

B:

Traffic engineering selects paths based on constraints beyond default shortest-path cost. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. A passing check should show: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.

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: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. A passing check should show: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.

D:

Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. A passing check should show: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link.

Question 323

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. Which underlying network infrastructure principle best explains the situation?

  1. RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route.
  2. Bandwidth reservation and queue treatment require traffic profiles that reflect burst demands.
  3. SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing.
  4. LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. The most directly supported response is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational. Technical basis: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Evidence of success: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link. Ongoing protection: Validate link-restoration timing for both IGP and LDP after planned interruptions.

Incorrect Answers

A:

RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. That is not the causal relationship tested by the current facts. The relevant principle is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness.

B:

Bandwidth reservation and queue treatment require traffic profiles that reflect burst demands. That is not the causal relationship tested by the current facts. The relevant principle is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness.

C:

SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. That is not the causal relationship tested by the current facts. The relevant principle is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness.

Question 324

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. Which continuing control best reduces recurrence of this problem?

  1. Verify locator reachability and supported endpoint functions at every transit boundary.
  2. Review affinity assignments in link build checklists.
  3. Validate link-restoration timing for both IGP and LDP after planned interruptions.
  4. Revalidate SR policy end-to-end paths after IGP metric revisions.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An OSPF transit link comes Up before LDP is ready and the shortest path immediately sends labeled VPN traffic into a missing transport LSP. The most directly supported response is: Apply supported IGP-LDP synchronization so the path is not preferred until label exchange is operational. Technical basis: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Evidence of success: IGP cost returns to normal after LDP forms and initial VPN packets avoid the unlabeled link. Ongoing protection: Validate link-restoration timing for both IGP and LDP after planned interruptions.

Incorrect Answers

A:

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-IGP synchronization coordinates packet-routing preference with label distribution readiness. Review this instead: Validate link-restoration timing for both IGP and LDP after planned interruptions.

B:

TE affinity constraints select links according to defined administrative groups. Maintaining that control would not track the failure described here. The relevant risk is: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. Review this instead: Validate link-restoration timing for both IGP and LDP after planned interruptions.

D:

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: LDP-IGP synchronization coordinates packet-routing preference with label distribution readiness. The focused prevention check is: Validate link-restoration timing for both IGP and LDP after planned interruptions.

Question 325

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Encode intended resource affinities consistently and apply the correct inclusion/exclusion constraints.
  2. Compute a supported topology-independent loop-free alternate repair path for the protected destination.
  3. Use platform-supported SRv6 locator and endpoint behavior with the required encapsulation mode.
  4. Enable supported LDP session protection with a reachable targeted hello relationship.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. The most directly supported response is: Enable supported LDP session protection with a reachable targeted hello relationship. Technical basis: LDP session protection can retain a session across certain directly connected link disruptions. Evidence of success: LDP session state survives eligible short link outages under the designed protection interval. Ongoing protection: Test protection timers and alternate IP reachability during outages.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: TE affinity constraints select links according to defined administrative groups. The stated problem instead depends on: LDP session protection can retain a session across certain directly connected link disruptions. The required response is: Enable supported LDP session protection with a reachable targeted hello relationship.

B:

The proposed option addresses this separate mechanism: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The stated problem instead depends on: LDP session protection can retain a session across certain directly connected link disruptions. The required response is: Enable supported LDP session protection with a reachable targeted hello relationship.

C:

The option fits a control for: SRv6 SIDs combine routable locators with endpoint behavior encoded in IPv6 addressing. The present failure is caused by a different mechanism: LDP session protection can retain a session across certain directly connected link disruptions. The targeted implementation is: Enable supported LDP session protection with a reachable targeted hello relationship.

Question 326

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. Which observable result most directly verifies that this network issue was resolved?

  1. Failure testing shows packets avoid microloops and recover through the planned repair within target.
  2. All selected path nodes accept signaling and the requested reservation appears.
  3. LDP session state survives eligible short link outages under the designed protection interval.
  4. The headend installs the intended segment list and the FIB resolves every segment.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. The most directly supported response is: Enable supported LDP session protection with a reachable targeted hello relationship. Technical basis: LDP session protection can retain a session across certain directly connected link disruptions. Evidence of success: LDP session state survives eligible short link outages under the designed protection interval. Ongoing protection: Test protection timers and alternate IP reachability during outages.

Incorrect Answers

A:

TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: LDP session protection can retain a session across certain directly connected link disruptions. A passing check should show: LDP session state survives eligible short link outages under the designed protection interval.

B:

The proposed test would be relevant to: RSVP-TE tunnel setup requires compatible signaling and resource support along the chosen route. The reported problem follows from: LDP session protection can retain a session across certain directly connected link disruptions. Instead, verify: LDP session state survives eligible short link outages under the designed protection interval.

D:

The proposed test would be relevant to: An SRTE policy is usable only when its segment instructions resolve through supported topology. The reported problem follows from: LDP session protection can retain a session across certain directly connected link disruptions. Instead, verify: LDP session state survives eligible short link outages under the designed protection interval.

Question 327

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. Which underlying network infrastructure principle best explains the situation?

  1. Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity.
  2. LDP session protection can retain a session across certain directly connected link disruptions.
  3. TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks.
  4. IGP traffic engineering extensions advertise resource attributes distinct from normal SPF reachability.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. The most directly supported response is: Enable supported LDP session protection with a reachable targeted hello relationship. Technical basis: LDP session protection can retain a session across certain directly connected link disruptions. Evidence of success: LDP session state survives eligible short link outages under the designed protection interval. Ongoing protection: Test protection timers and alternate IP reachability during outages.

Incorrect Answers

A:

The option explains a separate issue: Traffic engineering protection must consider physical shared-risk groups, not only logical hop diversity. The reported condition instead follows from: LDP session protection can retain a session across certain directly connected link disruptions.

C:

The option explains a separate issue: TI-LFA computes post-convergence-oriented local repair paths for segment-routing networks. The reported condition instead follows from: LDP session protection can retain a session across certain directly connected link disruptions.

D:

The option explains a separate issue: IGP traffic engineering extensions advertise resource attributes distinct from normal SPF reachability. The reported condition instead follows from: LDP session protection can retain a session across certain directly connected link disruptions.

Question 328

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. Which continuing control best reduces recurrence of this problem?

  1. Audit steering behavior after metric or topology changes.
  2. Inventory tunnel consumers and apply change sequencing controls.
  3. Test bidirectional VPN connectivity and tenant separation during mixed-domain migration.
  4. Test protection timers and alternate IP reachability during outages.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: A backbone's targeted LDP session resets whenever a transport adjacency briefly flaps, increasing service restoration time. The most directly supported response is: Enable supported LDP session protection with a reachable targeted hello relationship. Technical basis: LDP session protection can retain a session across certain directly connected link disruptions. Evidence of success: LDP session state survives eligible short link outages under the designed protection interval. Ongoing protection: Test protection timers and alternate IP reachability during outages.

Incorrect Answers

A:

The alternative guards against: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. The root condition for this case is: LDP session protection can retain a session across certain directly connected link disruptions. The focused prevention check is: Test protection timers and alternate IP reachability during outages.

B:

The alternative guards against: TE tunnel control-plane teardown and service-level forwarding dependencies must be coordinated. The root condition for this case is: LDP session protection can retain a session across certain directly connected link disruptions. The focused prevention check is: Test protection timers and alternate IP reachability during outages.

C:

The alternative guards against: SR-MPLS labels and SRv6 SID functions are different forwarding representations requiring explicit interworking. The root condition for this case is: LDP session protection can retain a session across certain directly connected link disruptions. The focused prevention check is: Test protection timers and alternate IP reachability during outages.

Question 329

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Use an appropriate adjacency SID or constrained SR policy segment list for explicit link steering.
  2. Supply supported TE delay or performance attributes to the topology and ensure they reach path computation.
  3. Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform.
  4. Check reservable bandwidth and adjust the engineered request or network capacity.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. The most directly supported response is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform. Technical basis: LDP bindings associate FECs with labels and can be constrained by control-plane policy. Evidence of success: The label database contains intended FEC mappings and unauthorized allocations stop appearing. Ongoing protection: Review label allocation filters and resource utilization as the routing table grows.

Incorrect Answers

A:

The option fits a control for: An SR node SID typically follows IGP shortest paths, while adjacency SIDs can encode a specific link. The present failure is caused by a different mechanism: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The targeted implementation is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform.

B:

The option fits a control for: Path computation depends on the attributes advertised or otherwise provided to its topology database. The present failure is caused by a different mechanism: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The targeted implementation is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform.

D:

RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable. That principle governs the alternative intervention. The issue described here is different: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The case-matched corrective action is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform.

Question 330

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. Which observable result most directly verifies that this network issue was resolved?

  1. The label database contains intended FEC mappings and unauthorized allocations stop appearing.
  2. Traffic continues over the approved fallback after the tunnel is removed.
  3. The ingress pushes valid segment labels and transit nodes forward to the intended PE.
  4. The tunnel enters the signaled state only after resources satisfy reservation constraints.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. The most directly supported response is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform. Technical basis: LDP bindings associate FECs with labels and can be constrained by control-plane policy. Evidence of success: The label database contains intended FEC mappings and unauthorized allocations stop appearing. Ongoing protection: Review label allocation filters and resource utilization as the routing table grows.

Incorrect Answers

B:

That observation tests a different mechanism: TE tunnel control-plane teardown and service-level forwarding dependencies must be coordinated. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.

C:

That observation tests a different mechanism: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.

D:

That observation tests a different mechanism: RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.