[Oct-2023] Free AZ-220 Exam Questions AZ-220 Actual Free Exam Questions
Verified AZ-220 dumps and 205 unique questions
The Microsoft AZ-220 exam measures the candidate's ability to develop solutions for IoT by using Azure services, including Azure Stream Analytics, Azure IoT Hub, Azure IoT Central, and Azure Event Grid. It also evaluates the candidate's knowledge of IoT security principles and practices, including device security, data security, and network security. Candidates must be able to troubleshoot IoT solutions and apply best practices for scalability, reliability, and performance.
NEW QUESTION # 121
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?
- A. Yes
- B. No
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
NEW QUESTION # 122
You have an Azure IoT solution that contains the Azure IoT Edge devices shown in the following table.
You have the standard deployments and target conditions shown in the following table.
You have the modules shown in the following table.
For each of the following statements, select Yes if the statement is true. Otherwise select No.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation
NEW QUESTION # 123
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?
- A. Yes
- B. No
Answer: A
Explanation:
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
NEW QUESTION # 124
You have an Azure IoT hub named Hub1 and an Azure Time Series Insights environment named tsi1. Tsi1 connects to Hub1. The solution has been operational for 6 months.
Tsi1 is configured as shown in the following exhibit.
Hub1 receives 1 million messages per day. Each message is up to 1 KB and is formatted as JSON.
Hub1 has seven days of retained telemetry.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation
Text, letter Description automatically generated
Reference:
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-overview
NEW QUESTION # 125
You have an Azure solution that contains an Azure loT Edge deployment.
You are configuring an Azure Stream Analytics Edge job as shown in the following exhibit.
How should you complete the query? To answer select the appropriate options m the answer area.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation
NEW QUESTION # 126
You have an Azure loT hub and an loT device that generates the following messages.
You need to route the messages to a custom Azure Event Hubs endpoint. The solution must route only messages that have the following values.
Which query should you use?
- A. Option A
- B. Option D
- C. Option B
- D. Option C
Answer: D
NEW QUESTION # 127
Your company is creating a new camera security system that will use Azure IoT Hub.
You plan to use an Azure IoT Edge device that will run Ubuntu Server 18.04.
You need to configure the IoT Edge device.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation:
Step 1: Run the following commands
Install the container runtime.
Azure IoT Edge relies on an OCI-compatible container runtime. For production scenarios, we recommended that you use the Moby-based engine provided below. The Moby engine is the only container engine officially supported with Azure IoT Edge. Docker CE/EE container images are compatible with the Moby runtime.
Install the Moby engine.
sudo apt-get install moby-engine
Install the Moby command-line interface (CLI). The CLI is useful for development but optional for production deployments.
sudo apt-get install moby-cli
Install the security daemon. The package is installed at /etc/iotedge/.
sudo apt-get install iotedge
Step 2: From IotHub,create an IoT Edge device registry entry.
Note: In your IoT Hub in the Azure portal, IoT Edge devices are created and managed separately from IOT devices that are not edge enabled.
Sign in to the Azure portal and navigate to your IoT hub.
In the left pane, select IoT Edge from the menu.
Select Add an IoT Edge device.
Provide a descriptive device ID. Use the default settings to auto-generate authentication keys and connect the new device to your hub.
Select Save.
Retrieve the connection string in the Azure portal
1. 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.
2. From the IoT Edge page in the portal, click on the device ID from the list of IoT Edge devices.
3. Copy the value of either Primary Connection String or Secondary Connection String.
Step 3: Add the connection string to..
To manually provision a device, you need to provide it with a device connection string that you can create by registering a new device in your IoT hub.
Open the configuration file.
sudo nano /etc/iotedge/config.yaml
Find the provisioning configurations of the file and uncomment the Manual provisioning configuration section. Update the value of device_connection_string with the connection string from your IoT Edge device.
Save and close the file.
After entering the provisioning information in the configuration file, restart the daemon:
sudosystemctl restart iotedge
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux
NEW QUESTION # 128
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?
- A. Emit custom metrics from the IoT device code and create an Azure Automation runbook alert.
- B. Create an Azure function that retrieves the quota metrics of the IoT hub.
- C. Create an SMS alert in IoT Hub for the Total number of messages used metric.
- D. Configure autoscaling in Azure Monitor.
Answer: B
Explanation:
Explanation
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/
NEW QUESTION # 129
You have an Azure IoT hub and three Azure IoT Edge devices. The device twin code for each device is shown in the following table.
A standard automatic deployment is already applied.
You have three layered deployments. The deployment code for each deployment is shown in the following table.
For each of the following statements, select Yes if the statement is true. Otherwise select No. NOTE: Each correct selection is worth one point.
Answer:
Explanation:
NEW QUESTION # 130
You need to install the Azure IoT Edge runtime on a new device that runs Windows 10 IoT Enterprise.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation
Step 1: From Azure IoT Hub, create an IoT Edge Device
Step 2: Deploy-IoTEdge
The Deploy-IoTEdge command checks that your Windows machine is on a supported version, turns on the containers feature, and then downloads the moby runtime and the IoT Edge runtime. The command defaults to using Windows containers.
{Invoke-WebRequest -useb https://aka.ms/iotedge-win} | Invoke-Expression; ` Deploy-IoTEdge Step 3: Initialize-IoTEdge The Initialize-IoTEdge command configures the IoT Edge runtime on your machine. The command defaults to manual provisioning with Windows containers.
{Invoke-WebRequest -useb https://aka.ms/iotedge
Step 4: Enter the IoT Edge device connection string.
When prompted, provide the device connection string that you retrieved in step 1. The device connection string associates the physical device with a device ID in IoT Hub.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/module-composition
NEW QUESTION # 131
You are developing an Azure IoT solution for a shipping company. The company's ships will have sensors used for predictive maintenance. Some sensor devices will be MQTT-capable, and others will use Modbus.
Each ship has an internet connection that is available only when the ship is docked.
You create an Azure IoT hub.
You need to implement an IoT solution that uses Azure IoT Edge.
What should you do?
- A. Add the MQTT devices to the loT hub. configure an loT Edge gateway, and set Enable connection to loT Hub to Disable. From the loT Edge gateway device, assign the MQTT devices as child devices of the gateway. Deploy the loT Edge Modbus module.
- B. Add the MQTT devices to the loT hub and configure an loT Edge gateway. From the loT Edge gateway device, assign the MQTT devices as child devices of the gateway. Use the File upload feature of loT Hub when internet connectivity is available.
- C. Add the MQTT devices to the loT hub and configure an loT Edge gateway. From the loT Edge gateway device, assign the MQTT devices as child devices of the gateway. Deploy an loT Edge Modbus module.
- D. Configure an loT Edge gateway. Deploy an loT Edge Modbus module. From the Azure portal, create loT devices and add connection strings to the devices.
Answer: A
Explanation:
https://docs.microsoft.com/en-us/azure/iot-edge/deploy-modbus-gateway
NEW QUESTION # 132
Your company is creating a new camera security system that will use Azure IoT Hub.
You plan to use an Azure IoT Edge device that will run Ubuntu Server 18.04.
You need to configure the IoT Edge device.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
Explanation:
Step 1: Run the following commands
Install the container runtime.
Azure IoT Edge relies on an OCI-compatible container runtime. For production scenarios, we recommended that you use the Moby-based engine provided below. The Moby engine is the only container engine officially supported with Azure IoT Edge. Docker CE/EE container images are compatible with the Moby runtime.
Install the Moby engine.
sudo apt-get install moby-engine
Install the Moby command-line interface (CLI). The CLI is useful for development but optional for production deployments.
sudo apt-get install moby-cli
Install the security daemon. The package is installed at /etc/iotedge/.
sudo apt-get install iotedge
Step 2: From Iot Hub,create an IoT Edge device registry entry.
Note: In your IoT Hub in the Azure portal, IoT Edge devices are created and managed separately from IOT devices that are not edge enabled.
Sign in to the Azure portal and navigate to your IoT hub.
In the left pane, select IoT Edge from the menu.
Select Add an IoT Edge device.
Provide a descriptive device ID. Use the default settings to auto-generate authentication keys and connect the new device to your hub.
Select Save.
Retrieve the connection string in the Azure portal
1. 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.
2. From the IoT Edge page in the portal, click on the device ID from the list of IoT Edge devices.
3. Copy the value of either Primary Connection String or Secondary Connection String.
Step 3: Add the connection string to..
To manually provision a device, you need to provide it with a device connection string that you can create by registering a new device in your IoT hub.
Open the configuration file.
sudo nano /etc/iotedge/config.yaml
Find the provisioning configurations of the file and uncomment the Manual provisioning configuration section. Update the value of device_connection_string with the connection string from your IoT Edge device.
Save and close the file.
After entering the provisioning information in the configuration file, restart the daemon:
sudo systemctl restart iotedge
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linux
NEW QUESTION # 133
You have an Azure IoT hub named Hub1 and a root certification authority (CA) named CA1. Hub1 is configured to use X.509 certificate device authentication.
You and a custom manufacturing partner complete a proof of possession flow.
You plan to deploy IoT devices manufactured by the custom manufacturing partner. Each device will have a certificate generated by an intermediate C You need to ensure that the custom devices can connect successfully to Hub1.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
Answer:
Explanation:
1 - Sign the intermediate CA certificate by using the CA1 certificate.
2 - Sign the device certificate by using the intermediate CA
3 - Deploy the certificate chain to the device.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/concepts-x509-attestation
NEW QUESTION # 134
You have an Azure loT hub
You have four Azure 10T Edge devices and. The device twin code shown in the following table.
You have three deployments and the deployment code shown in the following table.
For each of the following statements, select Yes if the statement is true. Otherwise, select No. NOTE: Each correct selection is worth one point.
Answer:
Explanation:
NEW QUESTION # 135
You plan to deploy Azure Time Series Insights.
What should you create on iothub1 before you deploy Time Series Insights?
- A. a new shared access policy
- B. a new message route
- C. a new consumer group
- D. an IP filter rule
Answer: C
Explanation:
Create a dedicated consumer group in the IoT hub for the Time Series Insights environment to consume from. Each Time Series Insights event source must have its own dedicated consumer group that isn't shared with any other consumer. If multiple readers consume events from the same consumer group, all readers are likely to exhibit failures.
Reference:
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-how-to-add-an-event-source- iothub
NEW QUESTION # 136
You have an Azure IoT hub that uses a Device Provision Service instance.
You plan to deploy 100 IoT devices.
You need to confirm the identity of the devices by using the Device Provision Service.
Which three device attestation mechanisms can you use? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
- A. Trusted Platform Module (TPM) 1.2
- B. Trusted Platform Module (TPM) 2.0
- C. X.509 certificates
- D. Symmetric key
- E. Device Identity Composition Engine (DICE)
Answer: B,C,D
Explanation:
The Device Provisioning Service supports the following forms of attestation:
* X.509 certificates based on the standard X.509 certificate authentication flow.
* Trusted Platform Module (TPM) based on a nonce challenge, using the TPM 2.0 standard for keys to present a signed Shared Access Signature (SAS) token. This does not require a physical TPM on the device, but the service expects to attest using the endorsement key per the TPM spec.
* Symmetric Key based on shared access signature (SAS) Security tokens, which include a hashed signature and an embedded expiration.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service#attestation-mechanism
NEW QUESTION # 137
......
Microsoft AZ-220 (Microsoft Azure IoT Developer) Certification Exam is a crucial certification for IoT developers seeking to enhance their career. AZ-220 exam covers a broad range of topics related to the development and deployment of IoT solutions on the Azure platform, and passing it demonstrates the candidate's expertise in Azure IoT services. Microsoft Azure IoT Developer certification is globally recognized and can lead to numerous career opportunities in IoT development.
Latest 100% Passing Guarantee - Brilliant AZ-220 Exam Questions PDF: https://www.prepawaytest.com/Microsoft/AZ-220-practice-exam-dumps.html
AZ-220 Dumps for Pass Guaranteed - Pass AZ-220 Exam: https://drive.google.com/open?id=1-jsFpxLRgas6Wn7_F4wejrDXqnJyCKGh