SAFE-DEVOPS Practice Questions

The Continuous Delivery Pipeline (CDP) is a key element of the Agile Product Delivery competency in

SAFe. It represents the workflows, activities, and automation needed to guide new functionality from

ideation to an on-demand release of value. The CDP consists of four aspects: Continuous Exploration

(CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. CE focuses

on creating alignment on what needs to be built, using design thinking and hypothesis-driven

development. CI focuses on building quality into the solution, using practices such as test

automation, code analysis, and continuous feedback

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.

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, Features are prioritized in

the ART Backlog in the Synthesize activity of Continuous Exploration. This activity involves creating

Solution hypotheses based on customer needs and market research, and then selecting the most

promising ones to be implemented in the ART Backlog. The handbook states that "Synthesize is the

activity of creating Solution hypotheses based on customer needs and market research, and then

selecting the most promising ones to be implemented in the ART Backlog."1 Therefore, Synthesize is

where Features are prioritized for continuous delivery.

According to the SAFe DevOps Practitioner 6.0 study guide1, continuous deployment enables release

continuously. Continuous deployment 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. Continuous deployment allows teams to deploy small, incremental

changes to production continually, enabling them to respond to market opportunities with the

highest possible value in the shortest sustainable lead time. Continuous deployment also helps

teams to reduce the risk of deploying faulty or incomplete code, as well as to optimize the

performance and resource consumption of the system. Therefore, continuous deployment enables

release continuously, which is a key business objective for delivering value to customers faster and

more reliably.

According to the SAFe DevOps Practitioner 6.0 study guide1, the Continuous Delivery Pipeline (CDP)

represents the workflows, activities, and automation needed to guide new functionality from

ideation to an on-demand release of value. The CDP consists of four aspects: Continuous Exploration

(CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. The CDP

enables organizations to deliver new functionality to users far more frequently than traditional

processes. The first step in the CDP is Continuous Exploration, which focuses on creating alignment

on what needs to be built. In CE, design thinking ensures the enterprise understands the market

problem or customer need and the solution required to meet that need. It starts with a hypothesis of

something that will provide value to customers. Therefore, an idea marks the beginning of the CDP in

CE.

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 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.

After conducting current-state mapping in the context of Value Stream Mapping, a team should be

able to identify and describe the biggest bottlenecks in the delivery pipeline. Current-state mapping

is a process of visualizing the entire flow of a product or service from start to finish, highlighting each

step and identifying where delays or inefficiencies occur. By understanding where these bottlenecks

are, teams can then work on strategies to improve the overall flow, reduce lead times, and enhance

efficiency. This step is crucial for identifying areas for improvement and setting the stage for future

actions to optimize the Value Stream.

According to the SAFe DevOps Practitioner 6.0 study guide and handbook, working in isolation on

long-lived code branches can have negative consequences for the Continuous Delivery Pipeline. This

includes making the trunk/main branch less stable and more prone to conflicts and errors. The

handbook states that "Working in isolation on long-lived code branches can make the trunk/main

branch less stable and more prone to conflicts and errors."1 Therefore, it is recommended to use

short-lived feature branches and merge them frequently into the trunk/main branch.

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