Question: In the context of IP Multimedia (IM) Subsystem's Sh interface, what is a consequence of updating shared Repository Data for a large number of subscribers with the same Service Indication using the standard Sh-Update procedure?
Option 1: It may trigger a minimal number of notifications to Application Servers (AS) subscribed to changes.
Option 2: It requires only a single update operation, regardless of the subscriber count.
Option 3: It implies a large amount of update operations, potentially triggering a large number of notifications to AS subscribed to these subscribers' changes.
Option 4: It necessitates a change in Service Indication for all affected subscribers.
Explanation: Updating shared Repository Data across many subscribers using the standard Sh-Update procedure can lead to inefficiency. Each update per subscriber may trigger multiple notifications for Application Servers tracking changes, highlighting the need for optimized solutions to manage shared data efficiently among multiple subscribers.