PSD I - Practice Assessment 3
Quiz-summary
0 of 80 questions completed
Questions:
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
Information
This is the third PSD I practice assessment with the following characteristics:
- Passing score: 85%
- Time limit: 60 minutes
- Number of questions: 80
- Format: Multiple Choice, Multiple Answer and True/False
- Difficulty: Intermediate
- Language: English only
You can navigate throughout the questions whenever you want. The unanswered questions are marked in the navigation bar. You can click on the “review question” button to flag it for later review.
You have already completed the quiz before. Hence you can not start it again.
Quiz is loading...
You must sign in or sign up to start the quiz.
You have to finish following quiz, to start this quiz:
Results
0 of 80 questions answered correctly
Your time:
Time has elapsed
You have reached 0 of 0 points, (0)
| Average score | |
| Your score |
Categories
- Not categorized 0%
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- Answered
- Review
- Question 1 of 80
1. Question
How should the Developers implement the software architecture in a Scrum Team?
Pick 1CorrectDevelopers should have some guidelines for deciding and handling architectural and infrastructural concerns. They should handle these concerns as a part of other Product Backlog Items during each Sprint. Doing a lot upfront in order to make a comprehensive architecture at the beginning of the project is a type of waste. Handling architecture should be done incrementally based on the learnings that emerge during the Sprints. It is obvious that it uses more effort at the early Sprints and decreases during the middle and last Sprints. On the other hand, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers. Therefore, adding architectural and infrastructural items to the Product Backlog in order to do in the early Sprints is a valid policy.
IncorrectDevelopers should have some guidelines for deciding and handling architectural and infrastructural concerns. They should handle these concerns as a part of other Product Backlog Items during each Sprint. Doing a lot upfront in order to make a comprehensive architecture at the beginning of the project is a type of waste. Handling architecture should be done incrementally based on the learnings that emerge during the Sprints. It is obvious that it uses more effort at the early Sprints and decreases during the middle and last Sprints. On the other hand, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers. Therefore, adding architectural and infrastructural items to the Product Backlog in order to do in the early Sprints is a valid policy.
- Question 2 of 80
2. Question
Which of the following options are true?
Pick 2CorrectDevelopers should have some guidelines for deciding and handling architectural and infrastructural concerns. They should handle these concerns as a part of other Product Backlog Items during each Sprint. Doing a lot upfront in order to make a comprehensive architecture at the beginning of the project is a type of waste. Handling architecture should be done incrementally based on the learnings that emerge during the Sprints. It is obvious that it uses more effort at the early Sprints and decreases during the middle and last Sprints. On the other hand, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers. Therefore, adding architectural and infrastructural items to the Product Backlog in order to do in the early Sprints is a valid policy.
IncorrectDevelopers should have some guidelines for deciding and handling architectural and infrastructural concerns. They should handle these concerns as a part of other Product Backlog Items during each Sprint. Doing a lot upfront in order to make a comprehensive architecture at the beginning of the project is a type of waste. Handling architecture should be done incrementally based on the learnings that emerge during the Sprints. It is obvious that it uses more effort at the early Sprints and decreases during the middle and last Sprints. On the other hand, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers. Therefore, adding architectural and infrastructural items to the Product Backlog in order to do in the early Sprints is a valid policy.
- Question 3 of 80
3. Question
What is the next step in Test Driven Development after test failure?
Pick 1CorrectTDD or Test-Driven Development or Test-First Development is a development process that has three steps:
Step 1 – Write a test and run it to fail
Step 2 – Write just enough code to pass the test
Step 3 – Refactor the written code
Another metaphor for TDD is: Red – Green – RefactorIncorrectTDD or Test-Driven Development or Test-First Development is a development process that has three steps:
Step 1 – Write a test and run it to fail
Step 2 – Write just enough code to pass the test
Step 3 – Refactor the written code
Another metaphor for TDD is: Red – Green – Refactor - Question 4 of 80
4. Question
What is Test-First Development?
Pick 1CorrectTDD or Test-Driven Development or Test-First Development is a development process that has three steps:
Step 1 – Write a test and run it to fail
Step 2 – Write just enough code to pass the test
Step 3 – Refactor the written code
Another metaphor for TDD is: Red – Green – RefactorIncorrectTDD or Test-Driven Development or Test-First Development is a development process that has three steps:
Step 1 – Write a test and run it to fail
Step 2 – Write just enough code to pass the test
Step 3 – Refactor the written code
Another metaphor for TDD is: Red – Green – Refactor - Question 5 of 80
5. Question
Who should fix the failed build in Continuous Integration?
Pick 1CorrectWhen a Continuous Integration build fails with a check in, the person who is in the context and knows what is happening is the best one to fix it. Hence, the person who broke the build is the ideal source to fix the failure.
IncorrectWhen a Continuous Integration build fails with a check in, the person who is in the context and knows what is happening is the best one to fix it. Hence, the person who broke the build is the ideal source to fix the failure.
- Question 6 of 80
6. Question
Which of the following could help create a better understanding of customer requirements?
Pick 2CorrectIn order to prevent creating the wrong product or having reworks, it is valuable using some approach to make a better understanding of customer requirements. These approaches are Sketch, Wireframe, Mockup, and Prototype. In addition, all of them occur before implementing any code.
IncorrectIn order to prevent creating the wrong product or having reworks, it is valuable using some approach to make a better understanding of customer requirements. These approaches are Sketch, Wireframe, Mockup, and Prototype. In addition, all of them occur before implementing any code.
- Question 7 of 80
7. Question
What is Behavior-Driven Development (BDD)?
Pick 1CorrectBehavior-Driven Development (BDD) is a software development process, which focuses on user and system interactions. Writing customer requirements as acceptance tests called ATDD.
IncorrectBehavior-Driven Development (BDD) is a software development process, which focuses on user and system interactions. Writing customer requirements as acceptance tests called ATDD.
- Question 8 of 80
8. Question
Which of the following is internally being used when you are developing via a BDD approach?
Pick all that applyCorrectBDD combines practices from Test-Driven Development (TDD) and Domain-Driven Design (DDD) along with the collaboration of development team and domain experts. BDD uses a simple Domain-Specific-Language (DSL) using natural language structure based on the ubiquitous language that can express the behaviors and the expected outcomes. For more information, BDD does not have any formal requirements for exactly how user stories must be written down but Gherkin is a wide-used format to write down the requirements in the BDD approach. BDD is also referred to as Specification by Example and is a synthesis and refinement based on TDD and Acceptance Test-Driven Development (ATDD) practices.
IncorrectBDD combines practices from Test-Driven Development (TDD) and Domain-Driven Design (DDD) along with the collaboration of development team and domain experts. BDD uses a simple Domain-Specific-Language (DSL) using natural language structure based on the ubiquitous language that can express the behaviors and the expected outcomes. For more information, BDD does not have any formal requirements for exactly how user stories must be written down but Gherkin is a wide-used format to write down the requirements in the BDD approach. BDD is also referred to as Specification by Example and is a synthesis and refinement based on TDD and Acceptance Test-Driven Development (ATDD) practices.
- Question 9 of 80
9. Question
Which stage is the best time for running the performance test?
Pick 1CorrectPerformance testing needs many resources and is time-consuming. So, it should ideally be carried out just before deploying to production and in an environment that, as closely as possible, replicates the production environment in which the system will ultimately run.
IncorrectPerformance testing needs many resources and is time-consuming. So, it should ideally be carried out just before deploying to production and in an environment that, as closely as possible, replicates the production environment in which the system will ultimately run.
- Question 10 of 80
10. Question
What is Dynamic Analysis?
Pick 1CorrectDynamic Analysis is executed while a program is in operation. A dynamic test will monitor system memory, functional behavior, response time, and overall performance of the system. On the other hand, Static Analysis is performed in a non-runtime environment. Typically, a static analysis tool will inspect program code for all possible run-time behaviors and seek out coding flaws, back doors, and potentially malicious code.
IncorrectDynamic Analysis is executed while a program is in operation. A dynamic test will monitor system memory, functional behavior, response time, and overall performance of the system. On the other hand, Static Analysis is performed in a non-runtime environment. Typically, a static analysis tool will inspect program code for all possible run-time behaviors and seek out coding flaws, back doors, and potentially malicious code.
- Question 11 of 80
11. Question
Having 100% Code Coverage is the best situation to ensure that the quality of code is perfect.
Pick 1CorrectCode coverage is a measure used to describe the degree to which the source code of a program is executed or exercised when a particular test suite runs. Note that 100% coverage will not assert that the quality is perfect, but a low number will tell you that you have insufficient testing and the source code is error‐prone.
IncorrectCode coverage is a measure used to describe the degree to which the source code of a program is executed or exercised when a particular test suite runs. Note that 100% coverage will not assert that the quality is perfect, but a low number will tell you that you have insufficient testing and the source code is error‐prone.
- Question 12 of 80
12. Question
What does a low Code Coverage mean?
Pick 1CorrectCode coverage is a measure used to describe the degree to which the source code of a program is executed or exercised when a particular test suite runs. Note that 100% coverage will not assert that the quality is perfect, but a low number will tell you that you have insufficient testing and the source code is error‐prone. In addition, for code coverage calculation all unit tests should be passed.
IncorrectCode coverage is a measure used to describe the degree to which the source code of a program is executed or exercised when a particular test suite runs. Note that 100% coverage will not assert that the quality is perfect, but a low number will tell you that you have insufficient testing and the source code is error‐prone. In addition, for code coverage calculation all unit tests should be passed.
- Question 13 of 80
13. Question
What of the following are the attributes of a good bug report?
Pick all that applyCorrectThere are several attributes that a good bug report could have such as evidence as screenshots or other attachments, expected results and observed results, version and build of the software under test, having simple and repeatable reproduction steps, having summary and detail description, the date and time that the defect occurred or reported, reported by, impacted related requirement, the severity of the defect, etc.
IncorrectThere are several attributes that a good bug report could have such as evidence as screenshots or other attachments, expected results and observed results, version and build of the software under test, having simple and repeatable reproduction steps, having summary and detail description, the date and time that the defect occurred or reported, reported by, impacted related requirement, the severity of the defect, etc.
- Question 14 of 80
14. Question
A Developer who writes the code in Pair Programming is usually called “driver” and the other who is reviewing the code is called “navigator.”
Pick 1CorrectPair programming is a technique in Agile Software Development where two engineers share a single workstation. In this technique, one engineer is the driver, who has control of the mouse and keyboard to write the code, while the other serves as the navigator, reviewing the code that the other is writing while providing tactical and analytical feedback. This pair will trade‐off on these roles at regular intervals, giving each other equal chance to both execute on the work or direct it.
IncorrectPair programming is a technique in Agile Software Development where two engineers share a single workstation. In this technique, one engineer is the driver, who has control of the mouse and keyboard to write the code, while the other serves as the navigator, reviewing the code that the other is writing while providing tactical and analytical feedback. This pair will trade‐off on these roles at regular intervals, giving each other equal chance to both execute on the work or direct it.
- Question 15 of 80
15. Question
Which of the following is a code quality metric?
Pick all that applyCorrectThere are many code metrics. Some of them measure code quality and others just prepare information about code situations.
Metrics that measure code quality: Class Coupling, Depth of Inheritance, Efferent Coupling, Afferent Coupling, Instability Index, Cyclomatic Complexity, Maintainability Index.
Metrics that do not measure code quality: Code Coverage, Lines of CodeIncorrectThere are many code metrics. Some of them measure code quality and others just prepare information about code situations.
Metrics that measure code quality: Class Coupling, Depth of Inheritance, Efferent Coupling, Afferent Coupling, Instability Index, Cyclomatic Complexity, Maintainability Index.
Metrics that do not measure code quality: Code Coverage, Lines of Code - Question 16 of 80
16. Question
Which of the following is a benefit of TDD?
Pick all that applyCorrectTDD is one of the most important concepts in Agile with the following benefits:
• Because you are writing small tests at a time, it forces your code to be more modular (otherwise they’d be hard to test against). TDD helps you learn, understand, and internalize the key principles of good modular design.
• Documents your code better than documentation (it doesn’t go out of date since you’re running it all the time).
• Makes code easier to maintain and refactor. TDD helps to provide clarity during the implementation process and provides a safety net when you want to refactor the code you have just written.
But its purpose is not preparing control for managers.IncorrectTDD is one of the most important concepts in Agile with the following benefits:
• Because you are writing small tests at a time, it forces your code to be more modular (otherwise they’d be hard to test against). TDD helps you learn, understand, and internalize the key principles of good modular design.
• Documents your code better than documentation (it doesn’t go out of date since you’re running it all the time).
• Makes code easier to maintain and refactor. TDD helps to provide clarity during the implementation process and provides a safety net when you want to refactor the code you have just written.
But its purpose is not preparing control for managers. - Question 17 of 80
17. Question
Which types of tests CANNOT be automated?
Pick all that applyCorrectThe following tests can be automated: Unit Test, Integration Test, Component Test, System Test, Functional Acceptance Test, User Acceptance Test and Non-functional Acceptance Test (Capacity, Security, Performance, etc.), etc.
However, the following tests cannot be automated: Exploratory Test, Usability Test, Showcase Test.IncorrectThe following tests can be automated: Unit Test, Integration Test, Component Test, System Test, Functional Acceptance Test, User Acceptance Test and Non-functional Acceptance Test (Capacity, Security, Performance, etc.), etc.
However, the following tests cannot be automated: Exploratory Test, Usability Test, Showcase Test. - Question 18 of 80
18. Question
In software development, what does DRY stand for?
Pick 1CorrectDon’t repeat yourself (DRY) is a principle of software development aimed at reducing repetition and duplication of software codes.
IncorrectDon’t repeat yourself (DRY) is a principle of software development aimed at reducing repetition and duplication of software codes.
- Question 19 of 80
19. Question
Which pair is not true?
Pick 2CorrectMany code metrics have synonym as following:
Lines of Code (LOC): Source Lines of Code (SLOC)
Class Coupling: Coupling Between Objects (CBO)
Depth of Inheritance: Depth of Inheritance Tree (DIT)
Efferent Coupling (Ce): Outgoing Dependencies
Afferent Coupling (Ca): Incoming Dependencies
Cyclomatic Complexity: Program ComplexityIncorrectMany code metrics have synonym as following:
Lines of Code (LOC): Source Lines of Code (SLOC)
Class Coupling: Coupling Between Objects (CBO)
Depth of Inheritance: Depth of Inheritance Tree (DIT)
Efferent Coupling (Ce): Outgoing Dependencies
Afferent Coupling (Ca): Incoming Dependencies
Cyclomatic Complexity: Program Complexity - Question 20 of 80
20. Question
Which is NOT software technical debt?
Pick 1CorrectTechnical debt comes from making bad technical decisions and is the eventual consequence of poor technical choices. The team should pay back continuously. Technical debt types are as following:
• Implementation debt: bad coding
• Architecture debt: Bad architectural principles, design rule violations, lacking design patterns
• Test debt: Missing test cases, lack of test coverage, lack of test automation
• Documentation debt: Missing documentation, poorly updated documentation, low traceability between documentation and implementationIncorrectTechnical debt comes from making bad technical decisions and is the eventual consequence of poor technical choices. The team should pay back continuously. Technical debt types are as following:
• Implementation debt: bad coding
• Architecture debt: Bad architectural principles, design rule violations, lacking design patterns
• Test debt: Missing test cases, lack of test coverage, lack of test automation
• Documentation debt: Missing documentation, poorly updated documentation, low traceability between documentation and implementation - Question 21 of 80
21. Question
Which of the following is NOT true about technical debt?
Pick 1CorrectTechnical debt comes from making bad technical decisions and is the eventual consequence of poor technical choices. The Team should pay back it continuously. If the Team does not pay back, it will decrease the development speed over time. Although its measurement is hard its growth would lead to wrong assumptions about Increments delivery and even might prevent creating a releasable product.
On the other hand, each Sprint’s purpose is to create at least one releasable business functionality. So stopping it to pay the technical debt back is not a proper policy.IncorrectTechnical debt comes from making bad technical decisions and is the eventual consequence of poor technical choices. The Team should pay back it continuously. If the Team does not pay back, it will decrease the development speed over time. Although its measurement is hard its growth would lead to wrong assumptions about Increments delivery and even might prevent creating a releasable product.
On the other hand, each Sprint’s purpose is to create at least one releasable business functionality. So stopping it to pay the technical debt back is not a proper policy. - Question 22 of 80
22. Question
What does merge mean in source control?
Pick 1CorrectMerging is a fundamental operation to combine and reconcile multiple changes, which results in a single collection of files containing both sets of changes.
IncorrectMerging is a fundamental operation to combine and reconcile multiple changes, which results in a single collection of files containing both sets of changes.
- Question 23 of 80
23. Question
Which of the following are benefits of having naming conventions for code?
Pick 2CorrectNaming Convention has the following benefits:
• To reduce the effort needed to read and understand source code;
• To enable code reviews to focus on more important issues than arguing over syntax and naming standards;
• To enable code quality review tools to focus their reporting mainly on significant issues other than syntax and style preferences;
• To help formalize expectations and promote consistency within a development team;
• To enable the use of automated refactoring or search and replace tools with minimal potential for error;
• To enhance clarity in cases of potential ambiguity;
• To enhance the aesthetic and professional appearance of work product (for example, by disallowing overly long names, comical or “cute” names, or abbreviations);
• To help avoid “naming collisions or frictions” that might occur when the work product of different organizations is combined;
• To provide meaningful data to be used in project handovers which require submission of program source code and all relevant documentation;
• To provide a better understanding in case of code reuse after a long interval of time.
In addition, an orphan, dead, or unreachable code is a code that will never be executed. It shows itself as variables that are declared but never used, functions that are never called, or code that is skipped because of a condition branch.IncorrectNaming Convention has the following benefits:
• To reduce the effort needed to read and understand source code;
• To enable code reviews to focus on more important issues than arguing over syntax and naming standards;
• To enable code quality review tools to focus their reporting mainly on significant issues other than syntax and style preferences;
• To help formalize expectations and promote consistency within a development team;
• To enable the use of automated refactoring or search and replace tools with minimal potential for error;
• To enhance clarity in cases of potential ambiguity;
• To enhance the aesthetic and professional appearance of work product (for example, by disallowing overly long names, comical or “cute” names, or abbreviations);
• To help avoid “naming collisions or frictions” that might occur when the work product of different organizations is combined;
• To provide meaningful data to be used in project handovers which require submission of program source code and all relevant documentation;
• To provide a better understanding in case of code reuse after a long interval of time.
In addition, an orphan, dead, or unreachable code is a code that will never be executed. It shows itself as variables that are declared but never used, functions that are never called, or code that is skipped because of a condition branch. - Question 24 of 80
24. Question
A high count for Lines of Code metric might be a warning that code will be hard to maintain.
Pick 1CorrectLines of Code is the number of lines in the text of the program’s source code with the following characteristics:
• A high count might indicate that a type or method is doing too much work
• A high count might also be a warning that code will be hard to maintain
• It isn’t a code quality metricIncorrectLines of Code is the number of lines in the text of the program’s source code with the following characteristics:
• A high count might indicate that a type or method is doing too much work
• A high count might also be a warning that code will be hard to maintain
• It isn’t a code quality metric - Question 25 of 80
25. Question
Through Afferent Coupling, classes with high afferent will affect other classes when changes are made.
Pick 1CorrectAfferent coupling measures how many classes depend on a given class and has the following characteristics:
• Classes with high afferent will affect other classes when changes are made.
• A large afferent coupling can indicate that you should reconsider the responsibilities of the class, because It will be very difficult to make changes to this class later when so many other classes are dependent on it
• It is a code quality metricIncorrectAfferent coupling measures how many classes depend on a given class and has the following characteristics:
• Classes with high afferent will affect other classes when changes are made.
• A large afferent coupling can indicate that you should reconsider the responsibilities of the class, because It will be very difficult to make changes to this class later when so many other classes are dependent on it
• It is a code quality metric - Question 26 of 80
26. Question
A large Efferent Coupling can indicate that a class is unfocused and may also indicate that it is unstable since it depends on the stability of all the types to which it is coupled.
Pick 1CorrectEfferent coupling measures the number of classes on which a given class depends and has the following characteristics:
• Classes with high efferent coupling will receive the effects of changes or defects in other classes
• A large efferent coupling can indicate that a class is unfocused and may also indicate that it is unstable since it depends on the stability of all the types to which it is coupled
• It is a code quality metricIncorrectEfferent coupling measures the number of classes on which a given class depends and has the following characteristics:
• Classes with high efferent coupling will receive the effects of changes or defects in other classes
• A large efferent coupling can indicate that a class is unfocused and may also indicate that it is unstable since it depends on the stability of all the types to which it is coupled
• It is a code quality metric - Question 27 of 80
27. Question
“A class should have one and only one reason to change, meaning that a class should have only one job.” Which SOLID principle does the before-mentioned sentence represent?
Pick 1CorrectThe Single Responsibility principle says to separate the code that different actors depend on. Also, gather together the things that change for the same reasons. Separate those things that change for different reasons. To sum up, a class should have one and only one reason to change, meaning that a class should have only one job.
IncorrectThe Single Responsibility principle says to separate the code that different actors depend on. Also, gather together the things that change for the same reasons. Separate those things that change for different reasons. To sum up, a class should have one and only one reason to change, meaning that a class should have only one job.
- Question 28 of 80
28. Question
The Dependency Inversion principle implies that entities must depend on abstractions, not on concretions.
Pick 1CorrectDependency Inversion principle: Entities must depend on abstractions, not on concretions. It states that the high-level module must not depend on the low-level module, but they should depend on abstractions.
IncorrectDependency Inversion principle: Entities must depend on abstractions, not on concretions. It states that the high-level module must not depend on the low-level module, but they should depend on abstractions.
- Question 29 of 80
29. Question
The principle of least privilege (PoLP) promotes maximum user profile privileges on computers, based on users’ job necessities.
Pick 1CorrectThe principle of least privilege (PoLP; also known as the principle of least authority) is an important concept in computer security, promoting minimal user profile privileges on computers, based on users’ job necessities. It can also be applied to processes on the computer; each system component or process should have the least authority necessary to perform its duties. This helps reduce the “attack surface” of the computer by eliminating unnecessary privileges that can result in network exploits and computer compromises.
IncorrectThe principle of least privilege (PoLP; also known as the principle of least authority) is an important concept in computer security, promoting minimal user profile privileges on computers, based on users’ job necessities. It can also be applied to processes on the computer; each system component or process should have the least authority necessary to perform its duties. This helps reduce the “attack surface” of the computer by eliminating unnecessary privileges that can result in network exploits and computer compromises.
- Question 30 of 80
30. Question
Refactoring is restructuring existing code with altering its internal and external behavior.
Pick 1CorrectRefactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. Advantages include improved code readability and maintainability and reduced complexity.
IncorrectRefactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. Advantages include improved code readability and maintainability and reduced complexity.
- Question 31 of 80
31. Question
Why should the Developers prepare documents?
Pick 2CorrectIf a Scrum Team decides to have the documentation in its development process, they can add it to the Definition of Done. Then they should adhere to it for each developed feature. Also, having enough documentation can help the Team to have easier software maintenance.
IncorrectIf a Scrum Team decides to have the documentation in its development process, they can add it to the Definition of Done. Then they should adhere to it for each developed feature. Also, having enough documentation can help the Team to have easier software maintenance.
- Question 32 of 80
32. Question
Instability Index is a code quality metric.
Pick 1CorrectThe instability index measures efferent coupling in relation to total coupling and is a code quality metric.
IncorrectThe instability index measures efferent coupling in relation to total coupling and is a code quality metric.
- Question 33 of 80
33. Question
In software development, KISS refers to:
Pick 3CorrectThe KISS principle states that most systems work best if they are kept simple rather than made complicated. It is explained as “Keep it simple, silly”, “keep it short and simple”, “keep it simple and straightforward”, “keep it small and simple” and “keep it stupid simple”.
In addition, Simplicity should be a key goal in design.IncorrectThe KISS principle states that most systems work best if they are kept simple rather than made complicated. It is explained as “Keep it simple, silly”, “keep it short and simple”, “keep it simple and straightforward”, “keep it small and simple” and “keep it stupid simple”.
In addition, Simplicity should be a key goal in design. - Question 34 of 80
34. Question
What is an architecture spike?
Pick 1CorrectAn architecture spike is an experiment that allows Developers to learn just enough about the technical and unknown elements of an architecture solution. Often, a spike is a quick and dirty implementation, a prototype that will be thrown away. There are many synonyms for spike such as Knowledge Acquisition, Research, Proof‐of‐Concept.
IncorrectAn architecture spike is an experiment that allows Developers to learn just enough about the technical and unknown elements of an architecture solution. Often, a spike is a quick and dirty implementation, a prototype that will be thrown away. There are many synonyms for spike such as Knowledge Acquisition, Research, Proof‐of‐Concept.
- Question 35 of 80
35. Question
Can a feature with small bugs be considered as a done deliverable?
Pick 1CorrectNo. Having a feature with small bugs means it is not releasable so the Product Owner cannot accept it as a deliverable.
IncorrectNo. Having a feature with small bugs means it is not releasable so the Product Owner cannot accept it as a deliverable.
- Question 36 of 80
36. Question
Which of the following is true about the required effort amount for preparing the development environment, tools, and infrastructures in a project lifecycle?
Pick 1CorrectThe development environment, tools, and infrastructures required for the development should be prepared and improved gradually during the project. It is obvious that it uses more effort at early Sprints and decreases during the middle and last Sprints. In addition, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers.
IncorrectThe development environment, tools, and infrastructures required for the development should be prepared and improved gradually during the project. It is obvious that it uses more effort at early Sprints and decreases during the middle and last Sprints. In addition, during each Sprint, the Team should try to produce at least one potential releasable business functionality in order to get feedback from customers.
- Question 37 of 80
37. Question
How are non‐functional requirements managed in Scrum?
Pick 2CorrectThe non-functional requirements or cross-cutting concerns are the features of the design that may apply across all layers and are related to the quality requirements. There are many non-functional requirements as following: Security, Reliability, Performance, Availability, Globalization, Scalability, Maintainability, Robustness, etc. They can be managed by adding them to the Definition of Done, the Product Backlog, or acceptance criteria.
IncorrectThe non-functional requirements or cross-cutting concerns are the features of the design that may apply across all layers and are related to the quality requirements. There are many non-functional requirements as following: Security, Reliability, Performance, Availability, Globalization, Scalability, Maintainability, Robustness, etc. They can be managed by adding them to the Definition of Done, the Product Backlog, or acceptance criteria.
- Question 38 of 80
38. Question
What does YAGNI stand for?
Pick 2CorrectYAGNI means always implement things when you actually need them, never when you just foresee that you need them. It is a principle behind the XP practice of “do the simplest thing that could possibly work.”
It stands for “You aren’t going to need it“, “You ain’t gonna need it.”IncorrectYAGNI means always implement things when you actually need them, never when you just foresee that you need them. It is a principle behind the XP practice of “do the simplest thing that could possibly work.”
It stands for “You aren’t going to need it“, “You ain’t gonna need it.” - Question 39 of 80
39. Question
A Sandbox is a type of test in production or live environment.
Pick 1CorrectA sandbox is a type of software testing environment that enables the isolated execution of software or programs from the production or live environment for independent evaluation, monitoring or testing. In an implementation, a sandbox also may be known as a test server, development server, or working directory.
IncorrectA sandbox is a type of software testing environment that enables the isolated execution of software or programs from the production or live environment for independent evaluation, monitoring or testing. In an implementation, a sandbox also may be known as a test server, development server, or working directory.
- Question 40 of 80
40. Question
Which of the following is true about Smoke testing?
Pick all that applyCorrectSmoke testing, or “Build Verification Testing”, is a type of software testing that includes a non-exhaustive set of tests that aim at ensuring that the most crucial and important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing.
Smoke testing is the preliminary check of the software after a build and before a release. This type of testing finds basic and critical issues in an application before critical testing is implemented.
The term smoke testing originates from a similarly basic type of hardware testing in which a device passes the test if it does not catch fire the first time it turns on.IncorrectSmoke testing, or “Build Verification Testing”, is a type of software testing that includes a non-exhaustive set of tests that aim at ensuring that the most crucial and important functions work. The result of this testing is used to decide if a build is stable enough to proceed with further testing.
Smoke testing is the preliminary check of the software after a build and before a release. This type of testing finds basic and critical issues in an application before critical testing is implemented.
The term smoke testing originates from a similarly basic type of hardware testing in which a device passes the test if it does not catch fire the first time it turns on. - Question 41 of 80
41. Question
Which of the following is true about White-box testing?
Pick all that applyCorrectWhite-box testing is a software testing method in which the internal structure/design/implementation of the item being tested is known to the tester. The tester chooses inputs to exercise paths through the code and determines the appropriate outputs. Also, it implies testing based on an analysis of the internal structure of the component or system. This method is named so because the software program, in the eyes of the tester, is like a white/transparent box; inside which one clearly sees.
IncorrectWhite-box testing is a software testing method in which the internal structure/design/implementation of the item being tested is known to the tester. The tester chooses inputs to exercise paths through the code and determines the appropriate outputs. Also, it implies testing based on an analysis of the internal structure of the component or system. This method is named so because the software program, in the eyes of the tester, is like a white/transparent box; inside which one clearly sees.
- Question 42 of 80
42. Question
Which of the following is true about the Definition of Done and Acceptance Criteria?
Pick 1CorrectDefinition of Done is a concept with a set of requirements that should be applied to a feature in order to be called complete. On the other hand, Acceptance Criteria or Conditions of Satisfaction contains a list of scenarios that should be passed to ensure that the feature is working as expected. The difference is that there is one Definition of Done for the product and is common for all features while there is a separate and specific Acceptance Criteria for each feature. Passing Acceptance Criteria would be an item of the Definition of Done.
IncorrectDefinition of Done is a concept with a set of requirements that should be applied to a feature in order to be called complete. On the other hand, Acceptance Criteria or Conditions of Satisfaction contains a list of scenarios that should be passed to ensure that the feature is working as expected. The difference is that there is one Definition of Done for the product and is common for all features while there is a separate and specific Acceptance Criteria for each feature. Passing Acceptance Criteria would be an item of the Definition of Done.
- Question 43 of 80
43. Question
Which of the following is the definition of the Maintainability Index metric?
Pick 1CorrectMaintainability Index measures how maintainable (easy to support and change) a source code is. It is an index value between 0 and 100. It is a code quality metric.
Other definitions imply other metrics as follows:
Cyclomatic Complexity: Measures the number of linearly independent paths through a program’s source code
Instability Index: Measures efferent coupling in relation to total coupling
Afferent Coupling: Measures how many classes depend on a given classIncorrectMaintainability Index measures how maintainable (easy to support and change) a source code is. It is an index value between 0 and 100. It is a code quality metric.
Other definitions imply other metrics as follows:
Cyclomatic Complexity: Measures the number of linearly independent paths through a program’s source code
Instability Index: Measures efferent coupling in relation to total coupling
Afferent Coupling: Measures how many classes depend on a given class - Question 44 of 80
44. Question
Which of the following is NOT a main category of Design Patterns?
Pick 1CorrectA software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is generally divided into three main categories: creational design patterns, structural design patterns, and behavioral design patterns.
IncorrectA software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is generally divided into three main categories: creational design patterns, structural design patterns, and behavioral design patterns.
- Question 45 of 80
45. Question
Who has the final say about the Product Backlog items order?
Pick 1CorrectThe Product Owner’s main accountability is maximizing the value of the product resulting from the work of the Developers. Furthermore, the Product Owner is the sole person accountable for managing the Product Backlog. Therefore, (s)he has the final say and decides about Product Backlog Items order.
IncorrectThe Product Owner’s main accountability is maximizing the value of the product resulting from the work of the Developers. Furthermore, the Product Owner is the sole person accountable for managing the Product Backlog. Therefore, (s)he has the final say and decides about Product Backlog Items order.
- Question 46 of 80
46. Question
Who is responsible to select enough Product Backlog Items for the Sprint?
Pick 1CorrectThe Product Owner or Scrum Master should not determine or force the Developers to select enough items from the Product Backlog because this manner decreases their commitment, as they may not believe they can finish all the selected items until the end of the Sprint. It is up to the Developers to select enough items for the Sprint without any worry about blame or outside force, as they know the best how to do the work. Therefore, the authority of selecting enough amount of PBIs for the Sprint belongs to the Developers.
IncorrectThe Product Owner or Scrum Master should not determine or force the Developers to select enough items from the Product Backlog because this manner decreases their commitment, as they may not believe they can finish all the selected items until the end of the Sprint. It is up to the Developers to select enough items for the Sprint without any worry about blame or outside force, as they know the best how to do the work. Therefore, the authority of selecting enough amount of PBIs for the Sprint belongs to the Developers.
- Question 47 of 80
47. Question
What are the Developers’ responsibilities?
Pick all that applyCorrectThe Developers have many responsibilities as following:
Developing and creating Increments, estimating the Product Backlog Items and tasks, creating the Sprint Backlog, selecting Items for the Sprint Backlog, decomposing selected Product Backlog Items into tasks, measuring Sprint performance and productivity, calculating velocity, resolving Team internal conflicts, collaborating in composing/refining the DoD, making technical decisions, etc.
On the other hand, ordering the Product Backlog is the Product Owner’s responsibility.
IncorrectThe Developers have many responsibilities as following:
Developing and creating Increments, estimating the Product Backlog Items and tasks, creating the Sprint Backlog, selecting Items for the Sprint Backlog, decomposing selected Product Backlog Items into tasks, measuring Sprint performance and productivity, calculating velocity, resolving Team internal conflicts, collaborating in composing/refining the DoD, making technical decisions, etc.
On the other hand, ordering the Product Backlog is the Product Owner’s responsibility.
- Question 48 of 80
48. Question
Who is in the Scrum Team accountable for instilling quality based on the Definition of Done?
Pick 1CorrectDevelopers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. All members are called developers and there is no title such as programmer, tester, etc. These are skills that each member might have some of them and accountability of instilling quality belongs to the whole Developers, not a special member such as tester, quality assurance specialist, etc.
IncorrectDevelopers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. All members are called developers and there is no title such as programmer, tester, etc. These are skills that each member might have some of them and accountability of instilling quality belongs to the whole Developers, not a special member such as tester, quality assurance specialist, etc.
- Question 49 of 80
49. Question
Which Scrum Team members can be part-time?
Pick 1CorrectThe Scrum Team consists of one Scrum Master, one Product Owner, and Developers. In fact, there are no Scrum Roles in Scrum anymore. Co-creators of Scrum have replaced the Scrum Roles with the three accountabilities. Because the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.
All Team members could be part-time or full-time but dedicated members are recommended for the Developers. In addition, one member can take two accountabilities at the same time for example as a Product Owner and a Developer.IncorrectThe Scrum Team consists of one Scrum Master, one Product Owner, and Developers. In fact, there are no Scrum Roles in Scrum anymore. Co-creators of Scrum have replaced the Scrum Roles with the three accountabilities. Because the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.
All Team members could be part-time or full-time but dedicated members are recommended for the Developers. In addition, one member can take two accountabilities at the same time for example as a Product Owner and a Developer. - Question 50 of 80
50. Question
Who is responsible for adding or removing members to/from the Scrum Team?
Pick 1CorrectThe Scrum Team is self-managing so it could make decisions about adding or removing members. In fact, they are the start point of making decisions for adding or removing members. However, each organization has its own process for adding or removing the Team members that is triggered by the Scrum Team. In addition, sometimes removing a member could be converted into an impediment. In such a case, the Scrum Master can intervene to help the Team removing that person.
IncorrectThe Scrum Team is self-managing so it could make decisions about adding or removing members. In fact, they are the start point of making decisions for adding or removing members. However, each organization has its own process for adding or removing the Team members that is triggered by the Scrum Team. In addition, sometimes removing a member could be converted into an impediment. In such a case, the Scrum Master can intervene to help the Team removing that person.
- Question 51 of 80
51. Question
Who makes the decisions about technical concerns?
Pick 1CorrectThe Developers manage all required work to implement and convert the Product Backlog into releasable Increments without receiving orders from outside the Team. In addition, the Developers know best about creating usable Increments so they decide on all technical concerns as a whole.
IncorrectThe Developers manage all required work to implement and convert the Product Backlog into releasable Increments without receiving orders from outside the Team. In addition, the Developers know best about creating usable Increments so they decide on all technical concerns as a whole.
- Question 52 of 80
52. Question
What is the purpose of each Sprint?
Pick 3CorrectThe Team tries to produce a done usable and potentially shippable and releasable Increment and a piece of working software at the end of each Sprint. Sprints are the heartbeat of Scrum, where ideas are turned into value.
IncorrectThe Team tries to produce a done usable and potentially shippable and releasable Increment and a piece of working software at the end of each Sprint. Sprints are the heartbeat of Scrum, where ideas are turned into value.
- Question 53 of 80
53. Question
When a person switches between two or more teams, his/her productivity will increase.
Pick 1CorrectWhen a person works in two or more teams, (s)he will pay context-switching cost. It means (s)he should pay warm-up, preparation time, and resource for each switch. Therefore, (s)he will be less productive rather than when just works on one team.
IncorrectWhen a person works in two or more teams, (s)he will pay context-switching cost. It means (s)he should pay warm-up, preparation time, and resource for each switch. Therefore, (s)he will be less productive rather than when just works on one team.
- Question 54 of 80
54. Question
Having a common language is one of the most important things that increases transparency.
Pick 1CorrectScrum is based on the agile mindset so collaboration is the most important thing that can help the Team to increase transparency. Also, effective collaboration needs a common language. In addition, having a Definition of Done is another important thing that can increase transparency. Furthermore, there are other things for increasing transparency but these are most important.
IncorrectScrum is based on the agile mindset so collaboration is the most important thing that can help the Team to increase transparency. Also, effective collaboration needs a common language. In addition, having a Definition of Done is another important thing that can increase transparency. Furthermore, there are other things for increasing transparency but these are most important.
- Question 55 of 80
55. Question
What does time-box mean?
Pick 1CorrectA time-box is a timeframe with a maximum duration. It means you can work in a time-box and if you achieve its goal, you can terminate it earlier. However, if you do not achieve its goal at the end of the timeframe, you cannot extend it.
IncorrectA time-box is a timeframe with a maximum duration. It means you can work in a time-box and if you achieve its goal, you can terminate it earlier. However, if you do not achieve its goal at the end of the timeframe, you cannot extend it.
- Question 56 of 80
56. Question
Which Scrum event can NOT be terminated before its time-box?
Pick 1CorrectExcept for the Sprint, all other Scrum events can be terminated before their time-box if the Team has achieved the event’s goal.
IncorrectExcept for the Sprint, all other Scrum events can be terminated before their time-box if the Team has achieved the event’s goal.
- Question 57 of 80
57. Question
Who should participate in the Sprint Review?
Pick all that applyCorrectParticipants of the Sprint Review are all Scrum Team members plus key stakeholders invited by the Product Owner.
IncorrectParticipants of the Sprint Review are all Scrum Team members plus key stakeholders invited by the Product Owner.
- Question 58 of 80
58. Question
Doing daily integration interrupts the Team’s focus. Therefore, they have decided to postpone all integration work into a separate Sprint called Integration Sprint. Is it acceptable behavior?
Pick 1CorrectThere is just regular Sprint in Scrum that within which the Developers try to create releasable Increment. Therefore, there are no such things as Sprint Zero, Hardening Sprint, Stabilization Sprint, Integration Sprint, etc.
On the other hand, if they postpone integration work to the future, they do not create a done Increment and cannot gather feedback from the market.IncorrectThere is just regular Sprint in Scrum that within which the Developers try to create releasable Increment. Therefore, there are no such things as Sprint Zero, Hardening Sprint, Stabilization Sprint, Integration Sprint, etc.
On the other hand, if they postpone integration work to the future, they do not create a done Increment and cannot gather feedback from the market. - Question 59 of 80
59. Question
When is a Sprint finished?
Pick 1CorrectSprint is the sole event that cannot be finished or over earlier or later than its predefined time-box duration. Other events are time-boxed but can be finished earlier if the team achieves each event’s goal.
On the other hand, it is possible the Team finishes all selected Sprint Backlog Items and tasks before the Sprint time-box, but the Team should continue the Sprint until the end of the related time-box through accepting new Items from the Product Backlog by negotiating with the Product Owner.
IncorrectSprint is the sole event that cannot be finished or over earlier or later than its predefined time-box duration. Other events are time-boxed but can be finished earlier if the team achieves each event’s goal.
On the other hand, it is possible the Team finishes all selected Sprint Backlog Items and tasks before the Sprint time-box, but the Team should continue the Sprint until the end of the related time-box through accepting new Items from the Product Backlog by negotiating with the Product Owner.
- Question 60 of 80
60. Question
How often should the Daily Scrum be conducted?
Pick 1CorrectDaily Scrum is a mandatory event of Scrum and is a feedback loop that the Developers synchronize their work daily and monitor progress toward the Sprint Goal. It should be conducted every working day during the Sprint.
IncorrectDaily Scrum is a mandatory event of Scrum and is a feedback loop that the Developers synchronize their work daily and monitor progress toward the Sprint Goal. It should be conducted every working day during the Sprint.
- Question 61 of 80
61. Question
Which of the following is a feedback loop?
Pick 3CorrectAll four Scrum events are a type of feedback loop or inspect and adapt opportunities include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Although Sprint is an event its role is being a container for other events. Product Backlog refinement is a continuous activity and is not a feedback loop.
IncorrectAll four Scrum events are a type of feedback loop or inspect and adapt opportunities include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Although Sprint is an event its role is being a container for other events. Product Backlog refinement is a continuous activity and is not a feedback loop.
- Question 62 of 80
62. Question
Why is conducting Daily Scrums at the same time and place important?
Pick 1CorrectThe Daily Scrum is a 15-minute daily meeting. Changing its place and time regularly leads to a coordination overhead for a member to prepare a place and increases complexity for the Team members to find the meeting time and place. Having it at the same time and place reduces its overhead and complexity.
IncorrectThe Daily Scrum is a 15-minute daily meeting. Changing its place and time regularly leads to a coordination overhead for a member to prepare a place and increases complexity for the Team members to find the meeting time and place. Having it at the same time and place reduces its overhead and complexity.
- Question 63 of 80
63. Question
How often should the Sprint Retrospective be conducted?
Pick 1CorrectSprint Retrospective is a mandatory event of Scrum and is a feedback loop that Team members could inspect their process to establish continuous improvement. It should be conducted at the end of each Sprint.
IncorrectSprint Retrospective is a mandatory event of Scrum and is a feedback loop that Team members could inspect their process to establish continuous improvement. It should be conducted at the end of each Sprint.
- Question 64 of 80
64. Question
Who are the participants of the Product Backlog Refinement?
Pick 1CorrectProduct Backlog Refinement is done by the Product Owner and the Developers’ collaboration. Even, stakeholders can be invited to the Product Backlog Refinement if needed.
IncorrectProduct Backlog Refinement is done by the Product Owner and the Developers’ collaboration. Even, stakeholders can be invited to the Product Backlog Refinement if needed.
- Question 65 of 80
65. Question
Which of the following is NOT an activity of the Product Backlog Refinement?
Pick 1CorrectThere are many activities in Product Backlog Refinement as follows:
- Breaking down the huge items (Epic)
- Creating new items
- Removing items
- Adding detail to the items
- Analysis
- Design
- Estimation
- Valuation
- Ordering
- …
In addition, breaking down the Product Backlog Items into sub-tasks is usually done in the Sprint Planning and even through the Sprint. Doing it before selecting the Product Backlog Items for development is a type of resource waste.
IncorrectThere are many activities in Product Backlog Refinement as follows:
- Breaking down the huge items (Epic)
- Creating new items
- Removing items
- Adding detail to the items
- Analysis
- Design
- Estimation
- Valuation
- Ordering
- …
In addition, breaking down the Product Backlog Items into sub-tasks is usually done in the Sprint Planning and even through the Sprint. Doing it before selecting the Product Backlog Items for development is a type of resource waste.
- Question 66 of 80
66. Question
Which of the following is the main purpose of the Sprint Review?
Pick 1CorrectEliciting feedback from the stakeholders and customers is the main purpose of the Sprint Review. In addition, there is not any hand-off / sign-off in it, and checking Team behavior is a topic that should be checked in the Sprint Retrospective.
IncorrectEliciting feedback from the stakeholders and customers is the main purpose of the Sprint Review. In addition, there is not any hand-off / sign-off in it, and checking Team behavior is a topic that should be checked in the Sprint Retrospective.
- Question 67 of 80
67. Question
Leaving the Sprint Backlog intact when the Developers find they have overcommitted in the middle of the Sprint, may lead to some undone items at the end of the Sprint.
Pick 1CorrectWhen the Developers are in the middle of the Sprint, they could not change the Sprint Backlog items by themselves. If they find they have overcommitted, they should inform the Product Owner to review the items together and negotiate the scope if necessary or they might leave the Sprint Backlog intact that may lead to some undone items at the end of the Sprint, which naturally will move back to the Product Backlog.
IncorrectWhen the Developers are in the middle of the Sprint, they could not change the Sprint Backlog items by themselves. If they find they have overcommitted, they should inform the Product Owner to review the items together and negotiate the scope if necessary or they might leave the Sprint Backlog intact that may lead to some undone items at the end of the Sprint, which naturally will move back to the Product Backlog.
- Question 68 of 80
68. Question
When does the Team create the Sprint Backlog?
Pick 1CorrectCreating the Sprint Backlog is a collaborative work that is done during the Sprint Planning not before or after it.
IncorrectCreating the Sprint Backlog is a collaborative work that is done during the Sprint Planning not before or after it.
- Question 69 of 80
69. Question
Can the Developers change the Sprint Backlog?
Pick 1CorrectSprint Backlog contains three elements: Sprint Goal, Sprint Backlog Items, and Tasks. Although changing Sprint Goal and Sprint Backlog Items are not allowed, tasks could be added or removed at any time during the Sprint when the Developers learn more about the work needed to realize the Sprint Goal. So, the Sprint Backlog could be updated and changed during the Sprint.
IncorrectSprint Backlog contains three elements: Sprint Goal, Sprint Backlog Items, and Tasks. Although changing Sprint Goal and Sprint Backlog Items are not allowed, tasks could be added or removed at any time during the Sprint when the Developers learn more about the work needed to realize the Sprint Goal. So, the Sprint Backlog could be updated and changed during the Sprint.
- Question 70 of 80
70. Question
Which one is True?
Pick 1CorrectScrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.
IncorrectScrum defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and the Scrum Master.
- Question 71 of 80
71. Question
Who creates the Sprint Goal?
Pick 1CorrectThe Sprint Goal is created through all Scrum Team members’ collaboration in the Sprint Planning.
IncorrectThe Sprint Goal is created through all Scrum Team members’ collaboration in the Sprint Planning.
- Question 72 of 80
72. Question
Items at the top of the Product Backlog are usually larger than the Items at the bottom.
Pick 1CorrectDuring Product Backlog refinement, Items are expressed with more details and broken down to the smaller Items that can be finished in a Sprint. In addition, more effort will pay for refining Items on the top of the Product Backlog because they have more probability to be implemented in the upcoming Sprints so usually PBIs on the top of the Product Backlog are smaller than PBIs at the bottom of it.
IncorrectDuring Product Backlog refinement, Items are expressed with more details and broken down to the smaller Items that can be finished in a Sprint. In addition, more effort will pay for refining Items on the top of the Product Backlog because they have more probability to be implemented in the upcoming Sprints so usually PBIs on the top of the Product Backlog are smaller than PBIs at the bottom of it.
- Question 73 of 80
73. Question
Which one is accountable for creating the Increment every Sprint?
Pick 1CorrectBased on the Scrum Guide 2020, the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
IncorrectBased on the Scrum Guide 2020, the entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
- Question 74 of 80
74. Question
Which topics are discussed in the Sprint Planning?
Pick all that applyCorrectThree topics are discussed in the Sprint Planning:
Topic One: Why is this Sprint valuable?
Topic Two: What can be Done this Sprint?
Topic Three: How will the chosen work get done?
However who topic is discussed during the implementation throughout the Sprint and is done by the DevelopersIncorrectThree topics are discussed in the Sprint Planning:
Topic One: Why is this Sprint valuable?
Topic Two: What can be Done this Sprint?
Topic Three: How will the chosen work get done?
However who topic is discussed during the implementation throughout the Sprint and is done by the Developers - Question 75 of 80
75. Question
Important improvements identified in the Sprint Retrospective should be implemented in the next Sprint.
Pick 1CorrectThe sentence of the question has come from the Scrum Guide 2017, while based on the 2020 version, the most impactful improvements are addressed as soon as possible not necessarily in the next Sprint.
IncorrectThe sentence of the question has come from the Scrum Guide 2017, while based on the 2020 version, the most impactful improvements are addressed as soon as possible not necessarily in the next Sprint.
- Question 76 of 80
76. Question
What are the commitments of the Artifacts?
Pick 1CorrectEach artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:
● For the Product Backlog it is the Product Goal.
● For the Sprint Backlog it is the Sprint Goal.
● For the Increment it is the Definition of Done.IncorrectEach artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured:
● For the Product Backlog it is the Product Goal.
● For the Sprint Backlog it is the Sprint Goal.
● For the Increment it is the Definition of Done. - Question 77 of 80
77. Question
What are the characteristics of the Product Goal?
Pick all that applyCorrectThe Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. However, Product Goals are the steps toward the product vision, not exactly the vision.
IncorrectThe Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next. However, Product Goals are the steps toward the product vision, not exactly the vision.
- Question 78 of 80
78. Question
When an Increment is born?
Pick 1CorrectThe moment a Product Backlog item meets the Definition of Done, an Increment is born. The Product Owner acceptance or finishing all tests do not mean meeting the Definition of Done, although they can be part of the Definition of Done. On the other hand, completing all tasks of the Product Backlog Item does not mean it works and is usable because the Developers might have not determined all required tasks to have a usable PBI.
IncorrectThe moment a Product Backlog item meets the Definition of Done, an Increment is born. The Product Owner acceptance or finishing all tests do not mean meeting the Definition of Done, although they can be part of the Definition of Done. On the other hand, completing all tasks of the Product Backlog Item does not mean it works and is usable because the Developers might have not determined all required tasks to have a usable PBI.
- Question 79 of 80
79. Question
Who creates the Definition of Done?
Pick 1CorrectIf the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
IncorrectIf the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product.
- Question 80 of 80
80. Question
What is a Product?
Pick all that applyCorrectBased on the Scrum Guide 2020 definition, a product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.
IncorrectBased on the Scrum Guide 2020 definition, a product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users or customers. A product could be a service, a physical product, or something more abstract.