According to theCore Valuesarticle on the Scaled Agile Framework website, the three items that are part of SAFe's Core Values are alignment, relentless improvement, and transparency. The article states that ''The four Core Values of alignment, transparency, respect for people, and relentless improvement represent the foundational beliefs that are key to SAFe's effectiveness. These tenets help guide the behaviors and actions of everyone participating in a SAFe portfolio.'' Therefore, the correct answers are A, alignment, B, relentless improvement, and F, transparency. The other options are not accurate, as they are not the core values of SAFe. Decentralized decision-making is a principle, not a value, of SAFe. Program execution is an outcome, not a value, of SAFe. Assume variability is not a term used in SAFe.

According to theScrum Masterarticle on the Scaled Agile Framework website, the Scrum Master should talk to the Product Owner, compare the new work to existing backlog priorities, and negotiate a sustainable solution when the Product Owner raises a red flag stating there is an additional requirement that needs to be added to the current Iteration. The article states that ''The Scrum Master helps the Product Owner manage the backlog effectively by facilitating backlog refinement and prioritization. The Scrum Master also helps the Product Owner understand and apply the concepts of WSJF, MVP, MMF, and other economic prioritization methods. The Scrum Master supports the Product Owner in negotiating with stakeholders, customers, and the team to ensure that the backlog items are clear, concise, and ready for implementation.'' Therefore, the correct answer is B, talk to the Product Owner, compare the new work to existing backlog priorities, and negotiate a sustainable solution. The other options are not accurate, as they do not follow the Scrum principles of self-organization, time-boxing, and delivering value. Meeting with the team and accepting the work if they agree to work overtime (A) would violate the team's autonomy and sustainability. Accepting the work and extending the Iteration would disrupt the cadence and synchronization of the team and the ART. Refusing the new requirement (D) would ignore the feedback and collaboration of the Product Owner and the stakeholders.

According to theVisualize and Limit WIP, Reduce Batch Sizes, and Manage Queue Lengthsarticle on the Scaled Agile Framework website, batch size optimization happens over time as teams figure out the balance between holding cost and transaction cost. The article states that ''To improve the economics of handling smaller batches---and thus increase throughput---teams must focus on reducing the transaction costs of any batch. This is a continuous improvement activity that happens over time as teams figure out the balance between holding cost and transaction cost.'' Therefore, the correct answer is A, batch size optimization happens over time as teams figure out the balance between holding cost and transaction cost. The other options are not accurate, as they are not the statements that are true about optimizing batch sizes for newly-formed SAFe teams in a program. Batch size is not optimized immediately by looking at transaction and holding costs (B), as it takes time for teams to understand the nature of the work, identify bottlenecks, and find the optimal batch size that minimizes both costs. Batch size is not already optimized if there is continuous flow , as optimization involves finding the right balance between batch size and costs, even within a continuous flow environment. Batch size is not optimized when transaction and holding costs seldom change (D), as holding costs and transaction costs can change over time due to various factors such as team size, workload, and external dependencies.

Two attributes of high-performing teams are:

They experience mutual trust. High-performing teams trust each other to deliver quality work, to support each other, and to resolve conflicts constructively. They also trust their leaders to provide clear direction, feedback, and empowerment.Trust is the foundation of effective collaboration and communication within and across teams12.

They are self-organizing. High-performing teams are able to plan and execute their work without excessive supervision or micromanagement. They have the autonomy and authority to make decisions that affect their work, and they hold themselves accountable for the outcomes.They also continuously inspect and adapt their processes and practices to improve their performance3

According to theApplying Lean Estimating and Forecasting in Cadencearticle on the Scaled Agile Framework website, ART velocities are used to conduct 'what if' analysis for estimating and forecasting in SAFe. The article states that ''The ART velocity is used to conduct 'what if' analysis, which helps determine the feasibility of the plan and the number of features that can be delivered in a PI. The ART velocity is also used to forecast the delivery of features and capabilities beyond the current PI.'' Therefore, the correct answer is C, ART velocities are used to conduct 'what if' analysis. The other options are not accurate, as they are not the statements that are true for estimating and forecasting in SAFe. Feature estimation is not independent of team-level input (A), as teams are involved in estimating the size and complexity of features using story points or normalized story points. Epics are not estimated by the Epic Owner (B), as they are estimated collaboratively by the Epic Owner, Enterprise Architect, and Lean Portfolio Management. Work breakdown structure to the task level does not help increase estimation accuracy (D), as it introduces unnecessary overhead and delays feedback.