A team wants a framework that runs HTTP request-driven services, automatically scales their replicas up and down with traffic including down to zero when idle, and manages revision-based traffic splitting between versions of a service. Which cloud native project is purpose-built for this serving model?
- AKEDA, an add-on that reads external event sources and drives autoscaling of existing workloads based on those signals.
- BPrometheus, a monitoring system that collects time-series metrics and evaluates alerting rules against them.
- CKnative, which runs request-driven services, scales them with traffic including to zero, and routes traffic across service revisions. Correct
- DCloudEvents, a specification that defines a common metadata format so events can be described consistently across producers.
Why A is wrong: Tempting because KEDA also enables scale to zero, but it is an event-driven autoscaler layered onto existing workloads; it does not itself provide an HTTP serving framework with revision-based traffic routing.
Why B is wrong: Tempting because its metrics can feed autoscaling decisions, but Prometheus is an observability and alerting system and does not run application services or route request traffic between revisions.
Why C is correct: Correct: Knative Serving provides exactly this model, deploying stateless request-driven services, autoscaling them on request concurrency down to zero, and managing revisions with configurable traffic splitting.
Why D is wrong: Tempting in an event-driven context, but CloudEvents is a data-format specification for event metadata, not a runtime that hosts services or performs autoscaling and traffic routing.