Transit fare kiosks need processing close to stations for low latency rather than sending every transaction to a distant central region. Which approach best addresses that need?
Select an answer to reveal the explanation.
Short Explanation
Kiosks hate waiting on a faraway brain the way a ticket booth hates calling headquarters for every swipe. Edge computing puts smarts near the stations so latency drops. Shipping every tap to a distant region or deep archive first is the opposite of that design.
Full Explanation
Edge computing places processing closer to end users or devices to reduce round-trip latency and dependence on a distant central region. Transit kiosks that must respond quickly benefit from local or near-station compute rather than exclusively remote archival storage or synchronous distant databases. Cloud+ architecture questions often contrast edge placement with centralized-only designs.