Learn container registry vocabulary: pushing images, image tags vs. digests, registry authentication, Artifactory as internal registry, image promotion workflow — essential for professional container workflows.
0 / 18 completed
1 / 18
The DevOps engineer says: 'The CI pipeline builds the image and pushes it to the registry.' What is a container registry?
A container registry is a centralised service for storing, versioning, and distributing container images. Docker Hub is the most well-known public registry. Organisations often use private registries (AWS ECR, Google Artifact Registry, JFrog Artifactory, GitHub Container Registry) to store proprietary images securely. 'Pushing to the registry' means uploading a built image so it can be pulled and run elsewhere.
2 / 18
The developer explains: 'The image tag is the version identifier — we tag release builds with the git commit SHA.' What is an image tag?
An image tag is a mutable label (e.g., 'v1.2.3', 'latest', 'abc123ef') assigned to an image in the registry. Tags are mutable — they can be reassigned to different image layers over time. This is why using 'latest' in production is discouraged: the 'latest' tag may point to a different image tomorrow than it does today. Using git commit SHAs or semantic version tags provides more stable references.
3 / 18
The security engineer says: 'Use the image digest, not the tag, for production deployments.' What is an image digest?
An image digest is the SHA-256 hash of the image manifest — it is immutable and uniquely identifies exact image content. Referencing an image by digest (e.g., nginx@sha256:abc123...) guarantees you always get exactly that image, even if the tag is later reassigned. This is important for reproducibility and security in production deployments.
4 / 18
The platform team says: 'The registry requires authentication — use docker login before pulling internal images.' Why does the registry require authentication?
Private container registries require authentication to control access. Authentication (via 'docker login' or service account tokens in CI/CD) ensures only authorised users and systems can pull (download) or push (upload) images. This protects proprietary application code packaged in images and prevents unauthorised access to internal infrastructure components.
5 / 18
The release manager describes: 'We promote images from the dev registry to the prod registry after staging sign-off.' What is an image promotion workflow?
Image promotion is the practice of moving a validated container image through registries or repositories as it passes quality gates — typically from a dev/CI registry to staging, then to a prod registry — without rebuilding the image. This ensures the exact same artefact that was tested in staging is deployed to production. Rebuilding introduces risk of non-deterministic build outputs.
6 / 18
PR Description
Subject: Update backend service with latest image
Body:
Hi team,
Please review and approve the PR. We've updated the `order-service` container using the latest tagged image from our private registry. The tag is `v2.1.3`. I've ensured the registry credentials are correctly configured in our CI environment.
Thanks!
John
This question assesses understanding of how developers discuss container registry usage within a code review context. The correct answer highlights that including the image tag (v2.1.3) is crucial for traceability and versioning. Importantly, it also acknowledges the configured credentials, which are often implicitly handled but should be mentioned to demonstrate awareness of security best practices. Options A, C, and D all represent common misconceptions – failing to mention the tag's purpose, ignoring authentication details, or assuming CI handles everything automatically without verification.
7 / 18
John in the PR description mentions using `v2.1.3` as the tag for the updated `order-service` container image. A senior developer asks you: 'Why are we using a tag instead of an image digest? It seems like a tag could change over time.' What is the primary reason for utilizing a tag in this scenario, according to best practices?
The correct answer highlights the importance of semantic versioning with tags. While image digests offer a higher level of integrity verification through cryptographic hashing, using tags (like `v2.1.3`) is standard practice in development workflows for tracking releases and managing deployments. The other options misrepresent the roles of digests or incorrectly suggest that tags are unnecessary for smaller images – both are valuable tools with distinct purposes; tags primarily focus on human-readable versioning.
8 / 18
PR Description
Subject: Update backend service with latest image
Body:
Hi team,
Please review and approve the PR. We've updated the `order-service` container using the latest tagged image from our private registry. The tag is `v2.1.3`. I've ensured the registry credentials are correctly configured in our CI environment.
Thanks!
John
This question assesses understanding of how developers discuss container registry usage within a code review context. The correct answer highlights that including the image tag (v2.1.3) is crucial for traceability and versioning. Importantly, it also acknowledges the configured credentials, which are often implicitly handled but should be mentioned to demonstrate awareness of security best practices. Options A, C, and D all represent common misconceptions – failing to mention the tag's purpose, ignoring authentication details, or assuming CI handles everything automatically without verification.
9 / 18
John in the PR description mentions using `v2.1.3` as the tag for the updated `order-service` container image. A senior developer asks you: 'Why are we using a tag instead of an image digest? It seems like a tag could change over time.' What is the primary reason for utilizing a tag in this scenario, according to best practices?
The correct answer highlights the importance of semantic versioning with tags. While image digests offer a higher level of integrity verification through cryptographic hashing, using tags (like `v2.1.3`) is standard practice in development workflows for tracking releases and managing deployments. The other options misrepresent the roles of digests or incorrectly suggest that tags are unnecessary for smaller images – both are valuable tools with distinct purposes; tags primarily focus on human-readable versioning.
10 / 18
PR Description
Subject: Update backend service with latest image
Body:
Hi team,
Please review and approve the PR. We've updated the `order-service` container using the latest tagged image from our private registry. The tag is `v2.1.3`. I've ensured the registry credentials are correctly configured in our CI environment.
Thanks!
John
This question assesses understanding of how developers discuss container registry usage within a code review context. The correct answer highlights that including the image tag (v2.1.3) is crucial for traceability and versioning. Importantly, it also acknowledges the configured credentials, which are often implicitly handled but should be mentioned to demonstrate awareness of security best practices. Options A, C, and D all represent common misconceptions – failing to mention the tag's purpose, ignoring authentication details, or assuming CI handles everything automatically without verification.
11 / 18
John in the PR description mentions using `v2.1.3` as the tag for the updated `order-service` container image. A senior developer asks you: 'Why are we using a tag instead of an image digest? It seems like a tag could change over time.' What is the primary reason for utilizing a tag in this scenario, according to best practices?
The correct answer highlights the importance of semantic versioning with tags. While image digests offer a higher level of integrity verification through cryptographic hashing, using tags (like `v2.1.3`) is standard practice in development workflows for tracking releases and managing deployments. The other options misrepresent the roles of digests or incorrectly suggest that tags are unnecessary for smaller images – both are valuable tools with distinct purposes; tags primarily focus on human-readable versioning.
12 / 18
PR Description
Subject: Update backend service with latest image
Body:
Hi team,
Please review and approve the PR. We've updated the `order-service` container using the latest tagged image from our private registry. The tag is `v2.1.3`. I've ensured the registry credentials are correctly configured in our CI environment.
Thanks!
John
This question assesses understanding of how developers discuss container registry usage within a code review context. The correct answer highlights that including the image tag (v2.1.3) is crucial for traceability and versioning. Importantly, it also acknowledges the configured credentials, which are often implicitly handled but should be mentioned to demonstrate awareness of security best practices. Options A, C, and D all represent common misconceptions – failing to mention the tag's purpose, ignoring authentication details, or assuming CI handles everything automatically without verification.
13 / 18
John in the PR description mentions using `v2.1.3` as the tag for the updated `order-service` container image. A senior developer asks you: 'Why are we using a tag instead of an image digest? It seems like a tag could change over time.' What is the primary reason for utilizing a tag in this scenario, according to best practices?
The correct answer highlights the importance of semantic versioning with tags. While image digests offer a higher level of integrity verification through cryptographic hashing, using tags (like `v2.1.3`) is standard practice in development workflows for tracking releases and managing deployments. The other options misrepresent the roles of digests or incorrectly suggest that tags are unnecessary for smaller images – both are valuable tools with distinct purposes; tags primarily focus on human-readable versioning.
14 / 18
Sarah (a junior developer) asks: 'I'm trying to pull the latest version of our database container from the registry. I just ran docker login and now I'm getting an 'access denied' error. What is likely causing this?'
Container registries often host both public and private images. Private images require authentication (like a username and password) to access. The 'access denied' error indicates the registry is refusing your request because you haven't provided valid credentials or don't have permission to pull from that specific repository. Using docker login correctly sets up this authentication.
15 / 18
You receive the following API response from the registry when trying to inspect an image: `{"image_id": "sha256:a1b2c3d4e5f6...", "tags": ["v1.0", "latest"]}`. What does the sha256 value represent in this context?
The sha256 value is a secure hash – specifically, a SHA-256 cryptographic hash. This means it's a fixed-size string generated from the entire content of the container image. It's used to uniquely identify an image and guarantees that if the image changes even slightly, the hash will be different, ensuring immutability and preventing accidental use of outdated or corrupted images.
16 / 18
During a stand-up meeting, David mentions: 'We're pushing new container images to the registry using tags like `production-db-v3`. We'll then trigger a deployment pipeline based on those tag names.' What is the primary purpose of using tags in this scenario?
Tags are crucial for managing container deployments. They provide a simple, human-friendly way to identify and reference specific versions of an image. These tags are then used as triggers in automated pipelines, allowing you to reliably deploy the correct version of your application without relying solely on numerical image digests.
17 / 18
In a Slack channel discussing container deployments, Maria says: 'We should always use the image digest instead of the tag when deploying to production. It guarantees we're getting the exact same image every time.' Why is this recommendation important?
The key difference between tags and image digests is immutability. Tags are strings that can change over time (e.g., if a new version is tagged). Image digests, on the other hand, are generated using a cryptographic hash function; any modification to the image content will result in a different digest. This guarantees that you're deploying exactly what you intended – preventing accidental deployments of modified or corrupted images.
18 / 18
You've received the following PR description:
`Subject: Update frontend service with latest image.
Body: We've updated the `frontend-service` container using the tagged image 'v1.2.0'. Please review.` What is the significance of 'v1.2.0' in this context?
In container images, tags often represent versions. The string 'v1.2.0' is a semantic versioning tag – it indicates that this particular container image represents update 1.2.0 of the `frontend-service`. This allows for tracking and managing different releases of your application.
What does the "Container Registry Vocabulary" exercise practise?
Learn container registry vocabulary: pushing images, image tags vs. digests, registry authentication, Artifactory as internal registry, image promotion workflow — essential for professional container workflows.
How many questions are in this exercise?
This exercise has 18 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Containers & Virtualization category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Container Registry Vocabulary" part of a larger series?
Yes — it's one exercise in the Containers & Virtualization category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Containers & Virtualization category page for related exercises, or browse the main Exercises hub for other IT English topics.