Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 61:

  Innovation accounting stresses the importance of avoiding what?

  A. ROI calculations
  B. Quantitative metrics
  C. Vanity metrics
  D. Objective metrics
  C. Vanity metrics

  ---

  Explanation

  Innovation accounting stresses the importance of avoiding vanity metrics. Vanity metrics are metrics that look good on paper but do not reflect the true value or impact of an innovation. Examples of vanity metrics include the number of downloads, page views, followers, or likes, which may not indicate whether the users are actually engaged, satisfied, or loyal to the product or service. Vanity metrics can be misleading, deceptive, or irrelevant, and can cause the enterprise to waste time and resources on pursuing the wrong goals or strategies. Innovation accounting, on the other hand, is a term coined by Eric Ries in his book The Lean Startup, which describes a process of measuring and learning from the outcomes of innovation experiments. Innovation accounting involves defining the hypothesis, building the minimum viable product (MVP), and evaluating the results using actionable metrics. Actionable metrics are metrics that demonstrate the cause and effect relationship between the actions taken and the outcomes achieved. Examples of actionable metrics include the conversion rate, retention rate, revenue per customer, or customer satisfaction score, which can indicate whether the product or service is delivering value to the customer and the enterprise. Actionable metrics can help the enterprise to validate or invalidate the hypothesis, and to decide whether to pivot or persevere with the innovation78

• Question 62:

  What should the team be able to do after current-state mapping?

  A. Define a plan to reduce the lead time and increase Active Time
  B. Identify those responsible for the biggest bottlenecks in the process
  C. Describe the biggest bottlenecks in the delivery pipeline
  D. Define Enabler Features that will improve the Value Stream
  C. Describe the biggest bottlenecks in the delivery pipeline

  ---

  Explanation

  After conducting current-state mapping in the context of Value Stream Mapping, a team should be able to identify and describe the biggest bottlenecks in the delivery pipeline. Current-state mapping is a process of visualizing the entire flow of a product or service from start to finish, highlighting each step and identifying where delays or inefficiencies occur. By understanding where these bottlenecks are, teams can then work on strategies to improve the overall flow, reduce lead times, and enhance efficiency. This step is crucial for identifying areas for improvement and setting the stage for future actions to optimize the Value Stream.

• Question 63:

  What is the primary goal of the Stabilize activity? Choose the correct option from below list

  A. To achieve active-active site replication
  B. To enhance stability with blue/green deployment
  C. To establish quality-of-service agreements with customers
  D. To avoid unplanned outages and security breaches
  D. To avoid unplanned outages and security breaches

  ---

  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

• Question 64:

  What is the correct order of activities in the Continuous Integration aspect?

  A. Stage, Develop, Build, Test end-to-end
  B. Build, Develop, Stage, Test end-to-end
  C. Develop, Test end-to-end, Build, Stage
  D. Develop, Build, Test end-to-end, Stage
  D. Develop, Build, Test end-to-end, Stage

  ---

  Explanation

  The correct order of activities in the Continuous Integration aspect is: Develop, Build, Test end-to-end, Stage. Continuous Integration (CI) is an aspect of the Continuous Delivery Pipeline that automates the development, testing, integration, and validation of new functionality in preparation for deployment and release. CI is the second aspect in the four- part Continuous Delivery Pipeline of Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. CI consists of four activities, as shown in Figure 1: Develop ?This activity involves implementing stories by refining features from the ART Backlog, coding, testing, and committing the work product into the source control system. Testing in this activity tends to focus on unit and story-level testing and often requires test doubles to replicate other components or subsystems that are not readily available or easily tested. Build ?This activity involves creating deployable binaries and merging development branches into the trunk. Building in this activity includes compiling, linking, packaging, and verifying the code and components. Building also involves applying code quality and security checks, such as static code analysis, code coverage, and code review. Test end-to-end ?This activity involves validating the solution end-to-end, including the functional and nonfunctional aspects, such as performance, usability, reliability, and security. Testing in this activity requires integrating the code and components with other subsystems and services, and using test environments that resemble the production environment as much as possible. Testing also involves applying automated testing tools and frameworks, such as regression testing, integration testing, system testing, and acceptance testing. Stage ?This activity involves hosting and validating solutions in a staging environment before production. Staging in this activity includes deploying the solution to a preproduction environment that mimics the production environment in terms of hardware, software, configuration, and data. Staging also involves applying final checks and verifications, such as smoke testing, exploratory testing, and user acceptance testing910

  1: https://www.lean.org/the-lean-post/articles/understanding-the-fundamentals-of-value- stream-mapping/ 2: https://www.gembaacademy.com/school-of-lean/value-stream- mapping/adapting-value-stream-mapping-for-office-and-serviceenvironments/what-is-the- c-a-percentage-complete-accurate-metric 3: https://scaledagileframework.com/guidance- applied-innovation-accounting-in-safe/ 4: https://support.scaledagile.com/s/article/Exam- Study-Guide-SDP-6-0-SAFe-for-DevOps 5: https://www.redhat.com/en/topics/devops/what- is-blue-green-deployment 6: https://docs.cloudfoundry.org/devguide/deploy-apps/blue- green.html 7: https://scaledagileframework.com/guidance-applied-innovation-accounting-insafe/ 8: https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for- DevOps 9: https://scaledagileframework.com/continuous-integration/ 10: https://support.scaledagile.com/s/article/Exam-Study-Guide-SDP-6-0-SAFe-for-DevOps

• Question 65:

  Why are canary releases used?

  A. To prevent outages
  B. To introduce minimum viable features
  C. To reduce deployment times
  D. To allow incremental release
  D. To allow incremental release

  ---

  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

• Question 66:

  When does the Continuous Integration aspect of the Continuous Delivery Pipeline begin?

  A. When code is checked in to version control
  B. When a User Story has satisfied its definition of done
  C. When a Feature has been pulled for work
  D. When the Team Backlog has been refined
  C. When a Feature has been pulled for work

  ---

  Explanation

• Question 67:

  In which activity are specific improvements to the Continuous Delivery Pipeline identified?

  A. Impact mapping
  B. Value Stream identification
  C. Problem-Solving Workshop
  D. Future-state Value Stream Mapping
  D. Future-state Value Stream Mapping

  ---

  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.

• Question 68:

  What is the recommended way to prioritize improvement items for the DevOps transformation?

  Choose the correct options from below list

  A. Minimum marketable feature
  B. Weighted Shortest Job First
  C. Lean business Case
  D. Minimum Viable Product
  B. Weighted Shortest Job First

  ---

  Explanation

  The recommended way to prioritize improvement items for the DevOps transformation is to use Weighted Shortest Job First (WSJF). WSJF is a prioritization model that considers the cost of delay, job size, and economic value of each improvement item. It helps to identify the most urgent and valuable items that can be delivered in the shortest amount of time

• Question 69:

  What is the first area that should be identified in Value Stream Mapping?

  A. The steps
  B. The people who supervise the work
  C. The bottlenecks
  D. Active Time, Flow Time. and Percent Complete and Accurate (%CandA)
  A. The steps

  ---

  Explanation

• Question 70:

  What is the purpose of a minimum viable product?

  A. To demo to Product Management for feedback
  B. To release to production
  C. To validate the hypothesis
  D. To sell to new markets
  C. To validate the hypothesis

  ---

  Explanation

  The purpose of a minimum viable product is to validate the hypothesis. A minimum viable product (MVP) is an early and minimal version of a new product or solution used to prove or disprove an epic hypothesis. An epic is a significant solution development initiative that requires the definition and approval of an MVP. An epic hypothesis is a statement that describes the expected outcome, benefit, and value of an epic. The MVP is the smallest possible solution that can be used to test the epic hypothesis with real customers or users, and to gather feedback and data. The MVP helps reduce the risk of investing in a solution that nobody wants or needs, and enables faster learning and adaptation. The MVP is not the final product or solution, but rather a starting point for further development and improvement