PSD-I Exam Dumps Reliable Resources for Top Scores and Fast Results

1. Scrum PSD-I Professional Scrum Developer (PSD) QUESTION & ANSWERS Visit Now: https://www.scrumdumps.com

2. QUESTION: 1 A measure of how closely connected two routines or modules are, is called: Option A : Transparency. Option B : Coupling. Option C : Cohesion. Option D : Dependency. Correct Answer: B Explanation/Reference: Coupling is the degree of interdependence between software modules. Coupling is a measure of how closely connected two routines or modules are. It is a measure of the strength of the relationships between modules. In essence, coupling indicates the strength of relation between software modules. When this coupling is high, we may assume that the software modules are interdependent, i.e., they cannot function without the other. There are several dimensions of coupling: 1)Content coupling – In this type of coupling, Module can access or modify the content of any other module. In essence, when a component passes parameters to control the activity of some other component, there is a control coupling amongst the two components. 2)Common coupling – In this type of coupling. Multiple modules having access to a shared global data. 3)Stamp coupling – In this is a type of coupling, data structure is used to pass information from one component in the system to another. 4)Control coupling – In this is a type of coupling, one module can change the flow of execution of another module. 5)Data coupling -- in this type of coupling, two modules interact by exchanging or passing data as a parameter. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 2 A company has team members with different perspectives (customer, development, testing) collaborating to write acceptance tests in advance of implementing the corresponding functionality. This company is practicing: Option A : Acceptance Test Driven Development Option B : Behavior Driven Development Option C : Application Lifecycle Management Option D : Branching Correct Answer: A

3. Explanation/Reference: Acceptance Test Driven Development is a Test-First software development practice in which acceptance criterias for new functionality are created before the implementation actually begins. These acceptance tests are supported by examples and other necessary information. Acceptance Test Driven development is the practice of expressing requirements as acceptance tests. Acceptance Test Driven Development (ATDD) involves team members with different perspectives (customer, development, testing) collaborating to write acceptance criteria in advance of implementing the corresponding functionality. Test case creation is moved to the beginning of the cycle thus reducing defects and bug fixing effort as project progresses. Advanced practices of test-driven development can lead to Acceptance Test-driven development (ATDD) where the criteria specified by the customer are automated into acceptance tests. This then drive the traditional unit test-driven development (UTDD) process. ATDD Cycle: Discuss: In this stage of an ATDD cycle, the agile team along with the business stake holders gets into a discussion. The team develops a detailed understanding of the behavior of the system from the user point of view in the discussion. And on the basis of the understanding, the agile team creates acceptance tests that can be executed either automatically or programmatically. Distill: In this stage of an ATDD cycle, the agile tries to implements the acceptance tests in an automatic testing framework. In this stage the team ensures that the tests are not just remain specifications but can be actually executed in the project.

4. Develop: During this stage, the agile team follows a Test First Development TFD approach, i.e. they will first execute the tests, make sure what are making them fail and then proceed to write the code that will make the tests pass. Demo: In this stage of ATDD cycle, the agile team provides a demo to the business stake holders. In the demo, they can also indicate the tests they have run and the vulnerabilities they have been identified through the tests. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 3 Which of the following are advantages of Continuous Integration? (choose the best two answers) Option A : The feature-branch is generally kept in a buildable state. Option B : Know immediately how a change affected the product. Option C : Reduce effort and risk when integrating changes. Option D : Readability of code is improved.

5. Correct Answer: B,C Explanation/Reference: Detailed Explanation: Continuous Integration ensures that changes are integrated and tested frequently, providing immediate feedback on their impact. It reduces the effort and risks associated with late integrations. QUESTION: 4 What are two differences between unit tests and integration tests? Option A : A unit tests only runs on the developer's computer Option B : A unit test is automated Option C : An integration test runs overnight Option D : A unit tests isolates a specific system behavior Option E : An integration test may be composed of unit tests Correct Answer: A,D Explanation/Reference: Unit tests are testing the smallest units of code possible and integration tests are testing the components of the system together. Unit tests aims at isolated pieces of behavior and integration tests could be composed of unit tests to test components. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 5 In Test First Development, the developer writes the code before the test cases. Option A : True Option B : False Correct Answer: B Explanation/Reference: Test First Development is also known as Test Driven Development (TDD). Test Driven Development is a development style in which one writes the unit tests before writing the code. Test Driven Development is a Predictable, Incremental and Emergent Software development approach / technique which relies

6. on Automated Test. "Test-Driven Development" refers to a style of programming in which three activities are tightly interwoven: Writing Test, Coding and Refactoring. Example: Test Driven Development for a feature / aspect of a program can be concisely described by the following: ·Write a "Single" Unit Test describing an aspect of the program. ·Run the test, which should fail because the program lacks that feature. ·Write "just enough" code to make the test pass. ·"Refactor" the code until it conforms to the Simplicity Criteria. ·Repeat, "Accumulating" unit tests over time. QUESTION: 6 The benefits of Test First Development are: (Choose all that Apply) Option A : It promotes good code design. Option B : It improves quality and reduces bugs. Option C : It causes the developer to construct a test harness that can be automated. Option D : It speeds the overall development process. Correct Answer: A,B,C,D Explanation/Reference: Test First Development is also known as Test Driven Development (TDD). Test Driven Development is a development style in

7. which one writes the unit tests before writing the code. Test Driven Development is a Predictable, Incremental and Emergent Software development approach / technique which relies on Automated Test. "Test-Driven Development" refers to a style of programming in which three activities are tightly interwoven: Writing Test, Coding and Refactoring. Example: Test Driven Development for a feature / aspect of a program can be concisely described by the following: 1)Write a "Single" Unit Test describing an aspect of the program. 2)Run the test, which should fail because the program lacks that feature. 3)Write "just enough" code to make the test pass. 4)"Refactor" the code until it conforms to the Simplicity Criteria. 5)Repeat, "Accumulating" unit tests over time. A test written with Test-Driven Development represents a technical requirement that must be satisfied. Test-Driven Development is easier to implement in in applications designed to unit test. Benefits of Test-Driven Development: 1)It promotes good design and separation of concerns. 2)It improves quality and reduces bugs. 3)It leads to the construct of an automated test harness. 4)It speeds the overall development process. 5)it reduces cost of maintenance over time. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 7 Which of the following are the examples of a Technical Spike?

8. Option A : Evaluation of potential performance or load impact of a new user story. Option B : Evaluation of specific implementation technologies that can be applied to a solution. Option C : Team needs to develop a more confident understanding of a desired approach. Option D : An activity to learn about technical elements of a solution. Option E : Mockups and Wireframes. Correct Answer: A,B,C,D Explanation/Reference: A Spike is a story or task aimed at answering a question or gathering information, rather than producing a shippable product. In practice, the spikes which teams take on, are often proof-of-concept activities. By definition the work done for a spike is not focused on the finished product. A Spike may even be designed to be thrown away at the end. Technical Spikes are used to research various technical approaches in a domain. Example of Technical Spikes: 1)Evaluation of potential performance or load impact due to a new user story. 2)Evaluation of specific implementation technologies that can be applied to a solution. 3)Team needs to develop more confidence by understanding the implications of a desired approach before committing the functionality to a timebox. Functional Spikes are used whenever there is significant uncertainty as to how a user might interact with the system. Functional spikes are often best evaluated through some level of prototyping, whether it be user interface mockups, wireframes, page flows, or whatever techniques is best suited to get feedback from the customer or stakeholders. Note: In the Exam, the difference between Technical and Functional Spike might not be asked, however its good to know the difference. QUESTION: 8 Which of the following Statements about Regression testing is true? (Choose all that apply) Option A : The purpose of Regression Test is to catch bugs that may have been accidentally introduced into a new build or release candidate. Option B : One Regression testing is run successfully, originally scripted tests are discarded and not run again. Option C : The purpose of Regression test is to ensure that previously eradicated bugs continue to stay dead. Option D : Regression testing is testing existing software applications to make sure that a code change or addition hasn’t broken any existing functionality. Option E : Regression test suites tend to decrease with each found defect. Correct Answer: A,C,D

9. Explanation/Reference: Regression Test: Whenever developers change or modify their software, a small tweak can have unexpected consequences. Regression testing is testing existing software applications to make sure that a code change or addition hasn’t broken any existing functionality. The purpose of Regression Test is to catch bugs that may have been accidentally introduced into a new build or release candidate. Its purpose is to ensure that previously eradicated bugs continue to stay dead. During Regression Test, by re-running testing scenarios that were originally scripted when known problems were first fixed, one can make sure that any new changes to an application haven’t resulted in a regression or caused components that formerly worked to fail. As software is updated or changed, emergence of new faults and/or re-emergence of old faults is quite common. Sometimes re- emergence occurs because a fix gets lost through poor revision control practices (or simple human error in revision control). Therefore, it is considered good coding practice, to record a test that exposes the bug and re-run that test regularly after subsequent changes to the program. Thus regression test suites tend to grow with each found defect, test automation is frequently involved. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 9 A Scrum team developer is working on Product Backlog item and encounters a bug. The developers should: Option A : Work on it in the current Sprint as the Dev team owns quality. They should go ahead, create a task, and fix it within this sprint. Option B : Discuss it with Product Owner and ask for his suggestion to resolve it now or in the future. Correct Answer: B Explanation/Reference: Talking with the Product Owner is the right thing to do. There needs to be an understanding of what the impact of the bug is, especially if it already exists. Perhaps some of the new development will cause more people to use the functionality and stumble across the bug. The existence of workarounds and how burdensome or effective those workarounds are also has an impact. Maybe the existence of the bug would make the resulting Increment not viable for use. QUESTION: 10 While developing new functionality, you find a bug that has already been delivered to the customer. What do you do? Option A : Fix the bug Option B : Revise the tests to hide the bug from the tests reports Option C : Talk to the product owner Option D : Stub out the code that causes the bug

10. Correct Answer: C Explanation/Reference: The product owner knows what creates most value. Since this is already delivered, it is not part of the current sprint. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 11 The purpose of a sprint is to produce a done increment of product Option A : False Option B : True Correct Answer: B Explanation/Reference: The sprint is the heartbeat of scrum, during the sprint the increment is created. The increment must be usable and all the work that's part of the increment should adhere to the definition of done. QUESTION: 12 Who represents the desires of stakeholders using the Product Backlog? Option A : Scrum Master Option B : Scrum Team Option C : Developers Option D : Product Owner Correct Answer: D Explanation/Reference: A Product Owner may represent the desires of stakeholders using the Product Backlog.

11. QUESTION: 13 Code coverage represents the quality of a Unit Test. Option A : True Option B : False Correct Answer: B Explanation/Reference: Code Coverage is NOT a metric of code quality. Code Coverage shows the ratio between the tested and untested code. Code Coverage does not tell you anything about the quality of the tests being run. Some Advantages of Code Coverage are: 1)It offers a Quantitative Measurement. 2)It defines the degree to which the source code has been tested. Some shortcomings of Code Coverage as a measurement are: 1)Code Coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests. 2)Code Coverage does not necessarily provide functional coverage. 3)Code Coverage could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing coverage. Note: 1)There are always parts of code that are hard to test (e.g. I/O, multi-threaded and network code) and the benefits of testing them might not always worth the costs. 2)Writing unit tests for every new feature or change (preferably before writing production code, by practicing Test Driven Development) helps achieve Code Coverage automatically. Code coverage does not represent or talk about the quality of the code which is being exercised. It just addresses “How much” code not “Which” code. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 14 Based on "Sprint 7 Burn-Down Chart," would you do anything different in Sprint 8? (choose the best two answers) Option A : The Developers may forecast less overall work in Sprint 8. Option B : Stakeholders will encourage the Scrum Team to estimate better during the Sprint 8 Planning Meeting. Option C : There is nothing wrong. The Developers will present all Product Backlog items selected for Sprint 7 at the end of the Sprint.

12. Option D : The Developers carry over incomplete Sprint Backlog items from Sprint 7 to Sprint 8 and monitor the Sprint 8 burn-down chart. As soon as deviation from trends is detected, the Developers work with the Product Owner to negotiate remaining work. Option E : The Scrum Master adds additional Developers for Sprint 8. Option F : The Developers put incomplete Product Backlog items back into the Product Backlog for re-ordering. The Product Owner may ask the Developers to complete the unfinished Product Backlog items from Sprint 7 in Sprint 8. Correct Answer: A,F Explanation/Reference: Detailed Explanation: If a burn-down chart shows issues in Sprint 7, the Developers may adjust the forecast for Sprint 8 based on learning. Incomplete items should be returned to the Product Backlog for reordering, ensuring prioritization aligns with goals. QUESTION: 15 What are two responsibilities of testers in the scrum team? (choose two) Option A : Finding bugs Option B : Tracking quality metrics Option C : All developers are responsible for quality Option D : Verifying the work of the programmers Option E : Scrum has no tester role Correct Answer: A,C Explanation/Reference: Specific roles don't exist in scrum, developers are creating the value.

13. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 16 Which are two benefits of establishing naming conventions for code? Option A : To make the code more readable Option B : To make it easy to distinguish between different software products Option C : To communicate the identity of the developer that wrote the code Option D : To reduce friction in a shared codebase Option E : To ensure that orphan functions are not created Correct Answer: A,C Explanation/Reference: Naming conventions help to make the code more readable and it can reduce naming clashes. QUESTION: 17 Cyclomatic complexity is a metric for: Option A : Measuring branching structures and nesting levels in code Option B : Assessing if code is written in as few lines as possible Option C : Determining the number of unit tests required to ensure correctness Option D : Demonstrating code is well structured and cleanly implemented

14. Correct Answer: A Explanation/Reference: Cyclomatic complexity is a number expressing the number of different paths that can be taken throughout the code. Higher means complex code. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 18 Select three criteria for the definition of done Option A : Code review is done Option B : Acceptance tests pass Option C : Regression tests pass Option D : The product is released at the end of every sprint Option E : Code coverage 90% Correct Answer: A,B,C QUESTION: 19 In Scrum, there is an assigned Role (e.g. a software architect) who makes sure a consistent architecture is developed. Option A : False Option B : True Correct Answer: A Explanation/Reference: There is no assigned Role (e.g. a software architect) who makes sure a consistent architecture is developed. Developers in the Scrum Team make sure that the architecture evolves based on the needs. QUESTION: 20

15. What is Class Coupling? Option A : Class coupling reflects the number of methods calls in a code. Option B : Class Coupling is a measure which reflects the strength of each class & its impact in a code. Option C : Class Coupling is a measure which reflects the number of classes in a code. Option D : Class coupling is a measure of the dependencies a class has on other classes. Correct Answer: D Explanation/Reference: Class coupling: Class coupling is a measure of dependencies a class has on other classes. This dependency is measured through parameters, method calls and interface implementations. In Class Coupling, the higher this number, the more likely a change in one class will affect other classes. For class coupling, a low value is good, and a high value is bad. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 21 A Developer is unsure of a bug priority however based on his analysis its seems to be impacting multiple features. In such situations the developers should: Option A : Talk to the Product Owner to check if he should resolve the bug right away. Option B : Resolve the bug right away as he is responsible for the quality of the Product. Correct Answer: A Explanation/Reference: Unless a company has specific guidance on fixing bugs, they represent work to be done and should be ordered on the Product Backlog by the Product Owner. If a Developer is unsure of what to do with a bug, he / she should talk to the Product Owner. QUESTION: 22 When should a newly discovered huge bug of a previous sprint be fixed? Option A : Immediately. Option B : Don't fix it immediately, but change the test to not show it as a temporary fix. Option C : Don't fix it, but stub out the code that causes it. Option D : Depends on what the product owner wants. Correct Answer: D

16. Explanation/Reference: 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.

17. QUESTION: 23 Which of the following is required by Scrum? (choose the best answer) Option A : Sprint Retrospective Option B : Developers must stand up at the Daily Scrum. Option C : Sprint Burndown Chart. Option D : Release Planning. Option E : All of the above. Correct Answer: A Explanation/Reference: Detailed Explanation: Scrum mandates the Sprint Retrospective to inspect and adapt. Other practices, such as burndown charts and release planning, are tools and techniques but are not required by Scrum. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 24 Regression Testing is: Option A : Extensive Testing to make sure that every functionality works as expected. Option B : Testing the existing software to make sure that a change or addition (of code) hasn’t broken existing functionality. Option C : Testing which cannot be automated. Option D : All of the above. Correct Answer: B Explanation/Reference: Regression Test: Whenever developers change or modify their software, a small tweak can have unexpected consequences. Regression testing is testing existing software applications to make sure that a code change or addition hasn’t broken any existing functionality. The purpose of Regression Test is to catch bugs that may have been accidentally introduced into a new build or release candidate. Its purpose is to ensure that previously eradicated bugs continue to stay dead. During Regression Test, by re-running testing scenarios that were originally scripted when known problems were first fixed, one can make sure that any new changes to an application haven’t resulted in a regression or caused components that

18. formerly worked to fail. As software is updated or changed, emergence of new faults and/or re-emergence of old faults is quite common. Sometimes re-emergence occurs because a fix gets lost through poor revision control practices (or simple human error in revision control). Therefore, it is considered good coding practice, to record a test that exposes the bug and re-run that test regularly after subsequent changes to the program. Thus regression test suites tend to grow with each found defect, test automation is frequently involved. A Regression test can be automated. QUESTION: 25 Who writes write test cases and documentations in Scrum? Option A : Product Owner Option B : Documentation and Quality analysis Option C : Developers Option D : Scrum Master Correct Answer: C Explanation/Reference: Developers do write tests and documentations in Scrum. There are no special designated Testers or Documenters in a Scrum Team. Members of the Scrum teams are responsible for writing test and documentation. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 26 Functional testing can be implemented by a team of testers, independent of the developers. Option A : True Option B : False Correct Answer: A

19. Explanation/Reference: Functional Test is a form of testing that deals with how applications functions. Functional testing is traditionally implemented by a team of testers, independent of the developers. Functional testing is a type of black-box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (unlike white-box). Functional tests can be automated. QUESTION: 27 What is the practice of branching code in a version control system? Option A : Combining two or more branches of code into a single code base Option B : Creating a copy of existing code, isolated from the original code Option C : Releasing a specific codebase into a production environment Option D : Tagging or labeling a particular codebase as production ready Correct Answer: B Explanation/Reference: Branching means that you create a new version from the code that exists indepently from the original code. It is not isolated forever, it can be merged back later. QUESTION: 28 How much time will there be after a sprint before the next one starts? Option A : Enough to deploy the increment and update the product backlog based on the outcome of the sprint review Option B : Enough to clean up lingering definition of done points Option C : None, a new sprint starts immediately after the end of the previous one Option D : At most a week for a one-month sprint Correct Answer: C

20. Explanation/Reference: The scrum guide says: 'A new Sprint starts immediately after the conclusion of the previous Sprint.' Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 29 When is refinement of a Product Backlog item complete? (choose the best answer) Option A : When the Product Owner says it is ready. Option B : At the end of Sprint Planning. Option C : When the Scrum Team agrees it is precise enough. Option D : When the Product Backlog Refinement timebox expires. Correct Answer: C Explanation/Reference: Detailed Explanation: Refinement is complete when the Scrum Team agrees that the Product Backlog item is clear and precise enough to proceed with planning or implementation. QUESTION: 30 Which of the following statements are true about Spike? Option A : Spikes are used to discover risk and uncertainty in a project. Option B : While the intent of the story may be understood, it’s may not be clear on how the system would need to interact with the user to achieve the benefit implied, for which a spike might be used. Option C : The team may use a spike to analyze the implied behavior, so they can split the story into estimable pieces. Option D : Spike allows the team an understanding of the upcoming Product Backlog items complexity. Option E : Spikes may be used for basic research to familiarize the team with a new technology or domain. Option F : Teams may have to do some research or prototyping (spikes) to gain confidence in a technological approach that will allow them to commit the user story to some future timebox. Correct Answer: A,B,C,D

21. Explanation/Reference: Spikes are special type of stories that are used to discover risk and uncertainty in a project. A Spike is a great way to mitigate risks early and promotes fluid iterations later in the project. Spike allows the team an understanding of the upcoming Product Backlog items complexity. The team may not have knowledge of a new domain, and spikes may be used for basic research to familiarize the team with a new technology or domain. Product backlog items may be too big to be estimated appropriately, and the team may use a spike to analyze the implied behavior, so they can split the story into estimable pieces. Product backlog items may contain significant technical risk, and the team may have to do some research or prototyping (using spikes) to gain confidence in a technological approach that will allow them to commit the user story to some future timebox. Product backlog items may contain significant functional risk. While the intent of the story may be understood, it’s may not be clear on how the system would need to interact with the user to achieve the benefit implied, for which a spike might be used.

22. QUESTION: 31 Code coverage ensures that the most important or highest risk areas of the code are being exercised by tests. Option A : True Option B : False Correct Answer: B Explanation/Reference: Code Coverage is a measure which describes the degree to which the source code of the program has been tested. Code Coverage is a form of white box testing which shows the areas of the program exercised by a set of test cases. Measuring Code Coverage can help increase software quality by identifying untested parts of codes in a product / application. Code Coverage is NOT a metric of code quality. Code Coverage shows the ratio between the tested and untested code. Code Coverage does not tell you anything about the quality of the tests being run. Some Advantages of Code Coverage are: 1)It offers a Quantitative Measurement. 2)It defines the degree to which the source code has been tested. Some shortcomings of Code Coverage as a measurement are: 1)Code Coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests. 2)Code Coverage does not necessarily provide functional coverage. 3)Code Coverage could create incentives to write tests that simply increase code coverage, rather than tests that find bugs without increasing coverage. Note: 1)There are always parts of code that are hard to test (e.g. I/O, multi-threaded and network code) and the benefits of testing them might not always worth the costs. 2)Writing unit tests for every new feature or change (preferably before writing production code, by practicing Test Driven Development) helps achieve Code Coverage automatically. Code coverage does not ensure that the most important or highest risk areas of the code are being exercised by tests. It just addresses “How much” code not “Which” code. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions QUESTION: 32

23. There is an assigned Role (such as Quality Analyst) who develops and executes the Test Cases. Option A : False Option B : True Correct Answer: A Explanation/Reference: There is no assigned Role (e.g. QA) who conducts the Test Cases. Developers are responsible for writing and executing the Test Cases. Download from Here: https://www.scrumdumps.com/PSD-I-exam-questions