Allocation Policy for IoT Device Distribution among Multiple Hubs
Question
You have to provision 400 devices and you need to distribute them among three IoT hubs, using Device Provisioning Service.
All the hubs are linked to the DPS and you need to design how the devices are distributed over the different hubs.
Here are the requirements for the different types of assets: Simple temperature and CO-sensors: can be attached to any of the 3 hubs, with no preference Edge devices: their data must be queried from a registry database; allocation on the basis of the result Surveillance cameras: the images must be available real time in case any actions need to be taken Which allocation policy would you use for the given scenarios?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: B.
Option A is incorrect because for the simple sensors the default allocation policy, i.e.
the evenly weighted distribution is the perfect choice.
Option B is CORRECT because The default allocation policy (i.e.
Evenly weighted) is the right selection for the simple sensors for which no specific rule applies; edge devices need a custom logic to be executed before deciding the allocation hub, therefore the “Custom” policy built as Azure Function App is suitable; telemetry data from cameras must reach the IoT hub with no delay, so the “Lowest latency” policy is the best choice.
Option C is incorrect because the requirement for the edge devices can be fulfilled by the custom policy (built as a Function App); the cameras must be allocated focusing on the latest latency.
(The simple sensors can be distributed evenly over the hubs, which is the default setting, so it is correct.)
Option D is incorrect because for the cameras requiring real-time visibility, the lowest latency setting must be used.
References:
To provision 400 devices and distribute them among three IoT hubs using the Device Provisioning Service, you need to determine the allocation policy for each device type.
For simple temperature and CO-sensors, there is no specific requirement for which hub they should be attached to, so any of the three hubs can be used. Therefore, an evenly weighted allocation policy can be used to distribute these devices across the three hubs.
For edge devices, their data needs to be queried from a registry database, and the allocation of these devices should be based on the result of the query. This means that a custom allocation policy should be used, which can be defined based on the results of the query.
For surveillance cameras, the images must be available in real-time, so the allocation policy for these devices should prioritize lowest latency. This ensures that the images are available as quickly as possible in case any actions need to be taken.
Therefore, the recommended allocation policy for the given scenarios would be:
- Simple temperature and CO-sensors: Evenly weighted
- Edge devices: Custom
- Surveillance cameras: Lowest latency
Based on these requirements, option B, which includes Default allocation policy for Edge devices instead of Custom, would not be suitable. Option A, which includes Static allocation policy for Simple temperature and CO-sensors, would not be necessary since evenly weighted allocation policy can be used. Option C and D both include the recommended allocation policy for each device type, but D includes Static allocation policy which is not necessary, so the best option would be C: Evenly weighted; Lowest latency; Custom.
