You have smart devices deployed all over your IoT solution. You need to monitor their operation health. You experience that some of the downstream devices have connectivity issues from time to time. You know that the $edgeHub’s metadata contains health and connectivity information, therefore you start investigating the module twin of the device’s edgeHub and here is what you see: 
<pre>{
"deviceId": "Windows109",
"moduleId": "$edgeHub",
"etag": "AAAAAAAAAAU=",
"deviceEtag": "NzgwNjA1MDU2",
"status": "enabled",
"statusUpdateTime": "0001-01-01T00:00:00Z",
"connectionState": "Disconnected",
"lastActivityTime": "0001-01-01T00:00:00Z",
"cloudToDeviceMessageCount": 0,
"authenticationType": "sas",
"x509Thumbprint": {
"primaryThumbprint": null,
"secondaryThumbprint": null
},
"version": 102,
"properties": {
"desired": { "···" },
"reported": {
"schemaVersion": "1.0",
"version": { "···" },
"lastDesiredVersion": 5,
"lastDesiredStatus": { "···" },
"clients": {
"Windows109/SimulatedTemperatureSensor": {
"status": "Disconnected",
"lastConnectedTimeUtc": "2020-04-08T21:42:42.1743956Z",
"lastDisconnectedTimeUtc": "2020-04-09T07:02:42.1398325Z"
}
},
"$metadata": { "···" },
"$version": 97
}
}
}
</pre>
Does it help you investigate the problem?

Answer options:

A.Yes
B.No

Correct Answer: A
Option A is CORRECT because the edgeHub module twin’s metadata section contains information about the connectivity status of the module. Here, you can see “connectionState”: “Disconnected”, which can be a good starting point for a deeper investigation.
Option B is incorrect because the edgeHub is the central communication point for the edge’s connected child devices, therefore, it is a good starting point when you experience issues with the data flows from the field.
Reference: 

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