SAFe-DevOps Exam Questions & Answers

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.

The Respond activity in the SAFe DevOps Health Radar is about proactively detecting and resolving production issues before they cause business disruption. It requires two skills: cross-team collaboration and version control. Cross-team collaboration enables faster resolution of incidents by involving the right people and teams.Version control enables tracking changes and restoring previous versions of the code or configuration if needed

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, Continuous Deployment is a practice that helps developers deploy their code into production. This means that Continuous Deployment involves moving changes from the staging environment to the production environment, without requiring manual intervention or approval.The handbook states that 'Continuous Deployment is the practice of moving changes from the staging environment to the production environment, without requiring manual intervention or approval.'1Therefore, Continuous Deployment enables teams to deliver value to customers faster and more reliably.

The correct answer is B. Flow Efficiency measures the percentage of time spent on value-added activities in the Value Stream. A Value Stream is a sequence of activities that deliver value to the customer, from concept to cash. Value-added activities are those that directly contribute to the customer value proposition, such as coding, testing, and deploying. Non-value-added activities are those that do not directly contribute to the customer value proposition, such as waiting, handoffs, rework, and approvals. Flow Efficiency is calculated by dividing the total time spent on value-added activities by the total flow time, which is the time elapsed from when a work item enters the Value Stream to when it is delivered to the customer. Flow Efficiency is a metric that helps to identify and eliminate waste and delays in the Value Stream, and to optimize the flow of value to the customer. Flow Efficiency can be improved by applying the principles and practices of DevOps, such as reducing batch size, limiting work in progress, implementing pull systems, managing queue lengths, reducing handoffs, implementing Work in Process (WIP) visualization, and implementing Work in Process (WIP) feedback

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