What is the purpose of the Fabric Activator destination in an eventstream?

• A. Ingested data in a lakehouse or eventhouse isn't visible until activated by the Fabric Activator.
• B. Data sent to an Activator destination can be used to trigger an automated action based on data values.
• C. The Activator resets any transformation that were applied in the eventstream, returning the data to a clean state.
• D. Activator stores historical data for auditing.

Answer: (D)

Fabric Activator as a destination is about keeping a durable history of events for auditing and provenance. By persisting event data over time, it creates an auditable trail that lets you verify what happened, when, and how data looked at different points in time. This supports governance, compliance, and the ability to replay or inspect past states when needed. The other ideas—gating visibility, triggering automated actions, or resetting transformations—aren’t the primary purpose of the Activator in this context; its main value is preserving historical records for auditing.