Free PSD Exam Braindumps
Professional Scrum Developer Questions 56–60 (page: 13)

Updated On: 10-Feb-2026

Which of the following describes an architecture spike?

  1. A fundamental architectural problem found in an existing application
  2. The result of an exhaustive architectural planning effort
  3. A small development activity to learn about technical elements of a proposed solution
  4. A decision made by a systems architect to settle disagreement amongst the developers

Answer(s): C

Explanation:

An architecture spike is a small development activity to learn about technical elements of a proposed solution.



What is technical debt?

  1. A term representing the eventual consequences of poor technical choices
  2. Developers that have to pay college debt
  3. Code that hasn't been documented
  4. The money an organization owes to tool and hardware vendors

Answer(s): A

Explanation:

Technical debt is the result of incomplete work going into the increment and poor design and architectural choices.



When should a newly discovered huge bug of a previous sprint be fixed?

  1. Immediately.
  2. Don't fix it immediately, but change the test to not show it as a temporary fix.
  3. Don't fix it, but stub out the code that causes it.
  4. Depends on what the product owner wants.

Answer(s): D

Explanation:

Hiding the bug won't make it go away. Discussing with the product owner is a good step to take, because he knows what work leads to maximum value.



Which two criteria are useful in deciding if something should be documented every sprint?

  1. It has always been documented in the past
  2. The documentation is used to enhance and maintain the software
  3. The scrum master demands it
  4. The software tool being used requires it
  5. It is required by the definition of done

Answer(s): B,E

Explanation:

if the documentation is adding to the quality and maintenance of the software this is definitely a good argument for documenting every sprint. Just because that's the way it's done and we don't want change is not a good reason. Tooling that requires is also isn't. And the scrum master cannot demand this kind of things. If the company's definition of done says so, you must :)



Which are four attributes of a good bug report?

  1. Screenshots or pictures of the bug in action, if possible
  2. Explains some new system functionality desired
  3. Includes build or version number where bug was found
  4. Expected results and observed results
  5. Provides simple and repeatable reproduction steps
  6. Includes code for a proposed fix

Answer(s): A,C,D,E



Viewing page 13 of 34
Viewing questions 61 - 65 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!