Run the following commands
Install the container runtime.
Azure IoT Edge relies on an OCI-compatible container runtime. For production scenarios, we recommended that you use the Moby-based engine provided below. The Moby engine is the only container engine officially supported with Azure
IoT Edge. Docker CE/EE container images are compatible with the Moby runtime.
Install the Moby engine. sudo
apt-get install moby-engine
Install the Moby command-line interface (CLI). The CLI is useful for development but optional for production deployments. sudo
apt-get install moby-cli
Install the security daemon. The package is installed at /etc/iotedge/.
sudo apt-get install iotedge
Step 2: From Iot Hub,create an IoT Edge device registry entry.
Note: In your IoT Hub in the Azure portal, IoT Edge devices are created and managed separately from IOT devices that are not edge enabled.
1. Sign in to the Azure portal and navigate to your IoT hub.
2. In the left pane, select IoT Edge from the menu.
3. Select Add an IoT Edge device.
4. Provide a descriptive device ID. Use the default settings to auto-generate authentication keys and connect the new device to your hub.
5. Select Save.
Retrieve the connection string in the Azure portal
1. When you’re ready to set up your device, you need the connection string that links your physical device with its identity in the IoT hub.
2. From the IoT Edge page in the portal, click on the device ID from the list of IoT Edge devices.
3. Copy the value of either Primary Connection String or Secondary Connection String.
Step 3: Add the connection string to..
To manually provision a device, you need to provide it with a device connection string that you can create by registering a new device in your IoT hub.
Open the configuration file. sudo
nano /etc/iotedge/config.yaml
Find the provisioning configurations of the file and uncomment the Manual provisioning configuration section. Update the value of device_connection_string with the connection string from your IoT Edge device. Save
and close the file.
After entering the provisioning information in the configuration file, restart the daemon: sudo
systemctl restart iotedge
Reference: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-install-iot-edgelinux

You use Blob storage for a cold path, and Service Bus or Event Hubs for a warm path.

Device Twins are used to synchronize state between an IoT solution’s cloud service and its devices. Each device’s twin exposes a set of desired properties and reported properties. The cloud service populates the desired properties with values it wishes to send to the device. When a device connects it requests and/or subscribes for its desired properties and acts on them.
Reference: https://azure.microsoft.com/sv-se/blog/deep-dive-into-azure-iot-hub-notifications-and-device-twin/

These three options appear in the Add Stream input drop-down list.

Box 1: tags.engine.warpDriveType=’VM105a’
Use tags to target twins. Before you create a configuration, you must specify which devices or modules you want to affect. Azure IoT Hub identifies devices and using tags in the device twin, and identifies modules using tags in the module
twin.
Box 2: properties.desired.warpOperating
The twin path, which is the path to the JSON section within the twin desired properties that will be set.
For example, you could set the twin path to properties.desired.chiller-water and then provide the following JSON content:
{
“temperature”: 66,
“pressure”: 28
}
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-automatic-devicemanagement

These are the three types of apps in Power Apps.

Instead add the desired properties to the device twin.
Note: Device Twins are used to synchronize state between an IoT solution’s cloud service and its devices. Each device’s twin exposes a set of desired properties and reported properties. The cloud service populates the desired properties with
values it wishes to send to the device. When a device connects it requests and/or subscribes for its desired properties and acts on them.
Reference: https://azure.microsoft.com/sv-se/blog/deep-dive-into-azure-iot-hub-notifications-and-device-twin/

MQTT over WebSockets, AMQP over WebSocket, and HTTPS use port 443.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols

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

The two common units of vibration are acceleration in m/s2, or in g-forces.

Correct. The data connection is through Workspace, and then Datasets.

Consider using jobs when you need to schedule and track progress any of the following activities on a set of devices:
Invoke direct methods
Update desired properties
Update tags
Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-jobs

All IoT devices connected to Azure use this endpoint.

Note: IoT Hub is scaled and priced based on an allowed number of messages per day across all devices connected to that IoT Hub. If you exceed the allowed message threshold for your chosen tier and number of units, IoT Hub will begin rejecting new messages. To date, there is no built-in mechanism for automatically scaling an IoT Hub to the next level of capacity if you approach or exceed that threshold.
Reference:
https://docs.microsoft.com/en-us/samples/azure-samples/iot-hub-dotnet-autoscale/iot-hub-dotnet-autoscale/

This is the order the status of an alert is changed by the operator.

Explanation:
Azure IoT Edge runs great on devices as small as a Raspberry Pi3 to server grade hardware.
Tier 1.
The systems listed in the following table are supported by Microsoft, either generally available or in public preview, and are tested with each new release.

Reference: https://docs.microsoft.com/en-us/azure/iot-edge/support

B: X.509 certificates are typically arranged in a certificate chain of trust. If a certificate at any stage in a chain becomes compromised, trust is broken. The certificate must be blacklisted to prevent Device Provisioning Service from provisioning
devices downstream in any chain that contains that certificate.
C: Individual enrollments apply to a single device and can use either X.509 certificates or SAS tokens (in a real or virtual TPM) as the attestation mechanism. (Devices that use SAS tokens as their attestation mechanism can be provisioned
only through an individual enrollment.) To blacklist a device that has an individual enrollment, you can either disable or delete its enrollment entry.
To blacklist a device that has an individual enrollment, you can either disable or delete its enrollment entry.
Reference: https://docs.microsoft.com/en-us/azure/iot-dps/how-to-revoke-deviceaccess-portal

Cosmos DB doesn’t have built-in support. You can build your own feature with Azure Functions.

You can send data to other subscriptions by entering a connection string, so this statement is false.

These displays can be customized using the WHERE, MEASURE, and SPLIT BY entries.

The ability to run modules on edge devices ensures a rapid response time by avoiding a round trip to the cloud.

If the module is running, it should simulate data like any other sensor in the field.

Generating a verification code helps ensure proof of possession.

Turning IoT data into actionable insights is the role of Time Series Insights.

Warm storage allows querying latest data faster.

Simulating the data through an edge module provides a flexible and a relatively inexpensive way to mimic the working of sensors in the field.

You select devices, device templates, and telemetry in the “Create data export” pane.

This sensor might be in a server room, on a factory floor, or on a wind turbine. Hence, the ambient data is relevant for analysis.

You deploy modules to your device by applying the deployment manifest that you configured with the module information.
Change directories into the folder where your deployment manifest is saved. If you used one of the VS Code IoT Edge templates, use the deployment.json file in the config folder of your solution directory and not the deployment.template.json file.
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-modulescli

This term is what you’ll see in the IoT Central portal.

This answer correctly identifies the purpose of all the action settings.

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

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

Use CA certificates in a production environment.

The service can be linked to one, or more, IoT Hubs.

The processed event data can be stored, run through Azure Stream Analytics, and other cloud processes.

Azure Maps enables many route finding options.

The IoT Hub name forms the unique part of the Azure URL, so must be unique across the web.

Session consistency works for many applications, and is the default.

Metrics requires some math ability!

Properties can be simple, such as device IDs, or more complex types such as conditional alerts.

This policy is the default, and the right one to use with a single IoT Hub.

In your Azure IoT Central application, add a real device to the device template 1.
On the Devices page, select the Environmental sensor device template.
2. Select + New.
3. Make sure that Simulated is Off. Then select Create.
Click on the device name, and then select Connect. Make a note of the device connection information on the Device Connection page – ID scope, Device ID, and Primary key. You need these values when you create your device code:

Reference: https://docs.microsoft.com/bs-cyrl-ba/azure/iot-central/core/tutorial-connect-device-python

You use Blob storage for a cold path, and Service Bus or Event Hubs for a warm path.

Automated re-provisioning support.
Microsoft added first-class support for device re-provisioning which allows devices to be reassigned to a different IoT solution sometime after the initial solution assignment. Re-provisioning support is available in two options:
Factory reset, in which the device twin data for the new IoT hub is populated from the enrollment list instead of the old IoT hub. This is common for factory reset scenarios as well as leased device scenarios. Migration,
in which device twin data is moved from the old IoT hub to the new IoT hub. This is common for scenarios in which a device is moving between geographies.
Reference: https://azure.microsoft.com/en-us/blog/new-year-newly-available-iot-hub-device-provisioning-service-features/

Altitude isn’t needed in our scenario, but some applications will certainly require it.

This requirement can increase the initial cost of deployment.

MQTT over WebSockets uses port 443.
Reference: https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols

A container is required, so this statement is false.