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 68

Question 670

A service-provider operations test targets: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. Which result is required?

  1. Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.
  2. Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss.
  3. An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing.
  4. A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop.

Explanation

Correct Answer

A:

Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated. This confirms the approved response: Assign service-specific route targets and restrict import policy to the approved tenant set. It is relevant because: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.

Incorrect Answers

B:

Normal traffic uses the intended primary site and cleanly fails to the approved backup during a simulated primary loss. This would validate ANOTHER scenario: A customer VRF needs dual-homed connectivity yet the provider sets local preference to favor the backup for all customer routes, causing avoidable transit cost. The specific correction here is: Assign service-specific route targets and restrict import policy to the approved tenant set.

C:

An IPv6 test prefix reaches the remote customer site without unintended mixing with IPv4-only service routing. This would validate ANOTHER scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. The specific correction here is: Assign service-specific route targets and restrict import policy to the approved tenant set.

D:

A link-loss test forwards traffic through the surviving PE without duplicates or a transient broadcast loop. This would validate ANOTHER scenario: An EVPN multihoming access service floods duplicates during an all-active ESI failover because designated forwarder election states disagree. The specific correction here is: Assign service-specific route targets and restrict import policy to the approved tenant set.

Question 671

A provider troubleshooting note states: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. Which mechanism is central?

  1. Shared Internet or extranet services require symmetric routing or supported translation for the return path.
  2. Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.
  3. VPN routing can preserve stale more-specific or static routes that override newly learned paths.
  4. EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy.

Explanation

Correct Answer

B:

Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability. This explains the investigated issue: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. The approved corrective response is: Assign service-specific route targets and restrict import policy to the approved tenant set.

Incorrect Answers

A:

Shared Internet or extranet services require symmetric routing or supported translation for the return path. That explains a DIFFERENT scenario: A remote customer site can send packets toward the Internet exit in a shared services VRF but the exit has no return route for the private customer prefix. The mechanism to prioritize for this question is: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.

C:

VPN routing can preserve stale more-specific or static routes that override newly learned paths. That explains a DIFFERENT scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. The mechanism to prioritize for this question is: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.

D:

EVPN Type-5 routes distribute IP prefix reachability and require appropriate service import policy. That explains a DIFFERENT scenario: A provider imports an EVPN Type-5 IP prefix into the wrong VRF because a route-target policy matches a customer label instead of the service's approved tenant RT. The mechanism to prioritize for this question is: Route targets act as membership signals and broad RT reuse can unintentionally expand VPN reachability.

Question 672

To prevent recurrence of this provider network issue: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. Which control should be retained?

  1. Include stale route and next-hop cleanup in VPN site migrations.
  2. Validate VPNv4 and VPNv6 service route counts independently.
  3. Review RT consumer inventories for every shared-service announcement.
  4. Test DR state when changing multicast LAN interfaces.

Explanation

Correct Answer

C:

Review RT consumer inventories for every shared-service announcement. This helps prevent recurrence of the issue: A provider advertises the same extranet shared-services prefix into two tenants, but a third tenant unexpectedly imports it because a generic RT is reused globally. Acceptance evidence should be: Prefix readback appears only in the two participating VRFs and all other VRFs remain isolated.

Incorrect Answers

A:

Include stale route and next-hop cleanup in VPN site migrations. That is a sensible control for ANOTHER scenario: A carrier moves an enterprise's primary VPN site but retains an old CE static route in the remote VRF, steering packets to the retired PE. It is less targeted to this issue than: Review RT consumer inventories for every shared-service announcement.

B:

Validate VPNv4 and VPNv6 service route counts independently. That is a sensible control for ANOTHER scenario: An enterprise customer is promised IPv6 VPN reachability but the PE provisions only VPNv4 MP-BGP and v4 VRF interfaces. It is less targeted to this issue than: Review RT consumer inventories for every shared-service announcement.

D:

Test DR state when changing multicast LAN interfaces. That is a sensible control for ANOTHER scenario: Two multicast access routers each act as designated router for the same LAN after a timer mismatch and receivers see repeated source register behavior. It is less targeted to this issue than: Review RT consumer inventories for every shared-service announcement.

Question 673

At a regional service-provider operations center, an engineering review finds: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. Which change most directly corrects the service problem?

  1. Correct the interlevel advertisement and summary scope after checking reachability to the component routes.
  2. Align both ends to a common supported IS-IS adjacency level with consistent interface settings.
  3. Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.
  4. Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology.

Explanation

Correct Answer

A:

Correct the interlevel advertisement and summary scope after checking reachability to the component routes. This directly addresses the fictional service-provider network case: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. The technical mechanism is: IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics. Verify success by: A test route follows the intended L1/L2 router and resolves to a valid downstream next hop.

Incorrect Answers

B:

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 link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix.

C:

Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. This would respond to a DIFFERENT fictional service-provider network issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It does not directly address the current situation: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix.

D:

Verify recursive next-hop and forwarding-plane independence for each ECMP member and correct the backup topology. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix.

Question 674

For a regional service-provider operations center, operators addressed: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. What is the strongest acceptance evidence?

  1. A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.
  2. A test route follows the intended L1/L2 router and resolves to a valid downstream next hop.
  3. Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.
  4. A test prefix is visible across the area boundary before the dependent BGP route recovers.

Explanation

Correct Answer

B:

A test route follows the intended L1/L2 router and resolves to a valid downstream next hop. This confirms the approved response: Correct the interlevel advertisement and summary scope after checking reachability to the component routes. It is relevant because: IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.

Incorrect Answers

A:

A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes. This would validate 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. The specific correction here is: Correct the interlevel advertisement and summary scope after checking reachability to the component routes.

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: Correct the interlevel advertisement and summary scope after checking reachability to the component routes.

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: Correct the interlevel advertisement and summary scope after checking reachability to the component routes.

Question 675

Which network protocol or forwarding behavior explains the following issue: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix.

  1. Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.
  2. Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.
  3. IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.
  4. Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately.

Explanation

Correct Answer

C:

IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics. This explains the investigated issue: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. The approved corrective response is: Correct the interlevel advertisement and summary scope after checking reachability to the component routes.

Incorrect Answers

A:

Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.

B:

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: IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.

D:

Shared-address NAT needs distinct translated transport identifiers to demultiplex flows accurately. That explains a DIFFERENT scenario: An ISP assigns customer IPv4 address blocks through CGNAT but configures identical port-set mappings on two subscribers behind the same public address, causing connection collisions. The mechanism to prioritize for this question is: IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.

Question 676

A core network change board wants to avoid: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. Which ongoing safeguard fits best?

  1. Maintain dual-stack adjacency and LSDB checks after MT feature changes.
  2. Review IGP link metrics against current network capacity and service objectives.
  3. Distinguish translation versus encapsulation requirements in IPv4-as-a-service profiles.
  4. Test component-prefix ownership before exporting aggregates.

Explanation

Correct Answer

D:

Test component-prefix ownership before exporting aggregates. This helps prevent recurrence of the issue: A link between routing domains advertises a summary into the wrong IS-IS level, so traffic loops toward an area without the actual component prefix. Acceptance evidence should be: A test route follows the intended L1/L2 router and resolves to a valid downstream next hop.

Incorrect Answers

A:

Maintain dual-stack adjacency and LSDB checks after MT feature changes. That is a sensible control for ANOTHER scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. It is less targeted to this issue than: Test component-prefix ownership before exporting aggregates.

B:

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: Test component-prefix ownership before exporting aggregates.

C:

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: Test component-prefix ownership before exporting aggregates.

Question 677

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

  1. Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.
  2. Match OSPF timers and authentication to the intended network type on both interfaces.
  3. Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.
  4. Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.

Explanation

Correct Answer

B:

Match OSPF timers and authentication to the intended network type on both interfaces. This directly addresses the fictional service-provider network case: 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 technical mechanism is: OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them. Verify success by: OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.

Incorrect Answers

A:

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 OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure.

C:

Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: 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.

D:

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

Question 678

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

  1. Neighbor state advances to Full and the LSDB includes the expected network LSA.
  2. The DR has Full adjacencies and LSDB convergence while DROTHER peers show their expected state.
  3. OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability.
  4. A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources.

Explanation

Correct Answer

C:

OSPF neighbors reach Full with consistent hellos and the BGP session subsequently obtains IGP reachability. This confirms the approved response: Match OSPF timers and authentication to the intended network type on both interfaces. It is relevant because: OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

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: Match OSPF timers and authentication to the intended network type on both interfaces.

B:

The DR has Full adjacencies and LSDB convergence while DROTHER peers show their expected state. This would validate 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. The specific correction here is: Match OSPF timers and authentication to the intended network type on both interfaces.

D:

A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources. This would validate ANOTHER scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. The specific correction here is: Match OSPF timers and authentication to the intended network type on both interfaces.

Question 679

At a wholesale transit provider, an engineer examines: 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. Which technical principle is most applicable?

  1. Improper OSPF area summarization can advertise reachability where no specific destination exists.
  2. OSPF area-type agreement is required for adjacency and stub routing behavior.
  3. Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.
  4. OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

Explanation

Correct Answer

D:

OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them. This explains the investigated 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. The approved corrective response is: Match OSPF timers and authentication to the intended network type on both interfaces.

Incorrect Answers

A:

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 neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

B:

OSPF area-type agreement is required for adjacency and stub routing behavior. That explains a DIFFERENT scenario: An OSPF stub area loses its expected default route when an engineer configures stub mode on the access router but not consistently on the area border router. The mechanism to prioritize for this question is: OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

C:

Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low. That explains a DIFFERENT scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The mechanism to prioritize for this question is: OSPF neighbors require compatible hello/dead settings and authentication before upper-layer reachability can rely on them.

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.