SAFe® 5 DevOps Certification SAFe® 5 DevOps: Continuous Deployment 2 — Questions and Answers
Question 1: Which SAFe® 5 DevOps practice helps teams achieve zero-downtime deployments?
- Deploying only during scheduled maintenance windows approved by the CAB
- Using deployment strategies such as blue-green, canary, or rolling updates (Correct answer)
- Requiring all team members to be on-call during every deployment
- Limiting deployments to once per Program Increment to reduce risk
Correct answer: Using deployment strategies such as blue-green, canary, or rolling updates
Techniques like blue-green, canary, and rolling deployments allow new versions to be introduced incrementally so users experience no downtime during the transition.
Question 2: In SAFe® 5 DevOps, what is the purpose of a deployment verification test (smoke test) run after production deployment?
- To run the full regression suite on the production environment to ensure all features work
- To quickly validate that critical functionality is working after a deployment before full traffic is enabled (Correct answer)
- To compare the production database schema against the staging schema
- To notify stakeholders that a deployment has been initiated
Correct answer: To quickly validate that critical functionality is working after a deployment before full traffic is enabled
Smoke tests after deployment quickly verify that critical system paths are operational, allowing teams to detect catastrophic failures immediately and roll back if needed.
Question 3: How does Continuous Deployment differ from Continuous Delivery in SAFe® 5 DevOps?
- Continuous Deployment is manual while Continuous Delivery is fully automated
- Continuous Delivery deploys every passing build to production automatically; Continuous Deployment requires a manual approval gate before production
- Continuous Deployment automatically deploys every passing build to production; Continuous Delivery keeps the software in a deployable state but may require a manual gate (Correct answer)
- There is no difference — the terms are used interchangeably in SAFe® 5
Correct answer: Continuous Deployment automatically deploys every passing build to production; Continuous Delivery keeps the software in a deployable state but may require a manual gate
Continuous Deployment pushes every passing build straight to production automatically, while Continuous Delivery ensures software is always release-ready but allows a manual approval step before production.
Question 4: What role does a rollback strategy play in SAFe® 5 DevOps Continuous Deployment?
- It provides a plan to revert a deployment quickly if critical defects are discovered in production (Correct answer)
- It defines how teams roll back sprint goals when capacity is exceeded
- It outlines the process for reverting code changes in the source control repository only
- It is used exclusively during blue-green deployments and not other deployment types
Correct answer: It provides a plan to revert a deployment quickly if critical defects are discovered in production
A rollback strategy defines how to quickly restore the previous stable version of an application if a new deployment introduces critical failures in production.
Question 5: In SAFe® 5 DevOps, which practice ensures that deployment scripts and infrastructure definitions are treated as first-class code artifacts?
- Continuous Integration
- Infrastructure as Code (IaC) (Correct answer)
- Release on Demand
- Value Stream Mapping
Correct answer: Infrastructure as Code (IaC)
Infrastructure as Code treats deployment scripts and infrastructure definitions as versioned source code, enabling automated, consistent, and repeatable deployments.
Question 6: What is the primary benefit of automating deployment pipelines in SAFe® 5 DevOps?
- It eliminates the need for developers to write automated tests
- It reduces deployment risk by making the process consistent, fast, and repeatable (Correct answer)
- It ensures that all deployments are approved by the Change Advisory Board
- It allows teams to skip the staging environment and deploy directly to production
Correct answer: It reduces deployment risk by making the process consistent, fast, and repeatable
Automated deployment pipelines reduce human error and inconsistency, making deployments faster, more reliable, and repeatable across all environments.
Question 7: In the context of SAFe® 5 DevOps, what does 'deployment frequency' indicate about an organization's DevOps maturity?
- Higher deployment frequency always indicates lower software quality
- Higher deployment frequency suggests smaller, safer changes and a more mature deployment pipeline (Correct answer)
- Deployment frequency is only relevant for web applications, not enterprise systems
- Deployment frequency measures how many developers are available to perform releases
Correct answer: Higher deployment frequency suggests smaller, safer changes and a more mature deployment pipeline
Higher deployment frequency is a sign of DevOps maturity because it means the team is making smaller, lower-risk changes with a reliable automated pipeline, as identified in the DORA research.
SAFe® 5 DevOps Certification SAFe® 5 DevOps: Continuous Deployment 2
Which SAFe® 5 DevOps practice helps teams achieve zero-downtime deployments?