Scaled Agile SAFe DevOps Practitioner Exam SDP (6.0) SAFe-DevOps Exam Practice Test

Answer : C

Refactoring is the activity of improving the internal structure or operation of a code or component without changing its external behavior. The goal of software development is the continuous delivery of business value to users and stakeholders. Constantly changing technology and evolving business objectives make maintaining and continuously increasing business value difficult. Refactoring enables an emergent design, ensuring the system continues to meet future business needs. Refactors are a particular type of Enabler story in SAFe, and, like any other Story, they must be estimable, verifiable, and valuable, as well as accepted by the Product Owner. SAFe emphasizes the importance of keeping all work visible, including refactoring. Like user value work, refactoring must be planned for, estimated, and prioritized.Therefore, developers should create and estimate refactoring Stories in the Team Backlog, and work on them according to their WSJF1

Answer : C

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the metric that reflects the quality of output at each step in the Value Stream is Percent Complete and Accurate (%C&A). This metric measures the relative cost of delay divided by the relative job duration, which indicates how efficiently the value stream delivers value to customers.The handbook states that 'Percent Complete and Accurate (%C&A) is a metric that measures the relative cost of delay divided by the relative job duration.'1Therefore, %C&A helps teams identify and eliminate any waste or inefficiencies in their value stream.

Answer : A

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the Release activity is triggered by a business decision to go live. This means that the Solution is ready to be delivered to end users and customers, based on the validation and testing done in the previous activities.The handbook states that 'The Release activity is triggered by a business decision to go live.'1Therefore, this activity involves releasing value to customers on demand, while also measuring and learning from the feedback.

Answer : D

Continuous Deployment (CD) is an aspect of the Continuous Delivery Pipeline that automates the migration of new functionality from a staging environment to production, where it is made available for release. CD is a technical practice that enables the ability to release value at any time, in a sustainable way. CD is not the same as Release on Demand, which is the business decision to make the new functionality available to end users.Release on Demand is the final aspect of the Continuous Delivery Pipeline, which enables the delivery of value to the end user as fast as possible, based on market demand

Answer : B

Under the Respond activity in the context of DevOps, the practice of Rollback is often included. Rollback is a key response mechanism used to quickly revert a system to a previous stable state in the event of a failure or issue in the production environment. This practice is critical for maintaining system stability and minimizing downtime.

Answer : D

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, one potential outcome of the Verify activity of the Continuous Delivery Pipeline is to analyze regression testing results. This means that the Verify activity involves checking the functionality and performance of the Solution after a deployment, and comparing it with the expected results.The handbook states that 'Verify is the activity of checking the functionality and performance of the Solution after a deployment, and comparing it with the expected results.'1Therefore, one of the possible outcomes of this activity is to analyze how well the Solution meets the quality standards and customer requirements.

Answer : A

Weighted Shortest Job First (WSJF) is a prioritization model used to sequence work for maximum economic benefit. In SAFe, WSJF is estimated as the relative cost of delay divided by the relative job duration. In a flow-based system, priorities must be continuously updated to provide the best economic outcomes. In other words, job sequencing produces the best results rather than prioritization based on a theoretical return on investment for each job. To that end, SAFe applies WSJF to prioritize backlogs. Backlogs are continuously prioritized based on a WSJF algorithm that uses relative user and business value, time criticality, risk reduction and/or opportunity enablement, and job size.WSJF also conveniently and automatically ignores sunk costs, a fundamental principle of Lean economics