Analytics beacons on a city portal accept POSTed events from browsers. What security concern must designers address?
Select an answer to reveal the explanation.
Short Explanation
An open beacon is a mailbox with no lock—spammers will stuff it. Validate, rate-limit, and design so junk cannot poison civic metrics. Hardening the collection edge protects both the pipeline and the decisions that trust it.
Full Explanation
Collection endpoints in web analyzers are attractive injection points for fake traffic. Designers should apply validation, rate limiting, and other hardening so beacons cannot be abused as open spam sinks. Compromised veracity at ingest undermines every downstream UX and ops metric.