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 45

Question 440

For an ISP route assurance team, the change record describes: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. What preventive validation should be standard?

  1. Record upstream acceptance of traffic-engineering communities and MED policy.
  2. Review candidate redistribution tables under a default-deny policy.
  3. Verify v4 and v6 filter family independently during peering certification.
  4. Validate dual-family translation behavior before onboarding IPv6-only customers.

Explanation

Correct Answer

A:

Record upstream acceptance of traffic-engineering communities and MED policy. This helps prevent recurrence of the issue: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. Acceptance evidence should be: A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS.

Incorrect Answers

B:

Review candidate redistribution tables under a default-deny policy. That is a sensible control for ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It is less targeted to this issue than: Record upstream acceptance of traffic-engineering communities and MED policy.

C:

Verify v4 and v6 filter family independently during peering certification. That is a sensible control for 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. It is less targeted to this issue than: Record upstream acceptance of traffic-engineering communities and MED policy.

D:

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: Record upstream acceptance of traffic-engineering communities and MED policy.

Question 441

For a converged broadband aggregation team, the failure is: 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. Which authorized correction best addresses it?

  1. Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy.
  2. Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics.
  3. Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.
  4. Align both ends to a common supported IS-IS adjacency level with consistent interface settings.

Explanation

Correct Answer

C:

Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes. Verify success by: Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.

Incorrect Answers

A:

Generate a reviewed intended-state diff and test representative prefixes before committing the revised policy. This would respond to a DIFFERENT fictional service-provider network issue: A policy deployer overwrites an existing RPL route policy in production without a prechange candidate diff, causing accidental withdrawal of one customer aggregate. It does not directly address the current situation: 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.

B:

Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics. This would respond to a DIFFERENT fictional service-provider network issue: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It does not directly address the current situation: 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.

D:

Align both ends to a common supported IS-IS adjacency level with consistent interface settings. This would respond to a DIFFERENT fictional service-provider network issue: A point-to-point IS-IS link remains up but an engineer changes circuit type to level-1-only at one side while the peer is level-2-only. It does not directly address the current situation: 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.

Question 442

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

  1. A safe prefix fixture accepts only the specified routes and rejects the unauthorized rest.
  2. A sandbox change shows the aggregate retained and the desired new filter applied before production approval.
  3. Neighbor state advances to Full and the LSDB includes the expected network LSA.
  4. Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.

Explanation

Correct Answer

D:

Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix. This confirms the approved response: Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor. It is relevant because: Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes.

Incorrect Answers

A:

A safe prefix fixture accepts only the specified routes and rejects the unauthorized rest. This would validate ANOTHER scenario: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. The specific correction here is: Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.

B:

A sandbox change shows the aggregate retained and the desired new filter applied before production approval. This would validate 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. The specific correction here is: Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.

C:

Neighbor state advances to Full and the LSDB includes the expected network LSA. This would validate ANOTHER scenario: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. The specific correction here is: Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.

Question 443

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

  1. Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes.
  2. Safe provider routing policy needs deterministic predeployment validation because small clause changes alter large-scale reachability.
  3. Route maps evaluate ordered policy clauses, and broad later matches must be carefully scoped.
  4. OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

Explanation

Correct Answer

A:

Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes. This explains the investigated issue: 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 approved corrective response is: Express the correct prefix-set length condition for the desired more-specific NLRI and bound it to the intended neighbor.

Incorrect Answers

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: Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes.

C:

Route maps evaluate ordered policy clauses, and broad later matches must be carefully scoped. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes.

D:

OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family. That explains a DIFFERENT scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The mechanism to prioritize for this question is: Prefix match logic distinguishes exact network/length pairs from inclusive ranges of more-specific prefixes.

Question 444

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

  1. Include tagged and untagged candidate routes in route-map test suites.
  2. Require boundary-prefix tests whenever prefix sets are edited.
  3. Enforce explicit domain boundaries in route-target and global export policy checks.
  4. Audit port-block assignments and exhausted mapping pools.

Explanation

Correct Answer

B:

Require boundary-prefix tests whenever prefix sets are edited. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.

Incorrect Answers

A:

Include tagged and untagged candidate routes in route-map test suites. That is a sensible control for 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. It is less targeted to this issue than: Require boundary-prefix tests whenever prefix sets are edited.

C:

Enforce explicit domain boundaries in route-target and global export policy checks. That is a sensible control for ANOTHER scenario: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. It is less targeted to this issue than: Require boundary-prefix tests whenever prefix sets are edited.

D:

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: Require boundary-prefix tests whenever prefix sets are edited.

Question 445

A provider backbone escalation identifies: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. What should the network team implement?

  1. Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.
  2. Align approved IS-IS authentication parameters and keys on all intended peer interfaces.
  3. Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family.
  4. Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.

Explanation

Correct Answer

D:

Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability. This directly addresses the fictional service-provider network case: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. The technical mechanism is: Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol. Verify success by: A test prefix is visible across the area boundary before the dependent BGP route recovers.

Incorrect Answers

A:

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: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom.

B:

Align approved IS-IS authentication parameters and keys on all intended peer interfaces. This would respond to a DIFFERENT fictional service-provider network issue: A service-provider IS-IS adjacency drops intermittently when one side uses authentication while the other still sends unauthenticated LSPs. It does not directly address the current situation: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom.

C:

Bind the correct IPv6 address-family policy and prefix filters to the matching BGP neighbor family. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 border router accepts an IPv6 customer route under an IPv4 route-policy address-family clause and quietly blocks legitimate IPv6 service NLRI. It does not directly address the current situation: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom.

Question 446

A service-provider operations test targets: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. Which result is required?

  1. A test prefix is visible across the area boundary before the dependent BGP route recovers.
  2. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.
  3. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.
  4. A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.

Explanation

Correct Answer

A:

A test prefix is visible across the area boundary before the dependent BGP route recovers. This confirms the approved response: Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability. It is relevant because: Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

Incorrect Answers

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: Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.

C:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This would validate ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The specific correction here is: Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.

D:

A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal. This would validate ANOTHER scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. The specific correction here is: Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.

Question 447

A provider troubleshooting note states: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. Which mechanism is central?

  1. BGP path usability depends on resolution through the underlying routing table.
  2. Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.
  3. BFD can accelerate fault detection but incorrectly aggressive timers can create false liveness failures.
  4. High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario.

Explanation

Correct Answer

B:

Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol. This explains the investigated issue: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. The approved corrective response is: Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.

Incorrect Answers

A:

BGP path usability depends on resolution through the underlying routing table. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

C:

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: Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

D:

High availability features depend on specific platform and image compatibility and cannot guarantee hitless upgrades in every scenario. That explains a DIFFERENT scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The mechanism to prioritize for this question is: Protocol troubleshooting should identify the originating control-plane gap rather than reset an unrelated dependent protocol.

Question 448

To prevent recurrence of this provider network issue: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. Which control should be retained?

  1. Verify IPv4/IPv6 route consistency after partial protocol changes.
  2. Include protocol-specific reachability and adjacency checks after ACL changes.
  3. Keep route-source and protocol-dependency maps for service circuits.
  4. Keep best-path attribute snapshots alongside policy change tickets.

Explanation

Correct Answer

C:

Keep route-source and protocol-dependency maps for service circuits. This helps prevent recurrence of the issue: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. Acceptance evidence should be: A test prefix is visible across the area boundary before the dependent BGP route recovers.

Incorrect Answers

A:

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: Keep route-source and protocol-dependency maps for service circuits.

B:

Include protocol-specific reachability and adjacency checks after ACL changes. That is a sensible control for ANOTHER scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. It is less targeted to this issue than: Keep route-source and protocol-dependency maps for service circuits.

D:

Keep best-path attribute snapshots alongside policy change tickets. That is a sensible control for ANOTHER scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. It is less targeted to this issue than: Keep route-source and protocol-dependency maps for service circuits.

Question 449

At a regional service-provider operations center, an engineering review finds: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. Which change most directly corrects the service problem?

  1. Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.
  2. Use nonoverlapping deterministic port-set allocations or stateful translation keyed by subscriber identity and proper port tracking.
  3. Configure the supported DS-Lite B4-to-AFTR IPv4-over-IPv6 tunnel and provider-side translation model.
  4. Trace shared-risk link groups and relocate one service path to independent optical facilities where required.

Explanation

Correct Answer

A:

Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration. This directly addresses the fictional service-provider network case: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. The technical mechanism is: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation. Verify success by: A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.

Incorrect Answers

B:

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 provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation.

C:

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: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation.

D:

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: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation.

Question 450

For a regional service-provider operations center, operators addressed: A provider tries to deliver MAP-T using an IPv4-in-IPv6 encapsulation template and loses packets because the customer expects stateless translation. What is the strongest acceptance evidence?

  1. A known IPv4-only test name yields a reachable synthesized AAAA result and end-to-end connectivity.
  2. A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload.
  3. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.
  4. A permitted IPv6 test prefix appears while an unapproved wider prefix remains denied.

Explanation

Correct Answer

B:

A lab flow exhibits the intended address and port-set translation without relying on a MAP-E encapsulated payload. This confirms the approved response: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration. It is relevant because: MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

Incorrect Answers

A:

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: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

C:

A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients. This would validate 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. The specific correction here is: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.

D:

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: Apply the correct MAP-T algorithmic mapping and translation domain settings rather than a tunnel-only configuration.