Which steps in the value stream should be the main focus when prioritizing improvement items?
Answer : B
According to the SAFe DevOps Practitioner 6.0 study guide1, when prioritizing improvement items, the steps with short Active Time and high %C&A in the future-state map should be the main focus. Active Time is the amount of time a step spends on performing work, while %C&A is the percentage of capacity utilization of a step. The future-state map shows how the Value Stream will look like after implementing improvements, based on customer feedback and business value. The improvement items are ranked by their impact on flow efficiency, customer satisfaction, and business agility. The steps with short Active Time and high %C&A in the future-state map indicate that they are bottlenecks or waste sources that need to be eliminated or reduced as soon as possible. Therefore, they should be prioritized for improvement actions.
Question 2
Which metric reflects the quality of output at each step in the Value Stream?
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.
Question 3
Which statement describes what could happen when development and operations do not collaborate early in the pipeline?
Answer : C
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.'1Therefore, it is important for teams to work together throughout the value stream to ensure continuous delivery.
Question 4
What differentiates Deployment and Release in the continuous Delivery Pipeline?
Choose the correct option from below list
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
Question 5
What is a consequence of working in isolation on long-lived code branches?
Answer : A
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.'1Therefore, it is recommended to use short-lived feature branches and merge them frequently into the trunk/main branch.
Question 6
Which statement describes a measurable benefit of adopting DevOps practices and principles?
Choose the correct option from below list
Answer : A
One of the measurable benefits of adopting DevOps practices and principles is that it results in faster lead time and more frequent deployments. Lead time is the time it takes from the moment a change is requested until it is delivered to the customer. Frequent deployments are the number of times a change is deployed to production. Both of these metrics indicate the speed and efficiency of the DevOps process, as well as the ability to respond to customer needs and feedback.According to the State of DevOps Report 2020, high-performing DevOps teams have 208 times faster lead times and 106 times more frequent deployments than low-performing teams
Question 7
Which statement is true about DevOps?
Answer : A
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
All Official Question Types