You are building a premium-tier Azure Event Hubs solution to track road toll events. Each road requires its own throttling policy. How should you configure the event hub to allow per-road throttling?

Application groups in Azure Event Hubs allow you to define custom throttling policies for specific applications or logical entities, such as individual roads in this scenario. By creating a unique application group for each road, you can apply distinct throttling rules (e.g., maximum ingress/egress bytes per second, maximum messages per second) to prevent one road's high event volume from impacting others. Using a unique consumer group for each road is incorrect because consumer groups are for managing event consumption, not for applying ingress throttling policies. Ensuring each road stores events in a different partition is also incorrect; partitions distribute events for parallel processing and do not directly offer per-entity throttling. Lastly, using a unique connection string for each road is not the mechanism for defining throttling policies; connection strings provide access credentials.