Explanation:
Step 1: Register a device in IoT Hub
Before you can use your IoT devices with Azure IoT Edge, you must register them with your IoT hub. Once a device is registered, you can retrieve a connection string to set up your device for IoT Edge workloads.
Step 2: Configure the device connection string on a device client.
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.
Step 3: Trigger a new send event from a device client.
Reference:
https://docs.microsoft.com/en-us/azure/iot-edge/how-to-register-device

Explanation:
Step 1: Provision Time Series Insights
Select Provision new IoT Hub to create a new IoT hub.
Step 2: Route telemetry from IoT Hub to a custom event.
Step 3: Add a data access policy to Time Series Insights for the dashboard web app Scenario: Requirements. Pilot Requirements During the pilot phase, devices will be deployed to 10 offices. Each office will have up to 1,000 devices.
During this phase, you will add Azure Time Series Insights in parallel to Stream Analytics to support real-time graphs and queries in a dashboard web app.
The pilot deployment must minimize operating costs.
Incorrect Answers:
No need to use an endpoint.
Reference:
https://docs.microsoft.com/en-us/azure/time-series-insights/time-series-insights-update-create-environment

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

Note: Symptoms
You see the error 409002 LinkCreationConflict in logs along with device disconnection or cloud-to-device message failure.
Cause
Generally, this error happens when IoT Hub detects a client has more than one connection. In fact, when a new connection request arrives for a device with an existing connection, IoT Hub closes the existing connection with this error.
Reference:
https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-troubleshoot-error-409002-linkcreationconflict#symptoms
https://devblogs.microsoft.com/iotdev/understand-different-connection-strings-in-azure-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