Free PSD Exam Braindumps
Professional Scrum Developer Questions 51–55 (page: 12)

Updated On: 10-Feb-2026

What are two reasons to use mock objects in unit tests?

  1. The behavior of a given object can be emulated to the system under test
  2. They are machine-generated and eliminate the need to write code by hand
  3. To increase tight coupling
  4. TDD is impossible without them
  5. Isolating a particular system component for controlled testing

Answer(s): A,E

Explanation:

Mock objects are simulating the behavior of dependencies such as persistance layers or APIs. By mocking these you can be sure about what you are testing, and not accidentally testing the external dependency.



Select three criteria for the definition of done

  1. Code review is done
  2. Acceptance tests pass
  3. Regression tests pass
  4. The product is released at the end of every sprint
  5. Code coverage 90%

Answer(s): A,B,C

Explanation:

Releasing the product at the end of the sprint doesn't relate to one item and when it's done. Code coverage does, but it's the worst criteria in this list, because it's a stimulus to write tests that cover a lot of lines rather than cover the functionality.



Which metric is least useful when measuring code maintainability?

  1. Function points
  2. Cyclometic complexity
  3. Depth of inheritance

Answer(s): A

Explanation:

The other two are good metrics. Function points are the points representing the amount of business functionality.



Is it a good idea to follow each automated build with the execution of automated tests?

  1. Yes, it will show code coverage which is an excellent metric of quality and progress
  2. No, it takes too much time
  3. No, the outcomes might disturb the developers' focus
  4. Yes, the tests may identify whether there are bugs that the developers should fix before proceeding

Answer(s): D

Explanation:

It's definitely a good practice. And not because you can see the code coverage (which also isn't an excellent metric of quality and progress), but because you can detect problems before moving on.



What are two ways developers can ensure a good architecture? (two answers)

  1. Architecture is an ongoing discussion amongst the developers, focusing on implementing current Sprint Backlog Items
  2. The developers focus only on adding functionality. The architecture will take care of itself as the developers add functionality
  3. The developers have a set of guiding architecture principles that every developer understands and follows when writing code
  4. Developers assign someone to the role of software architect to ensure the architecture
  5. Architecture is dealt with in sprint 0

Answer(s): A,C

Explanation:

There is no sprint 0, architecture won't take care of itself and there is no architect role. The architecture is an ongoing discussion and growing construct. There are guidelines and principles in place.



Viewing page 12 of 34
Viewing questions 56 - 60 out of 163 questions


Post your Comments and Discuss Scrum PSD exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!