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 17

Question 160

To prevent recurrence of this provider network issue: A provider triggers RTBH by announcing a route with an incorrect blackhole community, and legitimate subscriber traffic to the target continues to traverse the core. Which control should be retained?

  1. Verify MACsec secure-channel state after optics and link-aggregation changes.
  2. Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.
  3. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
  4. Require peer and prefix authorization and monitor FlowSpec rule impacts.

Explanation

Correct Answer

C:

Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. This helps prevent recurrence of the issue: A provider triggers RTBH by announcing a route with an incorrect blackhole community, and legitimate subscriber traffic to the target continues to traverse the core. Acceptance evidence should be: A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.

Incorrect Answers

A:

Verify MACsec secure-channel state after optics and link-aggregation changes. That is a sensible control for ANOTHER scenario: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

B:

Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance. That is a sensible control for ANOTHER scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

D:

Require peer and prefix authorization and monitor FlowSpec rule impacts. That is a sensible control for ANOTHER scenario: A route server receives a new FlowSpec route and applies a blanket drop to an entire customer prefix without checking the match and validation policy. It is less targeted to this issue than: Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.

Question 161

At a converged broadband aggregation team, an engineering review finds: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. Which change most directly corrects the service problem?

  1. Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.
  2. Correct the interlevel advertisement and summary scope after checking reachability to the component routes.
  3. Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.
  4. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

Explanation

Correct Answer

A:

Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. This directly addresses the fictional service-provider network case: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The technical mechanism is: Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled. Verify success by: IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable.

Incorrect Answers

B:

Correct the interlevel advertisement and summary scope after checking reachability to the component routes. This would respond to a DIFFERENT fictional service-provider network 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. It does not directly address the current situation: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database.

C:

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: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database.

D:

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: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database.

Question 162

For a converged broadband aggregation team, operators addressed: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. What is the strongest acceptance evidence?

  1. Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.
  2. IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable.
  3. A test route follows the intended L1/L2 router and resolves to a valid downstream next hop.
  4. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Explanation

Correct Answer

B:

IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable. This confirms the approved response: Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route. It is relevant because: Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.

Incorrect Answers

A:

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: Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.

C:

A test route follows the intended L1/L2 router and resolves to a valid downstream next hop. This would validate ANOTHER scenario: 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 specific correction here is: Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.

D:

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: Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.

Question 163

Which network protocol or forwarding behavior explains the following issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database.

  1. IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.
  2. Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.
  3. Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.
  4. Improper OSPF area summarization can advertise reachability where no specific destination exists.

Explanation

Correct Answer

C:

Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled. This explains the investigated issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The approved corrective response is: Verify IS-IS IPv6 address family and multitopology participation on all transit adjacencies along the route.

Incorrect Answers

A:

IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.

B:

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: Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.

D:

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: Separate IS-IS topologies can calculate IPv4 and IPv6 reachability independently when multitopology is enabled.

Question 164

A core network change board wants to avoid: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. Which ongoing safeguard fits best?

  1. Review IGP link metrics against current network capacity and service objectives.
  2. Document each node's IS-IS level and area role before topology extensions.
  3. Require ordered attribute comparison in BGP troubleshooting notes.
  4. Maintain dual-stack adjacency and LSDB checks after MT feature changes.

Explanation

Correct Answer

D:

Maintain dual-stack adjacency and LSDB checks after MT feature changes. This helps prevent recurrence of the issue: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. Acceptance evidence should be: IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable.

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: Maintain dual-stack adjacency and LSDB checks after MT feature changes.

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: Maintain dual-stack adjacency and LSDB checks after MT feature changes.

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: Maintain dual-stack adjacency and LSDB checks after MT feature changes.

Question 165

A carrier service activation check discovers: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. Which action best restores the intended behavior?

  1. Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.
  2. Enable the intended OSPFv3 address-family participation in the correct routing context.
  3. Align OSPF reference bandwidth and interface cost across the routing domain to the engineered capacity plan.
  4. Configure detection and multiplier values consistent with platform and WAN path characteristics.

Explanation

Correct Answer

B:

Enable the intended OSPFv3 address-family participation in the correct routing context. This directly addresses the fictional service-provider network case: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The technical mechanism is: OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family. Verify success by: IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged.

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: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF.

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: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF.

D:

Configure detection and multiplier values consistent with platform and WAN path characteristics. This would respond to a DIFFERENT fictional service-provider network issue: A BFD session on a long-haul link uses submillisecond detection and repeatedly declares faults during normal microbursts despite healthy optics. It does not directly address the current situation: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF.

Question 166

Following a supported configuration correction, the original issue was: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. 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. IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged.
  4. During a simulated link withdrawal, surviving links meet congestion and QoS objectives under measured peak load.

Explanation

Correct Answer

C:

IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged. This confirms the approved response: Enable the intended OSPFv3 address-family participation in the correct routing context. It is relevant because: OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

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: Enable the intended OSPFv3 address-family participation in the correct routing context.

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: Enable the intended OSPFv3 address-family participation in the correct routing context.

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: Enable the intended OSPFv3 address-family participation in the correct routing context.

Question 167

At an inter-AS service aggregation carrier, an engineer examines: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. Which technical principle is most applicable?

  1. OSPF area-type agreement is required for adjacency and stub routing behavior.
  2. IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally.
  3. MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.
  4. OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

Explanation

Correct Answer

D:

OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family. This explains the investigated issue: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The approved corrective response is: Enable the intended OSPFv3 address-family participation in the correct routing context.

Incorrect Answers

A:

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: OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

B:

IPv6 link-local addresses are scoped to their link and need an interface scope when referenced locally. That explains a DIFFERENT scenario: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The mechanism to prioritize for this question is: OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

C:

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: OSPFv3 control adjacency does not guarantee a route is installed in every VRF or address family.

Question 168

For an inter-AS service aggregation carrier, the change record describes: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. What preventive validation should be standard?

  1. Test protocol instance, VRF and AF together in route acceptance.
  2. Validate area-type consistency before enabling stub policy.
  3. Include reference bandwidth standards in routing config review.
  4. Identify traffic direction for each BGP tuning ticket.

Explanation

Correct Answer

A:

Test protocol instance, VRF and AF together in route acceptance. This helps prevent recurrence of the issue: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. Acceptance evidence should be: IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged.

Incorrect Answers

B:

Validate area-type consistency before enabling stub policy. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Test protocol instance, VRF and AF together in route acceptance.

C:

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: Test protocol instance, VRF and AF together in route acceptance.

D:

Identify traffic direction for each BGP tuning ticket. That is a sensible control for 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. It is less targeted to this issue than: Test protocol instance, VRF and AF together in route acceptance.

Question 169

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

  1. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.
  2. Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.
  3. Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.
  4. Trace shared-risk link groups and relocate one service path to independent optical facilities where required.

Explanation

Correct Answer

C:

Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost. Verify success by: A lab best-path trace shows the expected externally learned candidate winning when earlier attributes tie.

Incorrect Answers

A:

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

B:

Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: 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.

D:

Trace shared-risk link groups and relocate one service path to independent optical facilities where required. This would respond to a DIFFERENT fictional service-provider network issue: An operator assumes two physically diverse core paths are independent, yet both circuits terminate in the same optical amplifier shelf and fail together during power loss. It does not directly address the current situation: A provider 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.

Question 170

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

  1. Candidate traces identify the final tie-breaker and forwarding remains consistent across repeated resets.
  2. A fixture shows the expected origin-type comparison only after preceding attributes tie.
  3. The lab adjacency reaches Full and the stub router installs the designated default route.
  4. A lab best-path trace shows the expected externally learned candidate winning when earlier attributes tie.

Explanation

Correct Answer

D:

A lab best-path trace shows the expected externally learned candidate winning when earlier attributes tie. This confirms the approved response: Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it. It is relevant because: Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost.

Incorrect Answers

A:

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: Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.

B:

A fixture shows the expected origin-type comparison only after preceding attributes tie. This would validate 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. The specific correction here is: Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.

C:

The lab adjacency reaches Full and the stub router installs the designated default route. This would validate ANOTHER 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 specific correction here is: Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.