Explanation

Step 1: From Azure IoT hub, create an IoT Edge device
In the Azure Cloud Shell, enter the following command to create a device named myEdgeDevice in your hub.
az iot hub device-identity create --device-id myEdgeDevice --edge-enabled --hub-name {hub_name} View the connection string for your device, which links your physical device with its identity in IoT Hub.
Copy the value of the connectionString key from the JSON output and save it. This value is the device connection string. You'll use this connection string to configure the IoT Edge runtime in the step 3.
Step 2: From an elevated PowerShell prompt, run the Deploy-IoTEdge cmdlet.
Install the Azure IoT Edge runtime on your IoT Edge device.
* Run PowerShell as an administrator.
* Run the Deploy-IoTEdge command, which performs the following tasks:
- Checks that your Windows machine is on a supported version.
- Turns on the containers feature.
- Downloads the moby engine and the IoT Edge runtime.
Step 3: From an elevated PowerShell prompt, run the Initialize-IoTEdge cmdlet Step 4: Enter the IoT Edge device connection string.
Configure the IoT Edge device with a device connection string.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/quickstart

Explanation
Create an endpoint for Azure Digital Twins.
These are the supported types of endpoints that you can create for your instance:
* Event Grid
* Event Hubs
* Service Bus
Note: In Azure Digital Twins, you can route event notifications to downstream services or connected compute resources. This is done by first setting up endpoints that can receive the events. You can then create event routes that specify which events generated by Azure Digital Twins are delivered to which endpoints.
Reference:
https://docs.microsoft.com/en-us/azure/digital-twins/how-to-manage-routes

When you create a Time Series Insights Preview pay-as-you-go (PAYG) SKU environment, you create two Azure resources:
An Azure Storage general-purpose V1 blob account for cold data storage.
An Azure Time Series Insights Preview environment that can be configured for warm data storage.
Reference:
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-update-storage-ingress

Explanation:
Box 1: Cert2 only
Cert2: The leaf certificate, or end-entity certificate, identifies the certificate holder. It has the root certificate in its certificate chain as well as zero or more intermediate certificates. The leaf certificate is not used to sign any other certificates. It uniquely identifies the device to the provisioning service and is sometimes referred to as the device certificate.
Box 2: Cert1 only
Cert1: A root certificate is a self-signed X.509 certificate representing a certificate authority (CA). It is the terminus, or trust anchor, of the certificate chain. Root certificates can be self-issued by an organization or purchased from a root certificate authority.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/concepts-x509-attestation

Explanation
Text, letter Description automatically generated

Box 1: $connectionModuled
Add a route that tells the edge hub to route any message received by the IoT Edge device that was not sent by an IoT Edge module.
Box 2: $upstream
Send messages to $upstream, which passes the messages to the connected IoT Hub.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/tutorial-machine-learning-edge-06-custom-modules