Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 41:

  Continuous Deployment enables which key business objective?

  A. Time-to-market
  B. Manage technical debt
  C. Release continuously
  D. Business value
  A. Time-to-market

  ---

  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.

• Question 42:

  Which practice helps developers deploy their code into production?

  A. Deployment automation
  B. Continuous Deployment
  C. Infrastructure as code
  D. Self-service deployment
  B. Continuous Deployment

  ---

  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.

• Question 43:

  What are the first two actions for visualizing the current state of the Continuous Delivery Pipeline? (Choose two.)

  A. Calculate Total Process Time
  B. Identify improvement items
  C. Identify the steps
  D. Identify the people
  E. Calculate Total Lead Time
  C. Identify the steps
  D. Identify the people

  ---

  Explanation

  The first two actions for visualizing the current state of the Continuous Delivery Pipeline are to identify the steps and the people. The Continuous Delivery Pipeline (CDP) represents the workflows, activities, and automation needed to guide new functionality from ideation to an on-demand release of value. The CDP consists of four aspects: Continuous Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand. Visualizing the current state of the CDP helps the organization to understand the flow of value, measure the performance, and identify the improvement opportunities. To visualize the current state of the CDP, the first two actions are to identify the steps and the people involved in each aspect of the CDP. The steps are the activities and tasks that are performed to deliver value, such as ideation, development, testing, deployment, and release. The people are the roles and responsibilities that are involved in each step, such as product owners, developers, testers, operations, and security. Identifying the steps and the people helps to create a value stream map of the CDP, which is a visual representation of the end-to-end delivery process

• Question 44:

  The DevOps Health Radar aligns the four aspects of the Continuous Delivery Pipeline to which four stakeholder concerns?

  A. Portfolio, Solution, ART, team
  B. Productivity, efficiency, speed-to-market, competitive advantage
  C. Exploration, integration, development, reflection
  D. Alignment, quality, time-to-market, business value
  D. Alignment, quality, time-to-market, business value

  ---

  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

• Question 45:

  Who is responsible for ensuring quality is built into the code in SAFe?

  A. Product Owners
  B. Agile Teams
  C. Testers - xx
  D. Developers
  B. Agile Teams

  ---

  Explanation

  Agile Teams are responsible for ensuring quality is built into the code in SAFe. SAFe is a framework for scaling agile practices across the enterprise, based on the principles of Lean, Agile, and DevOps. SAFe organizes the enterprise into Agile Release Trains (ARTs), which are teams of Agile Teams that deliver value in a regular cadence. Agile Teams are the fundamental building blocks of SAFe, and they are cross-functional, self-organizing, and self-managing teams that deliver value in short iterations. Agile Teams are responsible for ensuring quality is built into the code in SAFe, by applying the following practices: Test-first ?Test-first is a practice that involves writing tests before writing code, to ensure that the code meets the requirements and standards, and does not introduce any defects or vulnerabilities. Test-first helps to improve the design and maintainability of the code, and to accelerate the feedback and validation process. Test-first can be implemented using various techniques, such as Test-Driven Development (TDD), Behavior-Driven Development (BDD), or Acceptance Test-Driven Development (ATDD). Built-in quality ?Built-in quality is a practice that involves applying quality standards and checks throughout the solution lifecycle, rather than inspecting quality after the fact. Built-in quality helps to prevent defects from escaping to downstream stages or customers, and to reduce the cost and risk of rework and waste. Built-in quality can be achieved using various methods, such as code quality and security analysis, code review, pair programming, refactoring, and continuous testing. Continuous testing ?Continuous testing is a practice that involves automating and executing tests at every stage of the Continuous Delivery Pipeline, to verify that the solution meets the functional and nonfunctional requirements and standards, and to detect and resolve any issues or defects as early as possible. Continuous testing helps to ensure the reliability and performance of the solution, and to support the delivery and deployment of value to the customer. Continuous testing can be performed using various tools and frameworks, such as unit testing, integration testing, system testing, acceptance testing, performance testing, and security testing

• Question 46:

  What can impede the progress of a DevOps transformation the most?

  A. Lack of funding for CI/CD pipeline tools
  B. When various groups in the organization have different directions and goals
  C. When there is no DevOps team
  D. When teams use frequent retrospectives
  B. When various groups in the organization have different directions and goals

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, one of the main challenges of a DevOps transformation is when various groups in the organization have different directions and goals. This can create silos, conflicts, and inefficiencies that hinder the collaboration and integration needed for continuous delivery. For example, some groups may prioritize speed over quality, while others may prioritize security over innovation. Some groups may resist change and adopt outdated practices, while others may embrace new technologies and methodologies. These differences can lead to misalignment, duplication, and waste of resources that slow down the delivery pipeline and reduce the value to customers. Therefore, having a common vision, culture, and set of technical practices that support the SAFe CALMR approach to DevOps is essential for overcoming this challenge.

• Question 47:

  What is one of the top advantages of mapping the current state of the delivery pipeline?

  A. To help identify and make short-term fixes
  B. To help with incremental software delivery
  C. To achieve a collective understanding and consensus around problems
  D. To identify some of the processes within the delivery pipeline
  C. To achieve a collective understanding and consensus around problems

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, one of the top advantages of mapping the current state of the delivery pipeline is to achieve a collective understanding and consensus around problems. Mapping the current state of the delivery pipeline is a technique that helps teams visualize and analyze their current processes, practices, and performance. Mapping the current state of the delivery pipeline enables teams to identify pain points, inefficiencies, and opportunities for improvement. Mapping the current state of the delivery pipeline also fosters collaboration, communication, and alignment among team members and stakeholders. By mapping the current state of the delivery pipeline, teams can gain a shared vision of their current situation, challenges, and goals. This can help them to reach a collective understanding and consensus around problems that need to be solved or opportunities that need to be pursued. Therefore, mapping the current state of the delivery pipeline is an advantage that can improve team cohesion and decision making.

• Question 48:

  Which statement illustrates the biggest bottleneck?

  A. WT = 5 days, AT = 2.5 days, %CandA = 100%
  B. WT = 10 days, AT = 0.5 day, %CandA = 100%
  C. WT = 1 day, AT = 0.5 day, %CandA = 90%
  D. WT = 6 days, AT = 5 days, %CandA = 100%
  B. WT = 10 days, AT = 0.5 day, %CandA = 100%

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the statement that illustrates the biggest bottleneck is

  B. WT = 10 days, AT = 0.5 day, %CandA = 100%. This means that the value stream has the longest lead time (WT), the shortest actual time (AT), and the highest relative economic value (CandA). These are the three metrics that are used to measure and optimize the value stream performance. The handbook states that "The three metrics used to measure and optimize value stream performance are WT, AT, and %CandA."1 Therefore, a bigger bottleneck indicates a lower value stream efficiency and a higher waste or inefficiency.

• Question 49:

  Which statement describes a measurable benefit of adopting DevOps practices and principles?

  Choose the correct option from below list

  A. It results in faster lead time, and more frequent deployments
  B. It identifies key Value Streams
  C. It guarantees an increase in profits and decrease in downtime
  D. It creates a highly functional, cross-team culture
  A. It results in faster lead time, and more frequent deployments

  ---

  Explanation

  One of the measurable benefits of adopting DevOps practices and principles is that it results in faster lead time and more frequent deployments. Lead time is the time it takes from the moment a change is requested until it is delivered to the customer. Frequent deployments are the number of times a change is deployed to production. Both of these metrics indicate the speed and efficiency of the DevOps process, as well as the ability to respond to customer needs and feedback. According to the State of DevOps Report 2020, high-performing DevOps teams have 208 times faster lead times and 106 times more frequent deployments than low-performing teams

• Question 50:

  Which two technical practices focus on Built-in Quality? (Choose two.)

  Choose the correct option from below list

  A. Environment configuration
  B. Pair work
  C. Test-driven development
  D. Feature toggles
  E. Canary releases
  B. Pair work
  C. Test-driven development

  ---

  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