Your Scrum Team is one of seven teams working on a product. All teams use the same version control system. Which is the best approach to deliver a high-quality Increment?
(choose the best answer)
A. Each team should have its own automated build.
B. There is one automated and integrated build for all seven teams.
C. Each team’s automated build is integrated toward the end of the Sprint.
D. Developers should perform a combination of local and private builds.

When do the Developers show their work to the Product Owner?
(choose the best answer)
A. Whenever the Product Owner asks.
B. During the Sprint Review.
C. Anytime the Developers need feedback from the Product Owner.
D. All of the above.

Which are four attributes of a good bug report?
(choose the best four answers)
A. Expected results and observed results.
B. Includes code for a proposed fix.
C. Includes build or version number where the bug was found.
D. Explains some new system functionality desired.
E. Provides simple and repeatable reproduction steps.
F. Screenshots or other pictures of bug in action.

Select two ways in which technical debt impacts transparency.
(choose the best two answers)
A. It enhances transparency for the Product Owner as the Developers are not allowed to do additional feature development in a Sprint as long as there is technical debt.
B. When calculated and estimated, the total amount of technical debt shows exactly how long until the Product Owner can release the Increment.
C. As development progresses and code is added, the system becomes more difficult to stabilize, which results in future work being slowed down in unpredictable ways.
D. It leads to false assumptions about the current state of the system, specifically of an Increment being releasable at the end of a Sprint.

Which metric is LEAST useful when measuring code maintainability?
(choose the best answer)
A. Function points.
B. Depth of inheritance.
C. Cyclomatic complexity.

Which model or idea increases code testability?
(choose the best answer)
A. INVEST (Independent, Negotiable, Valuable, Estimable, Small Enough, Testable)
B. CI (Continuous Integration)
C. SOLID (Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency Inversion)
D. PLP (Principle of Least Privilege)