You have 100 edge devices registered in your environment monitoring IoT infrastructure.
After several weeks of operation, you experience that 20 of them installed at distant places where the network bandwidth and stability result in communication problems and partial data loss.
To improve reliability, you decide to reconfigure the devices for an offline operation to cope with temporary network outages and you add this code to the edgeAgent and the edgeHub sections of your deployment manifest:
Does it help you achieve your goal?
Click on the arrows to vote for the correct answer
A. B.Correct Answer: A.
Option A is CORRECT because the .createOptions parameter of the deployment manifest allows for configuring the module containers at runtime.
It expands the control over the modules and enables tasks like allowing or restricting the module's access to the host device's resources.
Use the Binds parameter to specify the path to local storage.
The section must be added to both the edgeAgent and the edgeHub sections.
Option B is incorrect because specifying the path to local storage by the createOptions.Binds parameter is needed to solve the problem of storing data locally and operating offline.
References:
The code provided in the deployment manifest is related to containerization and volume mapping. It does not directly address the issue of offline operation and coping with temporary network outages.
The createOptions field is used to specify options that are passed to the container creation process. The HostConfig section specifies options related to the host configuration for the container. The Binds option is used to map a host directory to a container directory, which allows data to be shared between the host and the container.
In this case, the Binds option maps the host directory C:\emp to the container directory C:\contemp. This would allow the container to access files in the C:\emp directory on the host. However, it does not provide any specific functionality for offline operation or network outage handling.
Therefore, the answer is B. No, the provided code does not help achieve the goal of improving reliability in the face of temporary network outages. Additional configuration or code changes would be required to achieve this goal, such as implementing offline data storage and synchronization mechanisms, or implementing network resilience strategies such as retry mechanisms or redundant connectivity options.