[Mar-2024] Check your preparation for Scrum SAFe-DevOps On-Demand Exam [Q40-Q56]

Explanation
According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the statement that illustrates the biggest bottleneck is B. WT = 10 days, AT = 0.5 day, %C&A = 100%. This means that the value stream has the longest lead time (WT), the shortest actual time (AT), and the highest relative economic value (C&A).
These are the three metrics that are used to measure and optimize the value stream performance. The handbook states that “The three metrics used to measure and optimize value stream performance are WT, AT, and %C&A.”1 Therefore, a bigger bottleneck indicates a lower value stream efficiency and a higher waste or inefficiency.

Explanation
The desired frequency of deployment in SAFe is continuous, meaning that new functionality can be deployed to production as soon as it is ready, without waiting for fixed release dates or schedules. Continuous deployment is an aspect of the CDP that automates the migration of new functionality from a staging environment to production, where it is made available for release. Continuous deployment enables the ability to release value at any time, in a sustainable way

Explanation
The correct answer is D. Flow, quality, and value should be measured in a CALMR approach to DevOps. The CALMR approach to DevOps is a mindset that guides the ARTs toward achieving continuous value delivery by enhancing culture, automation, lean flow, measurement, and recovery. Measurement is one of the key elements of the CALMR approach, as it provides data and feedback to monitor and improve the performance and outcomes of the solution delivery process. Measurement involves collecting and analyzing metrics that reflect the flow, quality, and value of the solution, such as:
Flow metrics – Flow metrics measure the efficiency and reliability of the delivery process, such as lead time, cycle time, throughput, work in progress, and flow efficiency. Flow metrics help to identify and eliminate waste and bottlenecks in the value stream, and to optimize the flow of value to the customer.
Quality metrics – Quality metrics measure the functionality and stability of the solution, such as defect rate, defect density, defect leakage, mean time to detect, mean time to resolve, and test coverage.
Quality metrics help to ensure that the solution meets the functional and nonfunctional requirements and standards, and to detect and resolve any issues or defects as early as possible.
Value metrics – Value metrics measure the outcomes and benefits of the solution, such as customer satisfaction, retention, engagement, revenue, and net promoter score. Value metrics help to evaluate the validity of the hypotheses and assumptions about the customer value proposition, and to guide the decision making and prioritization of the features12

Explanation
The reason why it is important to take a structured approach to analyze problems in the delivery pipeline is that it helps ensure that actual causes of problems are addressed, rather than symptoms. A structured approach to problem analysis involves following a systematic and logical process to identify, define, and understand the root causes of a problem, and to propose and evaluate possible solutions. A structured approach can help avoid jumping to conclusions, making assumptions, or applying band-aid fixes that do not solve the underlying issues. A structured approach can also help involve the relevant stakeholders, collect and analyze data, prioritize and categorize problems, and communicate and document the findings and recommendations. Some examples of structured approaches to problem analysis are the 5 Whys, the fishbone diagram, the Pareto chart, and the PDCA cycle

Explanation
Culture is a core DevOps principle. DevOps is not only a set of technical practices, but also a mindset and a culture that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps culture is based on the following values and behaviors:
Shared responsibility – DevOps culture fosters a sense of shared ownership and accountability for the entire solution lifecycle, from ideation to operation. Development and operations teams work together, not only to help each other, but also to ensure that the overall organization succeeds. DevOps culture eliminates the blame game and the silo mentality, and encourages mutual trust and respect among all stakeholders.
Continuous learning – DevOps culture promotes a culture of continuous learning and improvement, where teams are constantly seeking feedback, experimenting with new ideas, and learning from failures.
DevOps culture embraces a growth mindset, where teams are not afraid to try new things, challenge the status quo, and learn from their mistakes. DevOps culture also supports a learning organization, where teams share their knowledge and best practices, and leverage the collective intelligence of the whole enterprise.
Customer focus – DevOps culture emphasizes the importance of delivering value to the customer, and aligning the solution to the customer needs and expectations. DevOps culture applies customer-centric and design thinking approaches, such as personas, empathy maps, and customer journeys, to understand and empathize with the customer problems and desires. DevOps culture also validates the assumptions and hypotheses about the customer value proposition, by collecting and analyzing data and feedback from the customer.
Automation – DevOps culture leverages automation to improve the efficiency, quality, and reliability of the solution delivery process. DevOps culture applies automation to various aspects of the Continuous Delivery Pipeline, such as testing, integration, deployment, monitoring, and security. DevOps culture also uses automation to reduce manual work, eliminate human errors, and accelerate feedback loops5

Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, a canary release is a type of release on demand that involves making a Solution available to any subset of users, such as a specific team, product, or region. A canary release allows the DevOps teams to test the Solution in a controlled environment and monitor its performance and feedback before rolling it out to the entire customer base. A canary release can help reduce the risk of introducing errors or failures into production and improve the quality and reliability of the Solution.

Explanation
The Release on Demand aspect enables the key business objective of delivering business value to customers.
Release on Demand is the process by which features deployed into production are released incrementally or immediately to customers based on market demand. It is the final aspect of the Continuous Delivery Pipeline (CDP) in SAFe DevOps, which enables the delivery of value to the end user as fast as possible, based on market demand. The decision of what and when to release is a critical economic driver that requires careful consideration of the customer needs, market rhythms, and economic outcomes. Release on Demand is decoupled from the Continuous Deployment activity, which automates the migration of new functionality from a staging environment to production, where it is made available for release. Release on Demand involves four activities: release, stabilize and operate, measure, and learn. These activities help to deliver the solution to end users, ensure the solution is working well from a functional and nonfunctional perspective, quantify the value delivered by the solution, and collect feedback and prepare for the next loop through the CDP3

Explanation
Trunk-based development is a version control management practice where all developers work on the same trunk of shared code. The trunk is always in a releasable state, which means that at least once a day, developers must integrate their changes to the trunk. This is accomplished through short-lived feature branches related to project tasks. Trunk-based development is a common practice among DevOps teams and part of the DevOps lifecycle since it streamlines merging and integration phases. It also enables continuous integration, which is the practice of merging all development versions of a code base several times a day. Trunk-based development has several benefits, such as:
It reduces the complexity and conflicts of merging long-lived branches
It improves the quality and consistency of the code by enforcing frequent testing and validation It accelerates the delivery and deployment of new functionality by minimizing the transaction cost and risk It fosters a culture of collaboration and transparency among developers

Explanation
Identifying the Minimal Marketable Feature (MMF) is part of Lean UX, which is a user-centric approach to designing and delivering products. An MMF is a small, self-contained feature that can be developed quickly and that delivers significant value to the user. It is the smallest unit of functionality that can be released to the market and generate feedback. Lean UX advocates for releasing MMFs as early and often as possible, to validate assumptions, learn from users, and iterate on the product

Explanation
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

Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, the Release activity is the final step in the Continuous Delivery Pipeline that deploys the Solution to production. Production is where the Solution is available for end users to operate and consume. The Release activity involves verifying that the Solution meets the quality and security requirements, monitoring its performance and health, and responding to any issues or incidents that may arise. The Release activity also enables continuous improvement by measuring the business value of the Solution and collecting feedback from customers and stakeholders.

Explanation
One skill that can significantly accelerate mean-time-to-restore by enabling support teams to see issues the way actual end users did is session replay. Session replay is a technique that allows the support team to replay end-user sessions to research incidents and identify problems. Session replay captures the user’s interactions with the application, such as clicks, scrolls, keystrokes, and mouse movements, and reproduces them in a video-like format. Session replay can help the support team to understand the user’s behavior, context, and feedback, as well as to reproduce and diagnose errors, bugs, and performance issues. Session replay can also help the support team to communicate and collaborate with the development team and the stakeholders, by providing visual evidence and data of the incidents. Session replay can significantly accelerate mean-time-to-restore by reducing the time and effort required to investigate and resolve issues, as well as by improving the quality and reliability of the application

Explanation
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

Explanation
The statement that is true about DevOps is that it enables low-risk releases and fast recovery with fast fix-forward. DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps aims to deliver value to customers whenever there is a business need, by applying the principles of continuous delivery, continuous integration, continuous deployment, and release on demand. DevOps also embraces a culture of learning and experimentation, where failures are opportunities for improvement and feedback. DevOps enables low-risk releases by breaking down large and complex changes into smaller and more frequent batches, which are easier to test, deploy, and rollback if needed. DevOps also enables fast recovery by implementing practices such as monitoring, alerting, incident response, and disaster recovery, which help to detect and resolve issues quickly, minimize the impact of failures, and restore normal operations as soon as possible. DevOps also supports the fast fix-forward approach, which means fixing errors in production by deploying new code, rather than rolling back to a previous state. This approach reduces the risk of introducing new errors, preserves the value of the new functionality, and accelerates the learning cycle

Explanation
According to the SAFe DevOps Practitioner 6.0 study guide and handbook, when development and operations do not collaborate early in the pipeline, surprises are found in deployment that lead to significant rework and delay. This means that the teams may not have a shared understanding of the quality, performance, and security requirements of the Solution, and may encounter issues that were not anticipated or tested. The handbook states that “When development and operations do not collaborate early in the pipeline, surprises are found in deployment that lead to significant rework and delay.”1 Therefore, it is important for teams to work together throughout the value stream to ensure continuous delivery.

Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, the Critical Flow Properties portion of the DevOps Transformation Canvas captures the flow properties that are most in need of improvement. Flow properties are the characteristics of a value stream that affect how well it delivers value to customers. The Critical Flow Properties portion identifies the flow properties that have the most impact on customer satisfaction and business outcomes, and prioritizes improvement actions accordingly. The Critical Flow Properties portion is based on data from monitoring systems, customer feedback, and business value analysis.
Therefore, it captures the flow properties that are most in need of improvement for each value stream.