Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 51:

  What work is performed in the Build activity of the Continuous Delivery Pipeline?

  A. Code review
  B. Compile
  C. Code
  D. Automated acceptance testing
  B. Compile

  ---

  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

• Question 52:

  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 Release
  B. Continuous Deployment
  C. Continuous Improvement
  D. Continuous Exploration
  E. Continuous Testing
  B. Continuous Deployment
  D. Continuous Exploration

  ---

  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

• Question 53:

  Gemba walks are an important competency in support of which activity of the DevOps Health Radar?

  A. Hypothesize
  B. Continuous Exploration
  C. Collaborate and Research
  D. Learn
  C. Collaborate and Research

  ---

  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.

• Question 54:

  Weighted shortest job first is applied to backlogs to identify what?

  Choose the correct option from below list

  A. Maximum economic value
  B. Epics, Features, and Capabilities
  C. User business value
  D. Proxy for job size
  A. Maximum economic value

  ---

  Explanation

  Weighted Shortest Job First (WSJF) is a prioritization model used to sequence work for maximum economic benefit. In SAFe, WSJF is estimated as the relative cost of delay divided by the relative job duration. In a flow-based system, priorities must be continuously updated to provide the best economic outcomes. In other words, job sequencing produces the best results rather than prioritization based on a theoretical return on investment for each job. To that end, SAFe applies WSJF to prioritize backlogs. Backlogs are continuously prioritized based on a WSJF algorithm that uses relative user and business value, time criticality, risk reduction and/or opportunity enablement, and job size. WSJF also conveniently and automatically ignores sunk costs, a fundamental principle of Lean economics

• Question 55:

  One goal of DevOps in SAFe is to fully automate the steps between which two pipeline activities?

  A. Code commit and release
  B. Code commit and user acceptance testing
  C. Code commit and deploy
  D. Code commit and stage
  A. Code commit and release

  ---

  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.

• Question 56:

  How frequently should Agile Release Trains release? Choose the correct option from below list

  A. One per PI
  B. On demand
  C. Continuously
  D. Once per iteration
  B. On demand

  ---

  Explanation

  Agile Release Trains (ARTs) should release on demand, which means releasing new functionality immediately or incrementally based on business and customer needs. Release on demand 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 decision of what and when to release is a critical economic driver that requires careful consideration of the customer needs, market rhythms, and economic outcomes. Release on demand 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 57:

  Which statement describes what could happen when development and operations do not collaborate early in the pipeline?

  A. Flow times are reduced
  B. Teams build things quickly but build the wrong things
  C. Surprises are found in deployment that lead to significant rework and delay
  D. Automation of integration test is not possible
  C. Surprises are found in deployment that lead to significant rework and delay

  ---

  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.

• Question 58:

  The Release on Demand aspect enables which key business objective?

  A. Business value
  B. Quality
  C. Time-to-market
  D. Alignment
  A. Business value

  ---

  Explanation

  The Release on Demand aspect enables the key business objective of delivering business value to customers. Release on Demand is the process by which features deployed into production are released incrementally or immediately to customers based on market demand. It 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 decision of what and when to release is a critical economic driver that requires careful consideration of the customer needs, market rhythms, and economic outcomes. Release on Demand 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. Release on Demand involves four activities: release, stabilize and operate, measure, and learn. These activities help to deliver the solution to end users, ensure the solution is working well from a functional and nonfunctional perspective, quantify the value delivered by the solution, and collect feedback and prepare for the next loop through the CDP3

• Question 59:

  What is true about the Critical Flow Properties portion of the DevOps Transformation Canvas?

  A. It captures the people who need to improve the flow properties
  B. It captures the flow properties that are most in need of improvement
  C. It captures the lowest priority improvement items
  D. It captures the work-in-process (WIP) limits that should be applied to the Value Stream
  B. It captures the flow properties that are most in need of improvement

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, the Critical Flow Properties portion of the DevOps Transformation Canvas captures the flow properties that are most in need of improvement. Flow properties are the characteristics of a value stream that affect how well it delivers value to customers. The Critical Flow Properties portion identifies the flow properties that have the most impact on customer satisfaction and business outcomes, and prioritizes improvement actions accordingly. The Critical Flow Properties portion is based on data from monitoring systems, customer feedback, and business value analysis. Therefore, it captures the flow properties that are most in need of improvement for each value stream.

• Question 60:

  What is true about the Boundaries and Limitations portion of the DevOps Transformation Canvas?

  Choose the correct options from below list

  A. It captures budget constraints that will prevent DevOps improvements
  B. It captures improvement items that require the support of other people or teams
  C. It captures the people who need to be involved in the DevOps transformation
  D. It captures the lowest priority improvement items
  B. It captures improvement items that require the support of other people or teams

  ---

  Explanation

  The Boundaries and Limitations portion of the DevOps Transformation Canvas is used to capture improvement items that require the support of other people or teams. These are items that are outside the scope or control of the current team or value stream, but are necessary for achieving the DevOps vision and goals. They help to identify dependencies, risks, and stakeholders that need to be engaged or aligned