Which description best captures the purpose of an artifact repository in a CI/CD workflow?

Which description best captures the purpose of an artifact repository in a CI/CD workflow?

• A. Stores source code.
• B. Stores build logs and temporary files.
• C. Monitors production environments.
• D. Stores build artifacts with versioning for reproducible deployments.

Answer: (D)

In CI/CD, you want a dependable, auditable place to store the outputs of your builds so you can deploy the exact artifact you tested. An artifact repository serves this role by holding build artifacts with versioning. Each artifact gets a unique version and metadata, making deployments reproducible across environments and allowing easy rollback to a previous version if needed. It also enables promotion through stages (dev, test, staging, prod) by moving the same artifact through the pipeline. This is distinct from storing source code in a code repository, which is about the original files, or from build logs and temporary files, which are typically transient. It’s also separate from monitoring production environments, which focuses on observing runtime behavior. For example, a compiled library or a Docker image is built, pushed to the artifact store with a version tag, and later pulled by deployment to guarantee that the exact same artifact is used. So the description that best captures the purpose is to store build artifacts with versioning for reproducible deployments.

In CI/CD, you want a dependable, auditable place to store the outputs of your builds so you can deploy the exact artifact you tested. An artifact repository serves this role by holding build artifacts with versioning. Each artifact gets a unique version and metadata, making deployments reproducible across environments and allowing easy rollback to a previous version if needed. It also enables promotion through stages (dev, test, staging, prod) by moving the same artifact through the pipeline. This is distinct from storing source code in a code repository, which is about the original files, or from build logs and temporary files, which are typically transient. It’s also separate from monitoring production environments, which focuses on observing runtime behavior. For example, a compiled library or a Docker image is built, pushed to the artifact store with a version tag, and later pulled by deployment to guarantee that the exact same artifact is used. So the description that best captures the purpose is to store build artifacts with versioning for reproducible deployments.