You have smart devices deployed around your IoT solution. You need to monitor their operation health. You experience that some of the devices have connectivity issues from time to time. You know that the $edgeAgent contains health and connectivity data about the edge modules, therefore you start investigating the module twin of the device’s edgeAgent: 
<pre class="brush:java;">{
"deviceId": "Windows004",
"moduleId": "$edgeAgent",
"etag": "AABBBBBAAAU=",
"deviceEtag": "KzfgNjA5mDKz",
"status": "enabled",
"statusUpdateTime": "2020-01-01T00:00:00Z",
"connectionState": "Disconnected",
"lastActivityTime": "2020-01-01T00:00:00Z",
"cloudToDeviceMessageCount": 0,
"authenticationType": "sas",
"x509Thumbprint": {
"primaryThumbprint": null,
"secondaryThumbprint": null
},
"version": 14,
"properties": {
"desired": { "···" },
"reported": {
"schemaVersion": "2.0",
"version": { "···" },
"lastDesiredStatus": { "···" },
"runtime": { "···" },
"systemModules": {
"edgeAgent": { "···" },
"edgeHub": { "···" }
},
"lastDesiredVersion": 2,
"modules": {
"TemperatureSensor": { "···" }
},
"$metadata": { "···" },
"$version": 22
}
}
}
</pre>
Does it help you investigate the problem?

Answer options:

A.Yes
B.No

Correct Answer: B
Option A is incorrect because while the edgeAgent is a good starting point to investigate the reason for connectivity issues in general, the given twin sample doesn’t really help us. You might think that the agent’s “disconnected” state is the key but unfortunately, it is not. You should check desired vs. reported properties, and values like exitcode and lastExitTimeUtc etc. to get closer to the solution.
Option B is CORRECT because while the “connectionState”: “Disconnected”, this is misleading because the connection state of the IoT Edge agent is always disconnected because this property refers to the device-to-cloud messages and the IoT Edge agent doesn`t send messages to the cloud. Therefore, the connection state of the edgeAgent itself has no clue for connectivity problems.
Reference: 

https://docs.microsoft.com/en-us/azure/iot-edge/how-to-monitor-module-twins?view=iotedge-2018-06#monitor-iot-edge-agent-module-twin