A parks department wants small event-driven handlers that run only when invoked, without managing worker shapes or patching guest OS. Which OCI approach matches that model?

OCI Functions is managed FaaS: you deploy a small unit of code, the service provisions execution infrastructure when that unit is invoked, and billing follows what ran. You do not choose Compute shapes, patch guest OS, or keep a warm worker pool merely to host the handler. Always-on OKE Deployments or dedicated hosts are valid for other workloads but are not the Functions model. Ask whether the work is a function, not which SKU hosts a Lambda-like process.