For easier management of your IoT infrastructure, you decide to use the Azure IoT Central platform.
As the first step, you are going to create templates for the different types of devices you have so that it can be used later for connecting real devices in a manageable way.
You start defining a template for a vibration sensor attached to a generator.
The device must be able to report if the machinery is running, and it should be able to get restarted remotely.
Which sections should you include in the device template?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: A.
Option A is CORRECT because the “Properties” in the device template can be used by devices to report statuses, pre-set limits etc.
A “Command” must be defined if you want to instruct your device to execute a task it is capable of (“Reboot” is a typical example).
Option B is incorrect because the “Component” section is a collection of device capabilities.
You have to add a “Command” section to be able to send cloud-to-device instructions.
Option C is incorrect because “Attribute” is not a valid section for device templates; section “Telemetry” defines the stream of data sent by the device regularly (e.g.
vibration values).
Option D is incorrect because cloud properties only exist in the IoT Central application and are not sent to, or received from, a device, i.e.
not suitable for status reports.
Reference:
When creating a device template for a vibration sensor attached to a generator in Azure IoT Central, there are several sections that should be included to ensure the device is manageable and meets the requirements specified in the question.
The first requirement is that the device must be able to report if the machinery is running. To achieve this, the device template should include a "Property" section for the run-state. This section will allow the device to report the current state of the machinery (i.e., running or not running) and make that information available for monitoring and analysis.
The second requirement is that the device should be able to get restarted remotely. To achieve this, the device template should include a "Command" section for the restart. This section will allow the device to receive commands from the cloud to restart itself remotely, providing a way to control the device without physically accessing it.
Therefore, the correct answer is option A: "Property" for the run-state; "Command" for the restart. Option B ("Component" for the restart) and option C ("Attribute" for the run-state; "Telemetry" for the restart) do not include the necessary sections for the two requirements specified in the question. Option D ("Cloud property" for the run-state; "Command" for the restart) is not a valid section in Azure IoT Central, and therefore, it is not the correct answer.