Scaled Agile SAFE-DEVOPS Online Practice Questions and Exam Preparation

Scaled Agile SAFE-DEVOPS Online Questions & Answers

• Question 91:

  What is a possible outcome of the Release activity?

  A. A Solution is migrated to the cloud
  B. A Solution is made available to internal users
  C. A Solution infrastructure is provisioned
  D. A Solution is deployed to production
  D. A Solution is deployed to production

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, the Release activity is the final step in the Continuous Delivery Pipeline that deploys the Solution to production. Production is where the Solution is available for end users to operate and consume. The Release activity involves verifying that the Solution meets the quality and security requirements, monitoring its performance and health, and responding to any issues or incidents that may arise. The Release activity also enables continuous improvement by measuring the business value of the Solution and collecting feedback from customers and stakeholders.

• Question 92:

  What is one potential outcome of the Verify activity of the Continuous Delivery Pipeline?

  A. Fix a broken build
  B. Capture usage metrics from a canary release
  C. Roll back a failed deployment
  D. Analyze regression testing results
  D. Analyze regression testing results

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, one potential outcome of the Verify activity of the Continuous Delivery Pipeline is to analyze regression testing results. This means that the Verify activity involves checking the functionality and performance of the Solution after a deployment, and comparing it with the expected results. The handbook states that "Verify is the activity of checking the functionality and performance of the Solution after a deployment, and comparing it with the expected results."1 Therefore, one of the possible outcomes of this activity is to analyze how well the Solution meets the quality standards and customer requirements.

• Question 93:

  Which steps in the value stream should be the main focus when prioritizing improvement items?

  A. Steps with a high Flow Efficiency
  B. Steps with short Active Time and high %CandA in the future-state map
  C. Steps with low Percent Complete and Accurate (%CandA) and short Active Time in the current-state map
  D. Steps with a long Active Time
  B. Steps with short Active Time and high %CandA in the future-state map

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, when prioritizing improvement items, the steps with short Active Time and high %CandA in the future-state map should be the main focus. Active Time is the amount of time a step spends on performing work, while %CandA is the percentage of capacity utilization of a step. The future- state map shows how the Value Stream will look like after implementing improvements, based on customer feedback and business value. The improvement items are ranked by their impact on flow efficiency, customer satisfaction, and business agility. The steps with short Active Time and high %CandA in the future-state map indicate that they are bottlenecks or waste sources that need to be eliminated or reduced as soon as possible. Therefore, they should be prioritized for improvement actions.

• Question 94:

  What triggers the Release activity?

  A. Business decision to go live
  B. Successful deployment to production
  C. Change validated in staging environment
  D. Successful user acceptance tests
  A. Business decision to go live

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide and handbook, the Release activity is triggered by a business decision to go live. This means that the Solution is ready to be delivered to end users and customers, based on the validation and testing done in the previous activities. The handbook states that "The Release activity is triggered by a business decision to go live."1 Therefore, this activity involves releasing value to customers on demand, while also measuring and learning from the feedback.

• Question 95:

  Ensuring that security controls such as threat modeling, application security, and penetration testing are in place throughout the Continuous Delivery Pipeline is an example of which stabilizing skill?

  A. Security Operations
  B. Design for operations
  C. Continuous security monitoring
  D. Failover/disaster recovery
  C. Continuous security monitoring

  ---

  Explanation

  Ensuring that security controls like threat modeling, application security, and penetration testing are in place throughout the Continuous Delivery Pipeline is an example of Continuous security monitoring. This skill involves the ongoing assessment and oversight of security measures within the pipeline to ensure that the software remains secure against potential threats at all stages of its development and deployment.

• Question 96:

  What is one aspect of the Continuous Delivery Pipeline?

  A. Continuous Security
  B. Continuous Integration
  C. Continuous Experimentation
  D. Continuous Delivery
  B. Continuous Integration

  ---

  Explanation

  One aspect of the Continuous Delivery Pipeline is Continuous Integration. Continuous Integration (CI) is the practice of merging all development versions of a code base several times a day and verifying them with automated tests. CI helps to improve the quality and consistency of the code, and to accelerate the delivery and deployment of new functionality. 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: develop, build, test end-to-end, and stage12

• Question 97:

  Feature toggles are useful for which activity?

  A. To accelerate the deployment process
  B. To decouple deployment from release
  C. To enable continuous code integration
  D. To enable continuous testing
  B. To decouple deployment from release

  ---

  Explanation

  According to the SAFe DevOps Practitioner 6.0 study guide1, feature toggles are useful for decoupling deployment from release. Feature toggles are a technique that allows code to be turned "on" or "off" without needing additional deployment. Feature toggles enable teams to experiment with different features, validate their assumptions, and learn from their failures without affecting the rest of the system. Feature toggles also help 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, feature toggles are useful for decoupling deployment from release, which is an aspect of the Continuous Delivery Pipeline that releases new functionality immediately or incrementally based on business and customer needs2.

• Question 98:

  What differentiates Deployment and Release in the continuous Delivery Pipeline?

  Choose the correct option from below list

  A. Deployment occurs multiple times per day; release occurs on demand
  B. Deployment occurs multiple times per day; release occurs in PI boundaries
  C. Deployment involves moving changes to staging; release involves moving them to productionwrong
  D. Deployment involves moving changes to production; release involves making them available to end users
  D. Deployment involves moving changes to production; release involves making them available to end users

  ---

  Explanation

  Continuous Deployment (CD) 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. CD is a technical practice that enables the ability to release value at any time, in a sustainable way. CD is not the same as Release on Demand, which is the business decision to make the new functionality available to end users. Release on Demand is the final aspect of the Continuous Delivery Pipeline, which enables the delivery of value to the end user as fast as possible, based on market demand