A building-permits office wants each new scan that lands in a bucket to be converted by serverless code. Which Events pattern implements that event-driven conversion?
Select an answer to reveal the explanation.
Short Explanation
Turn on object events, filter create-object (scoped to the bucket), and action a Function that reads the object—typically with a resource principal—and writes a result. That is the classic event-driven serverless pattern, not a cron on OKE or a Streaming detour.
Full Explanation
Official Events examples include converting a file when it lands: enable object state-change emissions, filter the create type (and bucket via attributes), and deliver to a Function. The function uses appropriate IAM (often resource principal) to read and write objects. Cron-on-OKE and Streaming-only paths miss the Events-driven serverless design this pattern teaches; Notifications informs rather than converting files by itself.