Permit-portal click events spike during storm season and streaming consumers fall behind. How does cloud elasticity primarily support the Velocity V in this scenario?
Select an answer to reveal the explanation.
Short Explanation
When the firehose opens wider, you add more hoses—not a smaller bucket. Autoscaling stream consumers is how cloud elasticity backs Velocity during civic event spikes. Freezing capacity just lets the backlog win.
Full Explanation
Velocity concerns how fast data arrives and must be processed. Cloud autoscaling lets consumer fleets expand during municipal event spikes and contract afterward, preserving timely analytics. Fixed capacity, indiscriminate deletes, and paper digests do not address streaming Velocity. Linking elasticity to Velocity is a BDPC cloud selection rationale.