Download Microsoft.AZ-220.ExamCollection.2021-07-11.88q.vcex

Box 1: iothub1The Azure IoT hub is named iothub1. Box 2: azure-devices.netThe format of the device connection string looks like:HostName={YourIoTHubName}.azure-devices.net;DeviceId=MyNodeDevice;SharedAccessKey={YourSharedAccessKey} Box 1: device1Device1 has a primary key of Uihuih76hbHb. Reference:https://docs.microsoft.com/en-us/azure/iot-hub/quickstart-control-device-dotnet

You may find it necessary to deprovision devices that were previously auto-provisioned through the Device Provisioning Service. 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/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices

Instead, 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. Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices

Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices

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.warpOperatingThe 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

Releases via the REST API. All of the operations that can be performed from the Console can also be automated using the REST API. You might do this to automate your build and release process, for example. You can build firmware using the Particle CLI or directly using the compile source code API. Note: Over-the-air (OTA) firmware updates are a vital component of any IoT system. Over-the-air firmware updates refers to the practice of remotely updating the code on an embedded device. Reference:https://docs.particle.io/tutorials/device-cloud/ota-updates/

C: To use the file upload functionality in IoT Hub, you must first associate an Azure Storage account with your hub. Select File upload to display a list of file upload properties for the IoT hub that is being modified. For Storage container: Use the Azure portal to select a blob container in an Azure Storage account in your current Azure subscription to associate with your IoT Hub. If necessary, you can create an Azure Storage account on the Storage accounts blade and blob container on the Containers A: IoT Hub has an endpoint specifically for devices to request a SAS URI for storage to upload a file. To start the file upload process, the device sends a POST request to {iot hub}.azure-devices.net/devices/ {deviceId}/files with the following JSON body:{     "blobName": "{name of the file for which a SAS URI will be generated}"} Incorrect Answers:D: Deprecated: initialize a file upload with a GET. Use the POST method instead.Reference:https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/iot-hub/iot-hub-configure-file-upload.md

2500* 6 KB * 12 = 180,000 KB/minute = 180 MB/Minute. B3, S3 can handle up to 814 MB/minute per unit. Incorrect Answers:A, C: B1, S1 can only handle up to 1111 KB/minute per unitB: B2, S2 can only handle up to 16 MB/minute per unit.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-scaling

Step 1: Register a device in IoT HubBefore you can use your IoT devices with Azure IoT Edge, you must register them with your IoT hub. Once a device is registered, you can retrieve a connection string to set up your device for IoT Edge workloads. Step 2: Configure the device connection string on a device client.When you're ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub. Step 3: Trigger a new send event from a device client.Reference:https://docs.microsoft.com/en-us/azure/iot-edge/how-to-register-device

Box 1: AMQPUse AMQP on field and cloud gateways to take advantage of connection multiplexing across devices. Box 2: MQTTMQTT is used on all devices that do not require to connect multiple devices (each with its own per-device credentials) over the same TLS connection. Box 3: HTTPSUse HTTPS for devices that cannot support other protocols. Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols