McAfee Secure

Cisco 350-501 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 Training 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

    Training Course

    253 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    1160 PDF Pages

    $24.99

Cisco 350-501 Practice Test 16

Question 150

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. Which observable result most directly verifies that this network issue was resolved?

  1. The IPv6 database shows advertised reachability and end-to-end IPv6 next hops resolve on the intended links.
  2. The expected router is elected DR under a controlled restart scenario.
  3. Service reachability failure triggers the intended route withdrawal instead of persistent blackholing.
  4. The peer receives public approved customer aggregates and no private addressing.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. The most directly supported response is: Set documented OSPF priorities and stable router IDs for designated-router candidates. Technical basis: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. Evidence of success: The expected router is elected DR under a controlled restart scenario. Ongoing protection: Keep DR selection in the network design and test after topology changes.

Incorrect Answers

A:

The proposed test would be relevant to: IS-IS can advertise separate IPv6 reachability information independently of its IPv4 control-plane transport. The reported problem follows from: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. Instead, verify: The expected router is elected DR under a controlled restart scenario.

C:

That observation tests a different mechanism: High availability requires validating application-relevant reachability rather than only local link carrier state. It cannot establish this case, whose mechanism is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. The needed verification is: The expected router is elected DR under a controlled restart scenario.

D:

That observation tests a different mechanism: BGP export policy is the boundary controlling which NLRI leaves an autonomous system. It cannot establish this case, whose mechanism is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. The needed verification is: The expected router is elected DR under a controlled restart scenario.

Question 151

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. Which underlying network infrastructure principle best explains the situation?

  1. BGP PIC precomputes viable alternate paths to reduce route-by-route failover delay.
  2. IS-IS can advertise separate IPv6 reachability information independently of its IPv4 control-plane transport.
  3. BGP evaluates ordered criteria, so later comparisons apply only when earlier attributes are tied.
  4. OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. The most directly supported response is: Set documented OSPF priorities and stable router IDs for designated-router candidates. Technical basis: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. Evidence of success: The expected router is elected DR under a controlled restart scenario. Ongoing protection: Keep DR selection in the network design and test after topology changes.

Incorrect Answers

A:

The alternative principle describes: BGP PIC precomputes viable alternate paths to reduce route-by-route failover delay. In this question, the decisive mechanism is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. These are distinct technical causes, even when they share a platform.

B:

The alternative principle describes: IS-IS can advertise separate IPv6 reachability information independently of its IPv4 control-plane transport. In this question, the decisive mechanism is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. These are distinct technical causes, even when they share a platform.

C:

The alternative principle describes: BGP evaluates ordered criteria, so later comparisons apply only when earlier attributes are tied. In this question, the decisive mechanism is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. These are distinct technical causes, even when they share a platform.

Question 152

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. Which continuing control best reduces recurrence of this problem?

  1. Keep DR selection in the network design and test after topology changes.
  2. Compare prefix-set ranges to ownership records before peering activation.
  3. Check inbound policy, next hop, and route preferences before changing peer attributes.
  4. Exercise RP switchover and process-state recovery with traffic generators.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An Ethernet OSPFv2 broadcast segment has many routers flapping DR roles after a series of maintenance reboots. The most directly supported response is: Set documented OSPF priorities and stable router IDs for designated-router candidates. Technical basis: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. Evidence of success: The expected router is elected DR under a controlled restart scenario. Ongoing protection: Keep DR selection in the network design and test after topology changes.

Incorrect Answers

B:

That recurring practice manages a separate exposure: Prefix-set ge and le bounds determine which subnet lengths a policy can match. The present case instead depends on: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. The suitable ongoing safeguard is: Keep DR selection in the network design and test after topology changes.

C:

That recurring practice manages a separate exposure: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The present case instead depends on: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. The suitable ongoing safeguard is: Keep DR selection in the network design and test after topology changes.

D:

NSR maintains routing protocol state on redundant controllers and differs from neighbor-assisted graceful restart. Maintaining that control would not track the failure described here. The relevant risk is: OSPF broadcast networks use DR and BDR elections to manage LSA exchange scale. Review this instead: Keep DR selection in the network design and test after topology changes.

Question 153

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Activate the appropriate AFI/SAFI for the neighbor and advertise authorized IPv6 routes.
  2. Use an IPv6 multitopology design where supported to avoid selecting IPv4-only transit devices.
  3. Engineer supported NAT64 translation with an appropriate DNS64 resolution strategy where required.
  4. Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values.

Explanation

Correct Answer

D:

For this scenario, the observed situation is: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. The most directly supported response is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values. Technical basis: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Evidence of success: The shortest-path tree reflects the intended relative capacity of 10G and 100G links. Ongoing protection: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

Incorrect Answers

A:

BGP transport session establishment does not automatically enable every address family. That principle governs the alternative intervention. The issue described here is different: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The case-matched corrective action is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values.

B:

IS-IS multitopology can maintain separate route calculations for distinct supported protocol topologies. That principle governs the alternative intervention. The issue described here is different: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The case-matched corrective action is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values.

C:

The proposed option addresses this separate mechanism: NAT64 bridges IPv6 endpoints to IPv4 destinations with state and addressing considerations. The stated problem instead depends on: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The required response is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values.

Question 154

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. Which observable result most directly verifies that this network issue was resolved?

  1. The shortest-path tree reflects the intended relative capacity of 10G and 100G links.
  2. Only approved more-specific prefixes are accepted and forwarding follows actual installed longest matches.
  3. The chosen route is explained by the actual effective attributes present in the BGP table.
  4. Each approved prefix follows one documented origin policy without repeated feedback paths.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. The most directly supported response is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values. Technical basis: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Evidence of success: The shortest-path tree reflects the intended relative capacity of 10G and 100G links. Ongoing protection: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

Incorrect Answers

B:

BGP routing policy controls prefix acceptance, while forwarding uses the most specific installed route. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. A passing check should show: The shortest-path tree reflects the intended relative capacity of 10G and 100G links.

C:

BGP evaluates ordered criteria, so later comparisons apply only when earlier attributes are tied. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. A passing check should show: The shortest-path tree reflects the intended relative capacity of 10G and 100G links.

D:

Redistribution without tagging and filtering can feed learned routes back into their origin domain. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. A passing check should show: The shortest-path tree reflects the intended relative capacity of 10G and 100G links.

Question 155

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. Which underlying network infrastructure principle best explains the situation?

  1. OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth.
  2. Prefix-set ge and le bounds determine which subnet lengths a policy can match.
  3. BGP transport session establishment does not automatically enable every address family.
  4. IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency.

Explanation

Correct Answer

A:

For this scenario, the observed situation is: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. The most directly supported response is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values. Technical basis: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Evidence of success: The shortest-path tree reflects the intended relative capacity of 10G and 100G links. Ongoing protection: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

Incorrect Answers

B:

Prefix-set ge and le bounds determine which subnet lengths a policy can match. That is not the causal relationship tested by the current facts. The relevant principle is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth.

C:

BGP transport session establishment does not automatically enable every address family. That is not the causal relationship tested by the current facts. The relevant principle is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth.

D:

IS-IS overload and high-cost advertisement can drain transit traffic without tearing down every adjacency. That is not the causal relationship tested by the current facts. The relevant principle is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth.

Question 156

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. Which continuing control best reduces recurrence of this problem?

  1. Audit address-family enablement and routing table parity after network upgrades.
  2. Compare both peers' timer settings during maintenance.
  3. Version the reference-bandwidth policy and deploy it consistently across the routing domain.
  4. Maintain OS-specific routing policy snippets with regression cases.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: An OSPF cost plan is built using default reference bandwidth, making two very different high-speed links appear to have equal cost. The most directly supported response is: Set an appropriate consistent OSPF reference bandwidth and engineered interface cost values. Technical basis: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Evidence of success: The shortest-path tree reflects the intended relative capacity of 10G and 100G links. Ongoing protection: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

Incorrect Answers

A:

IS-IS can advertise separate IPv6 reachability information independently of its IPv4 control-plane transport. Maintaining that control would not track the failure described here. The relevant risk is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Review this instead: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

B:

OSPF adjacency requires compatible hello parameters, not merely Layer 3 reachability. Maintaining that control would not track the failure described here. The relevant risk is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. Review this instead: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

D:

The alternative guards against: Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. The root condition for this case is: OSPF default cost calculations can lose resolution when link speeds exceed the reference bandwidth. The focused prevention check is: Version the reference-bandwidth policy and deploy it consistently across the routing domain.

Question 157

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. What is the best authorized corrective or investigative action for this service-provider network operations situation?

  1. Deploy suitable BFD on eligible neighbors with realistic detection timers.
  2. Compare BGP accepted NLRI, best-path state, route distance, and installed RIB entries.
  3. Troubleshoot bidirectional Hello reception, access lists, and interface behavior.
  4. Evaluate upstream filtering, longest-prefix match, and allowed deaggregation policy before making changes.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. The most directly supported response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior. Technical basis: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of success: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT. Ongoing protection: Use packet-level hello tests when control-plane filters change.

Incorrect Answers

A:

The proposed option addresses this separate mechanism: BFD supplies fast bidirectional failure detection independently of slower protocol hello timers. The stated problem instead depends on: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The required response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior.

B:

The proposed option addresses this separate mechanism: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The stated problem instead depends on: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The required response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior.

D:

The option fits a control for: BGP routing policy controls prefix acceptance, while forwarding uses the most specific installed route. The present failure is caused by a different mechanism: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The targeted implementation is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior.

Question 158

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. Which observable result most directly verifies that this network issue was resolved?

  1. The IPv6-only client reaches the IPv4 service through a measured translation state.
  2. The PE receives the intended VPN NLRI with labels and import targets under the service design.
  3. The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.
  4. Each approved prefix follows one documented origin policy without repeated feedback paths.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. The most directly supported response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior. Technical basis: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of success: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT. Ongoing protection: Use packet-level hello tests when control-plane filters change.

Incorrect Answers

A:

NAT64 bridges IPv6 endpoints to IPv4 destinations with state and addressing considerations. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. A passing check should show: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.

B:

The proposed test would be relevant to: BGP address families carry different kinds of NLRI and require explicit peer activation. The reported problem follows from: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Instead, verify: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.

D:

The proposed test would be relevant to: Redistribution without tagging and filtering can feed learned routes back into their origin domain. The reported problem follows from: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Instead, verify: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT.

Question 159

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. Which underlying network infrastructure principle best explains the situation?

  1. IOS XR RPL has distinct decision syntax and default disposition behavior from IOS route maps.
  2. BGP address families carry different kinds of NLRI and require explicit peer activation.
  3. OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery.
  4. CGNAT multiplexes many private subscribers over limited public IPv4 address space.

Explanation

Correct Answer

C:

For this scenario, the observed situation is: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. The most directly supported response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior. Technical basis: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of success: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT. Ongoing protection: Use packet-level hello tests when control-plane filters change.

Incorrect Answers

A:

The option explains a separate issue: IOS XR RPL has distinct decision syntax and default disposition behavior from IOS route maps. The reported condition instead follows from: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery.

B:

The option explains a separate issue: BGP address families carry different kinds of NLRI and require explicit peer activation. The reported condition instead follows from: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery.

D:

The option explains a separate issue: CGNAT multiplexes many private subscribers over limited public IPv4 address space. The reported condition instead follows from: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery.

Question 160

Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. Which continuing control best reduces recurrence of this problem?

  1. Check inbound policy, next hop, and route preferences before changing peer attributes.
  2. Use packet-level hello tests when control-plane filters change.
  3. Review redistribution policy and route limits after adding external peers.
  4. Maintain OS-specific routing policy snippets with regression cases.

Explanation

Correct Answer

B:

For this scenario, the observed situation is: OSPF adjacency to a provider core router remains in INIT because one side never sees its own router ID in received hellos. The most directly supported response is: Troubleshoot bidirectional Hello reception, access lists, and interface behavior. Technical basis: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. Evidence of success: The Hello neighbor field becomes reciprocal and the adjacency advances from INIT. Ongoing protection: Use packet-level hello tests when control-plane filters change.

Incorrect Answers

A:

The alternative guards against: Reception of BGP NLRI does not necessarily imply RIB or FIB installation. The root condition for this case is: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The focused prevention check is: Use packet-level hello tests when control-plane filters change.

C:

The alternative guards against: Unbounded redistribution expands IGP state and can affect convergence and resource use. The root condition for this case is: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The focused prevention check is: Use packet-level hello tests when control-plane filters change.

D:

That recurring practice manages a separate exposure: Cisco route-policy languages differ across operating systems and cannot always be pasted interchangeably. The present case instead depends on: OSPF INIT indicates a one-way neighbor relationship rather than full bidirectional discovery. The suitable ongoing safeguard is: Use packet-level hello tests when control-plane filters change.