Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 11:

  What is an element of CALMR?

  A. Recovery
  B. Application security
  C. Compliance
  D. Metrics
  A. Recovery

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, recovery is an element of CALMR. This means that recovery is the ability to restore the Solution to a desired state after a failure or incident. The handbook states that "Recovery is the ability to restore the Solution to a desired state after a failure or incident."1 Therefore, recovery is one of the key aspects of DevOps excellence that enables continuous delivery.

• Question 12:

  What organizational anti-pattern does DevOps help to address?

  A. Teams that are isolated and working within functional areas (e.g., business, operations, and technology)
  B. Too much focus on centralized planning
  C. Walls of confusion between Customers and the business
  D. Organizations that make decisions along functional lines
  A. Teams that are isolated and working within functional areas (e.g., business, operations, and technology)

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, one of the organizational anti-patterns that DevOps helps to address is teams that are isolated and working within functional areas (e.g., business, operations, and technology). This anti-pattern creates silos, conflicts, and inefficiencies that hinder the collaboration and integration needed for continuous delivery. For example, some teams may prioritize speed over quality, while others may prioritize security over innovation. Some teams 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, DevOps helps to break down the functional silos and enable cross-functional teams that work together to deliver value to customers faster and more reliably.

• Question 13:

  What is a consequence of working in isolation on long-lived code branches?

  A. Trunk/main will not always be in a deployable state
  B. End-to-end tests will fail
  C. Deployments will fail
  D. Rollbacks will be difficult
  A. Trunk/main will not always be in a deployable state

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, working in isolation on long-lived code branches can have negative consequences for the Continuous Delivery Pipeline. This includes making the trunk/main branch less stable and more prone to conflicts and errors. The handbook states that "Working in isolation on long-lived code branches can make the trunk/main branch less stable and more prone to conflicts and errors."1 Therefore, it is recommended to use short-lived feature branches and merge them frequently into the trunk/main branch.

• Question 14:

  Which two skills appear under the Respond activity? (Choose two.)

  Choose the correct options from below list

  A. Cross-team collaboration
  B. Version control
  C. Telemetry
  D. Automatic rollback
  E. Service virtualization
  A. Cross-team collaboration
  B. Version control

  ---

  Explanation

  The Respond activity in the SAFe DevOps Health Radar is about proactively detecting and resolving production issues before they cause business disruption. It requires two skills: cross-team collaboration and version control. Cross-team collaboration enables faster resolution of incidents by involving the right people and teams. Version control enables tracking changes and restoring previous versions of the code or configuration if needed

• Question 15:

  How should developers integrate refactoring into their workflow? Choose the correct option from below list

  A. Refactor continuously as part of test-driven development
  B. Allocate a portion of their capacity to refactoring in every Iteration
  C. Create and estimate refactoring Stories in the Team Backlog
  D. Create and estimate refactoring tasks for each Story in the Team Backlog
  C. Create and estimate refactoring Stories in the Team Backlog

  ---

  Explanation

  Refactoring is the activity of improving the internal structure or operation of a code or component without changing its external behavior. The goal of software development is the continuous delivery of business value to users and stakeholders. Constantly changing technology and evolving business objectives make maintaining and continuously increasing business value difficult. Refactoring enables an emergent design, ensuring the system continues to meet future business needs. Refactors are a particular type of Enabler story in SAFe, and, like any other Story, they must be estimable, verifiable, and valuable, as well as accepted by the Product Owner. SAFe emphasizes the importance of keeping all work visible, including refactoring. Like user value work, refactoring must be planned for, estimated, and prioritized. Therefore, developers should create and estimate refactoring Stories in the Team Backlog, and work on them according to their WSJF1

• Question 16:

  Why is hypothesis evaluation important when analyzing data from monitoring systems in the Release on Demand aspect?

  A. It helps define the minimum viable product (MVP)
  B. It helps operations teams know where to apply emergency fixes
  C. It helps quickly create balanced scorecards for stakeholder review
  D. It helps link objective production data to the hypothesis being tested
  D. It helps link objective production data to the hypothesis being tested

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, hypothesis evaluation is important when analyzing data from monitoring systems in the Release on Demand aspect because it helps link objective production data to the hypothesis being tested. Hypothesis evaluation is the process of measuring and comparing the actual outcomes of a hypothesis with the expected outcomes based on customer feedback and business value. Hypothesis evaluation helps DevOps teams to validate or invalidate their hypotheses, learn from their mistakes, and improve their solutions. By linking objective production data to the hypothesis being tested, DevOps teams can see how well their solutions are delivering value to customers and achieving their goals.

• Question 17:

  Which technical practice is key to enabling trunk-based development?

  A. Gated commits
  B. Refactoring
  C. Code freezes
  D. Feature branching
  A. Gated commits

  ---

  Explanation

  Gated commits are a key technical practice that enables trunk-based development. Gated commits are a mechanism that ensures that only code that passes certain quality checks and tests can be committed to the main trunk of the shared codebase. Gated commits prevent broken changes from affecting other developers or the Continuous Delivery Pipeline. Gated commits typically involve the following steps: A developer writes code and runs local tests on their own machine or branch. The developer pushes the code to a remote repository, where a pre-commit hook triggers a build and test process on a separate server. The build and test process verifies that the code meets the quality standards and does not introduce any errors or conflicts with the existing code on the trunk. If the build and test process succeeds, the code is automatically merged into the trunk and becomes available for other developers and downstream activities. If the build and test process fails, the code is rejected and the developer is notified of the issues that need to be fixed before retrying the commit. Gated commits support trunk-based development by ensuring that 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. Gated commits reduce the complexity and conflicts of merging long-lived branches, improve the quality and consistency of the code by enforcing frequent testing and validation, accelerate the delivery and deployment of new functionality by minimizing the transaction cost and risk, and foster a culture of collaboration and transparency among developers

• Question 18:

  Which practice prevents configuration drift between production and non-production environments?

  A. Session replay
  B. Self-service deployment
  C. Deployment automation
  D. Immutable infrastructure
  D. Immutable infrastructure

  ---

  Explanation

  One practice that prevents configuration drift between production and non-production environments is immutable infrastructure. Immutable infrastructure is a management approach for infrastructure resources where changes are made by deploying new versions of resources instead of modifying existing ones. In this approach, the infrastructure is treated as an immutable asset that is built, deployed, and disposed of, rather than modified in place. For example, instead of modifying an existing virtual machine (VM), a new VM with updated configurations and software is deployed, and the old VM is disposed of. This approach eliminates the possibility of configuration drift and reduces the risk of introducing unintended changes to the infrastructure. Immutable infrastructure also simplifies the management of infrastructure resources, increases the reliability and security of the infrastructure, and facilitates rapid and consistent deployment

• Question 19:

  Which practice appears under the Respond activity?

  A. Site Reliability
  B. Rollback
  C. Service virtualization
  D. Telemetry
  B. Rollback

  ---

  Explanation

  Under the Respond activity in the context of DevOps, the practice of Rollback is often included. Rollback is a key response mechanism used to quickly revert a system to a previous stable state in the event of a failure or issue in the production environment. This practice is critical for maintaining system stability and minimizing downtime.

• Question 20:

  Which statement is true about DevOps?

  A. It enables low-risk releases and fast recovery with fast fix-forward
  B. It enables low-risk releases and fast recovery with no room for errors
  C. It enables high-risk releases and fast recovery with fast fix-forward
  D. It enables a tolerance for low-risk, low-failure, and rapid recovery
  A. It enables low-risk releases and fast recovery with fast fix-forward

  ---

  Explanation

  The statement that is true about DevOps is that it enables low-risk releases and fast recovery with fast fix-forward. DevOps is a mindset, culture, and set of technical practices that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. DevOps aims to deliver value to customers whenever there is a business need, by applying the principles of continuous delivery, continuous integration, continuous deployment, and release on demand. DevOps also embraces a culture of learning and experimentation, where failures are opportunities for improvement and feedback. DevOps enables low-risk releases by breaking down large and complex changes into smaller and more frequent batches, which are easier to test, deploy, and rollback if needed. DevOps also enables fast recovery by implementing practices such as monitoring, alerting, incident response, and disaster recovery, which help to detect and resolve issues quickly, minimize the impact of failures, and restore normal operations as soon as possible. DevOps also supports the fast fix-forward approach, which means fixing errors in production by deploying new code, rather than rolling back to a previous state. This approach reduces the risk of introducing new errors, preserves the value of the new functionality, and accelerates the learning cycle