Ans C Cloud Build provides the following default substitutions: $TAG_NAME: build.Source.RepoSource.Revision.TagName

C inside cloudbuil.yml file can include release version

imho D cause Using GCR digest versioning involves using the SHA256 digest of the image as the unique identifier for the image. This ensures that the image can be reliably referenced and identified regardless of any tags that may be applied to it.

option C

Both option B and C are valid ways to ensure that a specific version of an application is deployed based on the release version tagged in source control, but option C is likely to be the more robust and flexible solution for managing your application deployments. With option B, Supply the source control tag as a parameter within the image name, you have to manually include the source control tag when you push the image to GCR. This can make it more prone to human error and also could require more manual work to keep track of the different versions and their correspondance with the codebase. On the other hand, option C, Use Cloud Build to include the release version tag in the application image, allows you to automate the process of adding the release version tag to the application image during the build process. This can make it easier to track the different versions of your application and their association with the codebase. Additionally, Cloud Build allows you to automate different steps of the build and deployment process, such as building, testing and deploying the images, making it easier to manage and keep track of your deployments.

Ans: C Exam passed and taken on 19/12/2022, 50/50 from this dump without buying the full access and looking for 'devops' word here: https://www.examtopics.com/discussions/google/1/

The correct answer is C

C should be right. https://cloud.google.com/build/docs/build-push-docker-image#build_an_image_using_a_build_config_file

C is a right option

I go for B https://cloud.google.com/container-registry/docs/pushing-and-pulling

Ans: C

C. tag your images with the sourced code release version.

I think is B, is the normal process in this cases