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 19

Question 180

A core network change board wants to avoid: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. Which ongoing safeguard fits best?

  1. Require boundary-prefix tests whenever prefix sets are edited.
  2. Maintain positive and negative RPL policy unit tests for each provider peer.
  3. Rotate peer keys through a coordinated overlap and verification plan.
  4. Include tagged and untagged candidate routes in route-map test suites.

Explanation

Correct Answer

D:

Include tagged and untagged candidate routes in route-map test suites. This helps prevent recurrence of the issue: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. Acceptance evidence should be: Test prefixes show the tagged route rejected and only approved routes advertised.

Incorrect Answers

A:

Require boundary-prefix tests whenever prefix sets are edited. That is a sensible control for ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.

B:

Maintain positive and negative RPL policy unit tests for each provider peer. That is a sensible control for ANOTHER scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.

C:

Rotate peer keys through a coordinated overlap and verification plan. That is a sensible control for ANOTHER scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. It is less targeted to this issue than: Include tagged and untagged candidate routes in route-map test suites.

Question 181

A carrier service activation check discovers: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. Which action best restores the intended behavior?

  1. Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.
  2. Align approved IS-IS authentication parameters and keys on all intended peer interfaces.
  3. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.
  4. Activate the IPv6 unicast address family and required export policies on both intended peers.

Explanation

Correct Answer

B:

Align approved IS-IS authentication parameters and keys on all intended peer interfaces. This directly addresses the fictional service-provider network case: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The technical mechanism is: Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization. Verify success by: Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges.

Incorrect Answers

A:

Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks. This would respond to a DIFFERENT fictional service-provider network issue: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It does not directly address the current situation: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs.

C:

Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. This would respond to a DIFFERENT fictional service-provider network issue: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. It does not directly address the current situation: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs.

D:

Activate the IPv6 unicast address family and required export policies on both intended peers. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs.

Question 182

Following a supported configuration correction, the original issue was: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. Which observation verifies success?

  1. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.
  2. In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.
  3. Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges.
  4. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Explanation

Correct Answer

C:

Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges. This confirms the approved response: Align approved IS-IS authentication parameters and keys on all intended peer interfaces. It is relevant because: Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.

Incorrect Answers

A:

The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged. This would validate ANOTHER scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The specific correction here is: Align approved IS-IS authentication parameters and keys on all intended peer interfaces.

B:

In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target. This would validate ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The specific correction here is: Align approved IS-IS authentication parameters and keys on all intended peer interfaces.

D:

Customer route queries show approved aggregate service routes but no internal infrastructure prefixes. This would validate ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The specific correction here is: Align approved IS-IS authentication parameters and keys on all intended peer interfaces.

Question 183

At a metro Ethernet service provider, an engineer examines: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. Which technical principle is most applicable?

  1. A physical adjacency can exist without all configured address families exchanging usable reachability.
  2. BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.
  3. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.
  4. Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.

Explanation

Correct Answer

D:

Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization. This explains the investigated issue: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The approved corrective response is: Align approved IS-IS authentication parameters and keys on all intended peer interfaces.

Incorrect Answers

A:

A physical adjacency can exist without all configured address families exchanging usable reachability. That explains a DIFFERENT scenario: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The mechanism to prioritize for this question is: Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.

B:

BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures. That explains a DIFFERENT scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. The mechanism to prioritize for this question is: Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.

C:

BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.

Question 184

For a metro Ethernet service provider, the change record describes: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. What preventive validation should be standard?

  1. Rotate peer keys through a coordinated overlap and verification plan.
  2. Keep route-source and protocol-dependency maps for service circuits.
  3. Tune BFD to observed transport behavior and test at peak utilization.
  4. Validate B4 reachability and AFTR capacity at subscriber activation.

Explanation

Correct Answer

A:

Rotate peer keys through a coordinated overlap and verification plan. This helps prevent recurrence of the issue: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. Acceptance evidence should be: Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges.

Incorrect Answers

B:

Keep route-source and protocol-dependency maps for service circuits. That is a sensible control for ANOTHER scenario: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. It is less targeted to this issue than: Rotate peer keys through a coordinated overlap and verification plan.

C:

Tune BFD to observed transport behavior and test at peak utilization. That is a sensible control for ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It is less targeted to this issue than: Rotate peer keys through a coordinated overlap and verification plan.

D:

Validate B4 reachability and AFTR capacity at subscriber activation. That is a sensible control for ANOTHER scenario: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. It is less targeted to this issue than: Rotate peer keys through a coordinated overlap and verification plan.

Question 185

For a global tier-one IP transit carrier, the failure is: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. Which authorized correction best addresses it?

  1. Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.
  2. Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.
  3. Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.
  4. Align stub-area configuration on the ABR and member routers and verify default advertisement.

Explanation

Correct Answer

C:

Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules. This directly addresses the fictional service-provider network case: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. The technical mechanism is: Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution. Verify success by: A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.

Incorrect Answers

A:

Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections.

B:

Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration. This would respond to a DIFFERENT fictional service-provider network issue: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. It does not directly address the current situation: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections.

D:

Align stub-area configuration on the ABR and member routers and verify default advertisement. This would respond to a DIFFERENT fictional service-provider network issue: An OSPF stub area loses its expected default route when an engineer configures stub mode on the access router but not consistently on the area border router. It does not directly address the current situation: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections.

Question 186

After fixing the following network problem, what should the team verify: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections.

  1. A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address.
  2. A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.
  3. Adjacent peer route views show additional paths only when both sides support and negotiate the feature.
  4. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.

Explanation

Correct Answer

D:

A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients. This confirms the approved response: Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules. It is relevant because: Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.

Incorrect Answers

A:

A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address. This would validate ANOTHER scenario: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. The specific correction here is: Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.

B:

A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload. This would validate ANOTHER scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The specific correction here is: Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.

C:

Adjacent peer route views show additional paths only when both sides support and negotiate the feature. This would validate ANOTHER scenario: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. The specific correction here is: Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.

Question 187

A carrier root-cause review considers: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. What underlying mechanism explains this?

  1. Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.
  2. Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.
  3. MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.
  4. Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

Explanation

Correct Answer

A:

Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution. This explains the investigated issue: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. The approved corrective response is: Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.

Incorrect Answers

B:

Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation. That explains a DIFFERENT scenario: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. The mechanism to prioritize for this question is: Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.

C:

MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation. That explains a DIFFERENT scenario: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The mechanism to prioritize for this question is: Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.

D:

Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol. That explains a DIFFERENT scenario: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. The mechanism to prioritize for this question is: Carrier-grade NAT shares a public address across subscribers and often requires port and time context for attribution.

Question 188

After addressing: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. Which recurring service assurance check is most useful?

  1. Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance.
  2. Test deterministic mapping and log lookup as part of CGNAT capacity exercises.
  3. Validate dual-family translation behavior before onboarding IPv6-only customers.
  4. Include reference bandwidth standards in routing config review.

Explanation

Correct Answer

B:

Test deterministic mapping and log lookup as part of CGNAT capacity exercises. This helps prevent recurrence of the issue: A CGNAT operator has millions of sessions but translation logs record only subscriber private addresses, making legal attribution impossible for shared public IPv4 connections. Acceptance evidence should be: A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.

Incorrect Answers

A:

Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance. That is a sensible control for 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. It is less targeted to this issue than: Test deterministic mapping and log lookup as part of CGNAT capacity exercises.

C:

Validate dual-family translation behavior before onboarding IPv6-only customers. That is a sensible control for ANOTHER scenario: An IPv6-only enterprise application must reach an IPv4-only legacy service, but the provider installs NAT44 and expects it to translate the address families. It is less targeted to this issue than: Test deterministic mapping and log lookup as part of CGNAT capacity exercises.

D:

Include reference bandwidth standards in routing config review. That is a sensible control for ANOTHER scenario: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. It is less targeted to this issue than: Test deterministic mapping and log lookup as part of CGNAT capacity exercises.

Question 189

A provider backbone escalation identifies: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. What should the network team implement?

  1. Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.
  2. Trace shared-risk link groups and relocate one service path to independent optical facilities where required.
  3. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.
  4. Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

Explanation

Correct Answer

D:

Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. This directly addresses the fictional service-provider network case: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The technical mechanism is: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior. Verify success by: A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.

Incorrect Answers

A:

Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology. This would respond to a DIFFERENT fictional service-provider network issue: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. It does not directly address the current situation: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover.

B:

Trace shared-risk link groups and relocate one service path to independent optical facilities where required. This would respond to a DIFFERENT fictional service-provider network issue: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. It does not directly address the current situation: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover.

C:

Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. This would respond to a DIFFERENT fictional service-provider network issue: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. It does not directly address the current situation: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover.

Question 190

A service-provider operations test targets: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. Which result is required?

  1. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.
  2. Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.
  3. Both links join one stable operational bundle and sampled customer flows traverse valid active members.
  4. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Explanation

Correct Answer

A:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This confirms the approved response: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. It is relevant because: NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.

Incorrect Answers

B:

Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic. This would validate ANOTHER scenario: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. The specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

C:

Both links join one stable operational bundle and sampled customer flows traverse valid active members. This would validate ANOTHER scenario: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. The specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.

D:

Parallel test sessions resolve to unique external tuples and return to the correct subscriber. This would validate ANOTHER 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 specific correction here is: Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.