Cisco 300-420 Practice Test 71
Question 700
A multicast distribution design has asymmetric unicast routes and the source-tree RPF check fails on one branch. The observed fault is: Ignoring RPF direction can break multicast even when the receiver joins the group successfully. Which recovery is BEST once this fault is identified?
- The controlled recovery is to correct the relevant upstream route or multicast routing table and test the expected source tree.
- The controlled recovery is to disable all multicast controls and claim this validates correct tree direction.
- The controlled recovery is to assume any incoming multicast packet must be accepted if the destination group exists.
- The controlled recovery is to change only a receiver DNS alias to repair an incorrect RPF incoming interface.
Explanation
Correct Answer
A:Multicast RPF accepts a packet only when it arrives on the expected upstream path toward the relevant source or RP. This corrects the described failure and provides a verifiable outcome.
Incorrect Answers
B:Disable all multicast controls and claim this validates correct tree direction. Ignoring RPF direction can break multicast even when the receiver joins the group successfully. Use the controlled remediation: correct the relevant upstream route or multicast routing table and test the expected source tree.
C:Assume any incoming multicast packet must be accepted if the destination group exists. Ignoring RPF direction can break multicast even when the receiver joins the group successfully. Use the controlled remediation: correct the relevant upstream route or multicast routing table and test the expected source tree.
D:Change only a receiver DNS alias to repair an incorrect RPF incoming interface. Ignoring RPF direction can break multicast even when the receiver joins the group successfully. Use the controlled remediation: correct the relevant upstream route or multicast routing table and test the expected source tree.
Question 701
A video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery. Which enterprise design procedure best meets this requirement?
- Assume any IGMPv2 group join can always specify a source IP with full SSM semantics.
- Configure an ordinary ASM RP as the only mandatory SSM delivery method.
- Use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
- Advertise a unicast BGP default route and treat that alone as the SSM receiver subscription.
Explanation
Correct Answer
C:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. This is the specific corrective action for SSM and IGMPv3 source-specific multicast.
Incorrect Answers
A:Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. The relevant action is use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
B:Configure an ordinary ASM RP as the only mandatory SSM delivery method. Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Instead inspect iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
D:Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. In this case, a video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery.
Question 702
A video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery. Which evidence best distinguishes the intended state from a superficial indicator?
- An old network diagram with no current route, policy, or redundancy state.
- One successful ping to an unrelated test host without a path or failover test.
- A marketing claim without measured routing, capacity or failure-domain evidence.
- IGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Explanation
Correct Answer
D:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. The intended procedure is use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
Incorrect Answers
A:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery.
B:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. The decisive evidence instead includes iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
C:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. A marketing claim without measured routing, capacity or failure-domain evidence.
Question 703
A video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery. Which underlying principle explains the correct decision?
- An operational up state alone proves every security and design objective is met.
- Any single device automatically guarantees high availability for every site.
- A longer IP prefix is always less specific than the default route.
- Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery.
Explanation
Correct Answer
D:This is why the appropriate action is use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit. Confirm it with iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Incorrect Answers
A:An operational up state alone proves every security and design objective is met. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
B:Any single device automatically guarantees high availability for every site. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
C:A longer IP prefix is always less specific than the default route. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Question 704
A video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery. Suppose the operator instead makes this incorrect change: Assume any IGMPv2 group join can always specify a source IP with full SSM semantics. What is the most material consequence of that mistake?
- The failure is entirely cosmetic because all control-plane changes are harmless.
- Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure.
- Collecting telemetry originally caused the missing route or service outage.
- A correct change-control review makes all WAN carriers fail simultaneously.
Explanation
Correct Answer
B:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. This explains why the proposed shortcut does not solve sSM and IGMPv3 source-specific multicast.
Incorrect Answers
A:The failure is entirely cosmetic because all control-plane changes are harmless. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
C:Collecting telemetry originally caused the missing route or service outage. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
D:A correct change-control review makes all WAN carriers fail simultaneously. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Question 705
A video platform knows the exact approved source IP and group but uses an RP-based ASM design with unnecessary discovery. The observed fault is: Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Which controlled remediation should be used?
- Configure an ordinary ASM RP as the only mandatory SSM delivery method.
- Enable supported source-specific joins and verify only approved source traffic reaches receivers.
- Advertise a unicast BGP default route and treat that alone as the SSM receiver subscription.
- Assume any IGMPv2 group join can always specify a source IP with full SSM semantics.
Explanation
Correct Answer
B:Relevant evidence includes iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Incorrect Answers
A:Configure an ordinary ASM RP as the only mandatory SSM delivery method. Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Use the controlled remediation: enable supported source-specific joins and verify only approved source traffic reaches receivers.
C:Advertise a unicast BGP default route and treat that alone as the SSM receiver subscription. Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Use the controlled remediation: enable supported source-specific joins and verify only approved source traffic reaches receivers.
D:That option would assume any IGMPv2 group join can always specify a source IP with full SSM semantics, but it addresses a different concern. Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery.
Question 706
A corporate streaming system needs subscribers to request only one trusted sender for a group. What is the most defensible configuration decision?
- For this enterprise design, the architect should configure an ordinary ASM RP as the only mandatory SSM delivery method.
- For this enterprise design, the architect should use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
- For this enterprise design, the architect should advertise a unicast BGP default route and treat that alone as the SSM receiver subscription.
- For this enterprise design, the architect should assume any IGMPv2 group join can always specify a source IP with full SSM semantics.
Explanation
Correct Answer
B:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Confirm the result using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Incorrect Answers
A:Configure an ordinary ASM RP as the only mandatory SSM delivery method. Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Instead inspect iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
C:Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. In this case, a corporate streaming system needs subscribers to request only one trusted sender for a group.
D:Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. This change targets the wrong mechanism for SSM and IGMPv3 source-specific multicast.
Question 707
A corporate streaming system needs subscribers to request only one trusted sender for a group. Which evidence BEST confirms the actual technical behavior?
- Inspect the following evidence: a hostname inventory without effective configuration or operational measurements.
- Inspect the following evidence: an old network diagram with no current route, policy, or redundancy state.
- Inspect the following evidence: one successful ping to an unrelated test host without a path or failover test.
- Inspect the following evidence: iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Explanation
Correct Answer
D:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. This evidence observes the actual sSM and IGMPv3 source-specific multicast mechanism and its result.
Incorrect Answers
A:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. A hostname inventory without effective configuration or operational measurements.
B:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. In this case, a corporate streaming system needs subscribers to request only one trusted sender for a group.
C:This observation alone cannot establish sSM and IGMPv3 source-specific multicast. One successful ping to an unrelated test host without a path or failover test.
Question 708
A corporate streaming system needs subscribers to request only one trusted sender for a group. What networking or enterprise network design concept best explains this scenario?
- The relevant principle is that a longer IP prefix is always less specific than the default route.
- The relevant principle is that an operational up state alone proves every security and design objective is met.
- The relevant principle is that source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery.
- The relevant principle is that encryption and segmentation are identical mechanisms and can replace each other.
Explanation
Correct Answer
C:This is why the appropriate action is use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
Incorrect Answers
A:A longer IP prefix is always less specific than the default route. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
B:An operational up state alone proves every security and design objective is met. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
D:Encryption and segmentation are identical mechanisms and can replace each other. This is an incorrect generalization for sSM and IGMPv3 source-specific multicast. The relevant rule is source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. Verify using iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Question 709
A corporate streaming system needs subscribers to request only one trusted sender for a group. Suppose the operator instead makes this incorrect change: Assume any IGMPv2 group join can always specify a source IP with full SSM semantics. Which resulting fault should the reviewer identify?
- The resulting technical fault is that using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure.
- The resulting technical fault is that a correct change-control review makes all WAN carriers fail simultaneously.
- The resulting technical fault is that the only issue is an inaccurate hostname while traffic paths are unaffected.
- The resulting technical fault is that collecting telemetry originally caused the missing route or service outage.
Explanation
Correct Answer
A:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. The right response is use SSM-capable PIM and IGMPv3 source-specific joins where endpoint and network support permit.
Incorrect Answers
B:A correct change-control review makes all WAN carriers fail simultaneously. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
C:The only issue is an inaccurate hostname while traffic paths are unaffected. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
D:Collecting telemetry originally caused the missing route or service outage. The actual failure is using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Check iGMPv3 source-group reports, PIM SSM tree, allowed source IP and receiver streams.
Question 710
A corporate streaming system needs subscribers to request only one trusted sender for a group. The observed fault is: Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. How should the issue be corrected and verified?
- The controlled recovery is to advertise a unicast BGP default route and treat that alone as the SSM receiver subscription.
- The controlled recovery is to enable supported source-specific joins and verify only approved source traffic reaches receivers.
- The controlled recovery is to assume any IGMPv2 group join can always specify a source IP with full SSM semantics.
- The controlled recovery is to configure an ordinary ASM RP as the only mandatory SSM delivery method.
Explanation
Correct Answer
B:Source-Specific Multicast joins a selected source and group without relying on the ordinary ASM rendezvous point discovery. This corrects the described failure and provides a verifiable outcome.
Incorrect Answers
A:Advertise a unicast BGP default route and treat that alone as the SSM receiver subscription. Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Use the controlled remediation: enable supported source-specific joins and verify only approved source traffic reaches receivers.
C:Assume any IGMPv2 group join can always specify a source IP with full SSM semantics. Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Use the controlled remediation: enable supported source-specific joins and verify only approved source traffic reaches receivers.
D:Configure an ordinary ASM RP as the only mandatory SSM delivery method. Using legacy joins without source selection can permit traffic from unwanted senders or need unnecessary RP infrastructure. Use the controlled remediation: enable supported source-specific joins and verify only approved source traffic reaches receivers.