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 31

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.

Question 301

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

  1. Review the eBGP-versus-iBGP preference step and adjust routing policy only if the intended traffic engineering requires it.
  2. Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules.
  3. Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported.
  4. Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

Explanation

Correct Answer

D:

Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection. This directly addresses the fictional service-provider network case: 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. The technical mechanism is: Local preference is an AS-wide policy attribute typically considered before AS_PATH length. Verify success by: A test route exits through the desired high-local-preference border where both paths are otherwise eligible.

Incorrect Answers

A:

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

B:

Inspect ordered BGP best-path attributes and compare AS_PATH length after local preference and other preceding decision rules. This would respond to a DIFFERENT fictional service-provider network issue: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. It does not directly address the current situation: 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.

C:

Validate PIC support, alternate paths and recursion so the forwarding plane can preinstall backup resolution where supported. This would respond to a DIFFERENT fictional service-provider network issue: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. It does not directly address the current situation: 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.

Question 302

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

  1. A test route exits through the desired high-local-preference border where both paths are otherwise eligible.
  2. Adjacent peer route views show additional paths only when both sides support and negotiate the feature.
  3. A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal.
  4. The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release.

Explanation

Correct Answer

A:

A test route exits through the desired high-local-preference border where both paths are otherwise eligible. This confirms the approved response: Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection. It is relevant because: Local preference is an AS-wide policy attribute typically considered before AS_PATH length.

Incorrect Answers

B:

Adjacent peer route views show additional paths only when both sides support and negotiate the feature. This would validate ANOTHER scenario: A route reflector learns several equivalent multipath candidates but advertises only its best path and a customer confuses multipath forwarding with multiple advertised path dissemination. The specific correction here is: Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

C:

A controlled pair of paths selects the expected shorter AS path when higher-priority attributes are equal. This would validate ANOTHER scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. The specific correction here is: Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

D:

The laboratory upgrade keeps the intended traffic classes forwarding while both supervisors reach the approved release. This would validate ANOTHER scenario: A dual-supervisor router reports standby Hot but an engineer schedules an in-service upgrade without checking platform release interoperability and ISSU prerequisites. The specific correction here is: Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

Question 303

A provider troubleshooting note states: 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. Which mechanism is central?

  1. Common BGP best-path algorithms prefer eBGP over iBGP before later tie-breakers such as internal next-hop cost.
  2. Local preference is an AS-wide policy attribute typically considered before AS_PATH length.
  3. Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length.
  4. MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection.

Explanation

Correct Answer

B:

Local preference is an AS-wide policy attribute typically considered before AS_PATH length. This explains the investigated 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. The approved corrective response is: Set and verify the intended local-preference policy and document that it outranks AS_PATH length in local best-path selection.

Incorrect Answers

A:

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: Local preference is an AS-wide policy attribute typically considered before AS_PATH length.

C:

Origin type can influence BGP selection after higher-priority criteria such as weight, local preference and path length. That explains a DIFFERENT 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 mechanism to prioritize for this question is: Local preference is an AS-wide policy attribute typically considered before AS_PATH length.

D:

MED usually influences a neighboring AS's choice, whereas local preference influences internal best-path selection. That explains a DIFFERENT scenario: 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 mechanism to prioritize for this question is: Local preference is an AS-wide policy attribute typically considered before AS_PATH length.

Question 304

To prevent recurrence of this 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. Which control should be retained?

  1. Avoid using accidental router IDs as a business traffic-engineering policy.
  2. Keep best-path attribute snapshots alongside policy change tickets.
  3. Compare inbound customer import policy with intended exit preferences.
  4. Verify community presence in route advertisements at the external boundary.

Explanation

Correct Answer

C:

Compare inbound customer import policy with intended exit preferences. This helps prevent recurrence of the 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. Acceptance evidence should be: A test route exits through the desired high-local-preference border where both paths are otherwise eligible.

Incorrect Answers

A:

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: Compare inbound customer import policy with intended exit preferences.

B:

Keep best-path attribute snapshots alongside policy change tickets. That is a sensible control for ANOTHER scenario: Two eBGP routes reach the same prefix with equal local preference, but operations assumes a shorter AS_PATH cannot affect selection and blames a metric change. It is less targeted to this issue than: Compare inbound customer import policy with intended exit preferences.

D:

Verify community presence in route advertisements at the external boundary. That is a sensible control for 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. It is less targeted to this issue than: Compare inbound customer import policy with intended exit preferences.

Question 305

At a managed VPN service carrier, an engineering review finds: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. Which change most directly corrects the service problem?

  1. Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.
  2. Redistribute only explicitly authorized service prefixes through prefix lists and route policy.
  3. Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required.
  4. Align stub-area configuration on the ABR and member routers and verify default advertisement.

Explanation

Correct Answer

A:

Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border. This directly addresses the fictional service-provider network case: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The technical mechanism is: BGP NLRI can be learned without being installed if the next-hop attribute is unreachable. Verify success by: The prefix becomes usable with a resolved next hop while the IGP remains stable.

Incorrect Answers

B:

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 iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive.

C:

Enable supported Additional Paths negotiation and policy only on links where multipath distribution is intentionally required. This would respond to a DIFFERENT fictional service-provider network issue: 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. It does not directly address the current situation: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive.

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 iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive.

Question 306

For a managed VPN service carrier, operators addressed: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. What is the strongest acceptance evidence?

  1. A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target.
  2. The prefix becomes usable with a resolved next hop while the IGP remains stable.
  3. A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS.
  4. The DR has Full adjacencies and LSDB convergence while DROTHER peers show their expected state.

Explanation

Correct Answer

B:

The prefix becomes usable with a resolved next hop while the IGP remains stable. This confirms the approved response: Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border. It is relevant because: BGP NLRI can be learned without being installed if the next-hop attribute is unreachable.

Incorrect Answers

A:

A link-loss test switches eligible prefixes onto the backup next hop within the documented recovery target. This would validate ANOTHER scenario: A provider enables BGP PIC in its core but expects instant convergence even though recursive alternate next hops were not installed for the affected VPN prefixes. The specific correction here is: Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.

C:

A test peer honors the agreed MED when comparing eligible paths from the same neighboring AS. This would validate ANOTHER scenario: A provider changes MED inbound on one customer edge and expects all distant autonomous systems to prefer that link for inbound traffic. The specific correction here is: Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.

D:

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: Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.

Question 307

Which network protocol or forwarding behavior explains the following issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive.

  1. BGP Add-Path requires capability agreement and path identifiers to advertise more than one route per NLRI to a peer.
  2. AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection.
  3. BGP NLRI can be learned without being installed if the next-hop attribute is unreachable.
  4. BGP path usability depends on resolution through the underlying routing table.

Explanation

Correct Answer

C:

BGP NLRI can be learned without being installed if the next-hop attribute is unreachable. This explains the investigated issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. The approved corrective response is: Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.

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 NLRI can be learned without being installed if the next-hop attribute is unreachable.

B:

AS-path prepending primarily affects external systems' route preference and not necessarily an AS's own egress selection. That explains a DIFFERENT 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. The mechanism to prioritize for this question is: BGP NLRI can be learned without being installed if the next-hop attribute is unreachable.

D:

BGP path usability depends on resolution through the underlying routing table. That explains a DIFFERENT scenario: BGP routes are received but a recursive next hop points to a withdrawn loopback, causing the FIB not to install otherwise valid customer NLRI. The mechanism to prioritize for this question is: BGP NLRI can be learned without being installed if the next-hop attribute is unreachable.

Question 308

A core network change board wants to avoid: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. Which ongoing safeguard fits best?

  1. Use a peer inventory to preflight local and remote AS values.
  2. Track Add-Path capabilities and route scale in peering acceptance tests.
  3. Include DNS synthesis and DNSSEC compatibility cases in NAT64 acceptance.
  4. Validate next-hop recursion for every new iBGP export policy.

Explanation

Correct Answer

D:

Validate next-hop recursion for every new iBGP export policy. This helps prevent recurrence of the issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. Acceptance evidence should be: The prefix becomes usable with a resolved next hop while the IGP remains stable.

Incorrect Answers

A:

Use a peer inventory to preflight local and remote AS values. That is a sensible control for ANOTHER scenario: A new eBGP handoff establishes TCP transport but remains Idle/Active because the peer configuration uses the wrong autonomous-system number. It is less targeted to this issue than: Validate next-hop recursion for every new iBGP export policy.

B:

Track Add-Path capabilities and route scale in peering acceptance tests. That is a sensible control for 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. It is less targeted to this issue than: Validate next-hop recursion for every new iBGP export policy.

C:

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: Validate next-hop recursion for every new iBGP export policy.

Question 309

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

  1. Rewrite the route-policy decisions with explicit conditional drops or controlled acceptance according to IOS XR RPL semantics.
  2. Preserve and transmit the negotiated community using the supported neighbor settings and route policy.
  3. Inspect sequence order and matching conditions and construct an explicit allowlist for intended routes.
  4. Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border.

Explanation

Correct Answer

B:

Preserve and transmit the negotiated community using the supported neighbor settings and route policy. This directly addresses the fictional service-provider network case: 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 technical mechanism is: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them. Verify success by: The upstream sandbox peer receives the intended community and applies only the agreed action.

Incorrect Answers

A:

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

C:

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

D:

Establish proper next-hop reachability via the IGP or an approved next-hop-self policy at the correct border. This would respond to a DIFFERENT fictional service-provider network issue: An iBGP core advertises a prefix with a next hop that access routers cannot resolve, causing BGP routes to be present but inactive. It does not directly address the current situation: 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.

Question 310

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

  1. Tests accept the specified /25 and deny an unrelated /25 outside the controlled prefix.
  2. Test prefixes show the tagged route rejected and only approved routes advertised.
  3. The upstream sandbox peer receives the intended community and applies only the agreed action.
  4. IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable.

Explanation

Correct Answer

C:

The upstream sandbox peer receives the intended community and applies only the agreed action. This confirms the approved response: Preserve and transmit the negotiated community using the supported neighbor settings and route policy. It is relevant because: BGP communities are optional policy metadata and must be explicitly propagated when the design depends on them.

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: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

B:

Test prefixes show the tagged route rejected and only approved routes advertised. This would validate 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. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.

D:

IPv6 topology and route output show the expected prefix end-to-end while IPv4 remains stable. This would validate ANOTHER scenario: An IPv6 service prefix disappears after enabling IS-IS multitopology, and operations only checks the IPv4 SPF database. The specific correction here is: Preserve and transmit the negotiated community using the supported neighbor settings and route policy.