Download Professional Scrum Developer (PSD) Exam Questions

test2022-11-09T06:45:02+00:00

Professional Scrum Developer (PSD) Exam Questions are available for you to best prepare for your test. Professional Scrum Developer (PSD) is a certification reserved for developers who use Scrum as their framework to produce complex software. The Professional Scrum Developer (PSD) certification validates your knowledge of how to deliver quality software using the Scrum framework while working in Scrum Teams including the application of modern Agile and DevOps practices. After studying Professional Scrum Developer (PSD) Exam Questions, you will pass your Scrum PSD exam successfully.

Try free PSD practice exam questions.

Page 1 of 3

1. Who is responsible for a sprint backlog item that contains several database tasks?

The developers

Product owner

The company’s database specialist

Scrum master

2. When are testers and QA experts ideally included in the project?

After every sprint review

From the beginning and throughout the sprints, but let's call them developers

When the developers are done

When the product is complete

3. What does code coverage show?

The ratio of the number of tests to lines of code in the system being tested

The quality of unit tests being written

Code being exercised by tests

The absence of defects in code

When a feature is done

4. What is a merge in a version control system?

Identifying a particular codebase as ready for distribution

Combining two or more versions of code into a single codebase

Copying a portion of a codebase to isolate it from the original codebase

Two or more developers working together to ensure proper coding and configuration management

5. What are the scrum values?

commitment, empiricism, focus, respect

commitment, focus, respect, transparency and courage

transparency, inspection, adaptations

commitment, focus, openness, respect and courage

6. Choose two common cross-cutting concerns in application architecture

Release documentation

Build automation

Security

Design pattern choices

Scalability

7. What is test first development?

The continuous restructuring of software to retain flexibility

Having the tester in the development team write the test plans before coding

Creating tests before satisfying them

Testing existing code before adding more code to it

8. Only technical writers can create documentation during a sprint

False

True

9. Which are two benefits of establishing naming conventions for code?

To make the code more readable

To make it easy to distinguish between different software products

To communicate the identity of the developer that wrote the code

To reduce friction in a shared codebase

To ensure that orphan functions are not created

10. The purpose of a sprint is to produce a done increment of product

False

True

Page 2 of 3

11. What is the step to take in TDD after the tests have failed?

Meet with the team to see why it fails

Change the test in a way that is passes

Run it again to verify it fails.

Write the code to satisfy the test

12. How long should the sprint review take? Choose the best answer

Until everyone is done.

Max two hours for a one month sprint

Max two hours

Max four hours

Max four hours for a one-month sprint

13. During the sprint the developers realize that they have selected too many product backlog items.

How should they go from there?

Inform the product owner and the stakeholders during the sprint review

As soon as they realize they should work with the product owner to remove some work while not endangering the sprint goal

Outsource the work to another team

Use a definition of done with lower standards to be able to finish all the work they committed to

14. What is the commitment for the product backlog?

Product goal

Sprint goal

Sprint planning outcome

Definition of done

15. What is the practice of branching code in a version control system?

Combining two or more branches of code into a single code base

Creating a copy of existing code, isolated from the original code

Releasing a specific codebase into a production environment

Tagging or labeling a particular codebase as production ready

16. Who writes tests in a scrum team?

Most junior developer

Product owner

QA specialists

Scrum master

The tester Developers

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

The behavior of a given object can be emulated to the system under test

They are machine-generated and eliminate the need to write code by hand

To increase tight coupling

TDD is impossible without them

Isolating a particular system component for controlled testing

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

Immediately.

Don't fix it immediately, but change the test to not show it as a temporary fix.

Don't fix it, but stub out the code that causes it.

Depends on what the product owner wants.

19. Which of the following best describes an increment of working software?

Additions features in a usable state that complement those delivered in previous iterations

UML diagrams that describe how to deliver functionality in future iterations

A new user interface design for functionality delivered in previous iterations

An automated test suite to verify functionality delivered in previous iterations

A decomposition of all product backlog items into tasks for future sprint backlog lists

20. Which of the following two best describe a ready product backlog item?

It is a complete user story with all the necessary components

It is well understood by the developers and product owner at the sprint planning

It has been changed from unready to ready status in the tracking tool

It has been fully described in the user requirements analysis

It can most likely be done within one sprint

Page 3 of 3

21. What is the purpose of a sprint retrospective? Choose two

Increase quality

Complain only in this session to avoid complaining in the rest of the sprint

Have more fun during the sprint

Increase effectiveness

22. Who must attend the daily scrum? Choose all that apply.

The developers

Everyone invited by the product owner

The scrum master

The manager of the IT department

It is optional, no one has to attend

The product owner

23. What is static analysis?

Analysis performed on software at runtime

A tool that inspects the correctness of static keyword usage

Work performed by the business analyst

Analysis performed on code

24. What is a sprint burn down chart?

Visual representation of work that is still to do and time that is left

A chart showing progress towards the product goal

A chart that shows whether bugs came up

Visual representation of the product backlog items left

25. Upon what type of process control is scrum based?

Deductive

Hybrid

Empirical

Technical

26. Database design must be complete before coding starts to ensure a solid foundation

False

True

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

Architecture is an ongoing discussion amongst the developers, focusing on implementing current Sprint Backlog Items

The developers focus only on adding functionality. The architecture will take care of itself as the developers add functionality

The developers have a set of guiding architecture principles that every developer understands and follows when writing code

Developers assign someone to the role of software architect to ensure the architecture

Architecture is dealt with in sprint 0

28. What is an integration test?

A test of the user interface

A test that runs during a continuous integration build

A test of multiple units of functionality

A test of a single unit of functionality

29. Several scrum teams share the scrum master. Developers of multiple teams approach the scrum master, because they need fulltime commitment from the same technical specialist for the next sprint.

What should the scrum master consider for the response to this problem? Choose the two best answers.

The need for a stable velocity

The benefit of the teams figuring it out theirselves

The need to have all developers busy with work

The ability of the scrum teams to produce integrated increments

30. When might a sprint be cancelled?

When the developers feel they aren't ready

When the project manager decides this.

Never, the sprint must always be finished.

When the sprint goal becomes obsolete