Explanation
According to the SAFe DevOps Practitioner 6.0 study guide1, one of the benefits of DevOps is better alignment between strategy and execution. 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 helps break down organizational silos and develop a Continuous Delivery Pipeline (CDP) - a high-performance innovation engine capable of delivering market-leading solutions at the speed of business.
By aligning strategy and execution, DevOps enables teams to deliver value to customers faster and more reliably, as well as to adapt to changing market conditions and customer needs. Therefore, better alignment between strategy and execution is one of the benefits of DevOps.

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

Explanation
Continuous means to deploy to production as often as possible and release when the business needs it in the context of continuous delivery in SAFe DevOps. Continuous delivery is the ability to deliver value to the end user whenever there is a business need. It requires a Continuous Delivery Pipeline (CDP) that supports the integration, automation, and collaboration needed to effectively develop and operate a solution. Continuous delivery enables the enterprise to respond to changing customer needs and market conditions with speed and quality. Continuous delivery does not mean releasing every change to the end user immediately. Rather, it means decoupling deployment from release, and allowing the business to decide when to release the new functionality based on customer demand and economic outcomes1

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

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