SAFe® 5 DevOps Certification SAFe 5 DevOps CI/CD Pipeline — Questions and Answers
Question 1: What is the primary purpose of Continuous Integration (CI) in SAFe DevOps?
- To merge code changes frequently and verify each integration with automated builds and tests (Correct answer)
- To deploy code directly to production
- To replace manual testing entirely
- To manage infrastructure provisioning
Correct 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.
Question 2: What is Continuous Deployment versus Continuous Delivery in SAFe?
- Continuous Deployment automatically releases every change to production; Continuous Delivery makes every change releasable but deployment is manual (Correct answer)
- They are the same thing
- Continuous Delivery is faster than Continuous Deployment
- Continuous Deployment only applies to non-production environments
Correct 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.
Question 3: What role does Infrastructure as Code (IaC) play in the SAFe DevOps pipeline?
- It enables consistent, version-controlled, and automated provisioning of infrastructure environments (Correct answer)
- It replaces all software testing
- It only manages physical server hardware
- It provides user interface design tools
Correct 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.
Question 4: What is the purpose of feature toggles (feature flags) in a DevOps context?
- To enable or disable features in production without deploying new code (Correct answer)
- To track feature requests from customers
- To toggle between different programming languages
- To switch between development environments
Correct 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.
Question 5: What is the SAFe recommended approach to testing in the CI/CD pipeline?
- Shift-left testing with automated unit, integration, and acceptance tests running at every stage (Correct answer)
- Manual testing only before production releases
- Testing only after deployment to production
- A single comprehensive test suite run monthly
Correct 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.
Question 6: What is the blast radius concept in DevOps release strategies?
- The scope of impact if a deployment fails, which should be minimized through incremental releases (Correct answer)
- The distance a notification travels through the organization
- The number of teams involved in a release
- The amount of code changed in a deployment
Correct 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.
SAFe® 5 DevOps Certification SAFe 5 DevOps CI/CD Pipeline
What is the primary purpose of Continuous Integration (CI) in SAFe DevOps?