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 75

Question 740

A core network change board wants to avoid: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. Which ongoing safeguard fits best?

  1. Inspect per-VRF service-label mapping after platform or route-policy changes.
  2. Require overlapping-address negative tests before new VPN attachments.
  3. Test DR state when changing multicast LAN interfaces.
  4. Retest primary and backup preference whenever CE prefixes change.

Explanation

Correct Answer

D:

Retest primary and backup preference whenever CE prefixes change. This helps prevent recurrence of the issue: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. Acceptance evidence should be: Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.

Incorrect Answers

A:

Inspect per-VRF service-label mapping after platform or route-policy changes. That is a sensible control for ANOTHER scenario: An L3VPN PE advertises a VPNv4 route but the egress fails to associate the received VPN label with the correct customer VRF, causing the route to appear in the wrong context. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.

B:

Require overlapping-address negative tests before new VPN attachments. That is a sensible control for ANOTHER scenario: Two customers use the same 10.10.0.0/16 prefix but a PE leaks VPNv4 routes into its global table, incorrectly merging their routing contexts. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.

C:

Test DR state when changing multicast LAN interfaces. That is a sensible control for ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It is less targeted to this issue than: Retest primary and backup preference whenever CE prefixes change.

Question 741

A carrier service activation check discovers: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. Which action best restores the intended behavior?

  1. Review policy order and community membership before changing network reachability or resetting all sessions.
  2. Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.
  3. Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions.
  4. Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment.

Explanation

Correct Answer

B:

Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required. This directly addresses the fictional service-provider network case: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. The technical mechanism is: BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer. Verify success by: A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.

Incorrect Answers

A:

Review policy order and community membership before changing network reachability or resetting all sessions. This would respond to a DIFFERENT fictional service-provider network issue: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. It does not directly address the current situation: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates.

C:

Separate inbound inter-AS path influence via prepending from locally controlled outbound local-preference decisions. This would respond to a DIFFERENT fictional service-provider network issue: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. It does not directly address the current situation: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates.

D:

Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. It does not directly address the current situation: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates.

Question 742

Following a supported configuration correction, the original issue was: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. Which observation verifies success?

  1. Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.
  2. The prefix becomes usable with a resolved next hop while the IGP remains stable.
  3. A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.
  4. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.

Explanation

Correct Answer

C:

A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes. This confirms the approved response: Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required. It is relevant because: BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.

Incorrect Answers

A:

Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit. This would validate ANOTHER scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. The specific correction here is: Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.

B:

The prefix becomes usable with a resolved next hop while the IGP remains stable. This would validate ANOTHER scenario: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The specific correction here is: Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.

D:

A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity. This would validate ANOTHER scenario: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. The specific correction here is: Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.

Question 743

At a metro Ethernet service provider, an engineer examines: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. Which technical principle is most applicable?

  1. BGP session establishment is distinct from activation of a specific MP-BGP address family.
  2. MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.
  3. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.
  4. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.

Explanation

Correct Answer

D:

BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer. This explains the investigated issue: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. The approved corrective response is: Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.

Incorrect Answers

A:

BGP session establishment is distinct from activation of a specific MP-BGP address family. That explains a DIFFERENT scenario: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. The mechanism to prioritize for this question is: BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.

B:

MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices. That explains a DIFFERENT scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. The mechanism to prioritize for this question is: BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.

C:

Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately. That explains a DIFFERENT scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. The mechanism to prioritize for this question is: BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.

Question 744

For a metro Ethernet service provider, the change record describes: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. What preventive validation should be standard?

  1. Track Add-Path capabilities and route scale in peering acceptance tests.
  2. Measure PIC behavior for each platform and address family before claiming fast failover.
  3. Use a peer inventory to preflight local and remote AS values.
  4. Test protocol instance, VRF and AF together in route acceptance.

Explanation

Correct Answer

A:

Track Add-Path capabilities and route scale in peering acceptance tests. This helps prevent recurrence of the issue: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. Acceptance evidence should be: A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.

Incorrect Answers

B:

Measure PIC behavior for each platform and address family before claiming fast failover. That is a sensible control for ANOTHER scenario: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. It is less targeted to this issue than: Track Add-Path capabilities and route scale in peering acceptance tests.

C:

Use a peer inventory to preflight local and remote AS values. That is a sensible control for ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It is less targeted to this issue than: Track Add-Path capabilities and route scale in peering acceptance tests.

D:

Test protocol instance, VRF and AF together in route acceptance. That is a sensible control for ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It is less targeted to this issue than: Track Add-Path capabilities and route scale in peering acceptance tests.

Question 745

For a global tier-one IP transit carrier, the failure is: 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. Which authorized correction best addresses it?

  1. Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum.
  2. Run both transport MPLS OAM and the service-specific VPN route/forwarding verification appropriate to the affected VRF.
  3. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.
  4. Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly.

Explanation

Correct Answer

C:

Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. This directly addresses the fictional service-provider network case: 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 technical mechanism is: MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries. Verify success by: The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution.

Incorrect Answers

A:

Recalculate supported label depth and adjust service transport or platform selection to the hardware maximum. This would respond to a DIFFERENT fictional service-provider network issue: A core node imposes two service labels on an access interface with a hardware label-stack depth limit below the engineered VPN service, causing selective drops. It does not directly address the current situation: 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.

B:

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

D:

Align Prefix-SID index planning and understand per-node SRGB label calculation so the intended segment resolves correctly. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

Question 746

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

  1. A service prefix traverses the core layers with valid outer transport labels and correct VPN label disposition at the egress PE.
  2. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.
  3. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  4. The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution.

Explanation

Correct Answer

D:

The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution. This confirms the approved response: Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. It is relevant because: MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.

Incorrect Answers

A:

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: Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.

B:

The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This would validate ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The specific correction here is: Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.

C:

Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed. This would validate ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The specific correction here is: Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.

Question 747

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

  1. MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.
  2. MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label.
  3. MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations.
  4. Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand.

Explanation

Correct Answer

A:

MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries. This explains the investigated issue: 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 approved corrective response is: Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.

Incorrect Answers

B:

MPLS stacks separate outer transport forwarding from inner VPN service identification, and PHP must not erase the service label. That explains a DIFFERENT scenario: A transit router keeps unexpectedly popping a provider's VPN label one hop before the target PE, sending customer traffic toward the global routing table. The mechanism to prioritize for this question is: MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.

C:

MPLS transport routers do not normally maintain customer VRFs or service labels for all VPN destinations. That explains a DIFFERENT scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. The mechanism to prioritize for this question is: MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.

D:

Reserved bandwidth accounting can differ from measured interface utilization and can persist beyond active demand. That explains a DIFFERENT scenario: One router reports TE bandwidth exhausted even though link counters show the circuit nearly idle, and operators increase interface speed without investigating reservations. The mechanism to prioritize for this question is: MPLS label forwarding depends on consistency among route reachability, label bindings and hardware forwarding entries.

Question 748

After addressing: 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. Which recurring service assurance check is most useful?

  1. Test route and label binding presence separately for every new backbone link.
  2. Alert on mismatched IGP FEC and LFIB installation counters.
  3. Review FEC label policy and routing context boundaries at PE-P handoffs.
  4. Inspect protection flags and test actual repair behavior instead of assuming FRR is armed.

Explanation

Correct Answer

B:

Alert on mismatched IGP FEC and LFIB installation counters. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: The stale FEC is no longer selected and legitimate rerouted VPN prefixes resume with correct label resolution.

Incorrect Answers

A:

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: Alert on mismatched IGP FEC and LFIB installation counters.

C:

Review FEC label policy and routing context boundaries at PE-P handoffs. That is a sensible control for ANOTHER scenario: A P router allocates labels for customer routes that should only exist at the VRF-aware PE, and the core sees unexpected VPN forwarding context. It is less targeted to this issue than: Alert on mismatched IGP FEC and LFIB installation counters.

D:

Inspect protection flags and test actual repair behavior instead of assuming FRR is armed. That is a sensible control for ANOTHER scenario: A primary RSVP-TE tunnel fails and no local FRR detour is active, forcing slow headend reconvergence during a protected fiber cut. It is less targeted to this issue than: Alert on mismatched IGP FEC and LFIB installation counters.

Question 749

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

  1. Introduce a controlled reoptimization interval and hysteresis for path changes under established TE objectives.
  2. Include available shared-risk link group constraints or explicit path diversity in TE computation.
  3. Implement the supported SRv6-to-MPLS service interworking behavior or keep the service within compatible transport domains.
  4. Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

Explanation

Correct Answer

D:

Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Local protection for a link and local protection for a full node require different bypass topology constraints. Verify success by: The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.

Incorrect Answers

A:

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

B:

Include available shared-risk link group constraints or explicit path diversity in TE computation. This would respond to a DIFFERENT fictional service-provider network issue: A traffic engineering policy considers only link bandwidth when selecting primary and backup paths, but both use one optical shared-risk group. It does not directly address the current situation: 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.

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

Question 750

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

  1. The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass.
  2. Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed.
  3. The replacement LSP becomes usable before the previous one is torn down in an acceptance test.
  4. During a single-link failure the session remains protected through the alternative route and bound FECs recover safely.

Explanation

Correct Answer

A:

The tunnel's protection state indicates the intended scope and a targeted failure test uses the proper bypass. This confirms the approved response: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link. It is relevant because: Local protection for a link and local protection for a full node require different bypass topology constraints.

Incorrect Answers

B:

Traffic remains on an eligible path through small utilization variations and moves only after a meaningful sustained threshold is crossed. This would validate ANOTHER scenario: A tunnel between regional PEs oscillates because an optimizer recomputes explicit paths on every small telemetry fluctuation. The specific correction here is: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

C:

The replacement LSP becomes usable before the previous one is torn down in an acceptance test. This would validate ANOTHER scenario: 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 specific correction here is: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.

D:

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: Align the requested bypass protection type with available disjoint repair paths and verify coverage for the protected node or link.