Scrum SAFe-DevOps Daily Practice Exam New 2024 Updated 100 Questions
Use Valid SAFe-DevOps Exam - Actual Exam Question & Answer
NEW QUESTION # 10
What falls outside the scope of the Stabilize activity?
- A. Continuous security monitoring is done
- B. Features are monitored after release
- C. Failover and recovery processes are in place
- D. Blue/green deployment
Answer: D
Explanation:
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
NEW QUESTION # 11
Why is hypothesis evaluation important when analyzing data from monitoring systems in the Release on Demand aspect?
- A. It helps link objective production data to the hypothesis being tested
- B. It helps operations teams know where to apply emergency fixes
- C. It helps quickly create balanced scorecards for stakeholder review
- D. It helps define the minimum viable product (MVP)
Answer: A
Explanation:
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, hypothesis evaluation is important when analyzing data from monitoring systems in the Release on Demand aspect because it helps link objective production data to the hypothesis being tested. Hypothesis evaluation is the process of measuring and comparing the actual outcomes of a hypothesis with the expected outcomes based on customer feedback and business value. Hypothesis evaluation helps DevOps teams to validate or invalidate their hypotheses, learn from their mistakes, and improve their solutions. By linking objective production data to the hypothesis being tested, DevOps teams can see how well their solutions are delivering value to customers and achieving their goals.
NEW QUESTION # 12
Ensuring that security controls such as threat modeling, application security, and penetration testing are in place throughout the Continuous Delivery Pipeline is an example of which stabilizing skill?
- A. Design for operations
- B. Failover/disaster recovery
- C. Security Operations
- D. Continuous security monitoring
Answer: D
Explanation:
Explanation
Ensuring that security controls like threat modeling, application security, and penetration testing are in place throughout the Continuous Delivery Pipeline is an example of Continuous security monitoring. This skill involves the ongoing assessment and oversight of security measures within the pipeline to ensure that the software remains secure against potential threats at all stages of its development and deployment.
NEW QUESTION # 13
What is the recommended way to prioritize improvement items for the DevOps transformation?
Choose the correct options from below list
- A. Minimum Viable Product
- B. Minimum marketable feature
- C. Lean business Case
- D. Weighted Shortest Job First
Answer: D
Explanation:
Explanation
The recommended way to prioritize improvement items for the DevOps transformation is to use Weighted Shortest Job First (WSJF). WSJF is a prioritization model that considers the cost of delay, job size, and economic value of each improvement item. It helps to identify the most urgent and valuable items that can be delivered in the shortest amount of time
NEW QUESTION # 14
Which practice helps developers deploy their code into production?
- A. Deployment automation
- B. Infrastructure as code
- C. Self-service deployment
- D. Continuous Deployment
Answer: D
Explanation:
Explanation
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."1 Therefore, Continuous Deployment enables teams to deliver value to customers faster and more reliably.
NEW QUESTION # 15
Who is responsible for ensuring quality is built into the code in SAFe?
- A. Agile Teams
- B. Developers
- C. Testers - xx
- D. Product Owners
Answer: A
Explanation:
Explanation
Agile Teams are responsible for ensuring quality is built into the code in SAFe. SAFe is a framework for scaling agile practices across the enterprise, based on the principles of Lean, Agile, and DevOps. SAFe organizes the enterprise into Agile Release Trains (ARTs), which are teams of Agile Teams that deliver value in a regular cadence. Agile Teams are the fundamental building blocks of SAFe, and they are cross-functional, self-organizing, and self-managing teams that deliver value in short iterations. Agile Teams are responsible for ensuring quality is built into the code in SAFe, by applying the following practices:
Test-first - Test-first is a practice that involves writing tests before writing code, to ensure that the code meets the requirements and standards, and does not introduce any defects or vulnerabilities. Test-first helps to improve the design and maintainability of the code, and to accelerate the feedback and validation process. Test-first can be implemented using various techniques, such as Test-Driven Development (TDD), Behavior-Driven Development (BDD), or Acceptance Test-Driven Development (ATDD).
Built-in quality - Built-in quality is a practice that involves applying quality standards and checks throughout the solution lifecycle, rather than inspecting quality after the fact. Built-in quality helps to prevent defects from escaping to downstream stages or customers, and to reduce the cost and risk of rework and waste. Built-in quality can be achieved using various methods, such as code quality and security analysis, code review, pair programming, refactoring, and continuous testing.
Continuous testing - Continuous testing is a practice that involves automating and executing tests at every stage of the Continuous Delivery Pipeline, to verify that the solution meets the functional and nonfunctional requirements and standards, and to detect and resolve any issues or defects as early as possible. Continuous testing helps to ensure the reliability and performance of the solution, and to support the delivery and deployment of value to the customer. Continuous testing can be performed using various tools and frameworks, such as unit testing, integration testing, system testing, acceptance testing, performance testing, and security testing
NEW QUESTION # 16
The Release on Demand aspect enables which key business objective?
- A. Quality
- B. Alignment
- C. Time-to-market
- D. Business value
Answer: D
Explanation:
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
NEW QUESTION # 17
Which two areas should be monitored in the Release on Demand aspect to support DevOps and Continuous Delivery? (Choose two.)
- A. Deployment cycle time
- B. Agile Release Train velocity
- C. Business Metrics
- D. Build status
- E. Full-stack system behavior
Answer: A,D
Explanation:
Explanation
Two areas that should be monitored in the Release on Demand aspect to support DevOps and Continuous Delivery are the build status and the deployment cycle time. The build status is the measure of whether the code and components can be successfully compiled, linked, packaged, and verified into deployable binaries.
The build status indicates the quality and consistency of the code and the readiness for deployment.
Monitoring the build status helps to support the Release on Demand aspect in SAFe by providing valuable information for the following purposes:
To identify and fix any errors or defects that may prevent the code from being deployed or released To ensure that the code meets the quality standards and security checks, such as static code analysis, code coverage, and code review To verify that the code and components are integrated and merged correctly into the trunk To track the progress and status of the features and capabilities that are being developed and delivered The deployment cycle time is the measure of how long it takes to deploy the code and components from the source control system to the production environment. The deployment cycle time indicates the efficiency and reliability of the deployment process and the speed of delivery. Monitoring the deployment cycle time helps to support the Release on Demand aspect in SAFe by providing valuable information for the following purposes:
To optimize the deployment process and reduce the lead time and variability To automate the deployment process and eliminate manual steps and errors To align the deployment process with the market demand and release strategy To evaluate the impact and value of the deployed features and capabilities 7
NEW QUESTION # 18
Which statement is true about DevOps?
- A. It enables low-risk releases and fast recovery with fast fix-forward
- B. It enables high-risk releases and fast recovery with fast fix-forward
- C. It enables a tolerance for low-risk, low-failure, and rapid recovery
- D. It enables low-risk releases and fast recovery with no room for errors
Answer: A
Explanation:
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
NEW QUESTION # 19
When preparing a DevOps backlog, prioritizing features using WSJF includes which two factors? (Choose two.) Choose the correct option from below list
- A. Total count of items on the Program Backlog
- B. Team velocity
- C. Business value
- D. Cost of delay
- E. Duration/job size
Answer: D,E
Explanation:
Explanation
When preparing a DevOps backlog, prioritizing features using WSJF includes two factors: cost of delay and duration/job size. WSJF stands for Weighted Shortest Job First, which is a prioritization model used to sequence work for maximum economic benefit. WSJF is estimated as the relative cost of delay divided by the relative job duration. Cost of delay is the money lost by delaying or not doing a job for a specific time. It is a measure of the economic value of a job over time. Job duration is the time it takes to complete a job. Jobs that can deliver the most value in the shortest duration provide the best economic return. WSJF also considers other factors that contribute to the cost of delay, such as user and business value, time criticality, and risk reduction and/or opportunity enablement
NEW QUESTION # 20
Which practice appears under the Respond activity?
- A. Telemetry
- B. Site Reliability
- C. Rollback
- D. Service virtualization
Answer: C
Explanation:
Explanation
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.
NEW QUESTION # 21
The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to which four stakeholder concerns?
- A. Portfolio, Solution, ART, team
- B. Alignment, quality, time-to-market, business value
- C. Productivity, efficiency, speed-to-market, competitive advantage
- D. Exploration, integration, development, reflection
Answer: B
Explanation:
Explanation
The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to four stakeholder concerns: alignment, quality, time-to-market, and business value. The DevOps Health Radar is a tool that helps Agile Release Trains (ARTs) and Solution Trains assess their ability to Release on Demand, which is the process of delivering value to customers whenever there is a business need. The DevOps Health Radar consists of four dimensions that correspond to the four aspects of the Continuous Delivery Pipeline: Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. Each dimension has four sub-dimensions that reflect the key practices and capabilities that enable the flow of value.
The DevOps Health Radar helps the ARTs and Solution Trains to measure their maturity in each sub-dimension, using a scale of Sit, Crawl, Walk, Run, or Fly. The DevOps Health Radar also helps the ARTs and Solution Trains to identify the gaps and improvement opportunities in their DevOps practices, and to prioritize the next steps toward achieving higher levels of maturity. The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to four stakeholder concerns, as shown in Figure 1:
Alignment - Alignment is the concern of ensuring that the solution is aligned with the customer needs, market opportunities, and strategic goals of the enterprise. Alignment is achieved by applying the CE aspect, which involves exploring the market and customer problems, defining a vision, roadmap, and set of features for the solution, and validating the assumptions and hypotheses with customer feedback and data.
Quality - Quality is the concern of ensuring that the solution meets the functional and nonfunctional requirements and standards, and that it does not introduce any defects or vulnerabilities. Quality is achieved by applying the CI aspect, which involves developing, testing, integrating, and validating new functionality in preparation for deployment and release.
Time-to-market - Time-to-market is the concern of ensuring that the solution can be delivered and deployed to the production environment as fast and as frequently as possible, without compromising quality or security. Time-to-market is achieved by applying the CD aspect, which involves automating and streamlining the deployment process, and ensuring the stability and reliability of the production environment.
Business value - Business value is the concern of ensuring that the solution delivers the expected outcomes and benefits to the customer and the enterprise, and that it can be adapted and improved based on the changing needs and feedback. Business value is achieved by applying the Release on Demand aspect, which involves releasing new functionality to the customer incrementally or immediately, based on the market demand, and measuring and learning from the results12
1: https://scaledagileframework.com/blog/assess-your-devops-health-with-the-safe-devops-radar/ 2:
https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps
NEW QUESTION # 22
What triggers the Release activity?
- A. Change validated in staging environment
- B. Successful deployment to production
- C. Successful user acceptance tests
- D. Business decision to go live
Answer: D
Explanation:
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the Release activity is triggered by a business decision to go live. This means that the Solution is ready to be delivered to end users and customers, based on the validation and testing done in the previous activities. The handbook states that "The Release activity is triggered by a business decision to go live."1 Therefore, this activity involves releasing value to customers on demand, while also measuring and learning from the feedback.
NEW QUESTION # 23
Where do features go after Continuous Exploration?
- A. Into Continuous Integration, where they are then split into Stories
- B. Into Continuous Development, where they are implemented in small batches
- C. Into Continuous Integration, where they are deployed with feature toggles
- D. Into the Portfolio Backlog, where they are then prioritized
Answer: A
Explanation:
Explanation
In the Scaled Agile Framework (SAFe), after features are defined and designed during Continuous Exploration, they move into Continuous Integration. Here, they are further broken down into smaller, implementable parts known as user stories. These stories are then developed, tested, and integrated into the existing codebase. This process ensures that new features are developed in a systematic and efficient manner, with regular integration and testing to maintain quality and readiness for release.
NEW QUESTION # 24
Which statement illustrates the biggest bottleneck?
- A. WT = 10 days, AT = 0.5 day, %C&A = 100%
- B. WT = 5 days, AT = 2.5 days, %C&A = 100%
- C. WT = 1 day, AT = 0.5 day, %C&A = 90%
- D. WT = 6 days, AT = 5 days, %C&A = 100%
Answer: A
Explanation:
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.
NEW QUESTION # 25
Who should be consulted first when calculating the % Complete and Accurate?
- A. The people responsible for the next step
- B. The lead developer
- C. End users
- D. Testers
Answer: A
Explanation:
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
NEW QUESTION # 26
What is the correct order of activities in the Continuous Integration aspect?
- A. Develop, Build, Test end-to-end, Stage
- B. Develop, Test end-to-end, Build, Stage
- C. Build, Develop, Stage, Test end-to-end
- D. Stage, Develop, Build, Test end-to-end
Answer: A
Explanation:
Explanation
The correct order of activities in the Continuous Integration aspect is: Develop, Build, Test end-to-end, Stage.
Continuous Integration (CI) is an aspect of the Continuous Delivery Pipeline that automates the development, testing, integration, and validation of new functionality in preparation for deployment and release. CI is the second aspect in the four-part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. CI consists of four activities, as shown in Figure 1:
Develop - This activity involves implementing stories by refining features from the ART Backlog, coding, testing, and committing the work product into the source control system. Testing in this activity tends to focus on unit and story-level testing and often requires test doubles to replicate other components or subsystems that are not readily available or easily tested.
Build - This activity involves creating deployable binaries and merging development branches into the trunk. Building in this activity includes compiling, linking, packaging, and verifying the code and components. Building also involves applying code quality and security checks, such as static code analysis, code coverage, and code review.
Test end-to-end - This activity involves validating the solution end-to-end, including the functional and nonfunctional aspects, such as performance, usability, reliability, and security. Testing in this activity requires integrating the code and components with other subsystems and services, and using test environments that resemble the production environment as much as possible. Testing also involves applying automated testing tools and frameworks, such as regression testing, integration testing, system testing, and acceptance testing.
Stage - This activity involves hosting and validating solutions in a staging environment before production. Staging in this activity includes deploying the solution to a pre-production environment that mimics the production environment in terms of hardware, software, configuration, and data. Staging also involves applying final checks and verifications, such as smoke testing, exploratory testing, and user acceptance testing910
1: https://www.lean.org/the-lean-post/articles/understanding-the-fundamentals-of-value-stream-mapping/ 2:
https://www.gembaacademy.com/school-of-lean/value-stream-mapping/adapting-value-stream-mapping-for-offi
https://scaledagileframework.com/guidance-applied-innovation-accounting-in-safe/ 4:
https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps 5:
https://www.redhat.com/en/topics/devops/what-is-blue-green-deployment 6:
https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html 7:
https://scaledagileframework.com/guidance-applied-innovation-accounting-in-safe/ 8:
https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps 9:
https://scaledagileframework.com/continuous-integration/ 10:
https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps
NEW QUESTION # 27
Which two skills appear under the Respond activity? (Choose two.)
Choose the correct options from below list
- A. Cross-team collaboration
- B. Telemetry
- C. Version control
- D. Automatic rollback
- E. Service virtualization
Answer: A,C
Explanation:
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
NEW QUESTION # 28
What are two important items to monitor in production to support the Release on Demand aspect in SAFe?
(Choose two.)
- A. Percent Complete and Accurate (%C&A)
- B. System performance
- C. Number of concurrent users
- D. Business value
- E. Unit test coverage
Answer: B,C
Explanation:
Explanation
Two important items to monitor in production to support the Release on Demand aspect in SAFe are the number of concurrent users and the system performance. The number of concurrent users is the number of users who are accessing the system at the same time. It is an indicator of the demand and popularity of the system, as well as the potential load and stress on the system resources. The system performance is the measure of how well the system responds to user requests and meets the nonfunctional requirements, such as availability, reliability, scalability, and security. Monitoring the number of concurrent users and the system performance helps to support the Release on Demand aspect in SAFe by providing valuable information for the following purposes:
To optimize the release strategy and timing, based on the user behavior and preferences To ensure the system can handle the expected and unexpected user traffic, and to scale up or down the system resources as needed To detect and resolve any issues or incidents that may affect the user experience and satisfaction To evaluate the impact and value of the released features, and to identify areas for improvement or innovation 5
NEW QUESTION # 29
Which statement describes the Lean startup lifecycle?
- A. Define the minimum viable product (MVP), build the MVP, implement Epic Features until all Features are delivered
- B. Create a hypothesis statement, assign an Epic owner, deliver Features created from the Lean business case, deploy
- C. Define the hypothesis, build a minimum viable product (MVP), continuously evaluate the MVP while implementing additional Features until WSJF determines work can stop
- D. Define a Lean business case, build a minimum viable product, implement the Epic Features until all Features are delivered
Answer: C
Explanation:
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
NEW QUESTION # 30
What does Value Stream Mapping help reveal in the Continuous Delivery Pipeline?
- A. Bottlenecks to the flow of value
- B. Who is responsible for optimizing the Value Stream
- C. DevOps practices that will improve the Value Stream
- D. Where automation is needed
Answer: A
Explanation:
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide and handbook, Value Stream Mapping helps reveal bottlenecks to the flow of value in the Continuous Delivery Pipeline. This means that Value Stream Mapping helps teams identify and eliminate any activities or processes that slow down or stop the delivery of value to customers. The handbook states that "Value Stream Mapping helps reveal bottlenecks to the flow of value in the Continuous Delivery Pipeline."1 Therefore, Value Stream Mapping helps teams optimize their value stream and improve their delivery performance.
NEW QUESTION # 31
......
Test Engine to Practice SAFe-DevOps Test Questions: https://www.practicedump.com/SAFe-DevOps_actualtests.html
SAFe-DevOps Real Exam Questions Test Engine Dumps Training With 100 Questions: https://drive.google.com/open?id=13tV0RahjjRdFKMrzf1FT3KV3tbI6XC6K