Artifact Management Vocabulary
Learn the IT-English vocabulary of build artifacts: versioning, immutability, retention policies and promotion between environments.
0 / 45 completed
1 / 45
What is a build 'artifact'?
An artifact is the deployable output produced by a build — a binary, image or archive.
2 / 45
A policy says artifacts must be 'immutable'. What does that mean?
Immutable artifacts are never modified after publication; fixes produce a new versioned artifact.
3 / 45
The team 'promotes' an artifact from staging to production. What does 'promote' mean here?
Promotion moves the exact same artifact through environments, ensuring you ship what you tested.
4 / 45
A 'retention policy' on the artifact registry does what?
A retention policy automatically purges old artifacts after a set time or count to control storage.
5 / 45
Which sentence correctly uses 'semantic versioning'?
Semantic versioning encodes meaning as MAJOR.MINOR.PATCH to signal compatibility.
6 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
7 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
8 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
9 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
10 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
11 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
12 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
13 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
14 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
15 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
16 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
17 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
18 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
19 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
20 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
21 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
22 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
23 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
24 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
25 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
26 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
27 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
28 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
29 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
30 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
31 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
32 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
33 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
34 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
35 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
36 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
37 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
38 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
39 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
40 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
41 / 45
Sarah: "Hey team, I've just built the latest version of the user authentication service. It's ready for testing in staging! Can someone push it to the artifact registry?" Mark (after reviewing the PR description): "Just to clarify, should we tag this build with a specific version number before pushing it? I'm thinking something like `v1.2.3`."This scenario highlights the importance of consistent versioning practices within artifact management. Using semantic versioning (major.minor.patch) allows developers to understand the type of changes introduced in each build – a '1' indicates a breaking change, '2' a new feature, and '3' a bug fix. It's crucial for tracking deployments and managing potential rollbacks effectively, which is why Mark's suggestion is appropriate; simply stating the version number ensures clarity and adherence to best practices.
42 / 45
Mark is suggesting tagging the build with a version number. The team's artifact management policy dictates that all artifacts should be tracked using semantic versioning to ensure traceability and prevent accidental deployments of older, potentially incompatible versions. Which of the following options best describes what Mark is trying to achieve?Option A: He's requesting the automated build system automatically assign a version number based on commit timestamps.
Option B: He's asking for the artifact registry to create a new artifact with the specified version number, effectively creating a copy.
Option C: He wants to designate a specific numerical identifier (e.g., `v1.2.3`) for this build to track its evolution and compatibility, aligning with semantic versioning principles.
Option D: He's suggesting they manually rename the artifact file itself to include
v1.2.3.Mark is advocating for *semantic versioning*, a standard practice in software development where version numbers (like `v1.2.3`) communicate the type of change made to the artifact – major, minor, or patch. Option B is incorrect because tagging doesn't create copies; it's a metadata label. Option A describes automated versioning which isn't necessarily what's being requested here, and option D is simply renaming the file, not applying semantic versioning.
43 / 45
The term 'cherry-pick' originates from software development and refers specifically to selecting individual commits (changes) from one branch and applying them to another. It's a manual process, not an automated merge; Lisa's confusion highlights the importance of understanding this terminology precisely. Selecting only relevant changes avoids unnecessary complexity and potential conflicts when integrating updates into the artifact registry.
44 / 45
Maria is misunderstanding how modern artifact registries function. The system typically *automatically* detects a new deployment to a staging environment and creates a new artifact based on that event – this is often tied to continuous integration/continuous delivery (CI/CD) pipelines. Versioning then happens automatically as part of the release process, not manually by tagging. Therefore, option 1 accurately describes the system's behavior.
45 / 45
Alex is utilizing semantic versioning, which involves using a numerical system (typically `major.minor.patch`) to track changes in software releases. This allows for clear communication about the compatibility of different versions and aids in managing deployments effectively. The incorrect options misinterpret semantic versioning as a deployment method or a random identifier; it's fundamentally about structured version control.
Frequently Asked Questions
What will I practice in "Artifact Management Vocabulary"?
This is a CI/CD Pipeline Language exercise set. It walks through 45 scenario-based multiple-choice questions built around real usage of CI/CD Pipeline Language terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 45 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the CI/CD Pipeline Language vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more CI/CD Pipeline Language exercises?
See the CI/CD Pipeline Language exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — CI/CD Pipeline Language vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.