300-910 · Question #102
A DevOps team is working on a Docker pipeline for CI. The Dockerfile is built out based on specifications. Linters are used to verify the Dockerfile committed. What is the next phase in the pipeline?
The correct answer is D. Build. After committing and linting a Dockerfile in a CI pipeline, the logical next step is to build the Docker image according to the Dockerfile specifications.
Question
Exhibit
Options
- ATest
- BRUN/STORE
- CRelease/Deploy
- DBuild
How the community answered
(25 responses)- A4% (1)
- B4% (1)
- D92% (23)
Why each option
After committing and linting a Dockerfile in a CI pipeline, the logical next step is to build the Docker image according to the Dockerfile specifications.
Testing typically occurs after the Docker image has been successfully built, as tests need a deployable artifact to run against.
'RUN/STORE' is not a standard CI pipeline phase; images are usually stored in a registry (e.g., pushed) after being built, and 'RUN' implies executing the container, which is part of testing or deployment.
Release/Deploy is a later stage in the CI/CD process, occurring after building and testing are complete and the artifact is deemed ready for deployment to environments.
In a CI pipeline focused on Docker, after a Dockerfile is committed and verified (linted), the immediate subsequent phase is to use that Dockerfile to build the Docker image. This 'Build' phase transforms the Dockerfile and application source code into a runnable container image, making it ready for subsequent testing or deployment.
Concept tested: Docker CI pipeline phases
Source: https://learn.microsoft.com/en-us/azure/devops/pipelines/ecosystems/containers/build-image?view=azure-devops#ci-cd-pipeline-for-containers
Topics
Community Discussion
No community discussion yet for this question.
