List essential components of a deployment pipeline.

List essential components of a deployment pipeline.

• A. Version control, code review, production monitoring.
• B. Source control, CI, build, test, artifact storage, deployment, verification, monitoring.
• C. Planning, budgeting, approvals, post-mortems.
• D. Design, coding, debugging, deployment.

Answer: (B)

A deployment pipeline is an automated, repeatable flow that starts with code in version control and ends with a running, observable system. The essential stages in this flow are: source control to manage code changes; continuous integration to automatically bring those changes together; build to compile and assemble artifacts; automatic tests to verify quality; artifact storage to keep build outputs for reproducible deployments; deployment to release the artifact into target environments; verification to confirm the deployment worked (health checks, smoke tests); and monitoring to observe performance and reliability in production and trigger alerts or rollbacks if needed. This combination captures the full lifecycle from code to production and includes validation and feedback loops at multiple points. The other options miss one or more of these core elements—focusing on planning or design, or omitting automated testing, artifact management, or verification—so they don’t represent the complete pipeline.

A deployment pipeline is an automated, repeatable flow that starts with code in version control and ends with a running, observable system. The essential stages in this flow are: source control to manage code changes; continuous integration to automatically bring those changes together; build to compile and assemble artifacts; automatic tests to verify quality; artifact storage to keep build outputs for reproducible deployments; deployment to release the artifact into target environments; verification to confirm the deployment worked (health checks, smoke tests); and monitoring to observe performance and reliability in production and trigger alerts or rollbacks if needed.

This combination captures the full lifecycle from code to production and includes validation and feedback loops at multiple points. The other options miss one or more of these core elements—focusing on planning or design, or omitting automated testing, artifact management, or verification—so they don’t represent the complete pipeline.