cert
cert-1
cert-2

Pass Cisco 350-601 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
350-601 Exam - Verified By Experts
350-601 Premium Bundle
$29.98

350-601 Premium Bundle

$79.99
$109.97
  • Premium File 613 Questions & Answers. Last update: Nov 10, 2026
  • Training Course 143 Video Lectures
  • Study Guide 1923 Pages
 
$109.97
$79.99
accept 46 downloads in last 7 days
block-screenshots
Purchase Cisco 350-601 Exam Training Products Individually
Cisco 350-601 Premium File
Premium File 613 Q&A
$76.99$69.99
Cisco 350-601 Video Training Course
Training Course 143 Lectures
$21.99 $19.99
Cisco 350-601 PDF Study Guide
Study Guide 1923 Pages
$21.99 $19.99
Cisco 350-601 Practice Test 8

Question 70

A scaled EVPN control plane shows route reflector adjacencies as up but leaves do not learn each other's advertised routes. The observed failure is: an up neighbor session without correct route-reflector client policy can leave overlay reachability partitioned. Which recovery action addresses the underlying technical fault?

  1. The controlled remediation is to turn off route advertisement on all leaves as a permanent workaround.
  2. The controlled remediation is to restore intended client-group and AF settings and confirm bidirectional route propagation.
  3. The controlled remediation is to force a full iBGP mesh by deleting the reflectors without a design review.
  4. The controlled remediation is to clear the entire underlay OSPF process whenever one EVPN route is missing.

Explanation

Correct Answer

B:

Validate against BGP client relationships, AF neighbor activation, received EVPN routes, and reflected route visibility.

Incorrect Answers

A:

Turn off route advertisement on all leaves as a permanent workaround. This would not reliably restore service after the stated fault. An up neighbor session without correct route-reflector client policy can leave overlay reachability partitioned. The controlled recovery is to restore intended client-group and AF settings and confirm bidirectional route propagation.

C:

Force a full iBGP mesh by deleting the reflectors without a design review. This would not reliably restore service after the stated fault. An up neighbor session without correct route-reflector client policy can leave overlay reachability partitioned. The controlled recovery is to restore intended client-group and AF settings and confirm bidirectional route propagation.

D:

Clear the entire underlay OSPF process whenever one EVPN route is missing. This would not reliably restore service after the stated fault. An up neighbor session without correct route-reflector client policy can leave overlay reachability partitioned. The controlled recovery is to restore intended client-group and AF settings and confirm bidirectional route propagation.

Question 71

Multicast receivers lose a stream because the transit switch receives multicast packets on an interface different from its unicast route toward the source. Which next step should the data center engineer select?

  1. Enable PortFast on every routed multicast transit interface.
  2. Replace a valid multicast group address with an IPv4 broadcast.
  3. Correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.
  4. Disable all reverse-path checks globally as the first troubleshooting step.

Explanation

Correct Answer

C:

This directly addresses PIM reverse-path forwarding because PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. Confirm the change against multicast routing table, RPF interface selection, source route lookup, and drop counters.

Incorrect Answers

A:

Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The relevant correction is to correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

B:

That option would replace a valid multicast group address with an IPv4 broadcast, but it addresses a different concern. This directly addresses PIM reverse-path forwarding because PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

D:

Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The appropriate action remains to correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

Question 72

Multicast receivers lose a stream because the transit switch receives multicast packets on an interface different from its unicast route toward the source. Which diagnostic record would most strongly confirm the result?

  1. An up management interface without the relevant routing or forwarding table.
  2. A pre-change network diagram with no live control-plane state.
  3. An interface description without the effective peer or VXLAN policy.
  4. Multicast routing table, RPF interface selection, source route lookup, and drop counters.

Explanation

Correct Answer

D:

These observations test the actual PIM reverse-path forwarding mechanism rather than a superficial management status. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

Incorrect Answers

A:

An up management interface without the relevant routing or forwarding table. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

B:

A pre-change network diagram with no live control-plane state. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

C:

An interface description without the effective peer or VXLAN policy. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

Question 73

Multicast receivers lose a stream because the transit switch receives multicast packets on an interface different from its unicast route toward the source. Which platform concept should guide the engineer’s assessment?

  1. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.
  2. A working management-plane ping proves every tenant and application path is healthy.
  3. A device description always determines actual forwarding policy regardless of running configuration.
  4. Physical link carrier guarantees all overlay and routing states are correct.

Explanation

Correct Answer

A:

This explains why the most appropriate response is to correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface. Validation depends on multicast routing table, RPF interface selection, source route lookup, and drop counters.

Incorrect Answers

B:

A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

C:

A device description always determines actual forwarding policy regardless of running configuration. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

D:

Physical link carrier guarantees all overlay and routing states are correct. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

Question 74

Multicast receivers lose a stream because the transit switch receives multicast packets on an interface different from its unicast route toward the source. Assume an engineer instead chooses to enable PortFast on every routed multicast transit interface. Which root-cause observation follows from that incorrect change?

  1. The defect exists solely because the engineer documented the change.
  2. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist.
  3. Preserving neighbor-state evidence is itself the source of the observed outage.
  4. Investigating the forwarding table is the reason a broken route cannot converge.

Explanation

Correct Answer

B:

PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The proper corrective action is to correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

Incorrect Answers

A:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. The meaningful failure is that continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist.

C:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. The relevant evidence is multicast routing table, RPF interface selection, source route lookup, and drop counters.

D:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. Investigating the forwarding table is the reason a broken route cannot converge.

Question 75

Multicast receivers lose a stream because the transit switch receives multicast packets on an interface different from its unicast route toward the source. The observed failure is: continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. Which recovery action addresses the underlying technical fault?

  1. Replace a valid multicast group address with an IPv4 broadcast.
  2. Disable all reverse-path checks globally as the first troubleshooting step.
  3. Restore a consistent source route and verify RPF and multicast forwarding entries.
  4. Enable PortFast on every routed multicast transit interface.

Explanation

Correct Answer

C:

PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. This addresses the observable fault while preserving a check of the expected result.

Incorrect Answers

A:

That option would replace a valid multicast group address with an IPv4 broadcast, but it addresses a different concern. This addresses the observable fault while preserving a check of the expected result.

B:

That option would disable all reverse-path checks globally as the first troubleshooting step, but it addresses a different concern. This addresses the observable fault while preserving a check of the expected result.

D:

Enable PortFast on every routed multicast transit interface. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

Question 76

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. What is the BEST supported implementation or corrective action?

  1. On this affected device, the engineer should replace a valid multicast group address with an IPv4 broadcast.
  2. On this affected device, the engineer should disable all reverse-path checks globally as the first troubleshooting step.
  3. On this affected device, the engineer should enable PortFast on every routed multicast transit interface.
  4. On this affected device, the engineer should correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

Explanation

Correct Answer

D:

This directly addresses PIM reverse-path forwarding because PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

Incorrect Answers

A:

Replace a valid multicast group address with an IPv4 broadcast. The proposed change targets the wrong mechanism or lacks essential validation. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. Relevant evidence is multicast routing table, RPF interface selection, source route lookup, and drop counters.

B:

Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. Disable all reverse-path checks globally as the first troubleshooting step.

C:

Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. In the given case, a PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink.

Question 77

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. Which evidence BEST verifies the intended technical behavior?

  1. For this deployment, examine multicast routing table, RPF interface selection, source route lookup, and drop counters.
  2. For this deployment, examine a healthy optical light without checking protocol neighbors or forwarding entries.
  3. For this deployment, examine an up management interface without the relevant routing or forwarding table.
  4. For this deployment, examine a pre-change network diagram with no live control-plane state.

Explanation

Correct Answer

A:

These observations test the actual PIM reverse-path forwarding mechanism rather than a superficial management status. They should be checked after correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

Incorrect Answers

B:

A healthy optical light without checking protocol neighbors or forwarding entries. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

C:

An up management interface without the relevant routing or forwarding table. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

D:

A pre-change network diagram with no live control-plane state. This information cannot independently verify PIM reverse-path forwarding. The decisive records instead include multicast routing table, RPF interface selection, source route lookup, and drop counters. PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.

Question 78

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. Which principle BEST explains why the recommended solution is appropriate?

  1. For this condition, the applicable principle is that physical link carrier guarantees all overlay and routing states are correct.
  2. For this condition, the applicable principle is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction.
  3. For this condition, the applicable principle is that a working management-plane ping proves every tenant and application path is healthy.
  4. For this condition, the applicable principle is that all control-plane protocols exchange state automatically after a cable is inserted.

Explanation

Correct Answer

B:

This explains why the most appropriate response is to correct the underlying unicast or multicast RPF route so source traffic arrives on the RPF-expected interface.

Incorrect Answers

A:

Physical link carrier guarantees all overlay and routing states are correct. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

C:

A working management-plane ping proves every tenant and application path is healthy. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

D:

All control-plane protocols exchange state automatically after a cable is inserted. This is an incorrect generalization for PIM reverse-path forwarding. The applicable technical behavior is that PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. The operator should verify multicast routing table, RPF interface selection, source route lookup, and drop counters.

Question 79

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. Assume an engineer instead chooses to enable PortFast on every routed multicast transit interface. What is the MOST significant failure introduced by that shortcut?

  1. The resulting defect is that investigating the forwarding table is the reason a broken route cannot converge.
  2. The resulting defect is that the only consequence of the wrong change is a different device description.
  3. The resulting defect is that continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist.
  4. The resulting defect is that preserving neighbor-state evidence is itself the source of the observed outage.

Explanation

Correct Answer

C:

PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. That is the direct consequence of choosing the misleading shortcut.

Incorrect Answers

A:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. In the given case, a PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink.

B:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. The only consequence of the wrong change is a different device description.

D:

This does not explain the actual PIM reverse-path forwarding defect after the shortcut. Preserving neighbor-state evidence is itself the source of the observed outage.

Question 80

A PIM deployment passes multicast joins, but forwarding drops appear after the RPF path changes to a different uplink. The observed failure is: continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. What is the BEST controlled recovery once this failure is recognized?

  1. The controlled remediation is to disable all reverse-path checks globally as the first troubleshooting step.
  2. The controlled remediation is to enable PortFast on every routed multicast transit interface.
  3. The controlled remediation is to replace a valid multicast group address with an IPv4 broadcast.
  4. The controlled remediation is to restore a consistent source route and verify RPF and multicast forwarding entries.

Explanation

Correct Answer

D:

PIM RPF checks prevent multicast loops by validating that packets arrive from the expected upstream direction. Validate against multicast routing table, RPF interface selection, source route lookup, and drop counters.

Incorrect Answers

A:

Disable all reverse-path checks globally as the first troubleshooting step. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

B:

Enable PortFast on every routed multicast transit interface. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

C:

Replace a valid multicast group address with an IPv4 broadcast. This would not reliably restore service after the stated fault. Continuing to send traffic on a non-RPF interface causes multicast drops even if joins exist. The controlled recovery is to restore a consistent source route and verify RPF and multicast forwarding entries.

Implementing and Operating Cisco Data Center Core Technologies (DCCOR) (350-601) Practice Tests