You have already completed the Test before. Hence you can not start it again.
Test is loading...
You must sign in or sign up to start the Test.
You have to finish following quiz, to start this Test:
Your results are here!! for" AZ-220 Practice Test 4 "
0 of 56 questions answered correctly
Your time:
Time has elapsed
Your Final Score is : 0
You have attempted : 0
Number of Correct Questions : 0 and scored 0
Number of Incorrect Questions : 0 and Negative marks 0
Average score
Your score
AZ-220: Microsoft Azure IoT Developer
You have attempted: 0
Number of Correct Questions: 0 and scored 0
Number of Incorrect Questions: 0 and Negative marks 0
You can review your answers by clicking view questions. Important Note : Open Reference Documentation Links in New Tab (Right Click and Open in New Tab).
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
Answered
Review
Question 1 of 56
1. Question
You have 100 devices that connect to an Azure IoT hub.You plan to use Azure functions to process all the telemetry messages from the devices before storing the messages.You need to configure the functions binding for the IoT hub.Which two configuration details should you use to configure the binding?
A. the name of the resource group that contains the IoT hub
B. the IoT hub’s connection string shared access key that has Service connect permissions
C. the connection string of the Azure Event Hub-compatible endpoint from the IoT Hub built-in endpoints
D. the Azure Event-Hub compatible name
Correct
C,D
EventHubName: Functions 2.x and higher. The name of the event hub. When the event hub name is also present in the connection string, that value overrides this property at runtime.
Connection: The name of an app setting that contains the connection string to the event hub’s namespace. Copy this connection string by clicking the Connection
Information button for the namespace, not the event hub itself. This connection string must have send permissions to send the message to the event stream.
Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-iot-output
Incorrect
C,D
EventHubName: Functions 2.x and higher. The name of the event hub. When the event hub name is also present in the connection string, that value overrides this property at runtime.
Connection: The name of an app setting that contains the connection string to the event hub’s namespace. Copy this connection string by clicking the Connection
Information button for the namespace, not the event hub itself. This connection string must have send permissions to send the message to the event stream.
Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-iot-output
Unattempted
C,D
EventHubName: Functions 2.x and higher. The name of the event hub. When the event hub name is also present in the connection string, that value overrides this property at runtime.
Connection: The name of an app setting that contains the connection string to the event hub’s namespace. Copy this connection string by clicking the Connection
Information button for the namespace, not the event hub itself. This connection string must have send permissions to send the message to the event stream.
Reference: https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-event-iot-output
Question 2 of 56
2. Question
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?
Correct
B,
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. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-health#device-telemetry
Incorrect
B,
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. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-health#device-telemetry
Unattempted
B,
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. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-monitor-resource-health#device-telemetry
Question 3 of 56
3. Question
You are making connection from devices to Azure IoT Hub and for this you need “Primary Connection String” from where in the Azure IoT hub you can find connection string ?
Which of the below control is being used for device template so that it can be used by everyone?
Correct
Publish is the correct answer. When you publish then the device became available.
Incorrect
Publish is the correct answer. When you publish then the device became available.
Unattempted
Publish is the correct answer. When you publish then the device became available.
Question 5 of 56
5. Question
You have an Azure IoT solution that includes a standard tier Azure IoT hub and an IoT device. The device sends one 100-KB device-to-cloud message every hour. You need to calculate the total daily message consumption of the device.
What is the total daily message consumption of the device?
Correct
Correct B
100 KB * 24 is around 2,400 bytes.
The 100 KB message is divided into 4 KB blocks, and it is billed for 25 messages. 25 times 24 is 600
Note: The maximum message size for messages sent from a device to the cloud is 256 KB. These messages are metered in 4 KB blocks for the paid tiers so for instance if the device sends a 16 KB message via the paid tiers it will be billed as 4 messages.
Reference: https://azure.microsoft.com/en-us/pricing/details/iot-hub/
Incorrect
Correct B
100 KB * 24 is around 2,400 bytes.
The 100 KB message is divided into 4 KB blocks, and it is billed for 25 messages. 25 times 24 is 600
Note: The maximum message size for messages sent from a device to the cloud is 256 KB. These messages are metered in 4 KB blocks for the paid tiers so for instance if the device sends a 16 KB message via the paid tiers it will be billed as 4 messages.
Reference: https://azure.microsoft.com/en-us/pricing/details/iot-hub/
Unattempted
Correct B
100 KB * 24 is around 2,400 bytes.
The 100 KB message is divided into 4 KB blocks, and it is billed for 25 messages. 25 times 24 is 600
Note: The maximum message size for messages sent from a device to the cloud is 256 KB. These messages are metered in 4 KB blocks for the paid tiers so for instance if the device sends a 16 KB message via the paid tiers it will be billed as 4 messages.
Reference: https://azure.microsoft.com/en-us/pricing/details/iot-hub/
Question 6 of 56
6. Question
You have 1,000 devices that connect to an Azure IoT hub. You are performing a scheduled check of deployed IoT devices.
You plan to run the following command from the Azure CLI prompt. az iot hub query –hub-name hub1 –query-command “SELECT * FROM devices WHERE connectionState = ‘Disconnected'”
What does the command return?
Correct
B , Device Twin is the correct Answer
Incorrect
B , Device Twin is the correct Answer
Unattempted
B , Device Twin is the correct Answer
Question 7 of 56
7. Question
You have an Azure IoT Edge device. You need to modify the credentials used to access the container registry.
What should you modify?
A. the @edgeHub module twin
B. the IoT Edge module
C. the $edgeAgent module twin
D. the Azure IoT Hub device twin
Correct
C ,
The module twin for the IoT Edge agent is called $edgeAgent and coordinates the communications between the IoT Edge agent running on a device and IoT Hub.
The desired properties are set when applying a deployment manifest on a specific device as part of a single-device or at-scale deployment.
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-edgeagent-edgehub
Incorrect
C ,
The module twin for the IoT Edge agent is called $edgeAgent and coordinates the communications between the IoT Edge agent running on a device and IoT Hub.
The desired properties are set when applying a deployment manifest on a specific device as part of a single-device or at-scale deployment.
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-edgeagent-edgehub
Unattempted
C ,
The module twin for the IoT Edge agent is called $edgeAgent and coordinates the communications between the IoT Edge agent running on a device and IoT Hub.
The desired properties are set when applying a deployment manifest on a specific device as part of a single-device or at-scale deployment.
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/module-edgeagent-edgehub
Question 8 of 56
8. Question
Which will be the suitable entry for each Boxes ?
__BOX1__ enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device.
__BOX2__runs on each IoT Edge device and manages communication for the modules deployed to each device.
__BOX3__ are units of execution implemented as Docker compatible containers. It can run business logic at the edge.
Please select Suitable answer for __BOX1__ ?
A. IoT Edge runtime
B. IoT Edge cloud interface
C. IoT Edge modules
D. IoT Edge Device
Correct
32) – B
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Incorrect
32) – B
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Unattempted
32) – B
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Question 9 of 56
9. Question
Which will be the suitable entry for each Boxes ?
__BOX1__ enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device.
__BOX2__runs on each IoT Edge device and manages communication for the modules deployed to each device.
__BOX3__ are units of execution implemented as Docker compatible containers. It can run business logic at the edge.
Please select Suitable answer for __BOX2__ ?
A. IoT Edge runtime
B. IoT Edge cloud interface
C. IoT Edge modules
D. IoT Edge Device
Correct
A
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Incorrect
A
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Unattempted
A
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Question 10 of 56
10. Question
Which will be the suitable entry for each Boxes ?
__BOX1__ enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device.
__BOX2__runs on each IoT Edge device and manages communication for the modules deployed to each device.
__BOX3__ are units of execution implemented as Docker compatible containers. It can run business logic at the edge.
Please select Suitable answer for __BOX3__ ?
Correct
C
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Incorrect
C
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Unattempted
C
IoT Edge modules are units of execution implemented as Docker compatible containers. IoT Edge modules can run business logic at the edge. IoT Edge modules can run Azure services, third-party services, or your code. Modules are deployed to IoT Edge devices and execute locally on those devices. You can configure modules to communicate with each other to create a pipeline for data processing. Modules can run offline if needed.
IoT Edge runtime runs on each IoT Edge device and manages the runtime and communication for the modules deployed to each device. IoT Edge runtime ensures that the modules are always running and report module health to the cloud.
The runtime performs several functions such as:
Installing and updating workloads
Maintaining IoT Edge security standards
Managing communication between downstream leaf devices and the IoT Edge device
Managing communication between modules on an IoT Edge device and managing communications between an IoT Edge device and the cloud.
IoT Edge cloud interface enables you to monitor and manage IoT Edge devices remotely. If your solution is running a diverse set of devices at scale, you can create and configure a workload to run on a specific type of device. You then need to deploy th e workload to a set of devices of that type. Once the devices are running, you need to monitor workloads centrally. IoT Edge cloud interface allows you to manage this overall lifecycle at scale for a diverse set of devices, which could be geographically scattered.
Question 11 of 56
11. Question
You are the Azure IoT Hub architecture and are designing the IoT application
Below is the IoT Edge high-level Architecture diagram is given ,
Which of the following is the most appropriate answer for the Box 1 ?
Correct
Below image is self explanatory answer the
Incorrect
Below image is self explanatory answer the
Unattempted
Below image is self explanatory answer the
Question 12 of 56
12. Question
You are the Azure IoT Hub architecture and are designing the IoT application
Below is the IoT Edge high-level Architecture diagram is given ,
Which of the following is the most appropriate answer for the Box 2 ?
Correct
Correct Answer – A
Incorrect
Correct Answer – A
Unattempted
Correct Answer – A
Question 13 of 56
13. Question
You have an Azure IoT hub that is being taken from prototype to production.
You plan to connect IoT devices to the IoT hub. The devices have hardware security modules (HSMs).
You need to use the most secure authentication method between the devices and the IoT hub. Company policy prohibits the use of internally generated certificates.
Which authentication method should you use?
A. an X.509 self-signed certificate
B. a certificate thumbprint
C. a symmetric key
D. An X.509 certificate signed by a root certification authority (CA).
Correct
D, Purchase X.509 certificates from a root certificate authority (CA). This method is recommended for production environments.
The hardware security module, or HSM, is used for secure, hardware-based storage of device secrets, and is the most secure form of secret storage. Both X.509 certificates and SAS tokens can be stored in the HSM
Reference: https://docs.microsoft.com/en-us/azure/iot-dps/concepts-security
Incorrect
D, Purchase X.509 certificates from a root certificate authority (CA). This method is recommended for production environments.
The hardware security module, or HSM, is used for secure, hardware-based storage of device secrets, and is the most secure form of secret storage. Both X.509 certificates and SAS tokens can be stored in the HSM
Reference: https://docs.microsoft.com/en-us/azure/iot-dps/concepts-security
Unattempted
D, Purchase X.509 certificates from a root certificate authority (CA). This method is recommended for production environments.
The hardware security module, or HSM, is used for secure, hardware-based storage of device secrets, and is the most secure form of secret storage. Both X.509 certificates and SAS tokens can be stored in the HSM
Reference: https://docs.microsoft.com/en-us/azure/iot-dps/concepts-security
Question 14 of 56
14. Question
You use Azure Security Center in an Azure IoT solution. You need to exclude some security events. The solution must minimize development effort.
What should you do?
A. Create an Azure function to filter security messages.
B. Add a configuration to the code of the physical IoT device.
C. Add configuration details to the device twin object.
D. Create an azureiotsecurity module twin and add configuration details to the module twin object.
Identify the below statement is correct or false ?
IoT Edge can function as a protocol gateway and thus provide connectivity and edge analytics to IoT devices that would otherwise not have these capabilities.
Correct
True statement
Incorrect
True statement
Unattempted
True statement
Question 16 of 56
16. Question
Identify the below statement is correct or false ?
With IoT Edge you cannot use Docker-compatible containers to run your business logic at the edge.
Correct
FALSE
IoT Edge allows you to use Docker-compatible containers to run your business logic at the edge.
Incorrect
FALSE
IoT Edge allows you to use Docker-compatible containers to run your business logic at the edge.
Unattempted
FALSE
IoT Edge allows you to use Docker-compatible containers to run your business logic at the edge.
Question 17 of 56
17. Question
Select correct responses in correspondence with each statement
__BOX1__ certificate is not used to validate devices, but only to validate leaf certificates.
__BOX2___is the end-entity certificate that is used to validate a device and can’t be used to validate other certificates.
__BOX3__ a certificate can be used to validate another certificate.This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
What will be the appropriate answer for Box1 ?
Correct
D
Box 1- An Intermediate certificate is not used to validate devices, but only to validate other intermediate certificates, or validate leaf certificates
Incorrect
D
Box 1- An Intermediate certificate is not used to validate devices, but only to validate other intermediate certificates, or validate leaf certificates
Unattempted
D
Box 1- An Intermediate certificate is not used to validate devices, but only to validate other intermediate certificates, or validate leaf certificates
Question 18 of 56
18. Question
Select correct responses in correspondence with each statement
__BOX1__ certificate is not used to validate devices, but only to validate leaf certificates.
__BOX2___is the end-entity certificate that is used to validate a device and can’t be used to validate other certificates.
__BOX3__ a certificate can be used to validate another certificate.This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
What will be the appropriate answer for Box2 ?
A) Root certificate
B) Leaf certificate
C) Visual Studio
D) Intermediate certificate
Correct
B
Box2 – Leaf certificates is the end-entity certificate that is used to validate a device. Leaf certificates can’t be used to validate other certificates.
Incorrect
B
Box2 – Leaf certificates is the end-entity certificate that is used to validate a device. Leaf certificates can’t be used to validate other certificates.
Unattempted
B
Box2 – Leaf certificates is the end-entity certificate that is used to validate a device. Leaf certificates can’t be used to validate other certificates.
Question 19 of 56
19. Question
Select correct responses in correspondence with each statement
__BOX1__ certificate is not used to validate devices, but only to validate leaf certificates.
__BOX2___is the end-entity certificate that is used to validate a device and can’t be used to validate other certificates.
__BOX3__ a certificate can be used to validate another certificate.This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
What will be the appropriate answer for Box3 ?
Correct
A
Box3- A Root certificate can be used to validate another certificate. Such a certificate is known as a root certificate, or sometimes a trust anchor. This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
Incorrect
A
Box3- A Root certificate can be used to validate another certificate. Such a certificate is known as a root certificate, or sometimes a trust anchor. This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
Unattempted
A
Box3- A Root certificate can be used to validate another certificate. Such a certificate is known as a root certificate, or sometimes a trust anchor. This one certificate isn’t used to validate any devices, for example, but is only used to validate a range of subordinate certificates.
Question 20 of 56
20. Question
You are required to ingest Telemetry data from remote IoT device to Azure IoT hub. You then need to select platform for which IoT hub can be use as event source and perform analytics and data and visualize the findings then store the raw data in Apache Parquet format.
You choose Azure Stream Analytics ?
Correct
Incorrect
Unattempted
Question 21 of 56
21. Question
You are required to ingest Telemetry data from remote IoT device to Azure IoT hub. You then need to select platform for which IoT hub can be use as event source and perform analytics and data and visualize the findings then store the raw data in Apache Parquet format.
You choose Azure Event Grid ?
Correct
No
Incorrect
No
Unattempted
No
Question 22 of 56
22. Question
You are required to ingest Telemetry data from remote IoT device to Azure IoT hub. You then need to select platform for which IoT hub can be use as event source and perform analytics and data and visualize the findings then store the raw data in Apache Parquet format.
You choose Azure Time series Insights ?
Correct
Yes
Incorrect
Yes
Unattempted
Yes
Question 23 of 56
23. Question
You deploy an Azure IoT hub.You need to demonstrate that the IoT hub can receive messages from a device. Which three actions should you perform in sequence?
Actions :
Register a device in IoT hub
Trigger a send event from device client
Get a service primary Key for IoT hub
Configure the DPS in IoT hub
Configure the device connection string on a device client
You need select actions in sequence , what will be the first appropriate step you will do ?
You deploy an Azure IoT hub.You need to demonstrate that the IoT hub can receive messages from a device. Which three actions should you perform in sequence?
Actions :
Register a device in IoT hub
Trigger a send event from device client
Get a service primary Key for IoT hub
Configure the DPS in IoT hub
Configure the device connection string on a device client
You need select actions in sequence , what will be the Second appropriate step you will do ?
You deploy an Azure IoT hub.You need to demonstrate that the IoT hub can receive messages from a device. Which three actions should you perform in sequence?
Actions :
Register a device in IoT hub
Trigger a send event from device client
Get a service primary Key for IoT hub
Configure the DPS in IoT hub
Configure the device connection string on a device client
You need select actions in sequence , what will be the Third appropriate step you will do ?
Correct
B
Incorrect
B
Unattempted
B
Question 26 of 56
26. Question
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 MyIoTHub.azure-devices.net.
You need to ensure that Sensors.csv is uploaded to the IoT hub.
Which two actions should you perform?
A. Upload Sensors.csv by using the IoT Hub REST API.
B. From the Azure subscription, select the IoT hub, select Message routing, and then configure a route to storage.
C. From the Azure subscription, select the IoT hub, select File upload, and then configure a storage container.
D. Configure the device to use a GET request to MyIoTHub.azure-devices.net/devices/Device1/files/notifications.
Correct
A, C
A device can start a file upload by sending a notification through a device-facing endpoint (/devices/{deviceId}/files). When a device notifies IoT Hub that an upload is complete, IoT Hub sends a file upload notification message through the /messages/servicebound/filenotifications service-facing endpoint.
Instead of brokering messages through IoT Hub itself, IoT Hub instead acts as a dispatcher to an associated Azure Storage account. A device requests a storage token from IoT Hub that is specific to the file the device wishes to upload. The device uses the SAS URI to upload the file to storage, and when the upload is complete the device sends a notification of completion to IoT Hub. IoT Hub checks the file upload is complete and then adds a file upload notification message to the service-facing file notification endpoint.
Before you upload a file to IoT Hub from a device, you must configure your hub by associating an Azure Storage account to it.
Your device can then initialize an upload and then notify IoT hub when the upload completes. Optionally, when a device notifies IoT Hub that the upload is complete, the service can generate a notification message. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-file-upload
Incorrect
A, C
A device can start a file upload by sending a notification through a device-facing endpoint (/devices/{deviceId}/files). When a device notifies IoT Hub that an upload is complete, IoT Hub sends a file upload notification message through the /messages/servicebound/filenotifications service-facing endpoint.
Instead of brokering messages through IoT Hub itself, IoT Hub instead acts as a dispatcher to an associated Azure Storage account. A device requests a storage token from IoT Hub that is specific to the file the device wishes to upload. The device uses the SAS URI to upload the file to storage, and when the upload is complete the device sends a notification of completion to IoT Hub. IoT Hub checks the file upload is complete and then adds a file upload notification message to the service-facing file notification endpoint.
Before you upload a file to IoT Hub from a device, you must configure your hub by associating an Azure Storage account to it.
Your device can then initialize an upload and then notify IoT hub when the upload completes. Optionally, when a device notifies IoT Hub that the upload is complete, the service can generate a notification message. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-file-upload
Unattempted
A, C
A device can start a file upload by sending a notification through a device-facing endpoint (/devices/{deviceId}/files). When a device notifies IoT Hub that an upload is complete, IoT Hub sends a file upload notification message through the /messages/servicebound/filenotifications service-facing endpoint.
Instead of brokering messages through IoT Hub itself, IoT Hub instead acts as a dispatcher to an associated Azure Storage account. A device requests a storage token from IoT Hub that is specific to the file the device wishes to upload. The device uses the SAS URI to upload the file to storage, and when the upload is complete the device sends a notification of completion to IoT Hub. IoT Hub checks the file upload is complete and then adds a file upload notification message to the service-facing file notification endpoint.
Before you upload a file to IoT Hub from a device, you must configure your hub by associating an Azure Storage account to it.
Your device can then initialize an upload and then notify IoT hub when the upload completes. Optionally, when a device notifies IoT Hub that the upload is complete, the service can generate a notification message. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-file-upload
Question 27 of 56
27. Question
You need to match the correct protocol with the definition mentioned below ,
Field gateways for TLS connection
Network traversal
Low resource devices – Devices less than 1-MB RAM
Select the correct protocol for “Field gateways for TLS connection” ?
Correct
B ,
Field gateways. MQTT and HTTPS support only a single device identity (device ID plus credentials) per TLS connection. For this reason, these protocols are not supported for field gateway scenarios that require multiplexing messages using multiple device identities across a single or a pool of upstream connections to IoT Hub. Such gateways can use a protocol that supports multiple device identities per connection, like AMQP,
Incorrect
B ,
Field gateways. MQTT and HTTPS support only a single device identity (device ID plus credentials) per TLS connection. For this reason, these protocols are not supported for field gateway scenarios that require multiplexing messages using multiple device identities across a single or a pool of upstream connections to IoT Hub. Such gateways can use a protocol that supports multiple device identities per connection, like AMQP,
Unattempted
B ,
Field gateways. MQTT and HTTPS support only a single device identity (device ID plus credentials) per TLS connection. For this reason, these protocols are not supported for field gateway scenarios that require multiplexing messages using multiple device identities across a single or a pool of upstream connections to IoT Hub. Such gateways can use a protocol that supports multiple device identities per connection, like AMQP,
Question 28 of 56
28. Question
You need to match the correct protocol with the definition mentioned below ,
Field gateways for TLS connection
Network traversal
Low resource devices – Devices less than 1-MB RAM
Select the correct protocol for “Network traversal” ?
Correct
A,B,C
Network traversal. The standard AMQP protocol uses port 5671, and MQTT listens on port 8883. Use of these ports could cause problems in networks that are closed to non-HTTPS protocols. Use MQTT over WebSockets, AMQP over WebSockets, or HTTPS in this scenario https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
Incorrect
A,B,C
Network traversal. The standard AMQP protocol uses port 5671, and MQTT listens on port 8883. Use of these ports could cause problems in networks that are closed to non-HTTPS protocols. Use MQTT over WebSockets, AMQP over WebSockets, or HTTPS in this scenario https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
Unattempted
A,B,C
Network traversal. The standard AMQP protocol uses port 5671, and MQTT listens on port 8883. Use of these ports could cause problems in networks that are closed to non-HTTPS protocols. Use MQTT over WebSockets, AMQP over WebSockets, or HTTPS in this scenario https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols
Question 29 of 56
29. Question
You need to match the correct protocol with the definition mentioned below ,
Field gateways for TLS connection
Network traversal
Low resource devices – Devices less than 1-MB RAM
Select the correct protocol for “Low resource devices” ?
Correct
A,C
Low resource devices. The MQTT and HTTPS libraries have a smaller footprint than the AMQP libraries. As such, if the device has limited resources (for example, less than 1-MB RAM), these protocols might be the only protocol implementation available.
Incorrect
A,C
Low resource devices. The MQTT and HTTPS libraries have a smaller footprint than the AMQP libraries. As such, if the device has limited resources (for example, less than 1-MB RAM), these protocols might be the only protocol implementation available.
Unattempted
A,C
Low resource devices. The MQTT and HTTPS libraries have a smaller footprint than the AMQP libraries. As such, if the device has limited resources (for example, less than 1-MB RAM), these protocols might be the only protocol implementation available.
Question 30 of 56
30. Question
You are using image of your Azure IoT Edge module and you would like to store privately in Azure that can be used by your company’s IoT Edge devices. The image repository should support Docker content trust and geo-replication. You need to chose an Azure Resource to store your image . Which resource do you chose ?
Correct
Premium Tier for ACR is the correct answer
Premium Premium registries provide the highest amount of included storage and concurrent operations, enabling high-volume scenarios. In addition to higher image throughput, Premium adds features such as geo-replication for managing a single registry across multiple regions, content trust for image tag signing, private link with private endpoints to restrict access to the registry.
Basic A cost-optimized entry point for developers learning about Azure Container Registry. Basic registries have the same programmatic capabilities as Standard and Premium (such as Azure Active Directory authentication integration, image deletion, and webhooks). However, the included storage and image throughput are most appropriate for lower usage scenarios.
Standard Standard registries offer the same capabilities as Basic, with increased included storage and image throughput. Standard registries should satisfy the needs of most production scenarios. https://docs.microsoft.com/en-us/azure/container-registry/container-registry-skus
Incorrect
Premium Tier for ACR is the correct answer
Premium Premium registries provide the highest amount of included storage and concurrent operations, enabling high-volume scenarios. In addition to higher image throughput, Premium adds features such as geo-replication for managing a single registry across multiple regions, content trust for image tag signing, private link with private endpoints to restrict access to the registry.
Basic A cost-optimized entry point for developers learning about Azure Container Registry. Basic registries have the same programmatic capabilities as Standard and Premium (such as Azure Active Directory authentication integration, image deletion, and webhooks). However, the included storage and image throughput are most appropriate for lower usage scenarios.
Standard Standard registries offer the same capabilities as Basic, with increased included storage and image throughput. Standard registries should satisfy the needs of most production scenarios. https://docs.microsoft.com/en-us/azure/container-registry/container-registry-skus
Unattempted
Premium Tier for ACR is the correct answer
Premium Premium registries provide the highest amount of included storage and concurrent operations, enabling high-volume scenarios. In addition to higher image throughput, Premium adds features such as geo-replication for managing a single registry across multiple regions, content trust for image tag signing, private link with private endpoints to restrict access to the registry.
Basic A cost-optimized entry point for developers learning about Azure Container Registry. Basic registries have the same programmatic capabilities as Standard and Premium (such as Azure Active Directory authentication integration, image deletion, and webhooks). However, the included storage and image throughput are most appropriate for lower usage scenarios.
Standard Standard registries offer the same capabilities as Basic, with increased included storage and image throughput. Standard registries should satisfy the needs of most production scenarios. https://docs.microsoft.com/en-us/azure/container-registry/container-registry-skus
Question 31 of 56
31. Question
You are have IoT devices that runs on ubuntu platform and you deploys the Azure IoT Edge runtime to support the IoT edge app.
And there is a need to update the IoT edge security daemon to enable compatibility with your App. Which two packaged should you update to achieve this goal ?
A) Azure-cli
B) Iotedge
C) libiothsm-std
D) libiothsm-ssl
E) libiothsm-prem
Correct
Iotedge and libiothsm-std
If you want to update to the most recent version of the security daemon, use the following command which also updates libiothsm-std to the latest version:
BashCopy
sudo apt-get install iotedge https://docs.microsoft.com/en-us/azure/iot-edge/how-to-update-iot-edge
Incorrect
Iotedge and libiothsm-std
If you want to update to the most recent version of the security daemon, use the following command which also updates libiothsm-std to the latest version:
BashCopy
sudo apt-get install iotedge https://docs.microsoft.com/en-us/azure/iot-edge/how-to-update-iot-edge
Unattempted
Iotedge and libiothsm-std
If you want to update to the most recent version of the security daemon, use the following command which also updates libiothsm-std to the latest version:
BashCopy
sudo apt-get install iotedge https://docs.microsoft.com/en-us/azure/iot-edge/how-to-update-iot-edge
Question 32 of 56
32. Question
You are required to change the repository address for IoT edge module. Select three actions which you will perform in sequence in order to change the repo address ?
Select Device Twin
Set modules on device
Update the URL
Update the URI
Update the IoT Edge module
Update Azure IoT Edge
Which step you will perform first ?
A) Select Device Twin
B) Set modules on device
C) Update the URL
D) Update the URI
E) Update the IoT Edge module
F) Update Azure IoT Edge
Correct
56- A
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Incorrect
56- A
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Unattempted
56- A
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Question 33 of 56
33. Question
You are required to change the repository address for IoT edge module. Select three actions which you will perform in sequence in order to change the repo address ?
Select Device Twin
Set modules on device
Update the URL
Update the URI
Update the IoT Edge module
Update Azure IoT Edge
Which step you will perform Second ?
A) Select Device Twin
B) Set modules on device
C) Update the URL
D) Update the URI
E) Update the IoT Edge module
F) Update Azure IoT Edge
Correct
E
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Incorrect
E
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Unattempted
E
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Question 34 of 56
34. Question
You are required to change the repository address for IoT edge module. Select three actions which you will perform in sequence in order to change the repo address ?
Steps :
Select Device Twin
Set modules on device
Update the URL
Update the URI
Update the IoT Edge module
Update Azure IoT Edge
Which step you will perform Third ?
A) Select Device Twin
B) Set modules on device
C) Update the URL
D) Update the URI
E) Update the IoT Edge module
F) Update Azure IoT Edge
Correct
D
58 – D
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Incorrect
D
58 – D
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Unattempted
D
58 – D
Explanation :
1. Sign in to the Azure portal and navigate to your IoT hub.
2. On the left pane, select IoT Edge from the menu.
3. Click on the ID of the target device from the list of devices.
4. On the upper bar, select Set Modules.
5. In the Container Registry Settings section of the page, provide the credentials to access any private container registries that contain your module images.
6. In the IoT Edge Modules section of the page, select Add.
7. Look at the types of modules from the drop-down menu:
o IoT Edge Module – You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0. If the module image is stored in a private container registry, add the credentials on this page to access the image.
o Marketplace Module – Modules hosted in the Azure Marketplace. Some marketplace modules require additional configuration, so review the module details in the Azure Marketplace IoT Edge Modules list.
o Azure Stream Analytics Module – Modules generated from an Azure Stream Analytics workload.
8. After adding a module, select the module name from the list to open the module settings. Fill out the optional fields if necessary. For more information about container create options, restart policy, and desired status see EdgeAgent desired properties. For more information about the module twin see Define or update desired properties.
9. If needed, repeat steps 5 through 8 to add additional modules to your deployment.
10. Select Next: Routes to continue to the routes section. https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-portal
Question 35 of 56
35. Question
You are developing IoT application in your organization for this purpose you need to use various SDKs
Below are the given scenarios select the correct SDKs for each of the given below scenarios.
Scenarios :
__BOX1__ SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub.
__BOX2__ SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
__BOX3__ SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
__BOX4__ SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service.
What will the appropriate SDK for Box1 ?
A) Provisioning Device SDKs
B) Provisioning Service SDKs
C) IoT Hub Device SDKs
D) IoT Hub Service SDKs
Correct
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Incorrect
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Unattempted
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Question 36 of 56
36. Question
You are developing IoT application in your organization for this purpose you need to use various SDKs
Below are the given scenarios select the correct SDKs for each of the given below scenarios.
Scenarios :
__BOX1__ SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub.
__BOX2__ SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
__BOX3__ SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
__BOX4__ SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service.
What will the appropriate SDK for Box2 ?
A) Provisioning Device SDKs
B) Provisioning Service SDKs
C) IoT Hub Device SDKs
D) IoT Hub Service SDKs
Correct
D
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Incorrect
D
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Unattempted
D
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Question 37 of 56
37. Question
You are developing IoT application in your organization for this purpose you need to use various SDKs
Below are the given scenarios select the correct SDKs for each of the given below scenarios.
Scenarios :
__BOX1__ SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub.
__BOX2__ SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
__BOX3__ SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
__BOX4__ SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service.
What will the appropriate SDK for Box3 ?
A) Provisioning Device SDKs
B) Provisioning Service SDKs
C) IoT Hub Device SDKs
D) IoT Hub Service SDKs
Correct
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Incorrect
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Unattempted
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Question 38 of 56
38. Question
You are developing IoT application in your organization for this purpose you need to use various SDKs
Below are the given scenarios select the correct SDKs for each of the given below scenarios.
Scenarios :
__BOX1__ SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub.
__BOX2__ SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
__BOX3__ SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
__BOX4__ SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service.
What will the appropriate SDK for Box4 ?
A) Provisioning Device SDKs
B) Provisioning Service SDKs
C) IoT Hub Device SDKs
D) IoT Hub Service SDKs
Correct
B
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Incorrect
B
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Unattempted
B
Explanation :
• IoT Hub Device SDKs enable you to build apps that run on your IoT devices using device client or module client. These apps send telemetry to your IoT hub, and optionally receive messages, job, method, or twin updates from your IoT hub. You can also use module client to author modules for Azure IoT Edge runtime.
• IoT Hub Service SDKs enable you to build backend applications to manage your IoT hub, and optionally send messages, schedule jobs, invoke direct methods, or send desired property updates to your IoT devices or modules.
In addition, we also provide a set of SDKs for working with the Device Provisioning Service.
• Provisioning Device SDKs enable you to build apps that run on your IoT devices to communicate with the Device Provisioning Service.
• Provisioning Service SDKs enable you to build backend applications to manage your enrollments in the Device Provisioning Service. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-sdks
Question 39 of 56
39. Question
You have three Azure IoT hubs named Hub1, Hub2, and Hub3, a Device Provisioning Service instance, and an IoT device named Device1.Each IoT hub is deployed to a separate Azure region.Device enrollment uses the Lowest latency allocation policy. The Device Provisioning Service uses the Lowest latency allocation policy.Device1 is auto-provisioned to Hub1 by using the Device Provisioning Service.
Device1 regularly moves between regions.
You need to ensure that Device1 always connects to the IoT hub that has the lowest latency.
What should you do?
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?
Correct
B , 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.
Incorrect
B , 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.
Unattempted
B , 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.
Question 41 of 56
41. Question
You have an Azure IoT solution that includes an Azure IoT Hub named Hub1 and an Azure IoT Edge device named Edge1. Edge1 connects to Hub1. You need to deploy a temperature module to Edge1.
What should you do?
A. From the Azure portal, navigate to Hub1 and select IoT Edge. Select Edge1, and then select Manage Child Devices. From a Bash prompt, run the following command: az iot edge set-modules -device-id Edge1 -hub-name Hub1 -content C:\deploymentMan1.json
B. Create an IoT Edge deployment manifest that specifies the temperature module and the route to $upstream. From a Bush prompt, run the following command: az iot hub monitor-events-device-id Edge1 -hub-name Hub1
C. From the Azure portal, navigate to Hub1 and select IoT Edge. Select Edge1, select Device Twin, and then set the deployment manifest as a desired property. From a Bash prompt, run the following command az iot hub monitor-events-device-id Edge1 -hub-name Hub1
D. Create an IoT Edge deployment manifest that specifies the temperature module and the route to $upstream. From a Bush prompt, run the following command: az iot edge set-modules -device-id Edge1 -hub-name Hub1 -content C:\deploymentMan1.json
Correct
D,
You deploy modules to your device by applying the deployment manifest that you configured with the module information.
Use the following command to apply the configuration to an IoT Edge device: az iot edge set-modules –device-id [device id] –hub-name [hub name] –content [file path]
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-cli
Incorrect
D,
You deploy modules to your device by applying the deployment manifest that you configured with the module information.
Use the following command to apply the configuration to an IoT Edge device: az iot edge set-modules –device-id [device id] –hub-name [hub name] –content [file path]
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-cli
Unattempted
D,
You deploy modules to your device by applying the deployment manifest that you configured with the module information.
Use the following command to apply the configuration to an IoT Edge device: az iot edge set-modules –device-id [device id] –hub-name [hub name] –content [file path]
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-deploy-modules-cli
Question 42 of 56
42. Question
You are the admin for Azure IoT Hub and you need to configure diagnostic logging so that in case of issues it can analyzed and you will be able to find the cause. Which logging should you choose ?
Correct
C
Log Analytics workspace
Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to leverage other Azure Monitor features such as alerts and visualizations.
Log Analytics workspace The workspace does not need to be in the same region as the resource being monitored. https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings
Incorrect
C
Log Analytics workspace
Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to leverage other Azure Monitor features such as alerts and visualizations.
Log Analytics workspace The workspace does not need to be in the same region as the resource being monitored. https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings
Unattempted
C
Log Analytics workspace
Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to leverage other Azure Monitor features such as alerts and visualizations.
Log Analytics workspace The workspace does not need to be in the same region as the resource being monitored. https://docs.microsoft.com/en-us/azure/azure-monitor/platform/diagnostic-settings
Question 43 of 56
43. Question
You are configuring Azure IoT hub metrics to display real-time device scenario. Below are the scenarios given and you need to select the correct Metric ?
Scenario:
Bytes transferred to and from any devices connected to IotHub
You are configuring Azure IoT hub metrics to display real-time device scenario. Below are the scenarios given and you need to select the correct Metric ?
Scenario:
Number of devices registered to your IoT hub –
After enabling Azure Security Center for IoT on your Azure IoT hub. You found threat prevention that still needs to be enabled on an IoT Hub device. What would you do ?
A) Deploy the edgeHub Agent
B) Enable the Threat prevention
C) Regenerate Security Keys
D) Make sure that azure iotsecurity twin is listed for IoT device.
Correct
D
Use the following workflow to deploy and test your Azure Security Center for IoT security agents:
1. Enable Azure Security Center for IoT service to your IoT Hub
2. If your IoT Hub has no registered devices, Register a new device.
3. Create an azureiotsecurity security module for your devices.
4. To install the agent on an Azure simulated device instead of installing on an actual device, spin up a new Azure Virtual Machine (VM) in an available zone.
5. Deploy an Azure Security Center for IoT security agent on your IoT device, or new VM.
6. Follow the instructions for trigger_events to run a harmless simulation of an attack.
7. Verify Azure Security Center for IoT alerts in response to the simulated attack in the previous step. Begin verification five minutes after running the script.
8. Explore alerts, recommendations, and deep dive using Log Analytics using IoT Hub. https://docs.microsoft.com/en-us/azure/asc-for-iot/security-agents
Incorrect
D
Use the following workflow to deploy and test your Azure Security Center for IoT security agents:
1. Enable Azure Security Center for IoT service to your IoT Hub
2. If your IoT Hub has no registered devices, Register a new device.
3. Create an azureiotsecurity security module for your devices.
4. To install the agent on an Azure simulated device instead of installing on an actual device, spin up a new Azure Virtual Machine (VM) in an available zone.
5. Deploy an Azure Security Center for IoT security agent on your IoT device, or new VM.
6. Follow the instructions for trigger_events to run a harmless simulation of an attack.
7. Verify Azure Security Center for IoT alerts in response to the simulated attack in the previous step. Begin verification five minutes after running the script.
8. Explore alerts, recommendations, and deep dive using Log Analytics using IoT Hub. https://docs.microsoft.com/en-us/azure/asc-for-iot/security-agents
Unattempted
D
Use the following workflow to deploy and test your Azure Security Center for IoT security agents:
1. Enable Azure Security Center for IoT service to your IoT Hub
2. If your IoT Hub has no registered devices, Register a new device.
3. Create an azureiotsecurity security module for your devices.
4. To install the agent on an Azure simulated device instead of installing on an actual device, spin up a new Azure Virtual Machine (VM) in an available zone.
5. Deploy an Azure Security Center for IoT security agent on your IoT device, or new VM.
6. Follow the instructions for trigger_events to run a harmless simulation of an attack.
7. Verify Azure Security Center for IoT alerts in response to the simulated attack in the previous step. Begin verification five minutes after running the script.
8. Explore alerts, recommendations, and deep dive using Log Analytics using IoT Hub. https://docs.microsoft.com/en-us/azure/asc-for-iot/security-agents
Question 46 of 56
46. Question
To confirm that the Azure IoT Edge Runtime is installed on the VM or on the machine , which command you will use (you can use bash/cmd to check)?
A) az iot version
B) iot version
C) iotedge version
D) Get-AzIoTEdge-Version
Correct
C
To confirm that the Azure IoT Edge Runtime is installed on the VM, run the following command:
Bash
iotedge version
This command will output the version of the Azure IoT Edge Runtime that is currently installed on the virtual machine.
The version will be similar to the following output:
Bash
username@AZ-220-VM-EDGEGW:~/certificates$ iotedge version
iotedge 1.0.8 (208b2204fd30e856d00b280112422130c104b9f0)
Incorrect
C
To confirm that the Azure IoT Edge Runtime is installed on the VM, run the following command:
Bash
iotedge version
This command will output the version of the Azure IoT Edge Runtime that is currently installed on the virtual machine.
The version will be similar to the following output:
Bash
username@AZ-220-VM-EDGEGW:~/certificates$ iotedge version
iotedge 1.0.8 (208b2204fd30e856d00b280112422130c104b9f0)
Unattempted
C
To confirm that the Azure IoT Edge Runtime is installed on the VM, run the following command:
Bash
iotedge version
This command will output the version of the Azure IoT Edge Runtime that is currently installed on the virtual machine.
The version will be similar to the following output:
Bash
username@AZ-220-VM-EDGEGW:~/certificates$ iotedge version
iotedge 1.0.8 (208b2204fd30e856d00b280112422130c104b9f0)
Question 47 of 56
47. Question
Within the Cloud Shell, which command you use to monitor the stream of events flowing to the Azure IoT Hub which will help to identify that metric sent to the IoT Edge Gateway, are being received by the Azure IoT Hub.
A) Az iot monitor-events -n
B) Az iot monitor -n
C) Az iot hub monitor-events -n
D) Az iot hub monitor -n
Correct
C
Correct commands :
az extension add –name azure-iot
az iot hub monitor-events -n
Incorrect
C
Correct commands :
az extension add –name azure-iot
az iot hub monitor-events -n
Unattempted
C
Correct commands :
az extension add –name azure-iot
az iot hub monitor-events -n
Question 48 of 56
48. Question
After you deploys a module that simulates data to the edge,
How will you ensure that the module is up and running:
A) By viewing the generated data.
B) By checking the status of the module.
C) By running a test for the module status
D) By checking the status from az cli
Correct
A
By viewing the generated data.
Incorrect
A
By viewing the generated data.
Unattempted
A
By viewing the generated data.
Question 49 of 56
49. Question
You are building new Azure IoT Edge module that should run continuously and you are designing back-end solution that integrated with Azure IoT hub. You need to ensure that this solution can send cloud-to-device messages.
A) Acquire endorsement key
B) Obtain X.509 certificate
C) Retrieve the primary connection string from service policy
D) Use transfer messaging solution.
Correct
C
To send one-way notifications to a device app from your solution back end, send cloud-to-device messages from your IoT hub to your device. For a discussion of other cloud-to-device options supported by Azure IoT Hub, see Cloud-to-device communications guidance.
Note
The features described in this article are available only in the standard tier of IoT Hub. For more information about the basic and standard/free IoT Hub tiers, see Choose the right IoT Hub tier.
You send cloud-to-device messages through a service-facing endpoint, /messages/devicebound. A device then receives the messages through a device-specific endpoint, /devices/{deviceId}/messages/devicebound.
To target each cloud-to-device message at a single device, your IoT hub sets the to property to /devices/{deviceId}/messages/devicebound.
Each device queue holds, at most, 50 cloud-to-device messages. To try to send more messages to the same device results in an error. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-c2d
Incorrect
C
To send one-way notifications to a device app from your solution back end, send cloud-to-device messages from your IoT hub to your device. For a discussion of other cloud-to-device options supported by Azure IoT Hub, see Cloud-to-device communications guidance.
Note
The features described in this article are available only in the standard tier of IoT Hub. For more information about the basic and standard/free IoT Hub tiers, see Choose the right IoT Hub tier.
You send cloud-to-device messages through a service-facing endpoint, /messages/devicebound. A device then receives the messages through a device-specific endpoint, /devices/{deviceId}/messages/devicebound.
To target each cloud-to-device message at a single device, your IoT hub sets the to property to /devices/{deviceId}/messages/devicebound.
Each device queue holds, at most, 50 cloud-to-device messages. To try to send more messages to the same device results in an error. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-c2d
Unattempted
C
To send one-way notifications to a device app from your solution back end, send cloud-to-device messages from your IoT hub to your device. For a discussion of other cloud-to-device options supported by Azure IoT Hub, see Cloud-to-device communications guidance.
Note
The features described in this article are available only in the standard tier of IoT Hub. For more information about the basic and standard/free IoT Hub tiers, see Choose the right IoT Hub tier.
You send cloud-to-device messages through a service-facing endpoint, /messages/devicebound. A device then receives the messages through a device-specific endpoint, /devices/{deviceId}/messages/devicebound.
To target each cloud-to-device message at a single device, your IoT hub sets the to property to /devices/{deviceId}/messages/devicebound.
Each device queue holds, at most, 50 cloud-to-device messages. To try to send more messages to the same device results in an error. https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-c2d
Question 50 of 56
50. Question
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?
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?
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?
Correct
No
Incorrect
No
Unattempted
No
Question 53 of 56
53. Question
You have an Azure IoT Central application that has a custom device template.
You need to configure the device template to support the following activities:
Activity :
Return the reported power consumption.
Configure the desired fan speed.
Run the device reset routine.
Read the fan serial number.
Which option should you use for “ Return the reported power consumption “ activity? Each correct answer presents part of the solution.
A) Command
B) Measurement
C) Properties
D) Settings
Correct
B
Measurement –
Telemetry/measurement is a stream of values sent from the device, typically from a sensor. For example, a sensor might report the ambient temperature.
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Incorrect
B
Measurement –
Telemetry/measurement is a stream of values sent from the device, typically from a sensor. For example, a sensor might report the ambient temperature.
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Unattempted
B
Measurement –
Telemetry/measurement is a stream of values sent from the device, typically from a sensor. For example, a sensor might report the ambient temperature.
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Question 54 of 56
54. Question
You have an Azure IoT Central application that has a custom device template.
You need to configure the device template to support the following activities:
Activity :
Return the reported power consumption.
Configure the desired fan speed.
Run the device reset routine.
Read the fan serial number.
Which option should you use for “ Configure the desired fan speed.“ activity? Each correct answer presents part of the solution.
A) Command
B) Measurement
C) Properties
D) Settings
Correct
C
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Incorrect
C
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Unattempted
C
Property –
The template can provide a writeable fan speed property
Properties represent point-in-time values. For example, a device can use a property to report the target temperature it’s trying to reach. You can set writeable properties from IoT Central.
Command –
You can call device commands from IoT Central. Commands optionally pass parameters to the device and receive a response from the device. For example, you can call a command to reboot a device in 10 seconds.
Reference: https://docs.microsoft.com/en-us/azure/iot-central/core/howto-set-up-template
Question 55 of 56
55. Question
You have an Azure IoT Central application that has a custom device template.
You need to configure the device template to support the following activities:
Activity :
Return the reported power consumption.
Configure the desired fan speed.
Run the device reset routine.
Read the fan serial number.
Which option should you use for “ Run the device reset routine“ activity? Each correct answer presents part of the solution.
A) Command
B) Measurement
C) Properties
D) Settings
You have an Azure IoT Central application that has a custom device template.
You need to configure the device template to support the following activities:
Activity :
Return the reported power consumption.
Configure the desired fan speed.
Run the device reset routine.
Read the fan serial number.
Which option should you use for “ Read the fan serial number“ activity? Each correct answer presents part of the solution.
A) Command
B) Measurement
C) Properties
D) Settings