Download Microsoft.AZ-220.TestKing.2020-04-21.36q.vcex

Download Exam

File Info

Exam Microsoft Azure IoT Developer
Number AZ-220
File Name Microsoft.AZ-220.TestKing.2020-04-21.36q.vcex
Size 1 MB
Posted Apr 21, 2020
Download Microsoft.AZ-220.TestKing.2020-04-21.36q.vcex

How to open VCEX & EXAM Files?

Files with VCEX & EXAM extensions can be opened by ProfExam Simulator.

Download
ProfExam Simulator

Purchase

Coupon: MASTEREXAM
With discount: 20%





Demo Questions

Question 1

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 question, 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?


  1. Yes
  2. No
Correct answer: A
Explanation:
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:1. 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.2. 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
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:
1. 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.
2. 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.



Question 2

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 question, 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?


  1. Yes
  2. No
Correct answer: B
Explanation:
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
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.



Question 3

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 question, 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?


  1. Yes
  2. No
Correct answer: B
Explanation:
Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-unprovision-devices



Question 4

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?


  1. a device-to-cloud message
  2. the device twin reported properties
  3. a cloud-to-device message
  4. a direct method
Correct answer: D
Explanation:
Explanation: 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/
Explanation: 
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.



Question 5

You have an IoT device that gathers data in a CSV file named Sensors.csv.
You deploy an Azure IoT hub that is accessible at ContosoHub.azure-devices.net.
You need to ensure that Sensors.csv is uploaded to the IoT hub.
Which two actions should you perform? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.


  1. Upload Sensors.csv by using the IoT Hub REST API.
  2. From the Azure subscription, select the IoT hub, select Message routing, and then configure a route to storage.
  3. From the Azure subscription, select the IoT hub, select File upload, and then configure a storage container.
  4. Configure the device to use a GET request to ContosoHub.azure-devices.net/devices/ContosoDevice1/files/notifications.
Correct answer: AC
Explanation:
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 ContainersA: 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
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.



Question 6

You plan to deploy an Azure IoT hub.
The IoT hub must support the following:
  •  Three Azure IoT Edge devices
  •  2,500 IoT devices
Each IoT device will spend a 6 KB message every five seconds.
You need to size the IoT hub to support the devices. The solution must minimize costs.
What should you choose?


  1. one unit of the S1 tier
  2. one unit of the B2 tier
  3. one unit of the B1 tier
  4. one unit of the S3 tier
Correct answer: D
Explanation:
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
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 unit
B: B2, S2 can only handle up to 16 MB/minute per unit.



Question 7

You create an Azure IoT hub by running the following command.
az iot hub create --resource-group MyResourceGroup --name MyIotHub --sku B1 --location westus --partition-count 4
What does MylotHub support?


  1. Device Provisioning Service
  2. cloud-to-device messaging
  3. Azure IoT Edge
  4. device twins
Correct answer: A
Explanation:
The Device Provisioning Service is included in the Basic Tiers (such as B1).Incorrect Answers:B, C, D: The Standard tier is needed for cloud-to-device messaging, Azure IoT Edge, and device twins.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-scaling
The Device Provisioning Service is included in the Basic Tiers (such as B1).
Incorrect Answers:
B, C, D: The Standard tier is needed for cloud-to-device messaging, Azure IoT Edge, and device twins.



Question 8

You have an existing Azure IoT hub.
You need to connect physical IoT devices to the IoT hub.
You are connecting the devices through a firewall that allows only port 443 and port 80.
Which three communication protocols can you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.


  1. MQTT over WebSocket
  2. AMQP
  3. AMQP over WebSocket
  4. MQTT
  5. HTTPS
Correct answer: ACE
Explanation:
MQTT over WebSockets, AMQP over WebSocket, and HTTPS use port 443.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
MQTT over WebSockets, AMQP over WebSocket, and HTTPS use port 443.



Question 9

You have an Azure IoT solution that includes an Azure IoT hub and 100 Azure IoT Edge devices.
You plan to deploy the IoT Edge devices to external networks. The firewalls of the external networks only allow traffic on port 80 and port 443.
You need to ensure that the devices can connect to the IoT hub. The solution must minimize costs.
What should you do?


  1. Configure the devices for extended offline operations.
  2. Configure the upstream protocol of the devices to use MQTT over WebSocket.
  3. Connect the external networks to the IoT solution by using ExpressRoute.
  4. Configure the devices to use an HTTPS proxy.
Correct answer: B
Explanation:
MQTT over WebSockets uses port 443.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols



Question 10

What should you do to identify the cause of the connectivity issues?


  1. Send cloud-to-device messages to the IoT devices.
  2. Use the heartbeat pattern to send messages from the IoT devices to iothub1.
  3. Monitor the connection status of the device twin by using an Azure function.
  4. Enable the collection of the Connections diagnostics logs and set up alerts for the connected devices count metric.
Correct answer: D
Explanation:
Scenario: You discover connectivity issues between the IoT gateway devices and iothub1, which cause IoT devices to lose connectivity and messages.To log device connection events and errors, turn on diagnostics for IoT Hub. We recommend turning on these logs as early as possible, because if diagnostic logs aren't enabled, when device disconnects occur, you won't have any information to troubleshoot the problem with.Step 1: Sign in to the Azure portal.Browse to your IoT hub.Select Diagnostics settings.Select Turn on diagnostics.Enable Connections logs to be collected.For easier analysis, turn on Send to Log Analytics (see pricing).Step 2: Set up alerts for device disconnect at scaleTo get alerts when devices disconnect, configure alerts on the Connected devices (preview) metric.Reference:https://docs.microsoft.com/bs-cyrl-ba/azure/iot-hub/iot-hub-troubleshoot-connectivity
Scenario: You discover connectivity issues between the IoT gateway devices and iothub1, which cause IoT devices to lose connectivity and messages.
To log device connection events and errors, turn on diagnostics for IoT Hub. We recommend turning on these logs as early as possible, because if diagnostic logs aren't enabled, when device disconnects occur, you won't have any information to troubleshoot the problem with.
Step 1: 
  1. Sign in to the Azure portal.
  2. Browse to your IoT hub.
  3. Select Diagnostics settings.
  4. Select Turn on diagnostics.
  5. Enable Connections logs to be collected.
  6. For easier analysis, turn on Send to Log Analytics (see pricing).
Step 2: 
Set up alerts for device disconnect at scale
To get alerts when devices disconnect, configure alerts on the Connected devices (preview) metric.









CONNECT US

Facebook

Twitter

PROFEXAM WITH A 20% DISCOUNT

You can buy ProfExam with a 20% discount!

Get Now!


HOW TO OPEN VCEX FILES

Use ProfExam Simulator to open VCEX files