This page was exported from Free Exam Dumps Collection [ http://free.examcollectionpass.com ] Export date:Wed Oct 23 13:25:44 2024 / +0000 GMT ___________________________________________________ Title: Updated May 07, 2022 AZ-220 Exam Dumps - PDF Questions and Testing Engine [Q23-Q40] --------------------------------------------------- Updated May 07, 2022 AZ-220  Exam Dumps - PDF Questions and Testing Engine New (2022) Microsoft AZ-220  Exam Dumps NO.23 You need to route events in Azure Digital Twins to a downstream service for additional processing.Which type of output endpoint can you use?  Azure Event Hubs  Azure Queue storage  Microsoft Power Bl  Azure Table storage ExplanationCreate an endpoint for Azure Digital Twins.These are the supported types of endpoints that you can create for your instance:* Event Grid* Event Hubs* Service BusNote: In Azure Digital Twins, you can route event notifications to downstream services or connected compute resources. This is done by first setting up endpoints that can receive the events. You can then create event routes that specify which events generated by Azure Digital Twins are delivered to which endpoints.Reference:https://docs.microsoft.com/en-us/azure/digital-twins/how-to-manage-routesNO.24 You have an Azure IoT Edge solution.You plan to deploy an Azure Security Center for IoT security agent. You need to configure the security agent to meet the following requirements:Connection events must be reported as high priority.High priority events must be collected every seven minutes.How should you configure the azureiotsecurity module twin? To answer, drag the appropriate values to the correct locations. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.NOTE: Each correct selection is worth one point. NO.25 You are troubleshooting an Azure IoT hub.You discover that some telemetry messages are dropped before they reach downstream processing. You suspect that IoT Hub throttling is the root cause.Which log in the Diagnostics settings of the IoT hub should you use to capture the throttling error events?  Routes  DeviceTelemetry  Connections  C2DCommands ExplanationThe device telemetry category tracks errors that occur at the IoT hub and are related to the telemetry pipeline.This category includes errors that occur when sending telemetry events (such as throttling) and receiving telemetry events (such as unauthorized reader). This category cannot catch errors caused by code running on the device itself.Note: The metric d2c.telemetry.ingress.sendThrottle is the number of throttling errors due to device throughput throttles.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-healthNO.26 You have an Azure IoT solution that includes multiple Azure IoT hubs in different geographic locations and a single Device Provision Service instance.You need to configure device enrollment to assign devices to the appropriate IoT hub based on the following requirements:* The registration ID of the device* The geographic location of the deviceThe load between the IoT hubs in the same geographic location must be balanced.What should you use to assign the devices to the IoT hubs?  Static configuration (via enrollment list only)  Lowest latency  Evenly weighted distribution  Custom (Use Azure Function) ExplanationSet the Device Provisioning Service allocation policyThe allocation policy is a Device Provisioning Service setting that determines how devices are assigned to an IoT hub. There are three supported allocation policies:* Lowest latency: Devices are provisioned to an IoT hub based on the hub with the lowest latency to the* device.* Evenly weighted distribution (default): Linked IoT hubs are equally likely to have devices provisioned to them. This is the default setting. If you are provisioning devices to only one IoT hub, you can keep this setting.* Static configuration via the enrollment list: Specification of the desired IoT hub in the enrollment list takes priority over the Device Provisioning Service-level allocation policy.Reference:https://docs.microsoft.com/en-us/azure/iot-dps/tutorial-provision-multiple-hubsNO.27 What should you do to identify the cause of the connectivity issues?  Send cloud-to-device messages to the IoT devices.  Use the heartbeat pattern to send messages from the IoT devices to iothub1.  Monitor the connection status of the device twin by using an Azure function.  Enable the collection of the Connections diagnostics logs and set up alerts for the connected devices count metric. 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 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 Provision and manage devices Question Set 2NO.28 You have an Azure IoT solution that includes a basic tier Azure IoT hub named Hub1 and a Raspberry Pi device named Device1. Device1 connects to Hub1.You back up Device1 and restore the backup to a new Raspberry Pi device.When you start the new Raspberry Pi device, you receive the following error message in the diagnostic logs of Hub1: “409002 LinkCreationConflict.” You need to ensure that Device1 and the new Raspberry Pi device can run simultaneously without error.Which two actions should you perform? Each correct answer presents part of the solution.NOTE: Each correct selection is worth one point.  On the new Raspberry Pi device, modify the connection string.  From Hub1, modify the device shared access policy.  Upgrade Hub1 to the standard tier.  From Hub1, create a new consumer group.  From Hub1, create a new IoT device. ExplanationNote: SymptomsYou see the error 409002 LinkCreationConflict in logs along with device disconnection or cloud-to-device message failure.CauseGenerally, this error happens when IoT Hub detects a client has more than one connection. In fact, when a new connection request arrives for a device with an existing connection, IoT Hub closes the existing connection with this error.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-troubleshoot-error-409002-linkcreationconflict#symptomhttps://devblogs.microsoft.com/iotdev/understand-different-connection-strings-in-azure-iot-hub/NO.29 You have an Azure subscription that contains an Azure IoT hub and two IoT devices named Device1 and Device2.You plan to deploy an Azure IoT Edge gateway device named Gateway1.You need to ensure that all device-to-cloud messages and twin change notifications from Device1 and Device2 to the IoT hub are routed by using Gateway1.What tasks should you perform to configure the devices? To answer, select the appropriate options in the answer area.NOTE: Each correct selection is worth one point. Reference:https://docs.microsoft.com/en-us/azure/iot-edge/how-to-authenticate-downstream-deviceNO.30 You have an Azure IoT solution.You need to test that the solution remains functional if IoT Hub is affected by a regional outage.What should you do?  From the loT hub, set Allow public network access to Disabled.  From the loT hub, start a manual failover.  From the Device Provisioning Service (DPS), unlink the loT hub.  From the loT hub, select Disable fallback route. Manual failover is a feature of the IoT Hub service that allows customers to failover their hub’s operations from a primary region to the corresponding Azure geo-paired region. Manual failover can be done in the event of a regional disaster or an extended service outage. You can also perform a planned failover to test your disaster recovery capabilities, although we recommend using a test IoT hub rather than one running in production.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/tutorial-manual-failoverNO.31 From the Device Provisioning Service, you create an enrollment as shown in the exhibit. (Click the Exhibit tab.)You need to deploy a new IoT device.What should you use as the device identity during attestation?  a self-signed X.509 certificate  the random string of alphanumeric characters  the HMACSHA256 hash of the device’s registration ID  the endorsement key of the device’s Trusted Platform Module (TPM) Each device uses its derived device key with your unique registration ID to perform symmetric key attestation with the enrollment during provisioning. To generate the device key, use the key you copied from your DPS enrollment to compute an HMAC-SHA256 of the unique registration ID for the device and convert the result into Base64 format.Reference:https://docs.microsoft.com/en-us/azure/iot-edge/how-to-auto-provision-symmetric-keysNO.32 You have an Azure IoT hub that receives messages from an IoT device. The messages are serialized as Protobuf.You need the IoT hub to route the messages.What should you do first?  From the Azure portal, add desired properties to the device twin.  Configure the loT device to add application properties to the messages.  From the Azure portal, configure the loT hub to add message enrichments.  Configure the loT device to add ASCII-encoded properties to the body of the messages. ExplanationDevice twins store device-related information that:Device and back ends can use to synchronize device conditions and configuration.The solution back end can use to query and target long-running operations.Desired properties. Used along with reported properties to synchronize device configuration or conditions. The solution back end can set desired properties, and the device app can read them. The device app can also receive notifications of changes in the desired properties.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-device-twinsTopic 1, ADatumCase StudyThis is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other question on this case study.At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next sections of the exam. After you begin a new section, you cannot return to this section.To start the case studyTo display the first question on this case study, click the button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the button to return to the question.Requirements. Planned ChangesADatum is developing an Azure IoT solution to monitor environmental conditions. The IoT solution consists of hardware devices and cloud services. All the devices will communicate directly to Azure IoT Hub.The hardware devices will be deployed to the branch offices and will collect data about various environmental conditions such as temperature, humidity, air quality, and noise level. The devices will be wired by using Power over Ethernet (PoE) connections.ADatum is developing the solution in the following three phases: proof of value (POV), pilot, and production.Requirements. POV RequirementsThe POV phase will demonstrate that a technical solution is viable. During this phase, 100 devices will be deployed to the main office and Azure Stream Analytics will be connected to an IoT hub to generate real-time alerts. Stream Analytics will perform the following processing:* Calculate the median rate of the telemetry across the entire devices that exceed the median rate by a factor of 4.* Compare the current telemetry to the specified thresholds and issue alerts when telemetry values are out of range.* Ensure that all message content during this phase is human readable to simplify debugging.Requirements. Pilot RequirementsDuring the pilot phase, devices will be deployed to 10 offices. Each office will have up to 1,000 devices.During this phase, you will add Azure Time Series Insights in parallel to Stream Analytics to support real-time graphs and queries in a dashboard web app.The pilot deployment must minimize operating costs.Requirements. Production RequirementsThe production phase will include all the offices.The production deployment will have one IoT hub in each Azure region. Devices must connect to the IoT hub in their region.The production phase must meet the following requirements:* Ensure that the IoT solution can support performance and scale targets.* Ensure that the IoT solution support up to 1,000 devices per office.* Minimize operating costs of the IoT solution.Requirements. Technical RequirementsDatum identifies the following requirements for the planned IoT solution:* The solution must generate real-time alerts when a fire condition is detected in an office. All the devices in that office must trigger an audible alarm siren within 10 seconds of the alert.* A dashboard UI must display alerts and the system status in real time and must allow device operators to make adjustments to the system.* Each device will send hourly updates to IoT Hub. Condition alerts will be sent immediately.* Multiple types of devices will collect telemetry that has different schemas.* IoT Hub must perform message routing based on the message body.* Direct methods must be used for cloud-to-device communication.* Reports must be provided monthly, quarterly, and annually.* Stored data queries must be as efficient as possible.* The device message size will be under 4 KB.* Development effort must be minimized.Requirements. Throttle and QuotasThe relevant throttles and quotas for various IoT Hub tiers are shown in the following table.Requirements. IoT Hub RoutingYou plan to implement IoT Hub routing during the POV phase as shown in the following exhibit.NO.33 How should you complete the GROUP BYclause to meet the Streaming Analytics requirements?  GROUP BY HoppingWindow(Second, 60, 30)  GROUP BY TumblingWindow(Second, 30)  GROUP BY SlidingWindow(Second, 30)  GROUP BY SessionWindow(Second, 30, 60) Scenario: You plan to use a 30-second period to calculate the average temperature reading of the sensors.Tumbling window functions are used to segment a data stream into distinct time segments and perform a function against them, such as the example below. The key differentiators of a Tumbling window are that they repeat, do not overlap, and an event cannot belong to more than one tumbling window.Incorrect Answers:A: Hopping window functions hop forward in time by a fixed period. It may be easy to think of them as Tumbling windows that can overlap, so events can belong to more than one Hopping window result set.Reference:https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-window-functions Process and manage data Testlet 2 Case Study This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.To start the case studyTo display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.Requirements. Planned ChangesADatum is developing an Azure IoT solution to monitor environmental conditions. The IoT solution consists of hardware devices and cloud services. All the devices will communicate directly to Azure IoT Hub.The hardware devices will be deployed to the branch offices and will collect data about various environmental conditions such as temperature, humidity, air quality, and noise level. The devices will be wired by using Power over Ethernet (PoE) connections.ADatum is developing the solution in the following three phases: proof of value (POV), pilot, and production.Requirements. POV RequirementsThe POV phase will demonstrate that a technical solution is viable. During this phase, 100 devices will be deployed to the main office and Azure Stream Analytics will be connected to an IoT hub to generate real-time alerts. Stream Analytics will perform the following processing:* Calculate the median rate of the telemetry across the entire device fleet and issue alerts for devices that exceed the median rate by a factor of 4.* Compare the current telemetry to the specified thresholds and issue alerts when telemetry values are out of range.* Ensure that all message content during this phase is human readable to simplify debugging.Requirements. Pilot RequirementsDuring the pilot phase, devices will be deployed to 10 offices. Each office will have up to 1,000 devices.During this phase, you will add Azure Time Series Insights in parallel to Stream Analytics to support real-time graphs and queries in a dashboard web app.The pilot deployment must minimize operating costs.Requirements. Production RequirementsThe production phase will include all the offices.The production deployment will have one IoT hub in each Azure region. Devices must connect to the IoT hub in their region.The production phase must meet the following requirements:* Ensure that the IoT solution can support performance and scale targets.* Ensure that the IoT solution supports up to 1,000 devices per office.* Minimize operating costs of the IoT solution.Requirements. Technical RequirementsDatum identifies the following requirements for the planned IoT solution:* The solution must generate real-time alerts when a fire condition is detected in an office. All the devices in that office must trigger an audible alarm siren within 10 seconds of the alert.* A dashboard UI must display alerts and the system status in real time and must allow device operators to make adjustments to the system.* Each device will send hourly updates to IoT Hub. Condition alerts will be sent immediately.* Multiple types of devices will collect telemetry that has different schemas.* IoT Hub must perform message routing based on the message body.* Direct methods must be used for cloud-to-device communication.* Reports must be provided monthly, quarterly, and annually.* Stored data queries must be as efficient as possible.* The device message size will be under 4 KB.* Development effort must be minimized.Requirements. Throttle and QuotasThe relevant throttles and quotas for various IoT Hub tiers are shown in the following table.Requirements. IoT Hub RoutingYou plan to implement IoT Hub routing during the POV phase as shown in the following exhibit.NO.34 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.  From the Linked IoT hubs blade of the Device Provisioning Service, link an Azure IoT hub.  From the Azure portal, create a new Azure IoT hub.  From the Manage allocation policy blade of the Device Provisioning Service, configure an allocation policy.  From the Certificates blade of the Device Provisioning Service, upload an X.509 certificate to the Device Provisioning Service. ExplanationA: 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 Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/concepts-serviceNO.35 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. ExplanationStep 1: Run the following commandsInstall 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-engineInstall the Moby command-line interface (CLI). The CLI is useful for development but optional for production deployments.sudo apt-get install moby-cliInstall the security daemon. The package is installed at /etc/iotedge/.sudo apt-get install iotedgeStep 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 portal1. 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.yamlFind 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 iotedgeReference:https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edge-linuxNO.36 You are troubleshooting an Azure IoT hub.You discover that some telemetry messages are dropped before they reach downstream processing.You suspect that IoT Hub throttling is the root cause.Which log in the Diagnostics settings of the IoT hub should you use to capture the throttling error events?  Routes  DeviceTelemetry  Connections  C2DCommands The device telemetry category tracks errors that occur at the IoT hub and are related to the telemetry pipeline.This category includes errors that occur when sending telemetry events (such as throttling) and receiving telemetry events (such as unauthorized reader). This category cannot catch errors caused by code running on the device itself.Note: The metric d2c.telemetry.ingress.sendThrottle is the number of throttling errors due to device throughput throttles.Reference:https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-healthNO.37 How should you complete the GROUP BY clause to meet the Streaming Analytics requirements?  GROUP BY HoppingWindow(Second, 60, 30)  GROUP BY TumblingWindow(Second, 30)  GROUP BY SlidingWindow(Second, 30)  GROUP BY SessionWindow(Second, 30, 60) Scenario: You plan to use a 30-second period to calculate the average temperature reading of the sensors.Tumbling window functions are used to segment a data stream into distinct time segments and perform a function against them, such as the example below. The key differentiators of a Tumbling window are that they repeat, do not overlap, and an event cannot belong to more than one tumbling window.InAnswers:A: Hopping window functions hop forward in time by a fixed period. It may be easy to think of them as Tumbling windows that can overlap, so events can belong to more than one Hopping window result set.Reference:https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-window-functionsTopic 1, ContosoTo start the case studyTo display the first question on this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.Existing Environment. Current State of DevelopmentContoso produces a set of Bluetooth sensors that read the temperature and humidity. The sensors connect to IoT gateway devices that relay the data.All the IoT gateway devices connect to an Azure IoT hub named iothub1.Existing Environment. Device TwinYou plan to implement device twins by using the following JSON sample.Existing Environment. Azure Stream AnalyticsEach room will have between three to five sensors that will generate readings that are sent to a single IoT gateway device. The IoT gateway device will forward all the readings to iothub1 at intervals of between 10 and 60 seconds.You plan to use a gateway pattern so that each IoT gateway device will have its own IoT Hub device identity.You draft the following query, which is missing the GROUP BY clause.SELECTAVG(temperature),System.TimeStamp() AS AsaTimeFROMIothubYou plan to use a 30-second period to calculate the average temperature reading of the sensors.You plan to minimize latency between the condition reported by the sensors and the corresponding alert issued by the Stream Analytics job.Existing Environment. Device MessagesThe IoT gateway devices will send messages that contain the following JSON data whenever the temperature exceeds a specified threshold.The level property will be used to route the messages to an Azure Service Bus queue endpoint named criticalep.Existing Environment. IssuesYou discover connectivity issues between the IoT gateway devices and iothub1, which cause IoT devices to lose connectivity and messages.Requirements. Planning ChangesContoso plans to make the following changes:Use Stream Analytics to process and view data.Use Azure Time Series Insights to visualize data.Implement a system to sync device statuses and required settings.Add extra information to messages by using message enrichment.Create a notification system to send an alert if a condition exceeds a specified threshold.Implement a system to identify what causes the intermittent connection issues and lost messages.Requirements. Technical RequirementsContoso must meet the following requirements:Use the built-in functions of IoT Hub whenever possible.Minimize hardware and software costs whenever possible.Minimize administrative effort to provision devices at scale.Implement a system to trace message flow to and from iothub1.Minimize the amount of custom coding required to implement the planned changes.Prevent read operations from being negatively affected when you implement additional services.NO.38 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.  X.509 certificates  Trusted Platform Module (TPM) 2.0  Trusted Platform Module (TPM) 1.2  Symmetric key  Device Identity Composition Engine (DICE)D18912E1457D5D1DDCBD40AB3BF70D5D  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. The Device Provisioning Service supports the following forms of attestation:Reference:https://docs.microsoft.com/en-us/azure/iot-dps/concepts-service#attestation-mechanismNO.39 You have an Azure IoT hub that uses a Device Provisioning Service instance.You have 1,000 legacy IoT devices that only support MAC address or serial number identities. The device do NOT have a security feature that can be used to securely identify the device or a hardware security module (HSM).You plan to deploy the devices to a secure environment.You need to configure the Device Provisioning Service instance to ensure that all the devices are identified securely before they receive updates.Which attestation mechanism should you choose?  Trusted Platform Module (TPM) 1.2 attestation  symmetric key attestation  X.509 certificates ExplanationA common problem with many legacy devices is that they often have an identity that is composed of a single piece of information. This identity information is usually a MAC address or a serial number. Legacy devices may not have a certificate, TPM, or any other security feature that can be used to securely identify the device.The Device Provisioning Service for IoT hub includes symmetric key attestation. Symmetric key attestation can be used to identify a device based off information like the MAC address or a serial number.Reference:https://docs.microsoft.com/bs-latn-ba/azure/iot-dps/how-to-legacy-device-symm-keyNO.40 You have 100 devices that connect to an Azure IoT hub.You need to be notified about failed local logins to a subnet of the devices.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. 1 – Enable Azure Security Center for IoT2 – Select a device security groupReference:https://docs.microsoft.com/bs-latn-ba/azure/asc-for-iot/how-to-security-data-accesshttps://docs.microsoft.com/en-us/rest/api/securitycenter/devicesecuritygroups/createorupdate Loading … Updated Verified Pass AZ-220 Exam - Real Questions and Answers: https://www.examcollectionpass.com/Microsoft/AZ-220-practice-exam-dumps.html --------------------------------------------------- Images: https://free.examcollectionpass.com/wp-content/plugins/watu/loading.gif https://free.examcollectionpass.com/wp-content/plugins/watu/loading.gif --------------------------------------------------- --------------------------------------------------- Post date: 2022-05-07 22:39:34 Post date GMT: 2022-05-07 22:39:34 Post modified date: 2022-05-07 22:39:34 Post modified date GMT: 2022-05-07 22:39:34