Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 21 of 63
Free Preview · 63 of 210 · questions 1–63 of 210 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
he correct approach to ensure your deployments are tied to specific releases is: B. Supply the source control tag as a parameter within the image name. Why this is the standard practice In Docker and Google Container Registry (GCR/Artifact Registry), the "image name" includes the tag (e.g., gcr.io/project-id/app:v1.2.3). By tagging the image with the same version string used in your source control (like Git), you create a direct, human-readable link between your code and your artifact.
C seems ok
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.