You have 10,000 IoT devices that connect to an Azure IoT hub. The devices do not support over-the-air (OTA) updates.
You need to decommission 1,000 devices. The solution must prevent connections and autoenrollment for the decommissioned devices.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer : CE
In general, deprovisioning a device involves two steps:
✑ Disenroll the device from your provisioning service, to prevent future auto-provisioning. Depending on whether you want to revoke access temporarily or permanently, you may want to either disable or delete an enrollment entry.
✑ Deregister the device from your IoT Hub, to prevent future communications and data transfer. Again, you can temporarily disable or permanently delete the device's entry in the identity registry for the IoT Hub where it was provisioned.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/how-to-unprovision-devices
HOTSPOT -
You have an Azure IoT Central application that has a custom device template.
You need to configure the device template to support the following activities:
✑ Return the reported power consumption.
✑ Configure the desired fan speed.
✑ Run the device reset routine.
✑ Read the fan serial number.
Which option should you use for each activity? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Hot Area:
Answer :
A device template in Azure IoT Central is a blueprint that defines the:
✑ Telemetry a device sends to IoT Central.
✑ Properties a device synchronizes with IoT Central.
✑ Commands that IoT Central calls on a device.
Box 1: Measurement -
Telemetry/measurement is a stream of values sent from the device, typically from a sensor. For example, a sensor might report the ambient temperature.
Box 2: Properties -
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it's trying to reach. You can set writeable properties from IoT Central.
Box 3: Properties -
Box 4: Command -
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference:
https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
DRAG DROP -
You have an Azure IoT Central application that includes a Device Provisioning Service instance.
You need to connect IoT devices to the application without first registering the devices.
In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order.
Select and Place:
Answer :
Step 1: Obtain the credential -
Obtain the group primary key from the IoT Central enrollment group.
Step 2: Generate device credentials
The group primary key used to generate device credentials
Step 3: Flash unique credentials to the devices
The OEM flashes each device with a device ID, a generated device SAS key, and the application ID scope value.
Step 4: Connect the devices to IoT Central
Step 5: Associate the devices to a template and approve the connections
Reference:
https://docs.microsoft.com/en-us/azure/iot-central/core/concepts-get-connected
You have an Azure IoT Central application.
You need to connect an IoT device to the application.
Which two settings do you require in IoT Central to configure the device? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer : AC
Required connection information:
✑ Group primary key: In your IoT Central application, navigate to Administration > Device Connection > SAS-IoT-Devices. Make a note of the shared access signature Primary key value.
✑ ID scope: In your IoT Central application, navigate to Administration > Device Connection. Make a note of the ID scope value.
Reference:
https://docs.microsoft.com/bs-cyrl-ba/azure/iot-central/core/tutorial-connect-device-python
You have an existing Azure IoT hub.
You use IoT Hub jobs to schedule long running tasks on connected devices.
Which three operations do the IoT Hub jobs support directly? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answer : BCF
Consider using jobs when you need to schedule and track progress any of the following activities on a set of devices:
✑ Invoke direct methods
✑ Update desired properties
✑ Update tags
Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-jobs
You have an Azure IoT hub.
You need to recommend a solution to scale the IoT hub automatically.
What should you include in the recommendation?
Answer : B
Note: IoT Hub is scaled and priced based on an allowed number of messages per day across all devices connected to that IoT Hub. If you exceed the allowed message threshold for your chosen tier and number of units, IoT Hub will begin rejecting new messages. To date, there is no built-in mechanism for automatically scaling an IoT Hub to the next level of capacity if you approach or exceed that threshold.
Reference:
https://docs.microsoft.com/en-us/samples/azure-samples/iot-hub-dotnet-autoscale/iot-hub-dotnet-autoscale/
You have an Azure IoT hub that uses a Device Provisioning Service instance.
You create a new individual device enrollment that uses symmetric key attestation.
Which detail from the enrollment is required to auto provision the device by using the Device Provisioning Service?
Answer : A
The registration ID is used to uniquely identify a device registration with the Device Provisioning Service. The device ID must be unique in the provisioning service
ID scope. Each device must have a registration ID.
Note: An individual enrollment is an entry for a single device that may register. Individual enrollments may use either X.509 leaf certificates or SAS tokens (from a physical or virtual TPM) as attestation mechanisms. The registration ID in an individual enrollment is alphanumeric, lowercase, and may contain hyphens.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service#enrollment
You have an Azure IoT hub that uses a Device Provisioning Service instance to automate the deployment of Azure IoT Edge devices.
The IoT Edge devices have a Trusted Platform Module (TPM) 2.0 chip.
From the Azure portal, you plan to add an individual enrollment to the Device Provisioning Service that will use the TPM of the IoT Edge devices as the attestation mechanism.
Which detail should you obtain before you can create the enrollment?
Answer : D
The TPM simulator's Registration ID and the Endorsement key, are used when you create an individual enrollment for your device.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-auto-provision-simulated-device-linux
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have devices that connect to an Azure IoT hub. Each device has a fixed GPS location that includes latitude and longitude.
You discover that a device entry in the identity registry of the IoT hub is missing the GPS location.
You need to configure the GPS location for the device entry. The solution must prevent the changes from being propagated to the physical device.
Solution: You use an Azure policy to apply tags to a resource group.
Does the solution meet the goal?
Answer : B
Instead tags should be added to the Device twin.
Tags: A section of the JSON document that the solution back end can read from and write to. Tags are not visible to device apps.
Reference:
https://docs.microsoft.com/de-de/azure/iot-hub/iot-hub-devguide-device-twins https://azure.microsoft.com/sv-se/blog/deep-dive-into-azure-iot-hub-notifications-and-device-twin/
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have devices that connect to an Azure IoT hub. Each device has a fixed GPS location that includes latitude and longitude.
You discover that a device entry in the identity registry of the IoT hub is missing the GPS location.
You need to configure the GPS location for the device entry. The solution must prevent the changes from being propagated to the physical device.
Solution: You add tags to the device twin.
Does the solution meet the goal?
Answer : A
Tags are not synced.
Tags: A section of the JSON document that the solution back end can read from and write to. Tags are not visible to device apps.
Reference:
https://docs.microsoft.com/de-de/azure/iot-hub/iot-hub-devguide-device-twins https://azure.microsoft.com/sv-se/blog/deep-dive-into-azure-iot-hub-notifications-and-device-twin/
You have an existing Azure IoT hub.
You use IoT Hub jobs to schedule long running tasks on connected devices.
Which two operations do the IoT Hub jobs support directly? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Answer : BC
Consider using jobs when you need to schedule and track progress any of the following activities on a set of devices:
✑ Invoke direct methods
Update desired properties -
You have 1,000 IoT devices that connect to an Azure IoT hub.
Each device has a property tag named city that is used to store the location of the device.
You need to update the properties on all the devices located at an office in the city of Seattle as quickly as possible. Any new devices in the Seattle office that are added to the IoT hub must receive the updated properties also.
What should you do?
Answer : A
Automatic device management in Azure IoT Hub automates many of the repetitive and complex tasks of managing large device fleets. With automatic device management, you can target a set of devices based on their properties, define a desired configuration, and then let IoT Hub update the devices when they come into scope. This update is done using an automatic device configuration or automatic module configuration, which lets you summarize completion and compliance, handle merging and conflicts, and roll out configurations in a phased approach.
Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-automatic-device-management
You have an Azure IoT Central application.
You add an IoT device named Oven1 to the application. Oven1 uses an IoT Central template for industrial ovens.
You need to send an email to the managers group at your company as soon as the oven temperature falls below 400 degrees.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
Answer : BE
Devices use telemetry to send numerical data from the device. A rule triggers when the selected telemetry crosses a specified threshold.
E: To create a telemetry rule, the device template must include at least one telemetry value. The rule monitors the temperature reported by the device and sends an email when it falls below 400 degrees.
B: Configure the rule conditions.
Conditions define the criteria that the rule monitors. In this tutorial, you configure the rule to fire when the temperature exceeds 70ֲ° F.
1. Select Temperature in the Telemetry dropdown.
2. Next, choose Is less than as the Operator and enter 400 as the Value.
You have an Azure IoT solution that includes multiple Azure IoT hubs in different geographic locations and a single Device Provision Service instance.
You need to configure device enrollment to assign devices to the appropriate IoT hub based on the following requirements:
✑ The registration ID of the device
The geographic location of the device
The load between the IoT hubs in the same geographic location must be balanced.
What should you use to assign the devices to the IoT hubs?
Answer : A
Set the Device Provisioning Service allocation policy
The allocation policy is a Device Provisioning Service setting that determines how devices are assigned to an IoT hub. There are three supported allocation policies:
✑ Lowest latency: Devices are provisioned to an IoT hub based on the hub with the lowest latency to the device.
✑ Evenly weighted distribution (default): Linked IoT hubs are equally likely to have devices provisioned to them. This is the default setting. If you are provisioning devices to only one IoT hub, you can keep this setting.
✑ Static configuration via the enrollment list: Specification of the desired IoT hub in the enrollment list takes priority over the Device Provisioning Service-level allocation policy.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/tutorial-provision-multiple-hubs
You are developing an Azure IoT Central application.
You add a new custom device template to the application.
You need to add a fixed location value to the device template. The value must be updated by the physical IoT device, read-only to device operators, and not graphed by IoT Central.
What should you add to the device template?
Answer : A
For example, a builder can create a device template for a connected fan that has the following characteristics:
✑ Sends temperature telemetry
✑ Sends location property
Reference:
https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Have any questions or issues ? Please dont hesitate to contact us