Exam AZ-400 topic 8 question 56 discussion

I think the most direct reference is https://docs.github.com/en/actions/creating-actions/about-custom-actions#good-practices-for-release-management "To use a specific action version, users can configure their GitHub Actions workflow to target a tag, a commit's SHA, or a branch named for a release."

Came in Exam June 23, 2024

Correct answer

Answers are A.B.D In practice, A is not human friendly, but it can be used as a good identifier because it's unique Tags are used the most along with branch names containing the version number. These are human friendly because we can clearly see the version instead of a hash.

ABD is the answer. https://docs.github.com/en/actions/creating-actions/about-custom-actions#good-practices-for-release-management To use a specific action version, users can configure their GitHub Actions workflow to target a tag, a commit's SHA, or a branch named for a release.

A. The SHA-based hashes: Each commit in a Git repository has a unique SHA-1 hash associated with it. Actions can be versioned using a specific commit SHA or a branch name. Using SHA-based hashes is the most reliable way to specify the version of an action. B. The tag: Tags are labels that are assigned to a specific commit. They can be used to identify the version of an action. D. The branch: Actions can be versioned using a branch name. This is a convenient way to specify the version of an action if the branch name is already known. So, the correct options are A, B, and D

hash, tag, branch to specify versions of code

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions "We strongly recommend that you include the version of the action you are using by specifying a Git ref, SHA, or Docker tag. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. Using the commit SHA of a released action version is the safest for stability and security. If the action publishes major version tags, you should expect to receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author. Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break." Answers are A, B and D