You need to ensure that the edge runtime is always updated to the latest version when it is available. You decide to use rolling version tags in your deployment manifest.
Does it fit the requirements?
Answer options:
A.Yes
B.No
Answer correct:
Correct Answer: A
Option A is CORRECT because using rolling tags (e.g. 1.0 - without specifying sub-versions)always updates to the latest version, i.e. for the given scenario, this is the right solution. There are two strategies for updating edge runtime modules (edgeAgent and edgeHub) using version tags: rolling tags and specific tags.
Option B is incorrect because using the other update strategy uses specific tags (like: 1.0.7) which will result in deploying the specific module version defined by the tag. In this case, no automatic upgrade to the latest version takes place.
References: