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 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 %C&A metric measures the percent of time downstream customers receive work that is usable as-is in the Continuous Delivery Pipeline. The %C&A metric is a measure of the quality of the work output from a process step. It indicates the percentage of time that the downstream customers receive work that is acceptable as is, without any rework or errors. To calculate the %C&A metric, the people responsible for the next step need to inspect the work output from the previous step and determine whether it meets the quality standards and expectations. They also need to provide feedback to the previous step on the defects or issues they find and how they affect the value stream. By measuring the %C&A metric, the enterprise can gain insight into the current state of the delivery process, such as the lead time, cycle time, throughput, quality, and waste. This insight can help the enterprise identify bottlenecks, dependencies, handoffs, delays, and inefficiencies that affect the flow of value. The %C&A metric can also help the enterprise understand how the flow of value can be improved by applying the principles and practices of DevOps, such as culture, automation, lean flow, measurement, and recovery. By improving the %C&A metric, the enterprise can increase customer satisfaction, reduce costs, accelerate time-to-market, and enhance business agility

Explanation
One of the recommended ways to architect for operations is to implement feature toggles, which are mechanisms that allow developers to turn features on or off without redeploying the code. Feature toggles enable faster and safer deployments, as well as experimentation and testing in production. They also allow the operations team to control when and how new features are released to the end users, based on business needs and market demand. Feature toggles can also be used to mitigate risks and roll back changes in case of errors or failures

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
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 purpose of value stream mapping is to visualize how value flows from concept to cash and to deliver incremental value in the form of working, tested software and systems. Value stream mapping helps to identify the current state of the value stream, the steps, activities, roles, and tools involved, and the delays, waste, and inefficiencies that can be eliminated or improved. It also helps to create a future state vision and an action plan for continuous improvement

Explanation
The people responsible for the next step should be consulted first when calculating the % Complete and Accurate (%C&A) metric. The %C&A metric is a measure of the quality of the work output from a process step. It indicates the percentage of time that the downstream customers receive work that is acceptable as is, without any rework or errors. To calculate the %C&A metric, the people responsible for the next step need to inspect the work output from the previous step and determine whether it meets the quality standards and expectations. They also need to provide feedback to the previous step on the defects or issues they find and how they affect the value stream. By consulting the people responsible for the next step, the %C&A metric can reflect the actual customer satisfaction and the potential waste in the process1

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
Value stream mapping metrics include calculations of three metrics: total process time, rolled % complete and accurate, and activity ratio. Value stream mapping is a lean technique to analyze, design, and manage the flow of materials and information required to bring a product or service to a customer. It uses a system of standard symbols to depict various work streams and information flows, and to identify value-adding and non-value-adding activities. Value stream mapping metrics are used to measure the efficiency and effectiveness of a production process, and to identify areas for improvement. Some of the common value stream mapping metrics are:
Total process time: the sum of the process times for all the activities in the value stream. It measures how long it takes to complete a unit of work from start to finish.
Rolled % complete and accurate: the percentage of units that are completed and accurate at each step of the value stream, multiplied across all the steps. It measures the quality and reliability of the process output.
Activity ratio: the ratio of value-adding time to total lead time. It measures the proportion of time spent on activities that create value for the customer, versus activities that do not

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
In addition to Continuous Integration, two other aspects of the CDP are Continuous Deployment and Continuous Exploration. Continuous Deployment 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. Continuous Exploration focuses on creating alignment on what needs to be built, using design thinking and hypothesis-driven development. Continuous Exploration enables the discovery of the most valuable solutions for the customers and the enterprise

Explanation
The purpose of the blue/green deployment pattern is to deploy between an inactive and active environment.
The blue/green deployment pattern is a change management strategy for software releases that reduces the downtime and risk of deploying new versions of software. The blue/green deployment pattern involves having two identical but separate environments: one is the active environment (blue) that serves the user traffic, and the other is the inactive environment (green) that hosts the new version of the software. The deployment process consists of switching the user traffic from the blue environment to the green environment, after verifying that the new version is working properly. The blue environment can then be kept as a backup or updated to become the next green environment. The blue/green deployment pattern has several benefits, such as:
It allows for fast and reliable rollback, in case of any issues or errors in the new version, by simply switching back to the blue environment.
It eliminates the need for complex and error-prone migration scripts, as the green environment can be prepared and tested in advance, without affecting the blue environment.
It enables testing and experimentation of the new version with a subset of users, by directing some user traffic to the green environment, before switching completely.
It facilitates continuous delivery and deployment, by automating the switching process and reducing the transaction cost and risk of moving changes to production

Explanation
The output of the Release activity is a Feature made available to end users. The Release activity 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 Release activity involves the practices needed to deliver the solution to end users, all at once or incrementally. The Release activity is a business decision that requires careful consideration of the customer needs, market rhythms, and economic outcomes. The Release activity 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

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
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
The statement that describes the Lean startup lifecycle is: Define the hypothesis, build a minimum viable product (MVP), continuously evaluate the MVP while implementing additional Features until WSJF determines work can stop. The Lean startup lifecycle is a highly iterative build-measure-learn cycle that has proven to be effective in optimizing the economic value of strategic investments. It consists of three learning milestones: MVP, tune the engine, and pivot or persevere. The MVP is the smallest possible experiment that allows the enterprise to test the assumptions and hypotheses of an epic or a large initiative. The tune the engine phase involves quickly adjusting and moving towards the goal based on the data and feedback gathered from the MVP. The pivot or persevere phase involves deciding whether to deliver additional value or move on to something more valuable based on the validated learning. The Lean startup lifecycle is supported by the SAFe Lean Startup Cycle, which provides guidance and tools for applying the Lean startup principles in the context of SAFe. The SAFe Lean Startup Cycle includes the following steps:
Define the hypothesis – This step involves creating an epic hypothesis statement that defines the initiative, its expected benefits, and its leading indicators.
Build the MVP – This step involves defining, building, and deploying the MVP that tests the hypothesis and delivers the minimum amount of value to the customer.
Evaluate the MVP – This step involves measuring and analyzing the results of the MVP against the leading indicators and the hypothesis.
Implement additional Features – This step involves developing and delivering additional features or capabilities that enhance the value proposition of the initiative, based on the learning from the MVP.
WSJF determines work can stop – This step involves using the Weighted Shortest Job First (WSJF) prioritization method to determine whether the initiative has delivered enough value to the customer and the enterprise, or whether it needs more investment or termination3

Explanation
Blue/green deployment falls outside the scope of the Stabilize activity. The Stabilize activity is part of the Release on Demand aspect of the Continuous Delivery Pipeline, which is responsible for releasing new functionality to end users, either immediately or incrementally, based on business and customer needs. The Stabilize activity ensures that the solution is working well from a functional and nonfunctional perspective, and that it can be operated and supported effectively. The Stabilize activity involves the following practices:
Continuous security monitoring – Applying automated tools and processes to detect and respond to security threats and vulnerabilities in the production environment, and ensuring compliance with security policies and standards.
Failover and recovery processes – Establishing and testing backup and restore mechanisms, disaster recovery plans, and business continuity procedures, to ensure the availability and resilience of the solution in case of failures or disruptions.
Features monitoring – Collecting and analyzing data on the usage, performance, and outcomes of the released features, to measure their value and impact, and to identify any issues or defects that need to be fixed or improved.
Support and maintenance – Providing ongoing support and maintenance for the solution, such as resolving incidents, handling requests, applying patches, and performing upgrades, to ensure the reliability and quality of the solution.
Blue/green deployment, on the other hand, is a technical practice that belongs to the Continuous Deployment aspect of the Continuous Delivery Pipeline, which is responsible for deploying new functionality into the production environment, where it can be tested and validated. Blue/green deployment is a change management strategy that reduces the downtime and risk of deploying new versions of software. It involves having two identical but separate environments: one is the active environment that serves the user traffic (blue), and the other is the inactive environment that hosts the new version of the software (green). The deployment process consists of switching a small portion of the user traffic from the blue environment to the green environment, after verifying that the new version is working properly. The portion of users who receive the new version are called canaries, as they serve as early indicators of the quality and performance of the new version. If the canary release is successful, the entire user traffic is gradually switched to the green environment, which becomes the new active environment. If the canary release fails, the user traffic is switched back to the blue environment, which remains the active environment. Blue/green deployment has several benefits, such as:
It allows for fast and reliable rollback, in case of any issues or errors in the new version, by simply switching back to the active environment.
It eliminates the need for complex and error-prone migration scripts, as the inactive environment can be prepared and tested in advance, without affecting the active environment.
It enables testing and experimentation of the new version with a subset of users, by directing some user traffic to the inactive environment, before switching completely.
It facilitates continuous delivery and deployment, by automating the switching process and reducing the transaction cost and risk of moving changes to production