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 69

Question 680

For a wholesale transit provider, the change record describes: 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. What preventive validation should be standard?

  1. Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
  2. Include reference bandwidth standards in routing config review.
  3. Test protocol instance, VRF and AF together in route acceptance.
  4. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.

Explanation

Correct Answer

A:

Verify lower-layer IGP readiness before diagnosing dependent BGP sessions. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.

Incorrect Answers

B:

Include reference bandwidth standards in routing config review. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.

C:

Test protocol instance, VRF and AF together in route acceptance. That is a sensible control for ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It is less targeted to this issue than: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.

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: Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.

Question 681

For a multi-region fiber backbone operator, the failure is: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. Which authorized correction best addresses it?

  1. Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.
  2. Use MED within its intended neighboring-AS comparison scope and coordinate inbound policy or communities with upstreams where needed.
  3. Redistribute only explicitly authorized service prefixes through prefix lists and route policy.
  4. Align effective MTU or approved interface configuration, then verify database exchange.

Explanation

Correct Answer

C:

Redistribute only explicitly authorized service prefixes through prefix lists and route policy. This directly addresses the fictional service-provider network case: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The technical mechanism is: Redistribution crosses route domains and must be scoped to prevent unintended advertisement. Verify success by: Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Incorrect Answers

A:

Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border. This would respond to a DIFFERENT fictional service-provider network issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. It does not directly address the current situation: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream.

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: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream.

D:

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: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream.

Question 682

After fixing the following network problem, what should the team verify: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream.

  1. The eBGP FSM reaches Established and the peer's AS is recorded correctly.
  2. Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit.
  3. Route verification shows full IPv6 prefix reachability with stable LSP exchange.
  4. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Explanation

Correct Answer

D:

Customer route queries show approved aggregate service routes but no internal infrastructure prefixes. This confirms the approved response: Redistribute only explicitly authorized service prefixes through prefix lists and route policy. It is relevant because: Redistribution crosses route domains and must be scoped to prevent unintended advertisement.

Incorrect Answers

A:

The eBGP FSM reaches Established and the peer's AS is recorded correctly. This would validate ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. The specific correction here is: Redistribute only explicitly authorized service prefixes through prefix lists and route policy.

B:

Lab inbound path attributes show the prepend toward an upstream while the local routing policy sets the expected outbound exit. This would validate ANOTHER scenario: A multihomed service-provider customer advertises a /24 prefix with multiple AS prepends yet expects the prepend to influence its own outbound preferred exit. The specific correction here is: Redistribute only explicitly authorized service prefixes through prefix lists and route policy.

C:

Route verification shows full IPv6 prefix reachability with stable LSP exchange. This would validate ANOTHER 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 specific correction here is: Redistribute only explicitly authorized service prefixes through prefix lists and route policy.

Question 683

A carrier root-cause review considers: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. What underlying mechanism explains this?

  1. Redistribution crosses route domains and must be scoped to prevent unintended advertisement.
  2. MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.
  3. BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution.
  4. BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

Explanation

Correct Answer

A:

Redistribution crosses route domains and must be scoped to prevent unintended advertisement. This explains the investigated issue: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. The approved corrective response is: Redistribute only explicitly authorized service prefixes through prefix lists and route policy.

Incorrect Answers

B:

MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Redistribution crosses route domains and must be scoped to prevent unintended advertisement.

C:

BGP Prefix Independent Convergence depends on precomputed forwarding alternatives and valid recursive next-hop resolution. That explains a DIFFERENT scenario: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The mechanism to prioritize for this question is: Redistribution crosses route domains and must be scoped to prevent unintended advertisement.

D:

BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Redistribution crosses route domains and must be scoped to prevent unintended advertisement.

Question 684

After addressing: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. Which recurring service assurance check is most useful?

  1. Audit per-neighbor AF activation during dual-stack turn-up.
  2. Review candidate redistribution tables under a default-deny policy.
  3. Use a peer inventory to preflight local and remote AS values.
  4. Baseline BFD jitter and loss before setting aggressive detection timers.

Explanation

Correct Answer

B:

Review candidate redistribution tables under a default-deny policy. This helps prevent recurrence of the issue: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. Acceptance evidence should be: Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Incorrect Answers

A:

Audit per-neighbor AF activation during dual-stack turn-up. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Review candidate redistribution tables under a default-deny policy.

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: Review candidate redistribution tables under a default-deny policy.

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: Review candidate redistribution tables under a default-deny policy.

Question 685

A provider backbone escalation identifies: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. What should the network team implement?

  1. Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan.
  2. Trace shared-risk link groups and relocate one service path to independent optical facilities where required.
  3. Inspect the full deterministic tie-breaking sequence and stabilize the intended export policy if one exit must be preferred.
  4. Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.

Explanation

Correct Answer

D:

Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies. This directly addresses the fictional service-provider network case: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The technical mechanism is: High availability must account for postfailure capacity, not merely the existence of an alternate topology path. Verify success by: During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.

Incorrect Answers

A:

Validate supported ISSU procedure, image compatibility and redundancy state before proceeding with a staged maintenance plan. This would respond to a DIFFERENT fictional service-provider network issue: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. It does not directly address the current situation: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up.

B:

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 core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up.

C:

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 core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up.

Question 686

A service-provider operations test targets: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. Which result is required?

  1. During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.
  2. A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state.
  3. A failure drill on one shelf leaves at least one approved end-to-end route available.
  4. A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.

Explanation

Correct Answer

A:

During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load. This confirms the approved response: Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies. It is relevant because: High availability must account for postfailure capacity, not merely the existence of an alternate topology path.

Incorrect Answers

B:

A failover test retains stable BGP peering where the platform supports NSR and shows synchronized protocol state. This would validate ANOTHER scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The specific correction here is: Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.

C:

A failure drill on one shelf leaves at least one approved end-to-end route available. This would validate ANOTHER scenario: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. The specific correction here is: Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.

D:

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: Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.

Question 687

A provider troubleshooting note states: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. Which mechanism is central?

  1. Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts.
  2. High availability must account for postfailure capacity, not merely the existence of an alternate topology path.
  3. Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk.
  4. Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.

Explanation

Correct Answer

B:

High availability must account for postfailure capacity, not merely the existence of an alternate topology path. This explains the investigated issue: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. The approved corrective response is: Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.

Incorrect Answers

A:

Graceful Restart relies on helpers and retained forwarding state to avoid unnecessary service interruption during control-plane restarts. That explains a DIFFERENT scenario: A provider enables graceful restart for BGP but withdraws all forwarding entries immediately after a planned route-processor switchover, ignoring forwarding preservation requirements. The mechanism to prioritize for this question is: High availability must account for postfailure capacity, not merely the existence of an alternate topology path.

C:

Logical ECMP diversity does not ensure physical failure independence when transport infrastructure shares common risk. That explains a DIFFERENT 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 mechanism to prioritize for this question is: High availability must account for postfailure capacity, not merely the existence of an alternate topology path.

D:

Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: High availability must account for postfailure capacity, not merely the existence of an alternate topology path.

Question 688

To prevent recurrence of this provider network issue: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. Which control should be retained?

  1. Verify port-channel membership and individual-link counters after physical changes.
  2. Audit FIB recursive adjacency groups as part of resiliency tests.
  3. Include N-1 link capacity tests in planned-maintenance readiness checks.
  4. Trend prefix counts and alert before capacity thresholds are reached.

Explanation

Correct Answer

C:

Include N-1 link capacity tests in planned-maintenance readiness checks. This helps prevent recurrence of the issue: A core routing node performs maintenance with all traffic temporarily pinned to one uplink, exceeding the designed capacity even though connectivity stays up. Acceptance evidence should be: During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.

Incorrect Answers

A:

Verify port-channel membership and individual-link counters after physical changes. That is a sensible control for ANOTHER scenario: A provider aggregates two PE uplinks in LACP but one port belongs to a different bundle ID, creating unpredictable blackholes for hashed subscriber flows. It is less targeted to this issue than: Include N-1 link capacity tests in planned-maintenance readiness checks.

B:

Audit FIB recursive adjacency groups as part of resiliency tests. That is a sensible control for ANOTHER scenario: A network uses two next hops with ECMP but one backup route resolves through the same failed access link and the team reports full path redundancy. It is less targeted to this issue than: Include N-1 link capacity tests in planned-maintenance readiness checks.

D:

Trend prefix counts and alert before capacity thresholds are reached. That is a sensible control for ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It is less targeted to this issue than: Include N-1 link capacity tests in planned-maintenance readiness checks.

Question 689

At a global tier-one IP transit carrier, an engineering review finds: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. Which change most directly corrects the service problem?

  1. Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.
  2. Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures.
  3. Align authorized LDP session authentication and transport addresses on the intended peers.
  4. Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth.

Explanation

Correct Answer

A:

Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels. This directly addresses the fictional service-provider network case: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. The technical mechanism is: MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress. Verify success by: Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.

Incorrect Answers

B:

Reconcile LDP label mapping with current IGP FEC reachability and refresh only the impacted forwarding state through supported procedures. This would respond to a DIFFERENT fictional service-provider network issue: Label advertisement remains present for a withdrawn IGP FEC due to a stale forwarding cache, producing a short-lived blackhole after a route-policy rollback. It does not directly address the current situation: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition.

C:

Align authorized LDP session authentication and transport addresses on the intended peers. This would respond to a DIFFERENT fictional service-provider network issue: Two neighboring MPLS routers use different LDP authentication credentials and fail to form a TCP session even though UDP discovery hellos arrive. It does not directly address the current situation: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition.

D:

Shorten the policy with supported binding SIDs or select hardware capable of the required maximum SID depth. This would respond to a DIFFERENT fictional service-provider network issue: The headend imposes an SR-MPLS list of eight SIDs on a platform supporting only six, causing only complex engineered paths to fail. It does not directly address the current situation: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition.

Question 690

For a global tier-one IP transit carrier, operators addressed: The forwarding plane sees an implicit-null label for a PE loopback and a troubleshooter treats it as an invalid unassigned label rather than checking the upstream label disposition. What is the strongest acceptance evidence?

  1. The test isolates a healthy transport LSP from a missing inner VPN route or label binding.
  2. Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly.
  3. The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present.
  4. CSPF selects an eligible path whose measured reserved capacity meets the service constraint.

Explanation

Correct Answer

B:

Packet tracing shows the upstream hop removes the appropriate outer label and the egress handles remaining context correctly. This confirms the approved response: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels. It is relevant because: MPLS implicit-null signals an upstream LSR to remove a label before forwarding to the egress.

Incorrect Answers

A:

The test isolates a healthy transport LSP from a missing inner VPN route or label binding. This would validate ANOTHER scenario: A provider applies MPLS LSP ping only to the global transport loopback while a customer L3VPN remains broken, then claims VPN reachability is fully proven. The specific correction here is: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

C:

The VPN transport path becomes operational only after both IGP recursion and the corresponding label are present. This would validate ANOTHER scenario: A remote PE receives an LDP label binding but the advertised transport loopback is absent from the IGP, making forwarding unresolved. The specific correction here is: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.

D:

CSPF selects an eligible path whose measured reserved capacity meets the service constraint. This would validate ANOTHER scenario: An MPLS traffic-engineering tunnel reserves 500 Mbps but physically traverses a 100 Mbps access link because the advertised TE bandwidth attributes are stale. The specific correction here is: Interpret implicit-null advertisement as penultimate-hop popping behavior and verify the service's remaining labels.