Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 1:

  What is one reason for test data management?

  A. To automate provisioning data to an application in order to set it to a known state before testing begins
  B. To track the results of automated test cases for use by corporate audit
  C. To provide a viable option for disaster-recovery management
  D. To truncate data from the database to enable fast-forward recovery
  A. To automate provisioning data to an application in order to set it to a known state before testing begins

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, test data management is one reason for test data management. This means that test data management helps teams ensure that the application under test has a consistent and reliable state, by automating the provisioning of data from various sources and formats. The handbook states that "Test data management is the process of automating provisioning of data to an application in order to set it to a known state before testing begins."1 Therefore, test data management enables teams to perform end-to-end testing with confidence and accuracy.

• Question 2:

  Which technical practice incorporates build-time identification of security vulnerabilities in the code?

  A. Dynamic code analysis
  B. Penetration testing
  C. Application security
  D. Threat modeling
  A. Dynamic code analysis

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, dynamic code analysis is a technical practice that incorporates build-time identification of security vulnerabilities in the code. This means that the code is scanned for potential security risks during the compilation or execution phase, rather than during the testing phase. The handbook states that "Dynamic code analysis is a technique that identifies security vulnerabilities in the code during compilation or execution."1 Therefore, dynamic code analysis helps teams detect and fix security issues early in the development process.

• Question 3:

  What is the purpose of Value Stream Mapping?

  A. To create an action plan for continuous improvement
  B. To create an understanding of the budget
  C. To understand the priorities of the Product Owner (PO)
  D. To deliver incremental value in the form of working tested software and systems
  A. To create an action plan for continuous improvement

  ---

  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.

• Question 4:

  Value stream mapping metrics include calculations of which three Metrics? (Choose three.)

  A. Total Process Time
  B. Release Frequency
  C. Rolled % Complete and Accurate
  D. Outage Frequency
  E. Emergency Change %
  F. Activity Ratio
  A. Total Process Time
  C. Rolled % Complete and Accurate
  F. Activity Ratio

  ---

  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

• Question 5:

  After the team maps the steps of the current state Value Stream during value stream mapping, what are the next two steps? (Choose two.)

  Choose the correct option from below list

  A. Identify who is involved in each step
  B. Create a future state value stream map
  C. Perform a SWOT analysis
  D. Calculate the Activity Ratio
  E. Measure the performance at each step
  E. Measure the performance at each step

  ---

  Explanation

  After the team maps the steps of the current state value stream during value stream mapping, the next two steps are to measure the performance at each step and calculate the activity ratio. Measuring the performance at each step involves collecting data on cycle time, lead time, process time, wait time, defect rate, and other relevant metrics. This helps to identify the sources of waste, delays, and inefficiencies in the value stream. Calculating the activity ratio involves dividing the total process time by the total lead time and multiplying by 100. This gives the percentage of time that is spent on value-adding activities versus non-value-adding activities. The activity ratio helps to quantify the flow and identify opportunities for improvement

• Question 6:

  Which two security skills are part of the Continuous Integration aspect? (Choose two.)

  A. Security board review
  B. Application security
  C. SOX compliance analysis
  D. Network security practices
  E. Penetration testing
  B. Application security
  E. Penetration testing

  ---

  Explanation

  Two security skills that are part of the Continuous Integration aspect are application security and penetration testing. Application security is the practice of protecting the software applications from malicious attacks, unauthorized access, data breaches, and other threats. It involves applying security principles and techniques throughout the software development lifecycle, such as secure coding, code analysis, code review, security testing, and security monitoring. Application security helps to ensure that the software meets the security requirements and standards, and that it does not introduce any vulnerabilities or risks to the system or the users910 Penetration testing is the practice of simulating real-world attacks on the software applications to identify and exploit any security weaknesses or flaws. It involves using various tools and methods to probe, scan, attack, and bypass the security defenses of the software, such as firewalls, encryption, authentication, and authorization. Penetration testing helps to evaluate the security posture and resilience of the software, and to provide recommendations for improvement or remediation. Penetration testing is usually performed by external or independent experts, who have the permission and authorization to conduct the tests

• Question 7:

  When should teams use root cause analysis to address impediments to continuous delivery?

  A. During the Iteration Retrospective
  B. During the management review and problem-solving portion of PI Planning
  C. During Iteration Planning
  D. During Inspect and Adapt (IandA)
  D. During Inspect and Adapt (IandA)

  ---

  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 and Adapt (IandA). However, the most effective time to use root cause analysis is during IandA, 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.

• Question 8:

  In what activity of Continuous Exploration are Features prioritized in the ART Backlog?

  A. Synthesize
  B. Research
  C. Hypothesize
  D. Finalize
  A. Synthesize

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, Features are prioritized in the ART Backlog in the Synthesize activity of Continuous Exploration. This activity involves creating Solution hypotheses based on customer needs and market research, and then selecting the most promising ones to be implemented in the ART Backlog. The handbook states that "Synthesize is the activity of creating Solution hypotheses based on customer needs and market research, and then selecting the most promising ones to be implemented in the ART Backlog."1 Therefore, Synthesize is where Features are prioritized for continuous delivery.

• Question 9:

  Which teams should coordinate when responding to production issues?

  A. Teams across the Value Stream
  B. Dev teams and Ops teams
  C. Support teams and Dev teams
  D. SRE teams and System teams
  A. Teams across the Value Stream

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, when responding to production issues, the DevOps teams should coordinate with each other and with the SRE teams and System teams. The DevOps teams are responsible for developing, building, integrating, testing, deploying, and monitoring the Solution, while the SRE teams and System teams are responsible for ensuring the reliability, availability, security, and performance of the Solution in production. The Ops teams are responsible for managing the infrastructure and services that support the Solution in production. Therefore, all three groups of teams should work together to resolve production issues effectively.

• Question 10:

  What are two important items to monitor in production to support the Release on Demand aspect in SAFe? (Choose two.)

  A. Number of concurrent users
  B. System performance
  C. Business value
  D. Unit test coverage
  E. Percent Complete and Accurate (%CandA)
  A. Number of concurrent users
  B. System performance

  ---

  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