Refer to the exhibit. A development team is designing an application that will include multiple components and services. To streamline the process, CO/CD must be implemented. Drag and drop the CI/CD p

Question

Explanation

This question tests knowledge of the correct sequential ordering of CI/CD pipeline stages in a modern DevOps workflow. Candidates must map each stage to its proper position in the pipeline based on logical dependency and industry best practice.

Approach. A standard CI/CD pipeline follows this sequence: (1) Source - code is committed/pushed to version control, triggering the pipeline; (2) Build - the application is compiled and artifacts are created; (3) Test - automated unit, integration, and static analysis tests validate the build; (4) Deploy to Staging - the artifact is deployed to a pre-production environment for further validation; (5) Acceptance/Integration Testing - end-to-end or UAT tests run against the staging environment; (6) Deploy to Production - after approval gates pass, the artifact is promoted to production. This order enforces the principle of 'fail fast and early' - catching defects at the cheapest stage possible before they reach production.

Concept tested. CI/CD pipeline stage sequencing - understanding the dependency chain from code commit through automated build, test, staging deployment, acceptance testing, and final production release, as well as how each stage gates the next.

Reference. CompTIA DevOps+ (DevOps+) Exam Objectives - Domain 2: Deployment Pipeline Automation; also aligns with DORA metrics and GitLab/Jenkins pipeline best practices.

No community discussion yet for this question.