The Bulk Provisioning Process for In-house Devices in Azure IoT Central
Question
You need to connect 100 distributed sensors to your Azure IoT infrastructure.
Most of the devices are Azure certified smart sensors developed by a major manufacturer but there are several devices developed in-house, by your engineering department.
You want to use the bulk provisioning process supported by IoT Central.
Which of the following steps cannot be skipped for your in-house devices?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Answer: C.
Option A is incorrect because during bulk provisioning, the device list, together with the credentials can be exported to CSV, which then can be used to update the code of the devices.
(This step must be preceded by the “Import list of devices from CSV” step.)
Option B is incorrect because when creating “standard” devices, selecting a device template is required.
For certified equipment, it is created automatically.
Option C is CORRECT because Azure certified device templates come fully pre-configured and they are ready to use.
For your own devices, however, the capabilities (as well as other properties of the device template) must be manually defined and configured.
Option D is incorrectduring bulk provisioning of devices, the list of device ID-s and names can be imported from CSV.
IoT Central then automatically generates the devices with the necessary SAS keys.
Imported devices are created as “Unassigned”, i.e.
not having a template associated.
Reference:
To connect 100 distributed sensors to your Azure IoT infrastructure, you can use the bulk provisioning process supported by IoT Central. This process enables you to provision a large number of devices simultaneously, saving time and effort.
For Azure certified smart sensors developed by a major manufacturer, the process is relatively straightforward. You can select the appropriate device template from the IoT Central device catalog and follow the steps to provision the devices.
However, for devices developed in-house, by your engineering department, there are additional steps that you need to follow. These steps include:
Create a device template: A device template defines the characteristics and capabilities of a device. You need to create a device template that matches the capabilities of your in-house devices.
Configure device capabilities: You need to configure the device capabilities in the device template to match the capabilities of your in-house devices. This includes defining telemetry, properties, and commands.
Export device data to CSV: You need to export the device data for your in-house devices to a CSV file. This includes device IDs and any other device-specific information that you want to include.
Import list of devices from CSV: You need to import the list of devices from the CSV file into IoT Central. This will create device identities and associate them with the appropriate device template.
Therefore, in order to provision your in-house devices using the bulk provisioning process supported by IoT Central, you cannot skip the following steps:
B. Create a device template: Without a device template, you cannot define the characteristics and capabilities of your in-house devices.
C. Configure device capabilities: Without configuring device capabilities, your devices will not be able to send telemetry, receive commands, or update properties.
D. Import list of devices from CSV: Without importing the list of devices, IoT Central will not create device identities and associate them with the appropriate device template.
A. Export device data to CSV: Although it is an important step, it can be skipped if you have already exported the device data to a CSV file.
