[2024年03月24日]SAFe-DevOps試験問題集でScrum練習テスト問題
最新でリアルなSAFe-DevOps試験問題集解答
質問 # 34
Value stream mapping metrics include calculations of which three Metrics? (Choose three.)
- A. Total Process Time
- B. Release Frequency
- C. Activity Ratio
- D. Emergency Change %
- E. Rolled % Complete and Accurate
- F. Outage Frequency
正解：A、C、E
解説：
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
質問 # 35
Mapping the value stream helps accomplish which two actions? (Choose two.)
- A. To understand how the flow of value can be improved
- B. To serve as a blueprint for development
- C. To prioritize the Program Backlog
- D. To add or remove user segments based on business decisions
- E. To gain insight into organizational efficiency
正解：A、E
解説：
Explanation
Mapping the value stream helps accomplish two actions: to gain insight into organizational efficiency and to understand how the flow of value can be improved. A value stream is the series of steps that an organization uses to implement solutions that provide a continuous flow of value to a customer. Mapping the value stream involves identifying the steps, people, inputs, outputs, tools, and metrics involved in delivering value from concept to cash. By mapping the value stream, the organization 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 organization identify bottlenecks, dependencies, handoffs, delays, and inefficiencies that affect the flow of value. Mapping the value stream also helps the organization 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 flow of value, the organization can increase customer satisfaction, reduce costs, accelerate time-to-market, and enhance business agility
質問 # 36
What does Flow Efficiency measure in the Value Stream?
- A. The percentage of time spent on manual activities
- B. The percentage of time spent on delays to the number of processes in the Value Stream
- C. The percentage of time spent on value-added activities
- D. The percentage of time spent on non-value-added activities
正解：C
解説：
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
質問 # 37
Which statement is true about DevOps?
- A. It enables low-risk releases and fast recovery with no room for errors
- B. It enables a tolerance for low-risk, low-failure, and rapid recovery
- C. It enables high-risk releases and fast recovery with fast fix-forward
- D. It enables low-risk releases and fast recovery with fast fix-forward
正解：D
解説：
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
質問 # 38
DevOps is a key enabler of continuous delivery.
What does continuous mean in this context?
Choose the correct option from below list
- A. To deploy to production and release on cadence every Iteration
- B. To deploy to production multiple times per year and release on a cadence once or twice a year
- C. To deploy to production as often as possible and release when the business needs it
- D. To deploy to production and release at least once every Program increment
正解：C
解説：
Explanation
Continuous means to deploy to production as often as possible and release when the business needs it in the context of continuous delivery in SAFe DevOps. Continuous delivery is the ability to deliver value to the end user whenever there is a business need. It requires a Continuous Delivery Pipeline (CDP) that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. Continuous delivery enables the enterprise to respond to changing customer needs and market conditions with speed and quality. Continuous delivery does not mean releasing every change to the end user immediately. Rather, it means decoupling deployment from release, and allowing the business to decide when to release the new functionality based on customer demand and economic outcomes1
質問 # 39
A canary release involves making a Solution available to whom?
- A. Internal users only
- B. External users only
- C. Any subset of users
- D. Users conducting User Acceptance Testing
正解：C
解説：
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.
質問 # 40
What is one aspect of the Continuous Delivery Pipeline?
- A. Continuous Integration
- B. Continuous Delivery
- C. Continuous Experimentation
- D. Continuous Security
正解：A
解説：
Explanation
One aspect of the Continuous Delivery Pipeline is Continuous Integration. Continuous Integration (CI) is the practice of merging all development versions of a code base several times a day and verifying them with automated tests. CI helps to improve the quality and consistency of the code, and to accelerate the delivery and deployment of new functionality. 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: develop, build, test end-to-end, and stage12
質問 # 41
When should teams use root cause analysis to address impediments to continuous delivery?
- A. During Iteration Planning
- B. During the management review and problem-solving portion of PI Planning
- C. During Inspect & Adapt (I&A)
- D. During the Iteration Retrospective
正解：C
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, root cause analysis is a technique that helps identify and eliminate the underlying causes of problems or defects in the Solution. Root cause analysis can be used to address impediments to continuous delivery by finding and fixing the root causes of issues such as delays, rework, waste, and errors. Root cause analysis can be performed during various phases of the PI, such as during the Iteration Retrospective, during the management review and problem-solving portion of PI Planning, or during Inspect & Adapt (I&A). However, the most effective time to use root cause analysis is during I&A, which is a significant event held at the end of each PI, where the current state of the Solution is demonstrated and evaluated. Teams then reflect and identify improvement backlog items via a structured problem-solving workshop. The result is a set of improvement backlog items that go into the ART Backlog for the next PI Planning event. Therefore, root cause analysis can help teams address impediments to continuous delivery by improving their performance and quality in the next PI.
質問 # 42
Which two statements describe the purpose of value stream mapping? (Choose two.) Choose the correct option from below list
- A. To create an understanding of the budget
- B. To create an action plan for continuos improvement
- C. To understand the Product Owner's priorities
- D. To visualize how value flows
- E. To deliver incremental value in the form of working, tested software and systemscorrect
正解：D、E
解説：
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
質問 # 43
What work is performed in the Build activity of the Continuous Delivery Pipeline?
- A. Code
- B. Automated acceptance testing
- C. Code review
- D. Compile
正解：D
解説：
Explanation
The correct answer is B. Compile. The Build activity of the Continuous Delivery Pipeline is responsible for creating deployable binaries and merging development branches into the trunk. The Build activity includes the following practices:
Compile - Compile is the process of transforming the source code into executable code that can run on a specific platform or environment. Compile involves checking the syntax, semantics, and dependencies of the code, and resolving any errors or conflicts. Compile also involves linking the code with other libraries or components that are required for the functionality of the solution.
Package - Package is the process of bundling the compiled code and other resources into a format that can be easily deployed to the target environment. Package involves creating archives, containers, or installers that contain the necessary files and metadata for the deployment process. Package also involves applying versioning and configuration information to the packages, to ensure traceability and consistency.
Verify - Verify is the process of ensuring that the code and packages meet the quality standards and security checks, and that they are ready for deployment and release. Verify involves applying automated tools and processes, such as static code analysis, code coverage, code review, and code quality metrics, to detect and resolve any issues or vulnerabilities in the code and packages. Verify also involves ensuring compliance with the coding standards and guidelines, and documenting the results and feedback of the verification process12
質問 # 44
One goal of DevOps in SAFe is to fully automate the steps between which two pipeline activities?
- A. Code commit and deploy
- B. Code commit and user acceptance testing
- C. Code commit and release
- D. Code commit and stage
正解：C
解説：
Explanation
The goal of DevOps in SAFe (Scaled Agile Framework) related to automating steps in the pipeline is best described in option A: between Code commit and Release.
In the context of SAFe, the aim is to establish a Continuous Delivery Pipeline where the process from code commit (when developers commit their code changes to a version control system) to release (when the software is made available to end users) is as automated as possible. This automation includes steps like automated builds, tests, and deployments, ensuring that the software is always in a releasable state with minimal manual intervention. This approach helps in achieving faster delivery times, improved software quality, and more efficient and reliable release processes.
質問 # 45
Which statement describes what could happen when development and operations do not collaborate early in the pipeline?
- A. Automation of integration test is not possible
- B. Teams build things quickly but build the wrong things
- C. Flow times are reduced
- D. Surprises are found in deployment that lead to significant rework and delay
正解：D
解説：
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.
質問 # 46
What are two parts of the Continuous Delivery Pipeline? (Choose two.)
Choose the correct option from below list
- A. Continuous Integration
- B. Continuous Delivery
- C. Continuous Exploration
- D. Continuous Experimentation
- E. Continuous Security
正解：A、C
解説：
Explanation
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
質問 # 47
Which two skills appear under the Respond activity? (Choose two.)
Choose the correct options from below list
- A. Service virtualization
- B. Telemetry
- C. Automatic rollback
- D. Cross-team collaboration
- E. Version control
正解：D、E
解説：
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
質問 # 48
Which statement describes a measurable benefit of adopting DevOps practices and principles?
Choose the correct option from below list
- A. It identifies key Value Streams
- B. It creates a highly functional, cross-team culture
- C. It results in faster lead time, and more frequent deployments
- D. It guarantees an increase in profits and decrease in downtime
正解：C
解説：
Explanation
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
質問 # 49
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. Weighted Shortest Job First
- D. Lean business Case
正解：C
解説：
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
質問 # 50
What is the purpose of a minimum viable product?
- A. To sell to new markets
- B. To demo to Product Management for feedback
- C. To validate the hypothesis
- D. To release to production
正解：C
解説：
Explanation
The purpose of a minimum viable product is to validate the hypothesis. A minimum viable product (MVP) is an early and minimal version of a new product or solution used to prove or disprove an epic hypothesis. An epic is a significant solution development initiative that requires the definition and approval of an MVP. An epic hypothesis is a statement that describes the expected outcome, benefit, and value of an epic. The MVP is the smallest possible solution that can be used to test the epic hypothesis with real customers or users, and to gather feedback and data. The MVP helps reduce the risk of investing in a solution that nobody wants or needs, and enables faster learning and adaptation. The MVP is not the final product or solution, but rather a starting point for further development and improvement
質問 # 51
Which practice appears under the Respond activity?
- A. Service virtualization
- B. Site Reliability
- C. Telemetry
- D. Rollback
正解：D
解説：
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.
質問 # 52
Which DevOps principle focuses on identifying and eliminating bottlenecks in the Continuous Delivery Pipeline?
- A. Lean flow
- B. Automation
- C. Measurement
- D. Recovery
正解：A
解説：
Explanation
Lean flow is the DevOps principle that focuses on identifying and eliminating bottlenecks in the Continuous Delivery Pipeline. Lean flow is the application of Lean thinking and principles to optimize the flow of value from ideation to delivery. Lean flow aims to reduce waste, increase efficiency, and deliver value faster and more reliably. Lean flow involves the following practices:
Reducing batch size - Breaking down large batches of work into smaller, more manageable pieces that can be delivered more frequently and with less risk.
Limiting work in progress (WIP) - Restricting the amount of work that can be started or in flight at any given time, to avoid overloading the system and creating queues and delays.
Implementing pull systems - Aligning the production and consumption of work by allowing downstream customers to pull work from upstream suppliers when they are ready, rather than pushing work based on forecasts or schedules.
Managing queue lengths - Monitoring and controlling the amount of work waiting to be processed at each stage of the value stream, to reduce lead time and variability.
Reducing handoffs - Minimizing the number of transitions and dependencies between different teams or individuals, to avoid communication gaps, context switching, and rework.
Implementing Work in Process (WIP) visualization - Making the work and its status visible to all stakeholders, using tools such as Kanban boards, Cumulative Flow Diagrams (CFDs), and Value Stream Maps (VSMs), to enable collaboration, coordination, and improvement.
Implementing Work in Process (WIP) feedback - Establishing fast and frequent feedback loops within and across the value stream, using tools such as automated testing, monitoring, and metrics, to detect and resolve issues, validate assumptions, and learn from outcomes3
質問 # 53
......
あなたを簡単に合格させるSAFe-DevOps試験正確なPDF問題：https://www.jpntest.com/shiken/SAFe-DevOps-mondaishu