Valid PSD Test Answers & Scrum PSD Exam PDF [Q22-Q40]

Rate this post

Valid PSD Test Answers & Scrum PSD Exam PDF

Scrum PSD Certification Real 2022 Mock Exam

NEW QUESTION 22
What is an inappropriate activity for a developer with special QA skills?

Create a plan for testing the application

Identify tools and techniques to be used in testing the product

Define acceptance criteria for features

Delay test activities until a feature has been coded

Test activities can start directly with the sprint.

NEW QUESTION 23
Choose three reasons why automated builds are important.

They support Continuous Integration

The eliminate the need for build engineers

They ensure your product remains bug free

They clearly define the build process

They allow frequent validation and ensure the product remains in a potentially releasable state

Automated builds are making builds of the code after every change to the codebase. As soon as something breaks, the developers get informed. In order to automate it, the build process needs to be cleary defined. They’re a corner stone for CI.

NEW QUESTION 24
How is the management external to the Scrum team involved in the daily scrum?

The product owner speaks on their behalf

The developers self-manage and they are the only management required at the daily scrum

The scrum master speaks on their behalf

The scrum master lets them know whether they need to be preset

Only the developers need to be present at the daily scrum, since they are self managing, that’s all the management necessary.

NEW QUESTION 25
What topics can be addressed during the sprint review? Choose the best answer.

The scrum process

All of these

The increment

Coding and engineering practices

These are all potentional topics for the sprint review. If you are not sure, please read the sprint review section in the scrum guide again.

NEW QUESTION 26
Which of the following describes an architecture spike?

A fundamental architectural problem found in an existing application

The result of an exhaustive architectural planning effort

A small development activity to learn about technical elements of a proposed solution

A decision made by a systems architect to settle disagreement amongst the developers

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

NEW QUESTION 27
Which four are benefits of TDD?

It promotes good design and separation of concerns

It causes you to construct a test harness that can be automated

It improves quality and reduces bugs

It reduces the cost of maintenance over time

It ensure there will be no bugs in the code

Nothing can really ensure it will be bug free.

NEW QUESTION 28
What are some disadvantages of code coverage as a measure for how well a system or product is tested? (three answers)

It does not measure usability

It is too complicated to explain to management

It only provides insights to programmers

It does not ensure that the most important or highest risk areas of the code are being exercised by tests

It could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing code coverage

Not being able to explain to management should never be the reason to not do it. It doesn’t only provide some data to programmers, the problem is that code coverage alone is not meaning a lot.

NEW QUESTION 29
If multiple teams are working on the same product, they should each have their own product backlog

False

True

One product backlog per product

NEW QUESTION 30
Which phrase best describes a product owner?

Team manager

Project manager

Requirements engineer

Mediator for the developers and customers

Value optimizer

The scrum guide says: “The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team.” The key here is the value maximizing part. Of course, he also comes up with requirements and acts as a go-between between developers and customers, but that is definitely not the best answer here.

NEW QUESTION 31
When more teams are working on the same product. How should they go about their definition of done?

Every team must make their own DoD, a meeting should be organised so that the differences are known.

It depends on the product owner

All development teams must have a DoD that makes their combined work releasable.

Every team uses its own. The differences are discussed in a hardening sprint.

The product must be releasable and done must mean the same for all additions to the product. So they must have a DoD that can combined. There is no hardening sprint.

NEW QUESTION 32
Choose two common cross-cutting concerns in application architecture

Release documentation

Build automation

Security

Design pattern choices

Scalability

The others are either not cross-cutting or not related to architecture.

NEW QUESTION 33
The practice of decomposing a requirement into failing tests is called:

Behavior driven development

Acceptance test driven development

Scrum testing

Regression testing

NEW QUESTION 34
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

The product owner can cancel the sprint if the sprint goal becomes obsolete. This is a very rare event. It can happen when a company losing a client or the client decides to take a completely different turn.

NEW QUESTION 35
Which best describes the practice of expressing requirements as acceptance tests?

Regression testing

Acceptance test driven development

Objective Driven Development

Quality Oriented Requirements Development

This is pretty much the definition of ATDD.

NEW QUESTION 36
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

The working increment is the goal of the sprint and should be kept in mind. The self-managing aspect of the teams is also crucial to take in mind. Stable velocity and optimally used developers are not the scrum master’s concern.

NEW QUESTION 37
How is architecture decided in a scrum team during a project?

The developers emerge architecture as the system is created

The architect works in the early part of each sprint to define the architecture of that sprint

Upfront designs are presented to the developers prior to the first sprint

The architecture cares for itself as code is written and deployed

An architect on the team undertakes all architecture tasks

Architecture emerges as more is created. There are often guidelines and principles in place.

NEW QUESTION 38
What are three of the best ways to address non-functional requirements?

Handle them during a risk mitigation phase before development

Scrum is for functional, frontend development only

Include them in the Product Backlog

Before the release, they should be tested and validated in a hardening sprint

Specific expectations can be used as acceptance criteria to specific product backlog items

Important, recurring non-functional requirements can be added to the definition of done

There is no hardening sprint, there are only regular sprints. If it’s an ever recurring non-functional requirement, it can be added to the definition of done. If it’s not it can be added (as a criteria) in the product backlog (item).

NEW QUESTION 39
Which of the following best describe continuous integration?

A software development practice used by integration teams to create best practice branching and merging strategies

A software development practice that continuously integrates feedback from users in the software design

A software development practice where developers all work on the same computer to assure a common codebase

A software development practice where developers integrate and verify their work frequently, often multiple times a day, to detect integration errors as quickly as possible

NEW QUESTION 40
Upon what type of process control is scrum based?

Deductive

Hybrid

Empirical

Technical

If you are not sure, please review the Scrum theory section in the scrum guide

Loading …