Microsoft Azure IoT Developer: Ensuring Edge Runtime Updates with Version Tags

Using Version Tags in Deployment Manifest for Ensuring Edge Runtime Updates

Question

You need to ensure that the edge runtime is always updated to the latest version when it is available.

You decide to use specific version tags in your deployment manifest.

Does it fit the requirements?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B.

Correct Answer: B.

Option A is incorrect because for the given scenario, rolling tags should be used.

There are two strategies for updating edge runtime modules (edgeAgent and edgeHub) using version tags.

Use rolling tags (e.g.

1.0) to update to the latest version and use specific tags (e.g.

1.0.8) to deploy exactly one version.

Option B is CORRECT because using specific tags (like: 1.0.8) will result in deploying the specific module version defined by the tag, i.e.

no automatic upgrade to the latest version takes place.

References:

The use of specific version tags in a deployment manifest can help ensure that the edge runtime is always updated to the latest version when it is available. This is because the deployment manifest specifies which versions of modules should be deployed to an edge device, and by using specific version tags, you can ensure that the latest version of the edge runtime is included in the deployment.

Therefore, the answer is "Yes," it fits the requirements. By using specific version tags in the deployment manifest, you can ensure that the edge runtime is always updated to the latest version when it is available.