Which is a benefit of establishing naming standards for code?
(choose the best answer)
A. To make it easy to distinguish between different software products.
B. To ensure that “orphan functions” are not created.
C. To make the code more readable.
D. To communicate the name of the developer that worked on the code.

The Product Backlog is ordered by:
(choose the best answer)
A. The Product Owner with the most valuable items placed at the top.
B. Risk, where safer items are at the top, and riskier items are at the bottom.
C. Size, where small items are at the top and large items are at the bottom.
D. Items are randomly arranged.

How is architecture decided by a Scrum Team?
(choose the best answer)
A. The architect works in the early part of each Sprint to define the architecture for that Sprint.
B. Upfront designs are presented to the Scrum Team prior to the first Sprint.
C. It emerges as the Developers create the system.
D. An architect on the Scrum Team undertakes all architecture tasks.
E. The architecture cares for itself as code is written and deployed.

Which are three attributes of a bad bug report?
(choose the best three answers)
A. Generic titles.
B. Vague statements or untested assumptions.
C. Assigning blame.
D. One bug per report.
E. Simple and repeatable reproduction steps.

A Developer takes the Scrum Master aside to express his concerns about data security issues. What should the Scrum Master do?
(choose the best answer)
A. Go check with the testers.
B. Create a Product Backlog item for security.
C. Tell the Product Owner to stop further development of features until the issues are fixed.
D. Ask the Developer to share the concern with the team as soon as possible.
E. Add security to the Definition of Done.

What are possible benefits of Test-Driven Development?
(choose the best three answers)
A. It helps break down complex problems into smaller ones that are much easier to be tackled.
B. It helps to identify gaps in understanding the desired behavior.
C. It increases collaboration between Developers as it requires Pair Programming.
D. It is a great way for Testers to contribute early in the Sprint as they can start creating all the tests from the beginning on.
E. It makes Integration Tests obsolete and by doing so saves a lot of time.
F. It might lead to better code as refactoring is a part of the Test-Driven Development cycle.