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 59

Question 580

A core network change board wants to avoid: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Which ongoing safeguard fits best?

  1. Archive policy diffs and route-acceptance fixtures with change approvals.
  2. Maintain positive and negative RPL policy unit tests for each provider peer.
  3. Teach neighbor-state expectations per OSPF network type in runbooks.
  4. Enforce explicit domain boundaries in route-target and global export policy checks.

Explanation

Correct Answer

D:

Enforce explicit domain boundaries in route-target and global export policy checks. This helps prevent recurrence of the issue: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. Acceptance evidence should be: A transit peer receives only global internet prefixes while VPN routes remain in authorized VRFs.

Incorrect Answers

A:

Archive policy diffs and route-acceptance fixtures with change approvals. That is a sensible control for ANOTHER scenario: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.

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: Enforce explicit domain boundaries in route-target and global export policy checks.

C:

Teach neighbor-state expectations per OSPF network type in runbooks. That is a sensible control for ANOTHER scenario: A multiaccess OSPF network forms neighbor relationships but routes stay stuck at 2-Way between two DROTHER peers, and the operator repeatedly resets them. It is less targeted to this issue than: Enforce explicit domain boundaries in route-target and global export policy checks.

Question 581

A carrier service activation check discovers: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. 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. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.
  3. Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.
  4. Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.

Explanation

Correct Answer

B:

Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. This directly addresses the fictional service-provider network case: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. The technical mechanism is: BGP path usability depends on resolution through the underlying routing table. Verify success by: BGP route state transitions to valid forwarding with the expected next-hop recursion resolved.

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: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI.

C:

Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment. This would respond to a DIFFERENT fictional service-provider network issue: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. It does not directly address the current situation: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI.

D:

Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It does not directly address the current situation: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI.

Question 582

Following a supported configuration correction, the original issue was: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. Which observation verifies success?

  1. A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources.
  2. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.
  3. BGP route state transitions to valid forwarding with the expected next-hop recursion resolved.
  4. Disconnecting the access link leaves a genuinely diverse next hop forwarding test traffic.

Explanation

Correct Answer

C:

BGP route state transitions to valid forwarding with the expected next-hop recursion resolved. This confirms the approved response: Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. It is relevant because: BGP path usability depends on resolution through the underlying routing table.

Incorrect Answers

A:

A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources. This would validate ANOTHER scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. The specific correction here is: Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

B:

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: Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

D:

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: Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

Question 583

At a mobile packet-core transport operator, an engineer examines: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. Which technical principle is most applicable?

  1. BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.
  2. Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.
  3. BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.
  4. BGP path usability depends on resolution through the underlying routing table.

Explanation

Correct Answer

D:

BGP path usability depends on resolution through the underlying routing table. This explains the investigated 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. The approved corrective response is: Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

Incorrect Answers

A:

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: BGP path usability depends on resolution through the underlying routing table.

B:

Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds. That explains a DIFFERENT scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. The mechanism to prioritize for this question is: BGP path usability depends on resolution through the underlying routing table.

C:

BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: BGP path usability depends on resolution through the underlying routing table.

Question 584

For a mobile packet-core transport operator, the change record describes: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. What preventive validation should be standard?

  1. Track next-hop reachability and route installation separately in alarms.
  2. Rotate peer keys through a coordinated overlap and verification plan.
  3. Verify IPv4/IPv6 route consistency after partial protocol changes.
  4. Validate B4 reachability and AFTR capacity at subscriber activation.

Explanation

Correct Answer

A:

Track next-hop reachability and route installation separately in alarms. This helps prevent recurrence of the 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. Acceptance evidence should be: BGP route state transitions to valid forwarding with the expected next-hop recursion resolved.

Incorrect Answers

B:

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: Track next-hop reachability and route installation separately in alarms.

C:

Verify IPv4/IPv6 route consistency after partial protocol changes. That is a sensible control for 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. It is less targeted to this issue than: Track next-hop reachability and route installation separately in alarms.

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: Track next-hop reachability and route installation separately in alarms.

Question 585

For a managed VPN service carrier, the failure is: 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. Which authorized correction best addresses it?

  1. Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.
  2. Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules.
  3. Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.
  4. Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

Explanation

Correct Answer

C:

Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately. Verify success by: Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Incorrect Answers

A:

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

B:

Record approved per-flow or deterministic mapping metadata including external port, public address and synchronized time within retention rules. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

D:

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

Question 586

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

  1. An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway.
  2. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.
  3. A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.
  4. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Explanation

Correct Answer

D:

Parallel test sessions resolve to unique external tuples and return to the correct subscriber. This confirms the approved response: Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking. It is relevant because: Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

Incorrect Answers

A:

An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway. This would validate 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. The specific correction here is: Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.

B:

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: Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.

C:

A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied. This would validate ANOTHER scenario: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. The specific correction here is: Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.

Question 587

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

  1. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.
  2. NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64.
  3. Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.
  4. Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.

Explanation

Correct Answer

A:

Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately. This explains the investigated 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. The approved corrective response is: Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.

Incorrect Answers

B:

NAT64 forwarding requires an IPv6 destination representation of the IPv4 server, frequently supplied by DNS64. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

C:

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: Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

D:

Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled. That explains a DIFFERENT scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The mechanism to prioritize for this question is: Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

Question 588

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

  1. Validate B4 reachability and AFTR capacity at subscriber activation.
  2. Audit port-block assignments and exhausted mapping pools.
  3. Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance.
  4. Tune BFD to observed transport behavior and test at peak utilization.

Explanation

Correct Answer

B:

Audit port-block assignments and exhausted mapping pools. This helps prevent recurrence of the 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. Acceptance evidence should be: Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Incorrect Answers

A:

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: Audit port-block assignments and exhausted mapping pools.

C:

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: Audit port-block assignments and exhausted mapping pools.

D:

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: Audit port-block assignments and exhausted mapping pools.

Question 589

A provider backbone escalation identifies: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. What should the network team implement?

  1. Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.
  2. Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology.
  3. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.
  4. Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

Explanation

Correct Answer

D:

Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan. This directly addresses the fictional service-provider network case: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The technical mechanism is: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario. Verify success by: The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.

Incorrect Answers

A:

Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies. This would respond to a DIFFERENT fictional service-provider network issue: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. It does not directly address the current situation: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites.

B:

Enable and verify supported Nonstop Routing state replication for the intended protocol and redundancy topology. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites.

C:

Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy. This would respond to a DIFFERENT fictional service-provider network issue: A BGP router holds multiple valid paths yet chooses an unanticipated route because one path has a smaller origin code, not because of a mistaken community. It does not directly address the current situation: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites.

Question 590

A service-provider operations test targets: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. Which result is required?

  1. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.
  2. During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget.
  3. A failure drill on one shelf leaves at least one approved end-to-end route available.
  4. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.

Explanation

Correct Answer

A:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This confirms the approved response: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan. It is relevant because: High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

Incorrect Answers

B:

During switchover, eligible traffic continues while routing sessions safely reestablish within the timer budget. This would validate ANOTHER scenario: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The specific correction here is: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

C:

A failure drill on one shelf leaves at least one approved end-to-end route available. This would validate ANOTHER scenario: 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. The specific correction here is: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.

D:

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: Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.