お手軽にダウンロードできるSAFe-DevOps試験問題集が更新されたのは100問があります
最新更新されたのはSAFe-DevOps試験問題2024年更新
質問 # 25
What are two aspects of the Continuous Delivery Pipeline, in addition to Continuous Integration? (Choose two.) Choose the correct option from below list
- A. Continuous Exploration
- B. Continuous Improvement
- C. Continuous Release
- D. Continuous Deployment
- E. Continuous Testing
正解：A、D
解説：
Explanation
In addition to Continuous Integration, two other aspects of the CDP are Continuous Deployment and Continuous Exploration. Continuous Deployment automates the migration of new functionality from a staging environment to production, where it is made available for release. Continuous Deployment enables the ability to release value at any time, in a sustainable way. Continuous Exploration focuses on creating alignment on what needs to be built, using design thinking and hypothesis-driven development. Continuous Exploration enables the discovery of the most valuable solutions for the customers and the enterprise
質問 # 26
Which practice prevents configuration drift between production and non-production environments?
- A. Session replay
- B. Immutable infrastructure
- C. Deployment automation
- D. Self-service deployment
正解：B
解説：
Explanation
One practice that prevents configuration drift between production and non-production environments is immutable infrastructure. Immutable infrastructure is a management approach for infrastructure resources where changes are made by deploying new versions of resources instead of modifying existing ones. In this approach, the infrastructure is treated as an immutable asset that is built, deployed, and disposed of, rather than modified in place. For example, instead of modifying an existing virtual machine (VM), a new VM with updated configurations and software is deployed, and the old VM is disposed of. This approach eliminates the possibility of configuration drift and reduces the risk of introducing unintended changes to the infrastructure. Immutable infrastructure also simplifies the management of infrastructure resources, increases the reliability and security of the infrastructure, and facilitates rapid and consistent deployment
質問 # 27
In which activity are specific improvements to the Continuous Delivery Pipeline identified?
- A. Problem-Solving Workshop
- B. Value Stream identification
- C. Impact mapping
- D. Future-state Value Stream Mapping
正解：D
解説：
Explanation
According to the SAFe DevOps Practitioner 6.0 study guide and handbook, specific improvements to the Continuous Delivery Pipeline are identified in Future-state Value Stream Mapping. This activity involves envisioning and designing the ideal state of the value stream, based on the current state and the desired outcomes. The handbook states that "Future-state Value Stream Mapping is a way of defining how you want your value stream to look like in the future."1 Therefore, Future-state Value Stream Mapping helps teams identify and prioritize the areas that need improvement in their Continuous Delivery Pipeline.
質問 # 28
The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to which four stakeholder concerns?
- A. Alignment, quality, time-to-market, business value
- B. Exploration, integration, development, reflection
- C. Productivity, efficiency, speed-to-market, competitive advantage
- D. Portfolio, Solution, ART, team
正解：A
解説：
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
質問 # 29
Which two skills appear under the Respond activity? (Choose two.)
Choose the correct options from below list
- A. Version control
- B. Cross-team collaboration
- C. Automatic rollback
- D. Service virtualization
- E. Telemetry
正解：A、B
解説：
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
質問 # 30
Which statement describes the Lean startup lifecycle?
- A. Create a hypothesis statement, assign an Epic owner, deliver Features created from the Lean business case, deploy
- B. Define the hypothesis, build a minimum viable product (MVP), continuously evaluate the MVP while implementing additional Features until WSJF determines work can stop
- C. Define the minimum viable product (MVP), build the MVP, implement Epic Features until all Features are delivered
- D. Define a Lean business case, build a minimum viable product, implement the Epic Features until all Features are delivered
正解：B
解説：
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
質問 # 31
Which skill can significantly accelerate mean-time-to-restore by enabling support teams to see issues the way actual end users did?
- A. Incident management
- B. Page analytics
- C. Blue/green deployment
- D. Session replay
正解：D
解説：
Explanation
One skill that can significantly accelerate mean-time-to-restore by enabling support teams to see issues the way actual end users did is session replay. Session replay is a technique that allows the support team to replay end-user sessions to research incidents and identify problems. Session replay captures the user's interactions with the application, such as clicks, scrolls, keystrokes, and mouse movements, and reproduces them in a video-like format. Session replay can help the support team to understand the user's behavior, context, and feedback, as well as to reproduce and diagnose errors, bugs, and performance issues. Session replay can also help the support team to communicate and collaborate with the development team and the stakeholders, by providing visual evidence and data of the incidents. Session replay can significantly accelerate mean-time-to-restore by reducing the time and effort required to investigate and resolve issues, as well as by improving the quality and reliability of the application
質問 # 32
What should be measured in a CALMR approach to DevOps?
- A. Mean time to restore
- B. Everything
- C. Deployment frequency
- D. Flow, quality, and value
正解：D
解説：
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
質問 # 33
How should developers integrate refactoring into their workflow?
Choose the correct option from below list
- A. Refactor continuously as part of test-driven development
- B. Allocate a portion of their capacity to refactoring in every Iteration
- C. Create and estimate refactoring Stories in the Team Backlog
- D. Create and estimate refactoring tasks for each Story in the Team Backlog
正解：C
解説：
Explanation
Refactoring is the activity of improving the internal structure or operation of a code or component without changing its external behavior. The goal of software development is the continuous delivery of business value to users and stakeholders. Constantly changing technology and evolving business objectives make maintaining and continuously increasing business value difficult. Refactoring enables an emergent design, ensuring the system continues to meet future business needs. Refactors are a particular type of Enabler story in SAFe, and, like any other Story, they must be estimable, verifiable, and valuable, as well as accepted by the Product Owner. SAFe emphasizes the importance of keeping all work visible, including refactoring. Like user value work, refactoring must be planned for, estimated, and prioritized. Therefore, developers should create and estimate refactoring Stories in the Team Backlog, and work on them according to their WSJF1
質問 # 34
Continuous Deployment enables which key business objective?
- A. Release continuously
- B. Business value
- C. Time-to-market
- D. Manage technical debt
正解：C
解説：
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.
質問 # 35
One goal of DevOps in SAFe is to fully automate the steps between which two pipeline activities?
- A. Code commit and user acceptance testing
- B. Code commit and stage
- C. Code commit and deploy
- D. Code commit and release
正解：D
解説：
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.
質問 # 36
What is the primary goal of the Stabilize activity?
Choose the correct option from below list
- A. To avoid unplanned outages and security breaches
- B. To enhance stability with blue/green deployment
- C. To establish quality-of-service agreements with customers
- D. To achieve active-active site replication
正解：A
解説：
Explanation
The primary goal of the Stabilize activity is to avoid unplanned outages and security breaches. The Stabilize activity is part of the Release on Demand aspect of the CDP in SAFe DevOps, which ensures the solution is working well from a functional and nonfunctional requirements (NFR) perspective. The Stabilize activity involves practices such as monitoring, logging, alerting, incident response, and disaster recovery. These practices help to detect and resolve issues quickly, minimize the impact of failures, and restore normal operations as soon as possible
質問 # 37
Which steps in the value stream should be the main focus when prioritizing improvement items?
- A. Steps with low Percent Complete and Accurate (%C&A) and short Active Time in the current-state map
- B. Steps with a long Active Time
- C. Steps with a high Flow Efficiency
- D. Steps with short Active Time and high %C&A in the future-state map
正解：D
解説：
Explanation
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.
質問 # 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
What is a core DevOps principle?
- A. Servant leadership
- B. Culture
- C. Iteration review
- D. Lean Budgets
正解：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
質問 # 40
Which practice helps developers deploy their code into production?
- A. Continuous Deployment
- B. Deployment automation
- C. Self-service deployment
- D. Infrastructure as code
正解：A
解説：
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.
質問 # 41
Which two technical practices focus on Built-in Quality? (Choose two.)
Choose the correct option from below list
- A. Environment configuration
- B. Canary releases
- C. Feature toggles
- D. Test-driven development
- E. Pair work
正解：D、E
解説：
Explanation
Two of the technical practices that focus on Built-in Quality are pair work and test-driven development. Pair work is a collaborative technique where two developers work together on the same code, one writing the code and the other reviewing it. Pair work improves the quality of the code by reducing defects, increasing knowledge sharing, and enhancing creativity and problem-solving. Test-driven development (TDD) is a practice where developers write automated tests before writing the code, and then refactor the code until it passes the tests. TDD ensures that the code meets the requirements and specifications, as well as improves the design, readability, and maintainability of the code
質問 # 42
......
無料更新されたScrum SAFe-DevOpsテストエンジン問題には100問題と解答：https://www.passtest.jp/Scrum/SAFe-DevOps-shiken.html
ベストな問題集を使おうSAFe Certification SAFe-DevOps専門試験問題：https://drive.google.com/open?id=1r12c93C20EJ-mbQzctDhW5xHQFi9499x