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 51

Question 500

A core network change board wants to avoid: 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. Which ongoing safeguard fits best?

  1. Validate NET configuration and IS-IS levels during provisioning.
  2. Document each node's IS-IS level and area role before topology extensions.
  3. Use a peer inventory to preflight local and remote AS values.
  4. Add a common-level check to link commissioning scripts.

Explanation

Correct Answer

D:

Add a common-level check to link commissioning scripts. This helps prevent recurrence of the 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. Acceptance evidence should be: A lab peering test establishes a stable adjacency and exchanges the intended LSPs.

Incorrect Answers

A:

Validate NET configuration and IS-IS levels during provisioning. That is a sensible control for ANOTHER scenario: A core interface comes up but its IS-IS hellos never result in adjacency because peer system IDs use incompatible area addressing on L1-only neighbors. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.

B:

Document each node's IS-IS level and area role before topology extensions. That is a sensible control for ANOTHER scenario: 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 is less targeted to this issue than: Add a common-level check to link commissioning scripts.

C:

Use a peer inventory to preflight local and remote AS values. That is a sensible control for ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It is less targeted to this issue than: Add a common-level check to link commissioning scripts.

Question 501

A carrier service activation check discovers: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. Which action best restores the intended behavior?

  1. Align effective MTU or approved interface configuration, then verify database exchange.
  2. Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.
  3. Verify the DR/BDR design and inspect Full adjacencies with the designated router rather than forcing every DROTHER to Full.
  4. Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design.

Explanation

Correct Answer

B:

Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan. This directly addresses the fictional service-provider network case: 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 technical mechanism is: OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces. Verify success by: The selected path follows the expected OSPF cost and remains consistent across neighbors.

Incorrect Answers

A:

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 circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links.

C:

Verify the DR/BDR design and inspect Full adjacencies with the designated router rather than forcing every DROTHER to Full. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links.

D:

Restore the intended IGP reachability to the correct BGP next hop or adjust policy consistently with design. This would respond to a DIFFERENT fictional service-provider network issue: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. It does not directly address the current situation: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links.

Question 502

Following a supported configuration correction, the original issue was: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. Which observation verifies success?

  1. Neighbor state advances to Full and the LSDB includes the expected network LSA.
  2. OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
  3. The selected path follows the expected OSPF cost and remains consistent across neighbors.
  4. During restart testing, other routers avoid the node for transit until its forwarding state is ready.

Explanation

Correct Answer

C:

The selected path follows the expected OSPF cost and remains consistent across neighbors. This confirms the approved response: Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan. It is relevant because: OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.

Incorrect Answers

A:

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: Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.

B:

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 OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.

D:

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: Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.

Question 503

At an inter-AS service aggregation carrier, an engineer examines: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. Which technical principle is most applicable?

  1. OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.
  2. OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.
  3. IPv6 IS-IS topology rules must be consistent to avoid partial SPF or route installation.
  4. OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.

Explanation

Correct Answer

D:

OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces. This explains the investigated issue: 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 approved corrective response is: Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.

Incorrect Answers

A:

OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them. That explains a DIFFERENT 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 mechanism to prioritize for this question is: OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.

B:

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: OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.

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: OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.

Question 504

For an inter-AS service aggregation carrier, the change record describes: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. What preventive validation should be standard?

  1. Include reference bandwidth standards in routing config review.
  2. Teach neighbor-state expectations per OSPF network type in runbooks.
  3. Revalidate summaries against the address plan after branch network changes.
  4. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

Explanation

Correct Answer

A:

Include reference bandwidth standards in routing config review. This helps prevent recurrence of the issue: A customer circuit has high latency but OSPF chooses it over the primary because reference bandwidth was never updated for modern high-speed links. Acceptance evidence should be: The selected path follows the expected OSPF cost and remains consistent across neighbors.

Incorrect Answers

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: Include reference bandwidth standards in routing config review.

C:

Revalidate summaries against the address plan after branch network changes. That is a sensible control for 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. It is less targeted to this issue than: Include reference bandwidth standards in routing config review.

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: Include reference bandwidth standards in routing config review.

Question 505

For a regional service-provider operations center, the failure is: 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. Which authorized correction best addresses it?

  1. Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.
  2. Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.
  3. Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.
  4. Align approved IS-IS authentication parameters and keys on all intended peer interfaces.

Explanation

Correct Answer

C:

Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix. Verify success by: Adjacent peer route views show additional paths only when both sides support and negotiate the feature.

Incorrect Answers

A:

Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

B:

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

D:

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

Question 506

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

  1. A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.
  2. Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets.
  3. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.
  4. Adjacent peer route views show additional paths only when both sides support and negotiate the feature.

Explanation

Correct Answer

D:

Adjacent peer route views show additional paths only when both sides support and negotiate the feature. This confirms the approved response: Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised. It is relevant because: Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.

Incorrect Answers

A:

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: Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.

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: Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.

C:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This would validate 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. The specific correction here is: Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.

Question 507

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

  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 compares multiple attributes in a defined order rather than relying solely on IGP metrics.
  3. BGP best-path selection includes deterministic final tie-breakers when major attributes are equal.
  4. Route targets control VPN route distribution and should not be treated as ordinary public BGP communities.

Explanation

Correct Answer

A:

Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix. This explains the investigated issue: 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 approved corrective response is: Distinguish local multipath forwarding eligibility from Additional Paths capability and policy when multiple BGP alternatives must be advertised.

Incorrect Answers

B:

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

C:

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: Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.

D:

Route targets control VPN route distribution and should not be treated as ordinary public BGP communities. That explains a DIFFERENT scenario: A route reflector exports every VRF route to a public transit peer after route targets are reused carelessly in an import policy. The mechanism to prioritize for this question is: Standard BGP advertises selected best routes unless mechanisms such as Add-Path permit multiple distinct paths for a prefix.

Question 508

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

  1. Keep best-path attribute snapshots alongside policy change tickets.
  2. Check negotiated capabilities before enabling multiple-path distribution expectations.
  3. Require ordered attribute comparison in BGP troubleshooting notes.
  4. Record the correct address scope for OSPF and management telemetry.

Explanation

Correct Answer

B:

Check negotiated capabilities before enabling multiple-path distribution expectations. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Adjacent peer route views show additional paths only when both sides support and negotiate the feature.

Incorrect Answers

A:

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: Check negotiated capabilities before enabling multiple-path distribution expectations.

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: Check negotiated capabilities before enabling multiple-path distribution expectations.

D:

Record the correct address scope for OSPF and management telemetry. That is a sensible control for ANOTHER scenario: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. It is less targeted to this issue than: Check negotiated capabilities before enabling multiple-path distribution expectations.

Question 509

A provider backbone escalation identifies: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. What should the network team implement?

  1. Redistribute only explicitly authorized service prefixes through prefix lists and route policy.
  2. Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.
  3. Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.
  4. Review policy order and community membership before changing network reachability or resetting all sessions.

Explanation

Correct Answer

D:

Review policy order and community membership before changing network reachability or resetting all sessions. This directly addresses the fictional service-provider network case: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. The technical mechanism is: BGP route policy can accept or reject NLRI independently of session health. Verify success by: Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered.

Incorrect Answers

A:

Redistribute only explicitly authorized service prefixes through prefix lists and route policy. This would respond to a DIFFERENT fictional service-provider network issue: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It does not directly address the current situation: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group.

B:

Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed. This would respond to a DIFFERENT fictional service-provider network issue: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. It does not directly address the current situation: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group.

C:

Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group.

Question 510

A service-provider operations test targets: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. Which result is required?

  1. Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered.
  2. A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.
  3. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.
  4. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.

Explanation

Correct Answer

A:

Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered. This confirms the approved response: Review policy order and community membership before changing network reachability or resetting all sessions. It is relevant because: BGP route policy can accept or reject NLRI independently of session health.

Incorrect Answers

B:

A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes. This would validate ANOTHER 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 specific correction here is: Review policy order and community membership before changing network reachability or resetting all sessions.

C:

Customer route queries show approved aggregate service routes but no internal infrastructure prefixes. This would validate ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The specific correction here is: Review policy order and community membership before changing network reachability or resetting all sessions.

D:

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: Review policy order and community membership before changing network reachability or resetting all sessions.