最新SAFe-DevOps合格保証試験問題集には正確で最新な問題があります
SAFe-DevOps試験ブレーン問題集で学習注釈と理論
質問 # 47
Why are canary releases used?
- A. To reduce deployment times
- B. To introduce minimum viable features
- C. To allow incremental release
- D. To prevent outages
正解：C
解説：
Explanation
Canary releases are used to allow incremental release of new functionality to customers. A canary release is a change management strategy for software releases that reduces the downtime and risk of deploying new versions of software. A canary release involves having two identical but separate environments: one is the active environment that serves the user traffic, and the other is the inactive environment that hosts the new version of the software. The release process consists of switching a small portion of the user traffic from the active environment to the inactive 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. The canary release 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
質問 # 48
Which technical practice is key to enabling trunk-based development?
- A. Code freezes
- B. Feature branching
- C. Refactoring
- D. Gated commits
正解：D
解説：
Explanation
Gated commits are a key technical practice that enables trunk-based development. Gated commits are a mechanism that ensures that only code that passes certain quality checks and tests can be committed to the main trunk of the shared codebase. Gated commits prevent broken changes from affecting other developers or the Continuous Delivery Pipeline. Gated commits typically involve the following steps:
A developer writes code and runs local tests on their own machine or branch.
The developer pushes the code to a remote repository, where a pre-commit hook triggers a build and test process on a separate server.
The build and test process verifies that the code meets the quality standards and does not introduce any errors or conflicts with the existing code on the trunk.
If the build and test process succeeds, the code is automatically merged into the trunk and becomes available for other developers and downstream activities.
If the build and test process fails, the code is rejected and the developer is notified of the issues that need to be fixed before retrying the commit.
Gated commits support trunk-based development by ensuring that the trunk is always in a releasable state, which means that at least once a day, developers must integrate their changes to the trunk. This is accomplished through short-lived feature branches related to project tasks. Gated commits reduce the complexity and conflicts of merging long-lived branches, improve the quality and consistency of the code by enforcing frequent testing and validation, accelerate the delivery and deployment of new functionality by minimizing the transaction cost and risk, and foster a culture of collaboration and transparency among developers
質問 # 49
What is the purpose of Value Stream Mapping?
- A. To create an action plan for continuous improvement
- B. To understand the priorities of the Product Owner (PO)
- C. To deliver incremental value in the form of working tested software and systems
- D. To create an understanding of the budget
正解：A
解説：
Explanation
The purpose of Value Stream Mapping is to create an action plan for continuous improvement. This tool is used to visually map the flow of steps, delays, and information required to deliver a product or service from start to finish. By identifying and understanding these elements, organizations can pinpoint inefficiencies and areas for improvement in their processes, ultimately leading to enhanced performance and value delivery.
質問 # 50
What is an output of the Release activity?
Choose the correct option from below list
- A. A Feature deployed to production
- B. A Feature made available to end users
- C. A Feature migrated to the cloud
- D. A Feature made available to internal users
正解：B
解説：
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
質問 # 51
Continuous Deployment enables which key business objective?
- A. Release continuously
- B. Business value
- C. Manage technical debt
- D. Time-to-market
正解：D
解説：
Explanation
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.
質問 # 52
Which two statements describe the purpose of value stream mapping? (Choose two.) Choose the correct option from below list
- A. To deliver incremental value in the form of working, tested software and systemscorrect
- B. To understand the Product Owner's priorities
- C. To visualize how value flows
- D. To create an understanding of the budget
- E. To create an action plan for continuos improvement
正解：A、C
解説：
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
質問 # 53
Who is responsible for building and continually improving the Continuous Delivery Pipeline?
Choose the correct option from below list
- A. Scrum Teams
- B. Agile Release Trains
- C. DevOps Teams
- D. System Teams
正解：B
解説：
Explanation
The Agile Release Trains (ARTs) are responsible for building and continually improving the Continuous Delivery Pipeline (CDP) in SAFe DevOps. The 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. Each ART builds and maintains, or shares, a pipeline with the assets and technologies needed to deliver solution value as independently as possible. The ARTs use the DevOps Health Radar to assess their current state and identify improvement opportunities for each aspect of the CDP. The ARTs also use the DevOps Transformation Canvas to create a vision, goals, and action plan for their DevOps transformation12
質問 # 54
What are two important items to monitor in production to support the Release on Demand aspect in SAFe?
(Choose two.)
- A. System performance
- B. Business value
- C. Unit test coverage
- D. Number of concurrent users
- E. Percent Complete and Accurate (%C&A)
正解：A、D
解説：
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
質問 # 55
What does the %C&A metric measure in the Continuous Delivery Pipeline?
- A. The percent complete and average times of each pipeline activity
- B. The percent of time downstream customers receive work that is usable as-is
- C. The percent concurrent and accurate process times of each pipeline activity
- D. The percent of change averages of each pipeline activity
正解：B
解説：
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
質問 # 56
Gemba walks are an important competency in support of which activity of the DevOps Health Radar?
- A. Continuous Exploration
- B. Hypothesize
- C. Learn
- D. Collaborate and Research
正解：D
解説：
Explanation
gemba walks are an important competency in support of the Collaborate and Research activity of the DevOps Health Radar. Collaborate and Research is the process of creating alignment on what needs to be built, synthesizing Solution ideas into ART Backlog Features, and utilizing WSJF to prioritize a DevOps backlog.
Gemba walks are a technique where the product team observes how stakeholders execute the specific activities in their operational value streams to identify opportunities for relentless improvement. Gemba walks help the product team understand the customer needs, market problems, and solution requirements from the perspective of those who deliver value to customers. Therefore, gemba walks are essential for collaborating and researching with stakeholders and validating or invalidating hypotheses.
質問 # 57
What does Value Stream Mapping help reveal in the Continuous Delivery Pipeline?
- A. Where automation is needed
- B. Bottlenecks to the flow of value
- C. Who is responsible for optimizing the Value Stream
- D. DevOps practices that will improve the Value Stream
正解：B
解説：
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.
質問 # 58
What should be measured in a CALMR approach to DevOps?
- A. Everything
- B. Flow, quality, and value
- C. Deployment frequency
- D. Mean time to restore
正解：B
解説：
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
質問 # 59
What is the first area that should be identified in Value Stream Mapping?
- A. The people who supervise the work
- B. Active Time, Flow Time. and Percent Complete and Accurate (%C&A)
- C. The steps
- D. The bottlenecks
正解：C
質問 # 60
What organizational anti-pattern does DevOps help to address?
- A. Walls of confusion between Customers and the business
- B. Organizations that make decisions along functional lines
- C. Teams that are isolated and working within functional areas (e.g., business, operations, and technology)
- D. Too much focus on centralized planning
正解：C
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, one of the organizational anti-patterns that DevOps helps to address is teams that are isolated and working within functional areas (e.g., business, operations, and technology). This anti-pattern creates silos, conflicts, and inefficiencies that hinder the collaboration and integration needed for continuous delivery. For example, some teams may prioritize speed over quality, while others may prioritize security over innovation. Some teams may resist change and adopt outdated practices, while others may embrace new technologies and methodologies. These differences can lead to misalignment, duplication, and waste of resources that slow down the delivery pipeline and reduce the value to customers. Therefore, DevOps helps to break down the functional silos and enable cross-functional teams that work together to deliver value to customers faster and more reliably.
質問 # 61
What is one recommended way to architect for operations?
Choose the correct option from below list
- A. Implement feature toggles
- B. Create detailed run books
- C. Require developers to support their own code
- D. Establish an architecture review board
正解：A
解説：
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
質問 # 62
Which practice appears under the Respond activity?
- A. Site Reliability
- B. Service virtualization
- C. Rollback
- D. Telemetry
正解：C
解説：
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.
質問 # 63
What is a core DevOps principle?
- A. Iteration review
- B. Culture
- C. Lean Budgets
- D. Servant leadership
正解：B
解説：
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
質問 # 64
......
合格させるScrum SAFe-DevOpsテスト練習問題 試験問題集：https://www.passtest.jp/Scrum/SAFe-DevOps-shiken.html
ベストSAFe Certification学習ガイドにはSAFe-DevOps試験問題集：https://drive.google.com/open?id=1r12c93C20EJ-mbQzctDhW5xHQFi9499x