A transit agency needs a long-running HTTP fare API with custom sidecars and readiness probes, plus a worker that keeps a Streaming cursor open. Where should those processes run?
Select an answer to reveal the explanation.
Short Explanation
A desk that must stay staffed all day with extra tools on the side belongs in the always-open OKE shop. Functions can be called from that world; they do not replace a long-running Deployment.
Full Explanation
Long-running HTTP services, consumers that must hold a Streaming cursor open, and workers that need custom sidecars and probes belong on OKE. Functions may be invoked from those systems, but they do not replace a Deployment for always-on or custom-runtime needs. Keeping idle cluster replicas solely for rare five-line handlers is the opposite anti-pattern.