A separate internal API is being moved to Container Apps and must scale to zero overnight. Which scaling configuration achieves this?
- A minReplicas 1 with a CPU rule
- B minReplicas 0 with an HTTP concurrency rule (correct answer)
- C A fixed replica count of 2
- D A CPU rule alone with minReplicas 0
Shortcut: Scale to zero requires minReplicas 0 together with an event-driven or HTTP rule, because KEDA needs a signal that can be evaluated while no replica is running. A CPU rule cannot scale from zero: with no replica there is no CPU metric to read.