Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 81:

  What is one recommended way to architect for operations?

  Choose the correct option from below list

  A. Create detailed run books
  B. Establish an architecture review board
  C. Require developers to support their own code
  D. Implement feature toggles
  D. Implement feature toggles

  ---

  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

• Question 82:

  What is trunk-based development?

  A. Each developer maintains a separate branch
  B. Teams with similar dependencies create one single branch for the team's work
  C. All teams committing their code into one trunk
  D. Every team works in their own trunk
  C. All teams committing their code into one trunk

  ---

  Explanation

  Trunk-based development is a version control management practice where all developers work on the same trunk of shared code. 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. Trunk-based development is a common practice among DevOps teams and part of the DevOps lifecycle since it streamlines merging and integration phases. It also enables continuous integration, which is the practice of merging all development versions of a code base several times a day. Trunk-based development has several benefits, such as: It reduces the complexity and conflicts of merging long-lived branches It improves the quality and consistency of the code by enforcing frequent testing and validation It accelerates the delivery and deployment of new functionality by minimizing the transaction cost and risk It fosters a culture of collaboration and transparency among developers

• Question 83:

  What is an output of the Release activity?

  Choose the correct option from below list

  A. A Feature migrated to the cloud
  B. A Feature deployed to production
  C. A Feature made available to end users
  D. A Feature made available to internal users
  C. A Feature made available to end users

  ---

  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

• Question 84:

  What is the desired frequency of deployment in SAFe? Choose the correct option from below list

  A. Continuous
  B. Daily
  C. Once per Iteration
  D. Once per PI
  A. Continuous

  ---

  Explanation

  The desired frequency of deployment in SAFe is continuous, meaning that new functionality can be deployed to production as soon as it is ready, without waiting for fixed release dates or schedules. Continuous deployment is an aspect of the CDP that 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

• Question 85:

  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
  A. The people responsible for the next step

  ---

  Explanation

  The people responsible for the next step should be consulted first when calculating the % Complete and Accurate (%CandA) metric. The %CandA 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 %CandA 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 %CandA metric can reflect the actual customer satisfaction and the potential waste in the process1

• Question 86:

  Which metric reflects the quality of output at each step in the Value Stream?

  A. Code quality
  B. Active Time
  C. Percent Complete and Accurate (%CandA)
  D. Flow Efficiency
  C. Percent Complete and Accurate (%CandA)

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the metric that reflects the quality of output at each step in the Value Stream is Percent Complete and Accurate (%CandA). This metric measures the relative cost of delay divided by the relative job duration, which indicates how efficiently the value stream delivers value to customers. The handbook states that "Percent Complete and Accurate (%CandA) is a metric that measures the relative cost of delay divided by the relative job duration."1 Therefore, %CandA helps teams identify and eliminate any waste or inefficiencies in their value stream.

• Question 87:

  What are two activities performed as part of defining the hypothesis in Continuous Exploration? (Choose two.)

  A. Elicit feedback
  B. Identify Metrics based on leading indicators
  C. Use value stream mapping
  D. Define the minimum viable product
  E. Develop a detailed business case
  B. Identify Metrics based on leading indicators
  D. Define the minimum viable product

  ---

  Explanation

  Two activities performed as part of defining the hypothesis in Continuous Exploration are identifying metrics based on leading indicators and defining the minimum viable product. Continuous Exploration (CE) is an aspect of the Continuous Delivery Pipeline that drives innovation and fosters alignment on what should be built by continually exploring the market and customer needs, defining a vision, roadmap, and set of features for a solution that addresses those needs. CE is based on applying customer-centric and design thinking to understand and create alignment on new development opportunities, while recognizing that all such ideas are hypotheses that need to be validated. CE involves four activities: hypothesize, collaborate and research, synthesize, and validate. The hypothesize activity describes the practices for generating ideas and the measurements needed to validate them with customers. The hypothesize activity involves the following practices: Identifying metrics based on leading indicators ?Leading indicators are metrics that measure the expected outcomes and benefits of the solution, such as customer satisfaction, retention, engagement, and revenue. Leading indicators 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 features. Leading indicators are also known as key performance indicators (KPIs) or

  objectives and key results (OKRs).

  Defining the minimum viable product (MVP) ?An MVP is a version of the solution that has just enough features to test the hypotheses and assumptions about the customer value proposition, and to elicit feedback from the customer. An MVP

  is not a fully functional or polished product, but rather a learning vehicle that allows the enterprise to validate the problem-solution fit and the product-market fit. An MVP helps to reduce the uncertainty and risk of developing the wrong solution,

  and to accelerate the learning and discovery process11

• Question 88:

  Which DevOps principle focuses on identifying and eliminating bottlenecks in the Continuous Delivery Pipeline?

  A. Measurement
  B. Automation
  C. Lean flow
  D. Recovery
  C. Lean flow

  ---

  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

• Question 89:

  Scanning application code for security vulnerabilities is an important step in which aspect of the Continuous Delivery Pipeline?

  A. Continuous Exploration
  B. Continuous Deployment
  C. Release on Demand
  D. Continuous Integration
  D. Continuous Integration

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, scanning application code for security vulnerabilities is an important step in the Continuous Integration aspect of the Continuous Delivery Pipeline. Continuous Integration is the process of developing, testing, integrating, and validating new functionality in preparation for deployment and release. Continuous Integration helps teams to improve quality, reduce risk, and establish a fast, reliable, and sustainable development pace. Scanning application code for security vulnerabilities is one of the ways to ensure that the code meets the quality standards and requirements, and that it does not contain any errors, bugs, or vulnerabilities that could compromise the security or functionality of the Solution. Scanning application code for security vulnerabilities can be performed by using tools such as GitHub Advanced Security for Azure DevOps2, which uses CodeQL to identify vulnerabilities in various languages and frameworks. Therefore, scanning application code for security vulnerabilities is an important step in the Continuous Integration aspect of the Continuous Delivery Pipeline.

• Question 90:

  Why is it important to take a structured approach to analyze problems in the delivery pipeline?

  A. It provides a structured roadmap for the SAFe implementation
  B. It helps ensure that actual causes of problems are addressed, rather than symptoms
  C. It ensures that solutions are more likely to be approved for implementation
  D. It allows the solution to be demoed to key stakeholders
  B. It helps ensure that actual causes of problems are addressed, rather than symptoms

  ---

  Explanation

  The reason why it is important to take a structured approach to analyze problems in the delivery pipeline is that it helps ensure that actual causes of problems are addressed, rather than symptoms. A structured approach to problem analysis involves following a systematic and logical process to identify, define, and understand the root causes of a problem, and to propose and evaluate possible solutions. A structured approach can help avoid jumping to conclusions, making assumptions, or applying band-aid fixes that do not solve the underlying issues. A structured approach can also help involve the relevant stakeholders, collect and analyze data, prioritize and categorize problems, and communicate and document the findings and recommendations. Some examples of structured approaches to problem analysis are the 5 Whys, the fishbone diagram, the Pareto chart, and the PDCA cycle