You have an Azure subscription that contains an Azure IoT hub, 500 IoT devices, and an Azure Time Series Insights Gen2 environment named Environment1.
You need to add calculated values to the Time Series Model.
What should you use?
Time Series Model types help you define variables or formulas for doing computations. Types are associated with a specific instance.
A type can have one or more variables. For example, a Time Series Model instance might be of type Temperature Sensor, which consists of the variables avg temperature, min temperature, and max temperature.
https://docs.microsoft.com/en-us/azure/time-series-insights/concepts-model-overview
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 are developing a custom Azure IoT Edge module.
The module needs to identify the device ID of the local device.
Solution: You configure the module to read the IOTEDGE_DEVICEID environment variable.
Does this meet the goal?
The Azure ID of the current device is available on the IOTEDGE_DEVICEID environment variable.
Instead read the device ID of the device twin.
Note: Device twins are JSON documents that store device state information including metadata, configurations, and conditions. Azure IoT Hub maintains a device twin for each device that you connect to IoT Hub.
Device identity properties. The root of the device twin JSON document contains the read-only properties from the corresponding device identity stored in the identity registry.
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twins
You have an Azure subscription that contains a resource group named RG1.
You need to deploy the Device Provisioning Service. The solution must ensure that the Device Provisioning Service can accept new device enrollments.
You create a Device Provisioning Service instance.
Which two actions should you perform next? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A: The Device Provisioning Service can only provision devices to IoT hubs that have been linked to it.
C: Allocation policy. The service-level setting that determines how Device Provisioning Service assigns devices to an IoT hub. There are three supported allocation policies:
Lowest latency: devices are provisioned to an IoT hub with the lowest latency to the device. Evenly weighted distribution
Static configuration via the enrollment list
https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/concepts-service
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?
An enrollment is the record of devices or groups of devices that may register through auto-provisioning. The enrollment record contains information about the device or group of devices, including:
the attestation mechanism used by the device
the optional initial desired configuration desired IoT hub
the desired device ID
Note: Azure IoT auto-provisioning can be broken into three phases:
1. Service configuration - a one-time configuration of the Azure IoT Hub and IoT Hub Device Provisioning Service instances, establishing them and creating linkage between them.
2. Device enrollment - the process of making the Device Provisioning Service instance aware of the devices that will attempt to register in the future. Enrollment is accomplished by configuring device identity information in the provisioning service, as either an 'individual enrollment' for a single device, or a 'group enrollment' for multiple devices.
3. Device registration and configuration
https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service#enrollment
You have an Azure subscription named Sub1.
You need to ensure that when a new Azure loT hub is created in Sub1, a warning appears indicating that communication must be allowed only from known networks. The solution must minimize development and administrative effort.
What should you include in the solution?
