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 52

Question 510

A service-provider operations test targets: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. Which result is required?

  1. Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered.
  2. A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes.
  3. Customer route queries show approved aggregate service routes but no internal infrastructure prefixes.
  4. A lab tuple resolves to the correct subscriber session without conflating two simultaneous clients.

Explanation

Correct Answer

A:

Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered. This confirms the approved response: Review policy order and community membership before changing network reachability or resetting all sessions. It is relevant because: BGP route policy can accept or reject NLRI independently of session health.

Incorrect Answers

B:

A packet or RIB inspection confirms unique path identifiers and the approved number of alternative routes. This would validate ANOTHER scenario: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. The specific correction here is: Review policy order and community membership before changing network reachability or resetting all sessions.

C:

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: Review policy order and community membership before changing network reachability or resetting all sessions.

D:

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: Review policy order and community membership before changing network reachability or resetting all sessions.

Question 511

A provider troubleshooting note states: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. Which mechanism is central?

  1. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.
  2. BGP route policy can accept or reject NLRI independently of session health.
  3. MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices.
  4. Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost.

Explanation

Correct Answer

B:

BGP route policy can accept or reject NLRI independently of session health. This explains the investigated issue: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. The approved corrective response is: Review policy order and community membership before changing network reachability or resetting all sessions.

Incorrect Answers

A:

BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer. That explains a DIFFERENT scenario: Two route reflectors advertise paths from the same client without Add-Path negotiation, and access PEs see one path even though each reflector knows multiple candidates. The mechanism to prioritize for this question is: BGP route policy can accept or reject NLRI independently of session health.

C:

MED is a hint for inbound exit selection and is not a global guarantee of all upstream route choices. That explains a DIFFERENT scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. The mechanism to prioritize for this question is: BGP route policy can accept or reject NLRI independently of session health.

D:

Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: BGP route policy can accept or reject NLRI independently of session health.

Question 512

To prevent recurrence of this provider network issue: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. Which control should be retained?

  1. Record upstream acceptance of traffic-engineering communities and MED policy.
  2. Verify v4 and v6 filter family independently during peering certification.
  3. Contract-test BGP import/export with representative community fixtures.
  4. Include protocol-specific reachability and adjacency checks after ACL changes.

Explanation

Correct Answer

C:

Contract-test BGP import/export with representative community fixtures. This helps prevent recurrence of the issue: A core route reflector exports only a subset of service prefixes after a route-policy edit because the import policy unintentionally rejects an entire community group. Acceptance evidence should be: Route-policy trace shows only approved prefixes accepted while unrelated customer families stay filtered.

Incorrect Answers

A:

Record upstream acceptance of traffic-engineering communities and MED policy. That is a sensible control for ANOTHER scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. It is less targeted to this issue than: Contract-test BGP import/export with representative community fixtures.

B:

Verify v4 and v6 filter family independently during peering certification. That is a sensible control for ANOTHER 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. It is less targeted to this issue than: Contract-test BGP import/export with representative community fixtures.

D:

Include protocol-specific reachability and adjacency checks after ACL changes. That is a sensible control for ANOTHER scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. It is less targeted to this issue than: Contract-test BGP import/export with representative community fixtures.

Question 513

At a multi-region fiber backbone operator, an engineering review finds: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. Which change most directly corrects the service problem?

  1. Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective.
  2. Inspect sequence order and matching conditions and construct an explicit allowlist for intended routes.
  3. Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics.
  4. Restrict the interarea summary to reachable components and ensure correct discard behavior for aggregate holes.

Explanation

Correct Answer

A:

Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective. This directly addresses the fictional service-provider network case: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. The technical mechanism is: MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection. Verify success by: Core BGP tables show the designated site as preferred while both border sessions remain healthy.

Incorrect Answers

B:

Inspect sequence order and matching conditions and construct an explicit allowlist for intended routes. This would respond to a DIFFERENT fictional service-provider network issue: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. It does not directly address the current situation: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged.

C:

Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics. This would respond to a DIFFERENT fictional service-provider network issue: An IOS XR route policy applies `pass` before a prefix filter and an engineer expects later reject logic to stop evaluation automatically. It does not directly address the current situation: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged.

D:

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 ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged.

Question 514

For a multi-region fiber backbone operator, operators addressed: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. What is the strongest acceptance evidence?

  1. Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.
  2. Core BGP tables show the designated site as preferred while both border sessions remain healthy.
  3. The upstream sandbox peer receives the intended community and applies only the agreed action.
  4. A test prefix is visible across the area boundary before the dependent BGP route recovers.

Explanation

Correct Answer

B:

Core BGP tables show the designated site as preferred while both border sessions remain healthy. This confirms the approved response: Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective. It is relevant because: MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.

Incorrect Answers

A:

Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix. This would validate ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. The specific correction here is: Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective.

C:

The upstream sandbox peer receives the intended community and applies only the agreed action. This would validate ANOTHER scenario: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. The specific correction here is: Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective.

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: Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective.

Question 515

Which network protocol or forwarding behavior explains the following issue: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged.

  1. Route maps evaluate ordered policy clauses, and broad later matches must be carefully scoped.
  2. BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.
  3. MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.
  4. IS-IS route leaking and summarization affect interlevel reachability, and an incorrect aggregate can conceal missing specifics.

Explanation

Correct Answer

C:

MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection. This explains the investigated issue: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. The approved corrective response is: Apply the appropriate inbound local-preference policy within the AS for its own traffic-engineering objective.

Incorrect Answers

A:

Route maps evaluate ordered policy clauses, and broad later matches must be carefully scoped. That explains a DIFFERENT scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. The mechanism to prioritize for this question is: MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.

B:

BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. That explains a DIFFERENT scenario: A provider uses BGP community 65000:123 as a traffic-engineering signal but one edge strips communities on eBGP export, so the upstream never applies the requested policy. The mechanism to prioritize for this question is: MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.

D:

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: MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.

Question 516

A core network change board wants to avoid: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. Which ongoing safeguard fits best?

  1. Require boundary-prefix tests whenever prefix sets are edited.
  2. Include tagged and untagged candidate routes in route-map test suites.
  3. Avoid using accidental router IDs as a business traffic-engineering policy.
  4. Label policy changes by inbound versus outbound traffic direction.

Explanation

Correct Answer

D:

Label policy changes by inbound versus outbound traffic direction. This helps prevent recurrence of the issue: An ISP announces the same customer prefix from two sites but a locally configured outbound route map modifies MED instead of local preference, so egress remains unchanged. Acceptance evidence should be: Core BGP tables show the designated site as preferred while both border sessions remain healthy.

Incorrect Answers

A:

Require boundary-prefix tests whenever prefix sets are edited. That is a sensible control for ANOTHER scenario: A route-policy template attempts to match a more-specific /25 by using an exact /24 prefix without a length range, mistakenly accepting only the aggregate. It is less targeted to this issue than: Label policy changes by inbound versus outbound traffic direction.

B:

Include tagged and untagged candidate routes in route-map test suites. That is a sensible control for ANOTHER scenario: A route map denies a tagged customer route but includes a later permit clause matching all prefixes, and operations misinterprets the first match behavior. It is less targeted to this issue than: Label policy changes by inbound versus outbound traffic direction.

C:

Avoid using accidental router IDs as a business traffic-engineering policy. That is a sensible control for 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. It is less targeted to this issue than: Label policy changes by inbound versus outbound traffic direction.

Question 517

A carrier service activation check discovers: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. Which action best restores the intended behavior?

  1. Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability.
  2. Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.
  3. Align supported BFD session parameters and measure them against the actual transport latency and loss envelope.
  4. Inspect origin and other ordered attributes using the platform's best-path detail before rewriting policy.

Explanation

Correct Answer

B:

Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment. This directly addresses the fictional service-provider network case: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The technical mechanism is: A physical adjacency can exist without all configured address families exchanging usable reachability. Verify success by: The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.

Incorrect Answers

A:

Trace the OSPF LSDB and ABR summary policy to restore the missing interarea reachability. This would respond to a DIFFERENT fictional service-provider network issue: An OSPF route vanishes from one area after an ABR summary change, yet the operator repeatedly resets BGP neighbors to fix the symptom. It does not directly address the current situation: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment.

C:

Align supported BFD session parameters and measure them against the actual transport latency and loss envelope. This would respond to a DIFFERENT fictional service-provider network issue: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It does not directly address the current situation: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment.

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 IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment.

Question 518

Following a supported configuration correction, the original issue was: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. Which observation verifies success?

  1. A lab adjacency reaches Full and the LSDB counts converge without permitting unrelated sources.
  2. A limited allowed route set is advertised and the threshold alerts only on unexpected growth.
  3. The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.
  4. A lab route count shows approved IPv6 NLRI exchanged without unintended IPv4 injection.

Explanation

Correct Answer

C:

The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged. This confirms the approved response: Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment. It is relevant because: A physical adjacency can exist without all configured address families exchanging usable reachability.

Incorrect Answers

A:

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: Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.

B:

A limited allowed route set is advertised and the threshold alerts only on unexpected growth. This would validate ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. The specific correction here is: Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.

D:

A lab route count shows approved IPv6 NLRI exchanged without unintended IPv4 injection. This would validate ANOTHER scenario: A carrier activates an IPv6-only peering exchange but leaves only IPv4 unicast activated, so the BGP session is Established yet receives no IPv6 prefixes. The specific correction here is: Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.

Question 519

At a metro Ethernet service provider, an engineer examines: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. Which technical principle is most applicable?

  1. Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds.
  2. Maximum-prefix limits guard route scale and can stop or restrict expected advertisements when set too low.
  3. NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior.
  4. A physical adjacency can exist without all configured address families exchanging usable reachability.

Explanation

Correct Answer

D:

A physical adjacency can exist without all configured address families exchanging usable reachability. This explains the investigated issue: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. The approved corrective response is: Examine IPv6-specific LSP reachability and restore the required IS-IS topology support for that segment.

Incorrect Answers

A:

Filtering routing-protocol IP traffic can prevent adjacency even when ordinary ICMP reachability succeeds. That explains a DIFFERENT scenario: Two OSPFv2 neighbors exchange hellos but a recently inserted ACL blocks protocol 89, preventing database synchronization on the transit segment. The mechanism to prioritize for this question is: A physical adjacency can exist without all configured address families exchanging usable reachability.

B:

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: A physical adjacency can exist without all configured address families exchanging usable reachability.

C:

NSR synchronizes control-plane protocol state to standby processors to minimize adjacency disruptions independently of neighbor GR behavior. That explains a DIFFERENT scenario: An IOS XR chassis uses NSR for one IGP but a critical BGP peer lacks state synchronization to the standby process, losing adjacency on failover. The mechanism to prioritize for this question is: A physical adjacency can exist without all configured address families exchanging usable reachability.

Question 520

For a metro Ethernet service provider, the change record describes: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. What preventive validation should be standard?

  1. Verify IPv4/IPv6 route consistency after partial protocol changes.
  2. Trend prefix counts and alert before capacity thresholds are reached.
  3. Tune BFD to observed transport behavior and test at peak utilization.
  4. Review candidate redistribution tables under a default-deny policy.

Explanation

Correct Answer

A:

Verify IPv4/IPv6 route consistency after partial protocol changes. This helps prevent recurrence of the issue: An IS-IS neighbor is Up but the remote IPv6 prefix is missing because the address-family topology was disabled on one transit segment. Acceptance evidence should be: The IPv6 route appears with a valid next hop while all existing IPv4 paths are unchanged.

Incorrect Answers

B:

Trend prefix counts and alert before capacity thresholds are reached. That is a sensible control for ANOTHER scenario: An eBGP exchange reports Established but a contracted prefix is missing because the advertiser rejects it under a maximum-prefix protection threshold. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.

C:

Tune BFD to observed transport behavior and test at peak utilization. That is a sensible control for ANOTHER scenario: A router's OSPF adjacency flaps after an optical circuit fails over because differing BFD timer expectations cause repeated session-down detection. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.

D:

Review candidate redistribution tables under a default-deny policy. That is a sensible control for ANOTHER scenario: An edge router injects all OSPF internals into BGP without tagging or policy, exposing infrastructure loopbacks to a customer upstream. It is less targeted to this issue than: Verify IPv4/IPv6 route consistency after partial protocol changes.