A hospital is deploying PIM sparse mode across Cisco and non-Cisco switches, needs automatic RP failover without manual mapping on every router, and requires open-standards operation. Which rendezvous point discovery method should the multicast design specify?

The correct design uses PIM Bootstrap Router because BSR is the open standards mechanism that works across Cisco and non-Cisco PIM sparse mode domains, where candidate RPs advertise to the elected BSR and the BSR floods the unified RP-set to all routers for consistent mapping with automatic failover without per-router manual changes. Auto-RP with candidate RPs and mapping agents fails by standards concept because it relies on Cisco proprietary announces processed by mapping agents, which delivers automatic discovery in Cisco-only networks but violates the explicit open-standards multivendor requirement. Static RP addresses distributed by automation templates fail by automation concept because centralized push still installs manual definitions on each router with no election protocol, so loss of the primary RP cannot trigger dynamic learning of an alternate and violates automatic failover without manual mapping. Anycast-RP with MSDP peering fails by discovery concept because configuring the same RP address on redundant routers with MSDP source exchange provides resilience but still requires manual RP definition on every router plus session maintenance, so it is not automatic discovery. As an exam caveat, separate discovery from redundancy: BSR elects and advertises RPs while Anycast makes multiple routers share one RP address. As a practical check, verify candidate BSR and RP priorities, confirm a consistent RP-set via show ip pim rp mapping, then disable the primary candidate RP to confirm automatic remapping.