What ate two reasons an admin should choose an Event over a Trigger when it comes to building out a solution?

What ate two reasons an admin should choose an Event over a Trigger when it comes to building out a solution?
A . Event order is not guaranteed within a topic
B . Events are asynchronous
C . Events cannot be subscribed lo in a batch for bulk operations
D . Events do not participate in a transaction scope

Answer: B, D

Explanation:

Two reasons an admin should choose an Event over a Trigger when it comes to building out a solution are:

Events are asynchronous. This means that events are processed in the background, without blocking the main execution thread. This can improve the performance and user experience of the solution, as well as avoid governor limits and timeouts.

Events do not participate in a transaction scope. This means that events are independent of the transaction that publishes them, and they do not affect the rollback or commit behavior of the transaction. This can avoid unwanted side effects and errors in the solution, as well as decouple the logic from the data.

Reference: https://developer.salesforce.com/docs/atlas.en-

us.platform_events.meta/platform_events/platform_events_intro.htm

https://developer.salesforce.com/docs/atlas.en-

us.platform_events.meta/platform_events/platform_events_considerations.htm