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 30

Question 290

For a multi-region fiber backbone operator, operators addressed: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. What is the strongest acceptance evidence?

  1. A lab target route resolves to the discard path while a neighboring nonvictim prefix remains reachable.
  2. An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic.
  3. Spoofed test source packets are rejected while legitimate multihomed customer traffic remains reachable.
  4. The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected.

Explanation

Correct Answer

B:

An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic. This confirms the approved response: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints. It is relevant because: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.

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: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

C:

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: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

D:

The legitimate adjacent session remains established while a distant test source with unsuitable TTL is rejected. This would validate ANOTHER scenario: A BGP session from an adjacent PE can be spoofed by packets arriving many router hops away because the provider leaves TTL-security disabled. The specific correction here is: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

Question 291

Which network protocol or forwarding behavior explains the following issue: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors.

  1. IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic.
  2. Loose uRPF tests reverse route existence, whereas strict checks incoming interface alignment, which matters for asymmetric paths.
  3. MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.
  4. Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation.

Explanation

Correct Answer

C:

MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption. This explains the investigated issue: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. The approved corrective response is: Align supported MACsec connectivity association, keying, cipher settings and operational policy at both link endpoints.

Incorrect Answers

A:

IPv6 neighbor discovery is required for link-layer resolution and must not be handled like optional generic ICMP traffic. That explains a DIFFERENT scenario: A provider limits subscriber attacks using an ingress ACL but accidentally filters essential ICMPv6 neighbor discovery on the same link. The mechanism to prioritize for this question is: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.

B:

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: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.

D:

Virtual packet processing can be constrained by scheduling, locality and data-plane I/O well before overall host averages show saturation. That explains a DIFFERENT scenario: An NFV cluster oversubscribes CPU cores for a carrier-grade packet gateway, leading to jitter despite abundant average utilization headroom. The mechanism to prioritize for this question is: MACsec protects Ethernet links through mutually compatible link-layer security associations rather than unilateral encryption.

Question 292

A core network change board wants to avoid: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. Which ongoing safeguard fits best?

  1. Exercise RTBH announcements with disposable prefixes and post-event withdrawal checks.
  2. Revalidate source-verification mode after subscriber routing changes.
  3. Audit hosted-app resource utilization and release compatibility on upgrades.
  4. Verify MACsec secure-channel state after optics and link-aggregation changes.

Explanation

Correct Answer

D:

Verify MACsec secure-channel state after optics and link-aggregation changes. This helps prevent recurrence of the issue: MACsec was enabled on only one end of a provider cross-connect, leaving the routed adjacency down with integrity errors. Acceptance evidence should be: An authorized lab peer establishes an encrypted link and passes the intended L3 adjacency and data traffic.

Incorrect Answers

A:

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: Verify MACsec secure-channel state after optics and link-aggregation changes.

B:

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: Verify MACsec secure-channel state after optics and link-aggregation changes.

C:

Audit hosted-app resource utilization and release compatibility on upgrades. That is a sensible control for ANOTHER scenario: An operations team deploys an application container directly onto a router control processor without checking vendor-supported hosting resources or isolation limits. It is less targeted to this issue than: Verify MACsec secure-channel state after optics and link-aggregation changes.

Question 293

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

  1. Correct the interlevel advertisement and summary scope after checking reachability to the component routes.
  2. Set the intended IS-IS wide metric on the optical link based on approved transport cost.
  3. Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence.
  4. Align stub-area configuration on the ABR and member routers and verify default advertisement.

Explanation

Correct Answer

B:

Set the intended IS-IS wide metric on the optical link based on approved transport cost. This directly addresses the fictional service-provider network case: 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 technical mechanism is: IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default. Verify success by: Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.

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

C:

Hold the overload condition until the router is ready to carry transit traffic and validate adjacency and route-table convergence. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables IS-IS overload on a recovering core node then removes the flag before the full route database is synchronized, leading to transient transit blackholes. It does not directly address the current situation: 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.

D:

Align stub-area configuration on the ABR and member routers and verify default advertisement. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

Question 294

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

  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. Parallel test sessions resolve to unique external tuples and return to the correct subscriber.

Explanation

Correct Answer

C:

Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies. This confirms the approved response: Set the intended IS-IS wide metric on the optical link based on approved transport cost. It is relevant because: IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

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: Set the intended IS-IS wide metric on the optical link based on approved transport cost.

B:

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: Set the intended IS-IS wide metric on the optical link based on approved transport cost.

D:

Parallel test sessions resolve to unique external tuples and return to the correct subscriber. This would validate ANOTHER 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 specific correction here is: Set the intended IS-IS wide metric on the optical link based on approved transport cost.

Question 295

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

  1. Level 1 IS-IS adjacency depends on compatible area membership, while L2 has broader adjacency rules.
  2. Neighbors must share a usable IS-IS level and compatible link parameters to exchange routing information.
  3. OSPF broadcast networks use DR/BDR adjacency optimization rather than full mesh formation.
  4. IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

Explanation

Correct Answer

D:

IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default. This explains the investigated issue: 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 approved corrective response is: Set the intended IS-IS wide metric on the optical link based on approved transport cost.

Incorrect Answers

A:

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 SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

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: IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

C:

OSPF broadcast networks use DR/BDR adjacency optimization rather than full mesh formation. That explains a DIFFERENT 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 mechanism to prioritize for this question is: IS-IS SPF chooses paths according to advertised link metrics rather than measured circuit latency by default.

Question 296

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

  1. Review IGP link metrics against current network capacity and service objectives.
  2. Validate NET configuration and IS-IS levels during provisioning.
  3. Maintain dual-stack adjacency and LSDB checks after MT feature changes.
  4. Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance.

Explanation

Correct Answer

A:

Review IGP link metrics against current network capacity and service objectives. This helps prevent recurrence of the issue: 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. Acceptance evidence should be: Route calculation shifts the test prefix to the expected lower-cost path without interrupting control adjacencies.

Incorrect Answers

B:

Validate NET configuration and IS-IS levels during provisioning. That is a sensible control for ANOTHER scenario: A core interface comes up but its IS-IS hellos never result in adjacency because peer system IDs use incompatible area addressing on L1-only neighbors. It is less targeted to this issue than: Review IGP link metrics against current network capacity and service objectives.

C:

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: Review IGP link metrics against current network capacity and service objectives.

D:

Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance. That is a sensible control for ANOTHER scenario: An IPv6-only access service installs NAT64 but does not provide a method to obtain suitable IPv6 destinations for IPv4-only DNS names, so subscribers fail by hostname. It is less targeted to this issue than: Review IGP link metrics against current network capacity and service objectives.

Question 297

For a global tier-one IP transit carrier, the failure is: 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. Which authorized correction best addresses it?

  1. Align stub-area configuration on the ABR and member routers and verify default advertisement.
  2. Enable the intended OSPFv3 address-family participation in the correct routing context.
  3. Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.
  4. Redistribute only explicitly authorized service prefixes through prefix lists and route policy.

Explanation

Correct Answer

C:

Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes. This directly addresses the fictional service-provider network case: 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 technical mechanism is: Improper OSPF area summarization can advertise reachability where no specific destination exists. Verify success by: Valid component destinations work and an unassigned prefix does not loop indefinitely.

Incorrect Answers

A:

Align stub-area configuration on the ABR and member routers and verify default advertisement. This would respond to a DIFFERENT fictional service-provider network issue: 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 does not directly address the current situation: 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.

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

D:

Redistribute only explicitly authorized service prefixes through prefix lists and route policy. This would respond to a DIFFERENT fictional service-provider network issue: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It does not directly address the current situation: 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.

Question 298

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

  1. IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged.
  2. The DR has Full adjacencies and LSDB convergence while DROTHER peers show their expected state.
  3. Both links join one stable operational bundle and sampled customer flows traverse valid active members.
  4. Valid component destinations work and an unassigned prefix does not loop indefinitely.

Explanation

Correct Answer

D:

Valid component destinations work and an unassigned prefix does not loop indefinitely. This confirms the approved response: Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes. It is relevant because: Improper OSPF area summarization can advertise reachability where no specific destination exists.

Incorrect Answers

A:

IPv6 prefixes appear in the target VRF while unrelated global tables remain unchanged. This would validate ANOTHER scenario: An OSPFv3 adjacency is up but IPv6 routes are absent because the required address-family instance is missing from the receiving VRF. The specific correction here is: Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.

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: Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.

C:

Both links join one stable operational bundle and sampled customer flows traverse valid active members. This would validate 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. The specific correction here is: Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.

Question 299

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

  1. Improper OSPF area summarization can advertise reachability where no specific destination exists.
  2. OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces.
  3. OSPF area-type agreement is required for adjacency and stub routing behavior.
  4. MP-BGP address families have separate route policies and prefix syntax even when sessions share a neighbor.

Explanation

Correct Answer

A:

Improper OSPF area summarization can advertise reachability where no specific destination exists. This explains the investigated 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. The approved corrective response is: Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.

Incorrect Answers

B:

OSPF auto-cost derives from a configurable reference bandwidth and can underdifferentiate fast interfaces. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: Improper OSPF area summarization can advertise reachability where no specific destination exists.

C:

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: Improper OSPF area summarization can advertise reachability where no specific destination exists.

D:

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: Improper OSPF area summarization can advertise reachability where no specific destination exists.

Question 300

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

  1. Include reference bandwidth standards in routing config review.
  2. Revalidate summaries against the address plan after branch network changes.
  3. Verify lower-layer IGP readiness before diagnosing dependent BGP sessions.
  4. Identify traffic direction for each BGP tuning ticket.

Explanation

Correct Answer

B:

Revalidate summaries against the address plan after branch network changes. This helps prevent recurrence of the 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. Acceptance evidence should be: Valid component destinations work and an unassigned prefix does not loop indefinitely.

Incorrect Answers

A:

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: Revalidate summaries against the address plan after branch network changes.

C:

Verify lower-layer IGP readiness before diagnosing dependent BGP sessions. That is a sensible control for ANOTHER scenario: Two OSPF routers connected through an L2VPN are configured with incompatible hello/dead timers and a monitoring dashboard calls the missing adjacency a BGP failure. It is less targeted to this issue than: Revalidate summaries against the address plan after branch network changes.

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: Revalidate summaries against the address plan after branch network changes.