Scenario: POV Requirements
* Ensure that all message content during this phase is human readable to simplify debugging.
Avro uses a binary format, so it is not human readable.
The more lightweight JSON (Javascript object notation) has become a popular alternative to XML for various reasons. A couple obvious ones are:
* Less verbose- XML uses more words than necessary
* JSON is faster- Parsing XML software is slow and cumbersome.
Reference:
https://blog.cloud-elements.com/json-better-xml
Process and manage data
Question Set 3

Explanation:
Step 1: 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.
Sign in to the Azure portal and navigate to your IoT hub.
In the left pane, select IoT Edge from the menu.
Select Add an IoT Edge device.
Provide a descriptive device ID. Use the default settings to auto-generate authentication keys and connect the new device to your hub.
Select Save.
Retrieve the connection string in the Azure 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-edge-linux

Max number of Streaming Units with one step and with no partitions is 6.
Reference:
https://docs.microsoft.com/en-us/azure/stream-analytics/stream-analytics-parallelization

Explanation:
To deprovision all of the devices that have been provisioned through an enrollment group:
Disable the enrollment group to disallow its signing certificate.
Use the list of provisioned devices for that enrollment group to disable or delete each device from the identity registry of its respective IoT hub.
After disabling or deleting all devices from their respective IoT hubs, you can optionally delete the enrollment group. Be aware, though, that, if you delete the enrollment group and there is an enabled enrollment group for a signing certificate higher up in the certificate chain of one or more of the devices, those devices can re-enroll.
Reference:
https://docs.microsoft.com/en-us/azure/iot-dps/how-to-unprovision-devices