An emergency-management agency uses SOAR to fan-out notifications to on-call and public-info officers. What orchestration pattern is that?

An emergency-management agency that uses SOAR to fan-out notifications to on-call and public-info officers is orchestrating multi-role notification during major civic incidents. Security and emergency events need technical responders and public-information channels engaged together so operational facts and public messaging stay aligned. Automated fan-out reaches the right rotations quickly instead of using SOAR notification fan-out to rotate on-call and public-info roles in civic major incidents, which changes who is assigned to the rotations rather than paging the needed rotations directly.

Why the other options fail by concept: Using SOAR notification fan-out to rotate on-call and public-info roles in civic major incidents changes schedule assignments rather than actively pushing alerts simultaneously to both rotations. Using SOAR notification fan-out to page on-call then public-info roles in civic major incidents serializes paging one role after the other instead of pushing it simultaneously to on-call and public-info officers. Using SOAR notification fan-out to audit on-call and public-info roles in civic major incidents reviews messages for compliance and performance instead of actively sending alerts out to those roles when the event is underway.

Exam caveat: Fan-out must respect privacy and operational security—not every technical detail belongs in public-info channels; templates should separate internal vs external content. Operational check: define notification groups for on-call and public-info, template messages by audience, test fan-out in exercises, and confirm acknowledgements so silent failures in paging do not go unnoticed.