CI/CD Pipeline Design and Architecture Questions
Structure and operation of continuous integration and continuous delivery pipelines: stages, triggers, build/test/deploy steps, pipeline-as-code, caching, and parallelization. Covers designing enterprise-scale CI/CD architecture, integrating version control with automated pipelines, and shaping delivery workflows across many services. Focuses on how work moves from commit to production, not on the individual test suites that run inside it.
An attacker exfiltrated a secret via a compromised third-party GitHub Action used in CI runs. Describe detection, containment and remediation, stakeholder communication, and the long-term prevention measures you'd put in place to stop the same class of compromise from recurring.
As a solutions architect evaluate three approaches for secrets in CI/CD: (A) a centralized Vault with dynamic credentials, (B) platform-native sealed secrets or cluster secret stores, and (C) encrypted variables stored in the CI system. For each approach discuss security guarantees, operational complexity, secret rotation capabilities, developer experience, and auditability. Recommend which to use for a regulated financial customer and why.
Design a policy-as-code framework to enforce organizational policies across CI pipelines and deployments (for example: no direct prod deploys, only approved base images, mandatory SBOM verification). Describe where policies should run (PR checks, pre-apply gates, Kubernetes admission controllers), policy versioning, and how to present actionable feedback to developers.
Design a CI/CD pipeline that builds container images from git commits for 200 microservices, performs static code analysis, runs unit tests, builds the image, generates an SBOM, scans the image for vulnerabilities, signs the image, and then promotes without rebuilding from dev to staging to prod. Sketch pipeline stages, gating criteria for promotion, optional manual approvals for prod, and tooling choices (examples: GitHub Actions/GitLab CI/Tekton, Trivy, Syft, Cosign).
Design a SQL schema for artifact metadata to support queries such as 'find all artifacts built from commit X' and 'list unsigned artifacts older than 30 days'. Provide a CREATE TABLE example with fields: artifact_id (PK), version, build_id, commit_sha, builder, created_at, size_bytes, signed (boolean), provenance_blob (JSON). Then write SQL queries for the two sample questions and explain indexing choices.
Unlock Full Question Bank
Get access to all 11 CI/CD Pipeline Design and Architecture interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.