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 32

Question 310

Following a supported configuration correction, the original issue was: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. Which observation verifies success?

  1. Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.
  2. Test prefixes show the tagged route rejected and only approved routes advertised.
  3. The upstream sandbox peer receives the intended community and applies only the agreed action.
  4. IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable.

Explanation

Correct Answer

C:

The upstream sandbox peer receives the intended community and applies only the agreed action. This confirms the approved response: Preserve and transmit the negotiated community using the supported neighbor settings and route policy. It is relevant because: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

Incorrect Answers

A:

Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix. This would validate 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. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

B:

Test prefixes show the tagged route rejected and only approved routes advertised. This would validate ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

D:

IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable. This would validate ANOTHER scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

Question 311

At a regional peering-exchange operator, an engineer examines: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. Which technical principle is most applicable?

  1. Routing Policy Language statements have defined evaluation semantics and must not be treated as arbitrary ordered ACL entries.
  2. Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.
  3. BGP session establishment is distinct from activation of a specific MP-BGP address family.
  4. BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

Explanation

Correct Answer

D:

BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. This explains the investigated issue: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. The approved corrective response is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

Incorrect Answers

A:

Routing Policy Language statements have defined evaluation semantics and must not be treated as arbitrary ordered ACL entries. That explains a DIFFERENT scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. The mechanism to prioritize for this question is: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

B:

Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability. That explains a DIFFERENT scenario: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. The mechanism to prioritize for this question is: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

C:

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 communities are optional policy metadata and must be explicitly propagated when the design depends on them.

Question 312

For a regional peering-exchange operator, the change record describes: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. What preventive validation should be standard?

  1. Verify community presence in route advertisements at the external boundary.
  2. Require boundary-prefix tests whenever prefix sets are edited.
  3. Maintain positive and negative RPL policy unit tests for each provider peer.
  4. Baseline BFD jitter and loss before setting aggressive detection timers.

Explanation

Correct Answer

A:

Verify community presence in route advertisements at the external boundary. This helps prevent recurrence of the issue: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. Acceptance evidence should be: The upstream sandbox peer receives the intended community and applies only the agreed action.

Incorrect Answers

B:

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: Verify community presence in route advertisements at the external boundary.

C:

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: Verify community presence in route advertisements at the external boundary.

D:

Baseline BFD jitter and loss before setting aggressive detection timers. That is a sensible control for ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It is less targeted to this issue than: Verify community presence in route advertisements at the external boundary.

Question 313

For an optical transport engineering team, the failure is: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. Which authorized correction best addresses it?

  1. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.
  2. Permit the required OSPF control traffic between approved peers at the correct interface policy boundary.
  3. Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.
  4. Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

Explanation

Correct Answer

C:

Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks. This directly addresses the fictional service-provider network case: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The technical mechanism is: Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low. Verify success by: A limited allowed route set is advertised and the threshold alerts only on unexpected growth.

Incorrect Answers

A:

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 eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold.

B:

Permit the required OSPF control traffic between approved peers at the correct interface policy boundary. This would respond to a DIFFERENT fictional service-provider network issue: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. It does not directly address the current situation: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold.

D:

Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold.

Question 314

After fixing the following network problem, what should the team verify: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold.

  1. Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges.
  2. In a test switchover, BFD stabilizes and the IGP reconverges within the agreed target.
  3. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.
  4. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.

Explanation

Correct Answer

D:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This confirms the approved response: Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks. It is relevant because: Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.

Incorrect Answers

A:

Adjacency and LSP integrity counters remain stable during repeated authenticated hello exchanges. This would validate ANOTHER scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The specific correction here is: Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.

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: Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.

C:

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: Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.

Question 315

A carrier root-cause review considers: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. What underlying mechanism explains this?

  1. Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.
  2. Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.
  3. Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization.
  4. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

Explanation

Correct Answer

A:

Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low. This explains the investigated issue: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The approved corrective response is: Reconcile intended route count and maximum-prefix behavior with the peer contract after checking for accidental route leaks.

Incorrect Answers

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: Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.

C:

Routing protocol authentication mismatches disrupt control-plane neighbor and database synchronization. That explains a DIFFERENT scenario: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. The mechanism to prioritize for this question is: Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.

D:

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: Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.

Question 316

After addressing: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. Which recurring service assurance check is most useful?

  1. Tune BFD to observed transport behavior and test at peak utilization.
  2. Trend prefix counts and alert before capacity thresholds are reached.
  3. Track next-hop reachability and route installation separately in alarms.
  4. Maintain release-specific ISSU qualification and rollback documentation.

Explanation

Correct Answer

B:

Trend prefix counts and alert before capacity thresholds are reached. This helps prevent recurrence of the issue: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. Acceptance evidence should be: A limited allowed route set is advertised and the threshold alerts only on unexpected growth.

Incorrect Answers

A:

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: Trend prefix counts and alert before capacity thresholds are reached.

C:

Track next-hop reachability and route installation separately in alarms. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Trend prefix counts and alert before capacity thresholds are reached.

D:

Maintain release-specific ISSU qualification and rollback documentation. That is a sensible control for ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. It is less targeted to this issue than: Trend prefix counts and alert before capacity thresholds are reached.

Question 317

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

  1. Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.
  2. Provide supported DNS64 synthesis or an equivalent discovery mechanism consistent with NAT64 deployment.
  3. Align effective MTU or approved interface configuration, then verify database exchange.
  4. Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

Explanation

Correct Answer

D:

Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation. Verify success by: A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address.

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 customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned.

B:

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

C:

Align effective MTU or approved interface configuration, then verify database exchange. This would respond to a DIFFERENT fictional service-provider network issue: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. It does not directly address the current situation: 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.

Question 318

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

  1. A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address.
  2. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.
  3. An IPv6-only test client resolves and reaches the target IPv4-only service through the transition gateway.
  4. Stability testing shows legitimate fault detection within budget without false down events under busy periods.

Explanation

Correct Answer

A:

A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address. This confirms the approved response: Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model. It is relevant because: Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

Incorrect Answers

B:

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: Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

C:

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: Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

D:

Stability testing shows legitimate fault detection within budget without false down events under busy periods. This would validate ANOTHER scenario: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. The specific correction here is: Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

Question 319

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.
  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. BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.

Explanation

Correct Answer

B:

Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation. This explains the investigated issue: 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 approved corrective response is: Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.

Incorrect Answers

A:

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: Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

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: Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

D:

BGP best-path selection includes deterministic final tie-breakers when major attributes are equal. That explains a DIFFERENT scenario: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. The mechanism to prioritize for this question is: Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

Question 320

To prevent recurrence of this provider network issue: 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. Which control should be retained?

  1. Test deterministic mapping and log lookup as part of CGNAT capacity exercises.
  2. Audit port-block assignments and exhausted mapping pools.
  3. Validate B4 reachability and AFTR capacity at subscriber activation.
  4. Test component-prefix ownership before exporting aggregates.

Explanation

Correct Answer

C:

Validate B4 reachability and AFTR capacity at subscriber activation. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A test IPv4 session traverses the IPv6 access and exits through the correct AFTR public address.

Incorrect Answers

A:

Test deterministic mapping and log lookup as part of CGNAT capacity exercises. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.

B:

Audit port-block assignments and exhausted mapping pools. That is a sensible control for 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. It is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.

D:

Test component-prefix ownership before exporting aggregates. That is a sensible control for ANOTHER scenario: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. It is less targeted to this issue than: Validate B4 reachability and AFTR capacity at subscriber activation.