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 4

Question 30

A service-provider operations test targets: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. Which result is required?

  1. A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.
  2. During restart testing, other routers avoid the node for transit until its forwarding state is ready.
  3. Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.
  4. During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.

Explanation

Correct Answer

A:

A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes. This confirms the approved response: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design. It is relevant because: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.

Incorrect Answers

B:

During restart testing, other routers avoid the node for transit until its forwarding state is ready. This would validate ANOTHER scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. The specific correction here is: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

C:

Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies. This would validate ANOTHER scenario: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. The specific correction here is: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

D:

During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load. This would validate ANOTHER scenario: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The specific correction here is: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

Question 31

A provider troubleshooting note states: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. Which mechanism is central?

  1. The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance.
  2. IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.
  3. IPv6 IS-IS topology rules must be consistent to avoid partial SPF or route installation.
  4. Local preference is an AS-wide policy attribute typically considered before AS_PATH length.

Explanation

Correct Answer

B:

IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability. This explains the investigated issue: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. The approved corrective response is: Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

Incorrect Answers

A:

The IS-IS overload bit can discourage transit forwarding through a router during startup or maintenance. That explains a DIFFERENT scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. The mechanism to prioritize for this question is: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.

C:

IPv6 IS-IS topology rules must be consistent to avoid partial SPF or route installation. That explains a DIFFERENT scenario: A new IPv6-only service is added to an IS-IS core, but routers run a single topology configuration where the IPv6 reachability bits are not negotiated consistently. The mechanism to prioritize for this question is: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.

D:

Local preference is an AS-wide policy attribute typically considered before AS_PATH length. That explains a DIFFERENT scenario: A carrier's inbound customer route has local preference 200 but another exit's route has a shorter AS_PATH, and the team incorrectly expects the short path to win. The mechanism to prioritize for this question is: IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.

Question 32

To prevent recurrence of this provider network issue: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. Which control should be retained?

  1. Review IGP link metrics against current network capacity and service objectives.
  2. Automate overload clearance only after readiness gates pass.
  3. Document each node's IS-IS level and area role before topology extensions.
  4. Require ordered attribute comparison in BGP troubleshooting notes.

Explanation

Correct Answer

C:

Document each node's IS-IS level and area role before topology extensions. This helps prevent recurrence of the issue: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. Acceptance evidence should be: A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.

Incorrect Answers

A:

Review IGP link metrics against current network capacity and service objectives. That is a sensible control for ANOTHER scenario: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. It is less targeted to this issue than: Document each node's IS-IS level and area role before topology extensions.

B:

Automate overload clearance only after readiness gates pass. That is a sensible control for ANOTHER scenario: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. It is less targeted to this issue than: Document each node's IS-IS level and area role before topology extensions.

D:

Require ordered attribute comparison in BGP troubleshooting notes. That is a sensible control for ANOTHER scenario: A provider expects an iBGP-learned path to beat an otherwise equal eBGP path simply because the iBGP router has a lower IGP cost to the next hop. It is less targeted to this issue than: Document each node's IS-IS level and area role before topology extensions.

Question 33

At an optical transport engineering team, an engineering review finds: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. Which change most directly corrects the service problem?

  1. Align effective MTU or approved interface configuration, then verify database exchange.
  2. Enable the intended OSPFv3 address-family participation in the correct routing context.
  3. Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.
  4. Set the intended IS-IS wide metric on the optical link based on approved transport cost.

Explanation

Correct Answer

A:

Align effective MTU or approved interface configuration, then verify database exchange. This directly addresses the fictional service-provider network case: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. The technical mechanism is: OSPF database description exchange checks compatibility such as MTU before completing adjacency. Verify success by: Neighbor state advances to Full and the LSDB includes the expected network LSA.

Incorrect Answers

B:

Enable the intended OSPFv3 address-family participation in the correct routing context. This would respond to a DIFFERENT fictional service-provider network issue: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It does not directly address the current situation: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU.

C:

Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes. This would respond to a DIFFERENT fictional service-provider network issue: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. It does not directly address the current situation: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU.

D:

Set the intended IS-IS wide metric on the optical link based on approved transport cost. This would respond to a DIFFERENT fictional service-provider network issue: An IS-IS L2 router forms adjacency but traffic chooses a high-latency optical link because the interface metric was left at a low default. It does not directly address the current situation: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU.

Question 34

For an optical transport engineering team, operators addressed: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. What is the strongest acceptance evidence?

  1. Valid component destinations work and an unassigned prefix does not loop indefinitely.
  2. Neighbor state advances to Full and the LSDB includes the expected network LSA.
  3. OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
  4. A failure drill on one shelf leaves at least one approved end-to-end route available.

Explanation

Correct Answer

B:

Neighbor state advances to Full and the LSDB includes the expected network LSA. This confirms the approved response: Align effective MTU or approved interface configuration, then verify database exchange. It is relevant because: OSPF database description exchange checks compatibility such as MTU before completing adjacency.

Incorrect Answers

A:

Valid component destinations work and an unassigned prefix does not loop indefinitely. This would validate ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The specific correction here is: Align effective MTU or approved interface configuration, then verify database exchange.

C:

OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability. This would validate ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. The specific correction here is: Align effective MTU or approved interface configuration, then verify database exchange.

D:

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: Align effective MTU or approved interface configuration, then verify database exchange.

Question 35

Which network protocol or forwarding behavior explains the following issue: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU.

  1. OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.
  2. Improper OSPF area summarization can advertise reachability where no specific destination exists.
  3. OSPF database description exchange checks compatibility such as MTU before completing adjacency.
  4. MAP-T uses stateless IPv4/IPv6 translation, whereas MAP-E relies on IPv4-in-IPv6 encapsulation.

Explanation

Correct Answer

C:

OSPF database description exchange checks compatibility such as MTU before completing adjacency. This explains the investigated issue: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. The approved corrective response is: Align effective MTU or approved interface configuration, then verify database exchange.

Incorrect Answers

A:

OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: OSPF database description exchange checks compatibility such as MTU before completing adjacency.

B:

Improper OSPF area summarization can advertise reachability where no specific destination exists. That explains a DIFFERENT scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The mechanism to prioritize for this question is: OSPF database description exchange checks compatibility such as MTU before completing adjacency.

D:

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: OSPF database description exchange checks compatibility such as MTU before completing adjacency.

Question 36

A core network change board wants to avoid: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. Which ongoing safeguard fits best?

  1. Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
  2. Teach neighbor-state expectations per OSPF network type in runbooks.
  3. Document nondefault origin modifications to avoid opaque path changes.
  4. Check interface MTU and OSPF packet parameters when commissioning peer links.

Explanation

Correct Answer

D:

Check interface MTU and OSPF packet parameters when commissioning peer links. This helps prevent recurrence of the issue: Two provider OSPFv2 routers share an Ethernet segment but never advance past EXSTART because one end uses an incompatible interface MTU. Acceptance evidence should be: Neighbor state advances to Full and the LSDB includes the expected network LSA.

Incorrect Answers

A:

Verify lower-layer IGP readiness before diagnosing dependent BGP sessions. That is a sensible control for ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. It is less targeted to this issue than: Check interface MTU and OSPF packet parameters when commissioning peer links.

B:

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: Check interface MTU and OSPF packet parameters when commissioning peer links.

C:

Document nondefault origin modifications to avoid opaque path changes. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Check interface MTU and OSPF packet parameters when commissioning peer links.

Question 37

A carrier service activation check discovers: 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. Which action best restores the intended behavior?

  1. Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.
  2. Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.
  3. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.
  4. Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.

Explanation

Correct Answer

B:

Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules. This directly addresses the fictional service-provider network case: 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 technical mechanism is: BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics. Verify success by: A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.

Incorrect Answers

A:

Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred. This would respond to a DIFFERENT fictional service-provider network issue: BGP flips between two equal candidates because a team ignores the router-id and neighbor-address tie-breakers after all higher-ranked attributes match. It does not directly address the current situation: 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.

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

D:

Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design. This would respond to a DIFFERENT fictional service-provider network issue: Two provider core routers form an IS-IS L1 adjacency but do not exchange a prefix from another area because the engineer assumes L1 routers have universal interarea visibility. It does not directly address the current situation: 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.

Question 38

Following a supported configuration correction, the original issue was: 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. Which observation verifies success?

  1. A test route exits through the desired high-local-preference border where both paths are otherwise eligible.
  2. Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets.
  3. A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.
  4. A test prefix is visible across the area boundary before the dependent BGP route recovers.

Explanation

Correct Answer

C:

A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal. This confirms the approved response: Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules. It is relevant because: BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.

Incorrect Answers

A:

A test route exits through the desired high-local-preference border where both paths are otherwise eligible. This would validate ANOTHER scenario: A carrier's inbound customer route has local preference 200 but another exit's route has a shorter AS_PATH, and the team incorrectly expects the short path to win. The specific correction here is: Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.

B:

Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets. This would validate ANOTHER 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 specific correction here is: Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.

D:

A test prefix is visible across the area boundary before the dependent BGP route recovers. This would validate 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. The specific correction here is: Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.

Question 39

At a carrier automation platform team, an engineer examines: 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. Which technical principle is most applicable?

  1. Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.
  2. BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.
  3. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.
  4. BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.

Explanation

Correct Answer

D:

BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics. This explains the investigated issue: 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 approved corrective response is: Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.

Incorrect Answers

A:

Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix. That explains a DIFFERENT 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 mechanism to prioritize for this question is: BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.

B:

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: BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.

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: BGP best-path selection compares multiple attributes in a defined order rather than relying solely on IGP metrics.

Question 40

For a carrier automation platform team, the change record describes: 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. What preventive validation should be standard?

  1. Keep best-path attribute snapshots alongside policy change tickets.
  2. Document nondefault origin modifications to avoid opaque path changes.
  3. Require ordered attribute comparison in BGP troubleshooting notes.
  4. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

Explanation

Correct Answer

A:

Keep best-path attribute snapshots alongside policy change tickets. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.

Incorrect Answers

B:

Document nondefault origin modifications to avoid opaque path changes. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.

C:

Require ordered attribute comparison in BGP troubleshooting notes. That is a sensible control for ANOTHER scenario: A provider expects an iBGP-learned path to beat an otherwise equal eBGP path simply because the iBGP router has a lower IGP cost to the next hop. It is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.

D:

Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles. That is a sensible control for 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. It is less targeted to this issue than: Keep best-path attribute snapshots alongside policy change tickets.