SAFe 5 DevOps CI/CD Pipeline Flashcards
6 cards from real SAFe® 5 DevOps Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 SAFe 5 DevOps CI/CD Pipeline flashcards as text
What is the primary purpose of Continuous Integration (CI) in SAFe DevOps?
Answer: To merge code changes frequently and verify each integration with automated builds and tests
CI ensures that developers frequently merge code changes into a shared repository, where automated builds and tests verify each integration, catching defects early and reducing integration risk.
What is Continuous Deployment versus Continuous Delivery in SAFe?
Answer: Continuous Deployment automatically releases every change to production; Continuous Delivery makes every change releasable but deployment is manual
Continuous Delivery means every change passes through the pipeline and is ready for production release, but deployment is a business decision. Continuous Deployment automates the final step, releasing every validated change automatically.
What role does Infrastructure as Code (IaC) play in the SAFe DevOps pipeline?
Answer: It enables consistent, version-controlled, and automated provisioning of infrastructure environments
Infrastructure as Code treats infrastructure configuration as software code, enabling version control, automated provisioning, consistent environments, and rapid scaling through tools like Terraform, Ansible, or CloudFormation.
What is the purpose of feature toggles (feature flags) in a DevOps context?
Answer: To enable or disable features in production without deploying new code
Feature toggles allow teams to merge incomplete features into the main branch and deploy to production while keeping them hidden, enabling trunk-based development, gradual rollouts, and quick rollbacks.
What is the SAFe recommended approach to testing in the CI/CD pipeline?
Answer: Shift-left testing with automated unit, integration, and acceptance tests running at every stage
SAFe advocates shift-left testing where automated tests are integrated at every pipeline stage, with fast unit tests running first, followed by integration tests, acceptance tests, and performance tests, catching defects as early as possible.
What is the blast radius concept in DevOps release strategies?
Answer: The scope of impact if a deployment fails, which should be minimized through incremental releases
Blast radius refers to the potential impact scope of a failed deployment. Techniques like canary releases, blue-green deployments, and feature flags minimize blast radius by limiting exposure of changes to small user segments initially.