The transit mobile backend should scale out when concurrent sessions or request queue depth crosses a load threshold. Which approach matches that requirement?
Select an answer to reveal the explanation.
Short Explanation
Concurrent sessions and queue depth are the “how crowded is the bus” gauges. When they cross the line, triggered scaling rolls out more backend capacity for riders. Waiting for angry tweets is not a load signal.
Full Explanation
Load-based triggered scaling uses signals such as concurrent sessions, request rate, or queue depth to add capacity. These metrics often reflect user demand more directly than CPU alone for session-oriented municipal apps. Configuring such policies is part of Cloud+ objective 3.2 scaling approaches.