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 43

Question 420

A core network change board wants to avoid: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Which ongoing safeguard fits best?

  1. Test AAA failure behavior and accounting completeness at scheduled intervals.
  2. Inventory exposed management listeners after each platform upgrade.
  3. Require postboot image attestation and rollback readiness in change acceptance.
  4. Run secret-scanning checks against network automation and management proxy logs.

Explanation

Correct Answer

D:

Run secret-scanning checks against network automation and management proxy logs. This helps prevent recurrence of the issue: A configuration pipeline invokes router REST APIs with bearer tokens embedded in URL parameters, which are copied into proxy logs. Acceptance evidence should be: A controlled request succeeds with credentials absent from URLs and audit logs.

Incorrect Answers

A:

Test AAA failure behavior and accounting completeness at scheduled intervals. That is a sensible control for ANOTHER scenario: TACACS+ accounting records disappear after a redundant server failover and the team continues privileged changes with no traceable command logs. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.

B:

Inventory exposed management listeners after each platform upgrade. That is a sensible control for ANOTHER scenario: A provider's router management API is reachable from the public internet using a broad admin token, even though the operations team uses a dedicated management VRF. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.

C:

Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It is less targeted to this issue than: Run secret-scanning checks against network automation and management proxy logs.

Question 421

A carrier service activation check discovers: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. Which action best restores the intended behavior?

  1. Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.
  2. Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.
  3. Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design.
  4. Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload.

Explanation

Correct Answer

B:

Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary. This directly addresses the fictional service-provider network case: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. The technical mechanism is: IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic. Verify success by: Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked.

Incorrect Answers

A:

Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. This would respond to a DIFFERENT fictional service-provider network issue: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. It does not directly address the current situation: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link.

C:

Choose strict or feasible-path uRPF as appropriate to the actual subscriber multihoming and reverse-route design. This would respond to a DIFFERENT fictional service-provider network issue: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. It does not directly address the current situation: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link.

D:

Use supported IOS XR process or application recovery procedures and verify expected route-processing behavior without a blanket chassis reload. This would respond to a DIFFERENT fictional service-provider network issue: An engineer assumes a process restart on an IOS XR control-plane node always reloads the entire router, causing an unnecessary maintenance outage. It does not directly address the current situation: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link.

Question 422

Following a supported configuration correction, the original issue was: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. Which observation verifies success?

  1. A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
  2. Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.
  3. Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked.
  4. Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session.

Explanation

Correct Answer

C:

Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked. This confirms the approved response: Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary. It is relevant because: IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.

Incorrect Answers

A:

A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable. This would validate ANOTHER scenario: 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. The specific correction here is: Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.

B:

Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable. This would validate ANOTHER scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. The specific correction here is: Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.

D:

Authorized neighbors exchange the intended FEC labels while an unapproved router cannot create a usable session. This would validate ANOTHER scenario: A provider accepts unbounded remote LDP label mappings from an unexpected neighbor in a shared transport environment. The specific correction here is: Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.

Question 423

At a regional peering-exchange operator, an engineer examines: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. Which technical principle is most applicable?

  1. Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.
  2. Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination.
  3. Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions.
  4. IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.

Explanation

Correct Answer

D:

IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic. This explains the investigated issue: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. The approved corrective response is: Refine IPv6 ACL placement and permitted neighbor discovery types according to the interface trust boundary.

Incorrect Answers

A:

Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths. That explains a DIFFERENT scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. The mechanism to prioritize for this question is: IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.

B:

Remotely Triggered Black Hole routing relies on agreed route policy and communities to steer selected traffic to a null destination. That explains a DIFFERENT scenario: 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. The mechanism to prioritize for this question is: IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.

C:

Cisco IOS software families have different feature and programmability interfaces despite overlapping CLI conventions. That explains a DIFFERENT scenario: A mixed fleet automation job expects an IOS XE NETCONF configuration schema to map identically to all classic IOS software releases. The mechanism to prioritize for this question is: IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.

Question 424

For a regional peering-exchange operator, the change record describes: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. What preventive validation should be standard?

  1. Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.
  2. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
  3. Revalidate source-verification mode after subscriber routing changes.
  4. Require postboot image attestation and rollback readiness in change acceptance.

Explanation

Correct Answer

A:

Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance. This helps prevent recurrence of the issue: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. Acceptance evidence should be: Benign IPv6 reachability and ND continue while the prohibited probe traffic is blocked.

Incorrect Answers

B:

Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks. That is a sensible control for ANOTHER scenario: 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. It is less targeted to this issue than: Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.

C:

Revalidate source-verification mode after subscriber routing changes. That is a sensible control for ANOTHER scenario: A PE applies loose uRPF on a single-homed subscriber port but an upstream source-spoofing event still enters through a route that exists via another edge. It is less targeted to this issue than: Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.

D:

Require postboot image attestation and rollback readiness in change acceptance. That is a sensible control for ANOTHER scenario: After an IOS XE image update, the route processor boots but a router retains an old package set because the team updated the boot variable without verifying install mode. It is less targeted to this issue than: Include positive ICMPv6 neighbor and packet-too-big fixtures in policy acceptance.

Question 425

For an optical transport engineering team, the failure is: 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. Which authorized correction best addresses it?

  1. Correct the interlevel advertisement and summary scope after checking reachability to the component routes.
  2. Introduce the appropriate L1/L2 boundary or L2 route advertisement and review the required reachability design.
  3. Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.
  4. Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.

Explanation

Correct Answer

C:

Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules. Verify success by: Both routers report the intended adjacency level and the local area route becomes reachable.

Incorrect Answers

A:

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

B:

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

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

Question 426

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

  1. A test route follows the intended L1/L2 router and resolves to a valid downstream next hop.
  2. A test prefix from the remote area appears in the intended routing table without unintended leaking of unrelated routes.
  3. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.
  4. Both routers report the intended adjacency level and the local area route becomes reachable.

Explanation

Correct Answer

D:

Both routers report the intended adjacency level and the local area route becomes reachable. This confirms the approved response: Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy. It is relevant because: Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.

Incorrect Answers

A:

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: Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.

B:

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: Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.

C:

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: Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.

Question 427

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

  1. Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.
  2. IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability.
  3. IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.
  4. Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation.

Explanation

Correct Answer

A:

Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules. This explains the investigated issue: 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 approved corrective response is: Reconcile the L1 area addresses or adjust the level participation according to the planned hierarchy.

Incorrect Answers

B:

IS-IS Level 1 routing remains within an area, while Level 2 carries interarea reachability. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.

C:

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: Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.

D:

Dual-Stack Lite transports IPv4 traffic over IPv6 access to a carrier AFTR performing shared IPv4 translation. That explains a DIFFERENT scenario: A customer uses DS-Lite but expects its home CPE to perform normal IPv4 public-NAT termination locally, and the B4 tunnel is never provisioned. The mechanism to prioritize for this question is: Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.

Question 428

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

  1. Test component-prefix ownership before exporting aggregates.
  2. Validate NET configuration and IS-IS levels during provisioning.
  3. Perform IPv6 topology capability verification for every new core node.
  4. Include N-1 link capacity tests in planned-maintenance readiness checks.

Explanation

Correct Answer

B:

Validate NET configuration and IS-IS levels during provisioning. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Both routers report the intended adjacency level and the local area route becomes reachable.

Incorrect Answers

A:

Test component-prefix ownership before exporting aggregates. That is a sensible control for 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. It is less targeted to this issue than: Validate NET configuration and IS-IS levels during provisioning.

C:

Perform IPv6 topology capability verification for every new core node. That is a sensible control for 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. It is less targeted to this issue than: Validate NET configuration and IS-IS levels during provisioning.

D:

Include N-1 link capacity tests in planned-maintenance readiness checks. That is a sensible control for 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. It is less targeted to this issue than: Validate NET configuration and IS-IS levels during provisioning.

Question 429

A provider backbone escalation identifies: 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. What should the network team implement?

  1. Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context.
  2. Enable the intended OSPFv3 address-family participation in the correct routing context.
  3. Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies.
  4. Align stub-area configuration on the ABR and member routers and verify default advertisement.

Explanation

Correct Answer

D:

Align stub-area configuration on the ABR and member routers and verify default advertisement. This directly addresses the fictional service-provider network case: 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 technical mechanism is: OSPF area-type agreement is required for adjacency and stub routing behavior. Verify success by: The lab adjacency reaches Full and the stub router installs the designated default route.

Incorrect Answers

A:

Separate OSPFv3 neighbor link-local scope from globally routed management addresses and preserve interface context. This would respond to a DIFFERENT fictional service-provider network issue: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. It does not directly address the current situation: 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.

B:

Enable the intended OSPFv3 address-family participation in the correct routing context. This would respond to a DIFFERENT fictional service-provider network issue: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. It does not directly address the current situation: 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.

C:

Model failure-state link utilization and apply appropriate premaintenance traffic-engineering or admission policies. This would respond to a DIFFERENT fictional service-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. It does not directly address the current situation: 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.

Question 430

A service-provider operations test targets: 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. Which result is required?

  1. The lab adjacency reaches Full and the stub router installs the designated default route.
  2. Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address.
  3. Valid component destinations work and an unassigned prefix does not loop indefinitely.
  4. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.

Explanation

Correct Answer

A:

The lab adjacency reaches Full and the stub router installs the designated default route. This confirms the approved response: Align stub-area configuration on the ABR and member routers and verify default advertisement. It is relevant because: OSPF area-type agreement is required for adjacency and stub routing behavior.

Incorrect Answers

B:

Peering remains healthy and management attempts use a routable endpoint instead of a bare link-local address. This would validate ANOTHER scenario: An OSPFv3 deployment uses a link-local neighbor address and the monitoring system mistakenly treats it as globally reachable offlink for management. The specific correction here is: Align stub-area configuration on the ABR and member routers and verify default advertisement.

C:

Valid component destinations work and an unassigned prefix does not loop indefinitely. This would validate ANOTHER scenario: An ABR summarizes branch routes into one large prefix that points into an area missing part of the address space, leading to a forwarding loop for unallocated addresses. The specific correction here is: Align stub-area configuration on the ABR and member routers and verify default advertisement.

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: Align stub-area configuration on the ABR and member routers and verify default advertisement.