Here you have the best Microsoft AZ-220 practice exam questions
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 an Azure IoT solution that includes an Azure IoT hub, a Device Provisioning Service instance, and 1,000 connected IoT devices.
All the IoT devices are provisioned automatically by using one enrollment group.
You need to temporarily disable the IoT devices from the connecting to the IoT hub.
Solution: From the Device Provisioning Service, you disable the enrollment group, and you disable device entries in the identity registry of the IoT hub to which the
IoT devices are provisioned.
Does the solution meet the goal?
To temporarily disable the IoT devices from connecting to the IoT hub, you need to perform two primary actions: first, disable the enrollment group in the Device Provisioning Service (DPS) to stop future auto-provisioning of devices, and second, disable the device entries in the identity registry of the IoT hub to prevent existing devices from communicating with the hub. This approach ensures that the devices are temporarily prevented from both auto-provisioning and current communication, effectively meeting the goal.
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 an Azure IoT solution that includes an Azure IoT hub, a Device Provisioning Service instance, and 1,000 connected IoT devices.
All the IoT devices are provisioned automatically by using one enrollment group.
You need to temporarily disable the IoT devices from the connecting to the IoT hub.
Solution: You delete the enrollment group from the Device Provisioning Service.
Does the solution meet the goal?
Deleting the enrollment group from the Device Provisioning Service will prevent new devices from being provisioned. However, it does not affect devices that are already provisioned and connected. To temporarily disable the IoT devices from connecting to the IoT hub, you must disable the enrollment group and disable the device entries in the identity registry of the IoT hub to which the devices are already provisioned.
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 an Azure IoT solution that includes an Azure IoT hub, a Device Provisioning Service instance, and 1,000 connected IoT devices.
All the IoT devices are provisioned automatically by using one enrollment group.
You need to temporarily disable the IoT devices from the connecting to the IoT hub.
Solution: From the IoT hub, you change the credentials for the shared access policy of the IoT devices.
Does the solution meet the goal?
Changing the credentials for the shared access policy of the IoT devices will indeed prevent the devices from connecting to the IoT hub. However, this method is not the most efficient nor temporary, as it requires you to manage and restore the credentials later. A more appropriate solution would be to disable the devices directly from the IoT hub or to temporarily disable the enrollment group, which would effectively and temporarily prevent the devices from connecting.
HOTSPOT -
You have an Azure IoT hub.
You plan to deploy 1,000 IoT devices by using automatic device management.
The device twin is shown below.
You need to configure automatic device management for the deployment.
Which target Condition and Device Twin Path should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: tags.engine.warpDriveType='VM105a'
Use tags to target twins. Before you create a configuration, you must specify which devices or modules you want to affect. Azure IoT Hub identifies devices and using tags in the device twin, and identifies modules using tags in the module twin.
Box 2: properties.desired.warpOperating
The twin path, which is the path to the JSON section within the twin desired properties that will be set.
For example, you could set the twin path to properties.desired.chiller-water and then provide the following JSON content:
{
"temperature": 66,
"pressure": 28
}
Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-automatic-device-management
You plan to deploy a standard tier Azure IoT hub.
You need to perform an over-the-air (OTA) update on devices that will connect to the IoT hub by using scheduled jobs.
What should you use?
To perform an over-the-air (OTA) update on devices connected to an Azure IoT hub using scheduled jobs, you should use a direct method. Direct methods are suitable for triggering specific actions on IoT devices in real-time, such as initiating a firmware update. This option allows the job to invoke the necessary update process on the devices, which aligns with the requirement of performing scheduled OTA updates. While other methods like cloud-to-device messages and device twin properties have their use cases, direct methods are specifically designed for executing precise actions like firmware updates on devices.