Question 800
Operations wants to avoid recurrence of this design flaw: The network team configures SSM on routers but old receiver clients send only IGMPv2 membership reports. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Validate receiver protocol version with application owners before SSM migration. This control targets the underlying design risk. SSM receivers normally signal a particular source/group using IGMPv3 or an equivalent mechanism. The follow-up acceptance check remains: Receiver membership state identifies the intended source and the multicast stream is delivered.
Incorrect Answers
Multicast can replicate traffic within the network only where receivers need it, reducing redundant source-side transmissions. The repeat risk here is different: SSM receivers normally signal a particular source/group using IGMPv3 or an equivalent mechanism. A directly relevant preventive control is: Validate receiver protocol version with application owners before SSM migration.
MSDP can advertise active sources between participating RPs in ASM deployments; it is not an SSM dependency. The repeat risk here is different: SSM receivers normally signal a particular source/group using IGMPv3 or an equivalent mechanism. A directly relevant preventive control is: Validate receiver protocol version with application owners before SSM migration.
OOB management can remain accessible when an in-band production network or routing plane fails. The repeat risk here is different: SSM receivers normally signal a particular source/group using IGMPv3 or an equivalent mechanism. A directly relevant preventive control is: Validate receiver protocol version with application owners before SSM migration.