SAFe® 5 DevOps: Continuous Deployment Flashcards
7 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 7 SAFe® 5 DevOps: Continuous Deployment flashcards as text
Which SAFe® 5 DevOps practice helps teams achieve zero-downtime deployments?
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.
In SAFe® 5 DevOps, what is the purpose of a deployment verification test (smoke test) run after production deployment?
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.
How does Continuous Deployment differ from Continuous Delivery in SAFe® 5 DevOps?
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.
What role does a rollback strategy play in SAFe® 5 DevOps Continuous Deployment?
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.
In SAFe® 5 DevOps, which practice ensures that deployment scripts and infrastructure definitions are treated as first-class code artifacts?
Answer: Infrastructure as Code (IaC)
Infrastructure as Code treats deployment scripts and infrastructure definitions as versioned source code, enabling automated, consistent, and repeatable deployments.
What is the primary benefit of automating deployment pipelines in SAFe® 5 DevOps?
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.
In the context of SAFe® 5 DevOps, what does 'deployment frequency' indicate about an organization's DevOps maturity?
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.