ISTQB Agile Public Sector ISTQB-Agile-Public Exam Practice Test

Page: 1 / 14
Total 40 questions
Question 1

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 2

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 3

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION



Answer : B


Question 4

Which of the following sentences related to Risk-based testing is CORRECT?

SELECT ONE OPTION



Answer : C

Risk-based testing is a strategic approach to testing that prioritizes testing activities based on the level of risk associated with various features or components of the software. In Agile development, this approach aligns well with the iterative and incremental nature of Agile methodologies. During both release and iteration planning, Agile teams assess and prioritize work based on risk, value, and other factors. This double layer of risk analysis allows teams to focus their testing efforts more effectively on areas that pose the greatest risk to the project's success, thereby enhancing the quality and reliability of the deliverables. This approach is consistent with Agile principles, which emphasize adaptability and the delivery of value to the customer.


Question 5

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customers monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

i) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

ii) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

iii) As a customer assistant I can log in to the system and change my password.

iv) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

v) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

vl) As a bank manager I can log in to the system within 10 seconds.

SELECT ONE OPTION



Answer : B

The acceptance test criteria for the user story should ensure that the system can effectively evaluate loan requests based on the specified conditions. Criteria i) and ii) allow the customer assistant to access and verify customer account history and repayment behaviors, which are essential for assessing loan eligibility as per the user story. Criteria iv) and v) enable the bank manager to review and make decisions on loan requests, aligning with the user story's stipulation that the bank manager is responsible for loan approvals. These criteria ensure the system supports both the customer assistant's preparatory role and the bank manager's decision-making role in the loan approval process.


Question 6

Which of the following describes the main purpose of a task management tool in agile projects?

SELECT ONE OPTION



Answer : C

In agile projects, task management tools play a crucial role in facilitating project management and team collaboration. Specifically, option C accurately describes the primary function of a task management tool in agile contexts. These tools are designed to manage and track various elements of agile projects, including user stories, tests, tasks, and more, thereby enabling teams to maintain visibility and control over the project's progress.

Agile methodologies prioritize adaptability, customer collaboration, and the delivery of value through iterative development cycles. Task management tools support these principles by providing a platform for organizing work, prioritizing tasks, and ensuring that all team members are aligned on the project's objectives and progress. This alignment is essential for maintaining the agility and responsiveness characteristic of agile projects.

For example, the Scrum framework, a popular agile methodology, involves creating a product backlog that contains all the user stories and tasks needed for the project. The task management tool would be used to track these items through various stages of development, from the backlog to in-progress, testing, and completion. This tracking ensures that the team can adapt to changes, manage workloads effectively, and deliver increments of value to the customer consistently.

In summary, option C is the verified answer as it encapsulates the essential purpose of a task management tool in agile projects, which is to manage and track user stories, tests, and other tasks, thereby supporting the agile principles of adaptability, customer collaboration, and iterative delivery of value.


Question 7

Which of the following allows a developer to define accurate unit tests focused on business needs?

SELECT ONE OPTION



Answer : A

Behavior-Driven Development (BDD) allows developers to define accurate unit tests focused on business needs by bridging the communication gap between technical and non-technical team members. BDD uses scenarios in plain language that describe the behavior of the application from the end-user's perspective, ensuring that the development focus remains on delivering features that provide real value to the business.


Question 8

Which ONE of the following is a testable acceptance criterion?

SELECT ONE OPTION



Answer : C

A testable acceptance criterion must be specific, measurable, and verifiable, which makes option C the correct choice. Stating that 'the response time to confirm a customer submission must not exceed 5 seconds' provides a clear, quantifiable measure that can be tested to determine whether the criterion has been met. This contrasts with more subjective criteria, such as the system being 'easy to use,' which cannot be easily quantified or measured in a straightforward manner. The specificity of the response time allows for the creation of test cases that can confirm whether the system meets this particular requirement, thus making it a testable acceptance criterion.


Question 9

Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

SELECT ONE OPTION



Answer : B

In Agile projects, the integration of development and testing activities involves close collaboration between developers and testers, but it does not typically involve testers replacing developers in writing unit test automation scripts. Agile methodologies, such as Scrum and XP (Extreme Programming), encourage developers to write their own unit tests as part of the Test-Driven Development (TDD) process. Testers often focus on higher-level testing activities, such as acceptance testing and exploratory testing, and may work alongside developers to enhance test coverage and effectiveness. The incorrect statement about testers replacing developers in writing unit test automation scripts contradicts the Agile principle of developers being responsible for the quality of their code, which includes writing and maintaining unit tests.


Question 10

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 11

Which of the following would provide the MOST independence for testers working with agile teams?

SELECT ONE OPTION



Answer : B

In Agile project environments, embedding testers within the Agile teams promotes close collaboration, immediate feedback, and continuous improvement, essential principles of Agile methodologies. This integration enables testers to be involved in all stages of the development process, from planning and design to execution and review, facilitating early detection of defects, understanding of user requirements, and adherence to quality standards. The Agile Manifesto emphasizes individuals and interactions over processes and tools, advocating for collaborative team environments where business people and developers work together daily throughout the project. This approach contrasts with traditional methods where testing is often conducted in isolation or after development phases, potentially leading to delays and reduced quality due to the late discovery of issues.


Question 12

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 13

What is the definition of agile software development?

SELECT ONE OPTION



Answer : A

Agile software development is characterized by its iterative and incremental approach, where development is conducted in cycles, and the work is divided into small, manageable chunks known as iterations or sprints. This approach allows for frequent reassessment of the project's direction, making it easier to incorporate changes and adapt to new information. Self-organizing, cross-functional teams are a hallmark of agile methodologies, emphasizing collaboration, flexibility, and team empowerment. This definition captures the essence of agile as described in various agile methodologies and the Agile Manifesto.


Question 14

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 15

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 16

Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?

SELECT ONE OPTION



Answer : B

Option B is not true regarding the benefits of Agile processes promoting early and frequent feedback. The statement, 'Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems,' overstates the capability of Agile methodologies. While Agile practices such as Scrum and Kanban emphasize continuous feedback and collaboration to improve project outcomes and adapt to changes, they do not claim to eliminate all communication problems.

Communication challenges can arise due to various factors, including but not limited to, differences in stakeholders' perspectives, misunderstandings, and external constraints. Agile methodologies aim to reduce the impact of these challenges by promoting transparency, regular interactions, and adaptive planning. Tools like daily stand-ups, retrospectives, and sprint reviews facilitate ongoing dialogue among team members and stakeholders, helping to identify and address issues promptly. However, these practices enhance communication effectiveness rather than eliminating all potential communication problems.

In contrast, options A, C, and D accurately reflect the principles and benefits of Agile methodologies. Early and frequent feedback helps in identifying and rectifying defects and misalignments with requirements more quickly (A), improves development processes through reflective practices like retrospectives (C), and ensures that the team prioritizes work that delivers the highest value to the customer (D).

Therefore, option B is the verified answer as it presents an unrealistic expectation of Agile processes' impact on communication challenges, contradicting the Agile Manifesto's acknowledgment of the complexity and collaborative nature of software development.


Question 17

Which of the following statements about the Planning poker test estimate technique are CORRECT?

i) Planning poker is a consensus based technique using a deck of cards.

ii) A low test estimate usually means the story should be broken down into multiple smaller stories.

iii) A high test estimate usually means the story should be broken down into multiple smaller stories.

iv) One poker round is played and then consensus has to be reached.

v) The risk level of each backlog item should be decided before the poker session.

SELECT ONE OPTION



Answer : C

Planning poker, a consensus-based estimation technique used in Agile planning sessions, involves team members making estimates by playing numbered cards face-down to the table, avoiding the influence of other participants. This process promotes a collective understanding and agreement on effort estimations. Statements i, ii, and iii accurately reflect the principles of Planning Poker. It's a consensus-based technique (i), and if the estimates are too high (iii) or too low (ii), it often indicates that the user story is not well understood or is too complex, suggesting it should be broken down into smaller, more manageable pieces. This approach aligns with Agile's preference for small, incremental changes that can be easily managed and adapted, fostering collaboration and collective decision-making within the team.


Question 18

Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

SELECT ONE OPTION



Answer : D

Maintaining the independence of the test team within an Agile development environment can be achieved by integrating testers into the Agile teams while ensuring they have a separate reporting line. This arrangement helps in preserving the objectivity of the testing function without isolating testers from the collaborative and fast-paced Agile environment. Testers contribute to the team's activities and participate in all Agile ceremonies, fostering a strong collaboration and understanding of the product. However, by reporting to a different manager, testers can maintain an independent perspective, which is crucial for unbiased quality assurance. This approach aligns with Agile values of collaboration and individuals and interactions over processes and tools, while also respecting the need for independent verification and validation of the software product.


Question 19

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 20

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 21

Which of the following allows a developer to define accurate unit tests focused on business needs?

SELECT ONE OPTION



Answer : A

Behavior-Driven Development (BDD) allows developers to define accurate unit tests focused on business needs by bridging the communication gap between technical and non-technical team members. BDD uses scenarios in plain language that describe the behavior of the application from the end-user's perspective, ensuring that the development focus remains on delivering features that provide real value to the business.


Question 22

What is the main benefit of the Test Pyramid?

SELECT ONE OPTION



Answer : B

The Test Pyramid is a concept that emphasizes the importance of incorporating testing early and throughout the software development cycle rather than leaving it until the end. This approach aligns with agile methodologies, which advocate for continuous integration and testing to identify and fix issues promptly, thereby improving the quality of the software and reducing the time and cost associated with late-stage testing.


Question 23

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 24

Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.

In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

SELECT ONE OPTION



Answer : C

Exploratory Testing is aligned with Quadrant 3 of the Testing Quadrants, which emphasizes business-facing tests that critique the product. This quadrant focuses on testing aspects that cannot be fully planned in advance and require a more ad-hoc, investigative approach to uncover issues from a business or user perspective. Exploratory Testing involves simultaneous learning, test design, and test execution, making it suitable for assessing the usability, relevance, and overall value of the product to the business, aligning with the goals of Quadrant 3.


Question 25

Which of the following would provide the MOST independence for testers working with agile teams?

SELECT ONE OPTION



Answer : B

In Agile project environments, embedding testers within the Agile teams promotes close collaboration, immediate feedback, and continuous improvement, essential principles of Agile methodologies. This integration enables testers to be involved in all stages of the development process, from planning and design to execution and review, facilitating early detection of defects, understanding of user requirements, and adherence to quality standards. The Agile Manifesto emphasizes individuals and interactions over processes and tools, advocating for collaborative team environments where business people and developers work together daily throughout the project. This approach contrasts with traditional methods where testing is often conducted in isolation or after development phases, potentially leading to delays and reduced quality due to the late discovery of issues.


Question 26

What is the definition of agile software development?

SELECT ONE OPTION



Answer : A

Agile software development is characterized by its iterative and incremental approach, where development is conducted in cycles, and the work is divided into small, manageable chunks known as iterations or sprints. This approach allows for frequent reassessment of the project's direction, making it easier to incorporate changes and adapt to new information. Self-organizing, cross-functional teams are a hallmark of agile methodologies, emphasizing collaboration, flexibility, and team empowerment. This definition captures the essence of agile as described in various agile methodologies and the Agile Manifesto.


Question 27

Which tasks are typically performed by a tester on an Agile project?

i) Implementing test strategy.

ii) Documenting business requirements.

iii) Measuring and reporting test coverage.

iv) Coaching development team in relevant aspects of testing.

v) Executing test-driven development tests.

SELECT ONE OPTION



Answer : A

In an agile project, testers often perform tasks beyond traditional testing roles, including implementing test strategy (i), measuring and reporting test coverage (iii), and coaching the development team on relevant aspects of testing (iv). Implementing test strategy involves planning how testing will be conducted within the agile framework, ensuring that testing aligns with agile principles and practices. Measuring and reporting test coverage help the team understand the extent to which the codebase is tested, which is crucial for maintaining quality in fast-paced agile environments. Coaching the development team involves sharing knowledge on testing best practices and fostering a quality-centric mindset across the team. These activities contribute to the collaborative and iterative nature of agile projects, where continuous feedback and improvement are emphasized.


Question 28

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 29

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 30

What is the definition of agile software development?

SELECT ONE OPTION



Answer : A

Agile software development is characterized by its iterative and incremental approach, where development is conducted in cycles, and the work is divided into small, manageable chunks known as iterations or sprints. This approach allows for frequent reassessment of the project's direction, making it easier to incorporate changes and adapt to new information. Self-organizing, cross-functional teams are a hallmark of agile methodologies, emphasizing collaboration, flexibility, and team empowerment. This definition captures the essence of agile as described in various agile methodologies and the Agile Manifesto.


Question 31

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 32

Which of the following statements is FALSE regarding early and frequent feedback?

SELECT ONE OPTION



Answer : C

Early and frequent feedback is fundamental in Agile methodologies to ensure the product meets customer needs and to identify and resolve issues promptly. However, the statement that early feedback decreases the time needed for system testing (Option C) is misleading. While early feedback helps in identifying and resolving issues at an early stage, it does not necessarily reduce the overall time required for system testing. System testing is a comprehensive phase that assesses the system's compliance with the specified requirements. Agile practices, such as continuous integration and testing, aim to maintain a high quality throughout the development process, but they do not eliminate the need for thorough system testing to validate the product before release.


Question 33

Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.

In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

SELECT ONE OPTION



Answer : C

Exploratory Testing is aligned with Quadrant 3 of the Testing Quadrants, which emphasizes business-facing tests that critique the product. This quadrant focuses on testing aspects that cannot be fully planned in advance and require a more ad-hoc, investigative approach to uncover issues from a business or user perspective. Exploratory Testing involves simultaneous learning, test design, and test execution, making it suitable for assessing the usability, relevance, and overall value of the product to the business, aligning with the goals of Quadrant 3.


Question 34

Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

SELECT ONE OPTION



Answer : B

In Agile projects, the integration of development and testing activities involves close collaboration between developers and testers, but it does not typically involve testers replacing developers in writing unit test automation scripts. Agile methodologies, such as Scrum and XP (Extreme Programming), encourage developers to write their own unit tests as part of the Test-Driven Development (TDD) process. Testers often focus on higher-level testing activities, such as acceptance testing and exploratory testing, and may work alongside developers to enhance test coverage and effectiveness. The incorrect statement about testers replacing developers in writing unit test automation scripts contradicts the Agile principle of developers being responsible for the quality of their code, which includes writing and maintaining unit tests.


Question 35

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 36

Which of the following is a risk that continuous integration introduces?

SELECT ONE OPTION



Answer : A

Continuous integration introduces the risk of having too many builds for testers to evaluate, potentially reducing the quality of testing. With frequent integration of new code and automated builds, testers may face challenges in keeping up with the pace, leading to less thorough testing and the possibility of defects slipping through.


Question 37

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 38

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 39

Which ONE of the following is a testable acceptance criterion?

SELECT ONE OPTION



Answer : C

A testable acceptance criterion must be specific, measurable, and verifiable, which makes option C the correct choice. Stating that 'the response time to confirm a customer submission must not exceed 5 seconds' provides a clear, quantifiable measure that can be tested to determine whether the criterion has been met. This contrasts with more subjective criteria, such as the system being 'easy to use,' which cannot be easily quantified or measured in a straightforward manner. The specificity of the response time allows for the creation of test cases that can confirm whether the system meets this particular requirement, thus making it a testable acceptance criterion.


Question 40

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 41

Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

SELECT ONE OPTION



Answer : C


Question 42

Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

SELECT ONE OPTION



Answer : D

Maintaining the independence of the test team within an Agile development environment can be achieved by integrating testers into the Agile teams while ensuring they have a separate reporting line. This arrangement helps in preserving the objectivity of the testing function without isolating testers from the collaborative and fast-paced Agile environment. Testers contribute to the team's activities and participate in all Agile ceremonies, fostering a strong collaboration and understanding of the product. However, by reporting to a different manager, testers can maintain an independent perspective, which is crucial for unbiased quality assurance. This approach aligns with Agile values of collaboration and individuals and interactions over processes and tools, while also respecting the need for independent verification and validation of the software product.


Question 43

During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

SELECT ONE OPTION



Answer : C

Agile retrospectives focus on the process, practices, and tools, rather than personal critiques. The effectiveness of a retrospective lies in its ability to foster a positive, constructive environment where the team can discuss what worked well, what didn't, and how to improve going forward. Focusing on an individual's perceived shortcomings, such as being 'disruptive and lazy' (Option C), does not align with the Agile principle of building projects around motivated individuals and trusting them to get the job done. It could lead to a negative atmosphere, reducing the team's willingness to openly share and collaborate on solutions. Instead, retrospectives should concentrate on actionable items that can lead to process improvements, such as addressing frequent automation test failures, discrepancies in effort estimations, and delays in the build process, as mentioned in options A, B, and D respectively.


Question 44

A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations. Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?

I) A task to design the features planned for the next sprint.

ii) A task to run an acceptance test for a user story.

iii) A task to automate regression tests.

iv) A task to participate in training in preparation for the fourth sprint.

v) A task to produce a daily progress report for the agile team members.

SELECT ONE OPTION



Answer : D


Question 45

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 46

Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.

In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

SELECT ONE OPTION



Answer : C

Exploratory Testing is aligned with Quadrant 3 of the Testing Quadrants, which emphasizes business-facing tests that critique the product. This quadrant focuses on testing aspects that cannot be fully planned in advance and require a more ad-hoc, investigative approach to uncover issues from a business or user perspective. Exploratory Testing involves simultaneous learning, test design, and test execution, making it suitable for assessing the usability, relevance, and overall value of the product to the business, aligning with the goals of Quadrant 3.


Question 47

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 48

Which of the following describes the main purpose of a task management tool in agile projects?

SELECT ONE OPTION



Answer : C

In agile projects, task management tools play a crucial role in facilitating project management and team collaboration. Specifically, option C accurately describes the primary function of a task management tool in agile contexts. These tools are designed to manage and track various elements of agile projects, including user stories, tests, tasks, and more, thereby enabling teams to maintain visibility and control over the project's progress.

Agile methodologies prioritize adaptability, customer collaboration, and the delivery of value through iterative development cycles. Task management tools support these principles by providing a platform for organizing work, prioritizing tasks, and ensuring that all team members are aligned on the project's objectives and progress. This alignment is essential for maintaining the agility and responsiveness characteristic of agile projects.

For example, the Scrum framework, a popular agile methodology, involves creating a product backlog that contains all the user stories and tasks needed for the project. The task management tool would be used to track these items through various stages of development, from the backlog to in-progress, testing, and completion. This tracking ensures that the team can adapt to changes, manage workloads effectively, and deliver increments of value to the customer consistently.

In summary, option C is the verified answer as it encapsulates the essential purpose of a task management tool in agile projects, which is to manage and track user stories, tests, and other tasks, thereby supporting the agile principles of adaptability, customer collaboration, and iterative delivery of value.


Question 49

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customers monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

i) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

ii) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

iii) As a customer assistant I can log in to the system and change my password.

iv) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

v) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

vl) As a bank manager I can log in to the system within 10 seconds.

SELECT ONE OPTION



Answer : B

The acceptance test criteria for the user story should ensure that the system can effectively evaluate loan requests based on the specified conditions. Criteria i) and ii) allow the customer assistant to access and verify customer account history and repayment behaviors, which are essential for assessing loan eligibility as per the user story. Criteria iv) and v) enable the bank manager to review and make decisions on loan requests, aligning with the user story's stipulation that the bank manager is responsible for loan approvals. These criteria ensure the system supports both the customer assistant's preparatory role and the bank manager's decision-making role in the loan approval process.


Question 50

Which of the following statements is FALSE regarding early and frequent feedback?

SELECT ONE OPTION



Answer : C

Early and frequent feedback is fundamental in Agile methodologies to ensure the product meets customer needs and to identify and resolve issues promptly. However, the statement that early feedback decreases the time needed for system testing (Option C) is misleading. While early feedback helps in identifying and resolving issues at an early stage, it does not necessarily reduce the overall time required for system testing. System testing is a comprehensive phase that assesses the system's compliance with the specified requirements. Agile practices, such as continuous integration and testing, aim to maintain a high quality throughout the development process, but they do not eliminate the need for thorough system testing to validate the product before release.


Question 51

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 52

During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

SELECT ONE OPTION



Answer : C

Agile retrospectives focus on the process, practices, and tools, rather than personal critiques. The effectiveness of a retrospective lies in its ability to foster a positive, constructive environment where the team can discuss what worked well, what didn't, and how to improve going forward. Focusing on an individual's perceived shortcomings, such as being 'disruptive and lazy' (Option C), does not align with the Agile principle of building projects around motivated individuals and trusting them to get the job done. It could lead to a negative atmosphere, reducing the team's willingness to openly share and collaborate on solutions. Instead, retrospectives should concentrate on actionable items that can lead to process improvements, such as addressing frequent automation test failures, discrepancies in effort estimations, and delays in the build process, as mentioned in options A, B, and D respectively.


Question 53

Which of the following statements about the Planning poker test estimate technique are CORRECT?

i) Planning poker is a consensus based technique using a deck of cards.

ii) A low test estimate usually means the story should be broken down into multiple smaller stories.

iii) A high test estimate usually means the story should be broken down into multiple smaller stories.

iv) One poker round is played and then consensus has to be reached.

v) The risk level of each backlog item should be decided before the poker session.

SELECT ONE OPTION



Answer : C

Planning poker, a consensus-based estimation technique used in Agile planning sessions, involves team members making estimates by playing numbered cards face-down to the table, avoiding the influence of other participants. This process promotes a collective understanding and agreement on effort estimations. Statements i, ii, and iii accurately reflect the principles of Planning Poker. It's a consensus-based technique (i), and if the estimates are too high (iii) or too low (ii), it often indicates that the user story is not well understood or is too complex, suggesting it should be broken down into smaller, more manageable pieces. This approach aligns with Agile's preference for small, incremental changes that can be easily managed and adapted, fostering collaboration and collective decision-making within the team.


Question 54

You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.

As an agile tester, which of the following actions should you take?

SELECT ONE OPTION



Answer : C

In Agile teams, collaboration and direct communication are key. When faced with blocked tests due to ongoing development or failing unit tests, an agile tester should collaborate with the developer to identify and resolve the issues. This approach encourages teamwork, knowledge sharing, and problem-solving, leading to more efficient and effective resolution of blocking issues.


Question 55

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customers monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

i) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

ii) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

iii) As a customer assistant I can log in to the system and change my password.

iv) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

v) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

vl) As a bank manager I can log in to the system within 10 seconds.

SELECT ONE OPTION



Answer : B

The acceptance test criteria for the user story should ensure that the system can effectively evaluate loan requests based on the specified conditions. Criteria i) and ii) allow the customer assistant to access and verify customer account history and repayment behaviors, which are essential for assessing loan eligibility as per the user story. Criteria iv) and v) enable the bank manager to review and make decisions on loan requests, aligning with the user story's stipulation that the bank manager is responsible for loan approvals. These criteria ensure the system supports both the customer assistant's preparatory role and the bank manager's decision-making role in the loan approval process.


Question 56

Which of the following allows a developer to define accurate unit tests focused on business needs?

SELECT ONE OPTION



Answer : A

Behavior-Driven Development (BDD) allows developers to define accurate unit tests focused on business needs by bridging the communication gap between technical and non-technical team members. BDD uses scenarios in plain language that describe the behavior of the application from the end-user's perspective, ensuring that the development focus remains on delivering features that provide real value to the business.


Question 57

Which of the following activities are done in release planning?

i. Identifying testable user stories with acceptance criteria.

ii. Elaborating the user stories into tasks.

iii. Prioritizing the user stories.

iv. Creating acceptance tests for the user stories.

v. Analyzing risks for each of the user stories.

vi. Performing high level estimation for the release.

SELECT ONE OPTION



Answer : A

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.


Question 58

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 59

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 60

Which of the following statements about the Planning poker test estimate technique are CORRECT?

i) Planning poker is a consensus based technique using a deck of cards.

ii) A low test estimate usually means the story should be broken down into multiple smaller stories.

iii) A high test estimate usually means the story should be broken down into multiple smaller stories.

iv) One poker round is played and then consensus has to be reached.

v) The risk level of each backlog item should be decided before the poker session.

SELECT ONE OPTION



Answer : C

Planning poker, a consensus-based estimation technique used in Agile planning sessions, involves team members making estimates by playing numbered cards face-down to the table, avoiding the influence of other participants. This process promotes a collective understanding and agreement on effort estimations. Statements i, ii, and iii accurately reflect the principles of Planning Poker. It's a consensus-based technique (i), and if the estimates are too high (iii) or too low (ii), it often indicates that the user story is not well understood or is too complex, suggesting it should be broken down into smaller, more manageable pieces. This approach aligns with Agile's preference for small, incremental changes that can be easily managed and adapted, fostering collaboration and collective decision-making within the team.


Question 61

Consider an online application that allows registered users to pay the annual car tax based on the vehicle's engine power in kW. Given the following user story:

''As a customer I need the online application to calculate the annual car tax amount that I need to pay for my car":

- If the power of the vehicle is less than 20 kW, then the annual car tax is free

- If the power of the vehicle is more or equal than 20 kW but less or equal than 150 kW, then the annual car tax is 250 Euros

- If the power of the vehicle is more than 150 kW, then the annual car tax is 750 Euros"

What is the MOST suitable use of a black-box test design technique for this user story?

SELECT ONE OPTION



Answer : C


Question 62

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 63

Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?

SELECT ONE OPTION



Answer : D

Maintaining the independence of the test team within an Agile development environment can be achieved by integrating testers into the Agile teams while ensuring they have a separate reporting line. This arrangement helps in preserving the objectivity of the testing function without isolating testers from the collaborative and fast-paced Agile environment. Testers contribute to the team's activities and participate in all Agile ceremonies, fostering a strong collaboration and understanding of the product. However, by reporting to a different manager, testers can maintain an independent perspective, which is crucial for unbiased quality assurance. This approach aligns with Agile values of collaboration and individuals and interactions over processes and tools, while also respecting the need for independent verification and validation of the software product.


Question 64

Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?

SELECT ONE OPTION



Answer : C


Question 65

Which of the following statements is FALSE regarding early and frequent feedback?

SELECT ONE OPTION



Answer : C

Early and frequent feedback is fundamental in Agile methodologies to ensure the product meets customer needs and to identify and resolve issues promptly. However, the statement that early feedback decreases the time needed for system testing (Option C) is misleading. While early feedback helps in identifying and resolving issues at an early stage, it does not necessarily reduce the overall time required for system testing. System testing is a comprehensive phase that assesses the system's compliance with the specified requirements. Agile practices, such as continuous integration and testing, aim to maintain a high quality throughout the development process, but they do not eliminate the need for thorough system testing to validate the product before release.


Question 66

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 67

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 68

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 69

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 70

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 71

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 72

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 73

You have been asked to execute an exploratory testing session on Park & Ride system. The test charter has been titled as "Buy a bus ticket". As a result, a number of defects were reported, the titles of which are listed below.

Which defect is out of scope for the given test charter?

SELECT ONE OPTION



Answer : D

The defect titled 'Payment for parking ticket is restricted to cash only (no credit card supported)' is out of scope for the given test charter titled 'Buy a bus ticket' because it pertains to a different functionality not covered by the charter. The charter focuses on the process of purchasing a bus ticket, which involves functionality such as selecting a ticket type, choosing a journey, and completing the transaction. A defect related to payment methods for a parking ticket does not relate to these functions and is therefore considered out of scope for the testing session focused on buying a bus ticket.


Question 74

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 75

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 76

Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

i) User access for all roles has been validated.

ii) A static analysis tool has been executed for all code.

iii) 100% of the existing regression test suite has passed.

Iv) System is responding In less than 3 seconds, 90% of the time.

v) A new version of Internet Explorer has been included.

SELECT ONE OPTION



Answer : B

The acceptance criteria for a sprint focused on improving the performance of a system, like the one described for Sprint 5, typically include ensuring that the system meets specific performance benchmarks and that the functionality implemented in previous sprints continues to work as expected. Therefore, the most relevant acceptance criteria for such a sprint would be:

iii) '100% of the existing regression test suite has passed.' This criterion ensures that the new performance enhancements have not adversely affected the existing functionalities of the system. It's a common practice in agile projects to maintain the integrity and quality of the system by running regression tests. This is supported by the notion that continuous testing and quality assurance are integral components of agile methodologies, ensuring that each increment of the project maintains and improves the quality of the product (Source: Agile Project Management methodologies).

iv) 'System is responding in less than 3 seconds, 90% of the time.' This criterion directly addresses the goal of the sprint, which is to increase the performance of the system. Setting a specific target for response times is a quantifiable and testable way to measure the improvement in performance. This aligns with agile principles, which emphasize delivering valuable, working software and encourage adaptive planning and continuous improvement. Performance targets like these help the team focus on delivering specific, valuable improvements to the system (Source: Principles behind the Agile Manifesto).

Options i) and v) are less relevant to the specific focus of Sprint 5, which is on performance improvement, and more about user roles and software compatibility, which are not directly tied to the performance objectives of the sprint. Therefore, options iii) and iv) constitute the most appropriate acceptance criteria for Sprint 5, focusing on ensuring that the system's performance meets the set benchmarks without compromising existing functionalities.


Question 77

Which of the following statements about a test charter are CORRECT?

i) It is used mainly in exploratory tests.

ii) It is used to monitor a test process.

iii) It may make reference to user stories.

iv) It contains notes taken during a test session.

v) It is used to outline the company test policy.

SELECT ONE OPTION



Answer : A

A test charter is primarily used in exploratory testing (i) to guide the test session with a clear mission or objective, which might be related to specific functionalities, user stories, or areas of the application, making reference to user stories (iii) plausible. It also contains notes taken during the test session (iv), which are crucial for documenting observations, anomalies, and insights gained during exploratory testing. This approach aligns with Agile's emphasis on individuals and interactions and responding to change, as exploratory testing is inherently adaptive and relies on the tester's skill, creativity, and intuition. It contrasts with more traditional, documentation-heavy approaches, emphasizing the value of working software and collaboration.


Question 78

Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

i) User access for all roles has been validated.

ii) A static analysis tool has been executed for all code.

iii) 100% of the existing regression test suite has passed.

Iv) System is responding In less than 3 seconds, 90% of the time.

v) A new version of Internet Explorer has been included.

SELECT ONE OPTION



Answer : B

The acceptance criteria for a sprint focused on improving the performance of a system, like the one described for Sprint 5, typically include ensuring that the system meets specific performance benchmarks and that the functionality implemented in previous sprints continues to work as expected. Therefore, the most relevant acceptance criteria for such a sprint would be:

iii) '100% of the existing regression test suite has passed.' This criterion ensures that the new performance enhancements have not adversely affected the existing functionalities of the system. It's a common practice in agile projects to maintain the integrity and quality of the system by running regression tests. This is supported by the notion that continuous testing and quality assurance are integral components of agile methodologies, ensuring that each increment of the project maintains and improves the quality of the product (Source: Agile Project Management methodologies).

iv) 'System is responding in less than 3 seconds, 90% of the time.' This criterion directly addresses the goal of the sprint, which is to increase the performance of the system. Setting a specific target for response times is a quantifiable and testable way to measure the improvement in performance. This aligns with agile principles, which emphasize delivering valuable, working software and encourage adaptive planning and continuous improvement. Performance targets like these help the team focus on delivering specific, valuable improvements to the system (Source: Principles behind the Agile Manifesto).

Options i) and v) are less relevant to the specific focus of Sprint 5, which is on performance improvement, and more about user roles and software compatibility, which are not directly tied to the performance objectives of the sprint. Therefore, options iii) and iv) constitute the most appropriate acceptance criteria for Sprint 5, focusing on ensuring that the system's performance meets the set benchmarks without compromising existing functionalities.


Question 79

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 80

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 81

Which of the following is a risk that continuous integration introduces?

SELECT ONE OPTION



Answer : A

Continuous integration introduces the risk of having too many builds for testers to evaluate, potentially reducing the quality of testing. With frequent integration of new code and automated builds, testers may face challenges in keeping up with the pace, leading to less thorough testing and the possibility of defects slipping through.


Question 82

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 83

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION



Answer : B


Question 84

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 85

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 86

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 87

Which of the following describes the main purpose of a task management tool in agile projects?

SELECT ONE OPTION



Answer : C

In agile projects, task management tools play a crucial role in facilitating project management and team collaboration. Specifically, option C accurately describes the primary function of a task management tool in agile contexts. These tools are designed to manage and track various elements of agile projects, including user stories, tests, tasks, and more, thereby enabling teams to maintain visibility and control over the project's progress.

Agile methodologies prioritize adaptability, customer collaboration, and the delivery of value through iterative development cycles. Task management tools support these principles by providing a platform for organizing work, prioritizing tasks, and ensuring that all team members are aligned on the project's objectives and progress. This alignment is essential for maintaining the agility and responsiveness characteristic of agile projects.

For example, the Scrum framework, a popular agile methodology, involves creating a product backlog that contains all the user stories and tasks needed for the project. The task management tool would be used to track these items through various stages of development, from the backlog to in-progress, testing, and completion. This tracking ensures that the team can adapt to changes, manage workloads effectively, and deliver increments of value to the customer consistently.

In summary, option C is the verified answer as it encapsulates the essential purpose of a task management tool in agile projects, which is to manage and track user stories, tests, and other tasks, thereby supporting the agile principles of adaptability, customer collaboration, and iterative delivery of value.


Question 88

Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?

SELECT ONE OPTION



Answer : B

Option B is not true regarding the benefits of Agile processes promoting early and frequent feedback. The statement, 'Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems,' overstates the capability of Agile methodologies. While Agile practices such as Scrum and Kanban emphasize continuous feedback and collaboration to improve project outcomes and adapt to changes, they do not claim to eliminate all communication problems.

Communication challenges can arise due to various factors, including but not limited to, differences in stakeholders' perspectives, misunderstandings, and external constraints. Agile methodologies aim to reduce the impact of these challenges by promoting transparency, regular interactions, and adaptive planning. Tools like daily stand-ups, retrospectives, and sprint reviews facilitate ongoing dialogue among team members and stakeholders, helping to identify and address issues promptly. However, these practices enhance communication effectiveness rather than eliminating all potential communication problems.

In contrast, options A, C, and D accurately reflect the principles and benefits of Agile methodologies. Early and frequent feedback helps in identifying and rectifying defects and misalignments with requirements more quickly (A), improves development processes through reflective practices like retrospectives (C), and ensures that the team prioritizes work that delivers the highest value to the customer (D).

Therefore, option B is the verified answer as it presents an unrealistic expectation of Agile processes' impact on communication challenges, contradicting the Agile Manifesto's acknowledgment of the complexity and collaborative nature of software development.


Question 89

Your agile team is using the Testing Quadrants to ensure that all important test levels and test types are covered in the test plan.

In relation to Quadrant 3 - business facing and product critique, what should be considered for the plan?

SELECT ONE OPTION



Answer : C

Exploratory Testing is aligned with Quadrant 3 of the Testing Quadrants, which emphasizes business-facing tests that critique the product. This quadrant focuses on testing aspects that cannot be fully planned in advance and require a more ad-hoc, investigative approach to uncover issues from a business or user perspective. Exploratory Testing involves simultaneous learning, test design, and test execution, making it suitable for assessing the usability, relevance, and overall value of the product to the business, aligning with the goals of Quadrant 3.


Question 90

You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.

As an agile tester, which of the following actions should you take?

SELECT ONE OPTION



Answer : C

In Agile teams, collaboration and direct communication are key. When faced with blocked tests due to ongoing development or failing unit tests, an agile tester should collaborate with the developer to identify and resolve the issues. This approach encourages teamwork, knowledge sharing, and problem-solving, leading to more efficient and effective resolution of blocking issues.


Question 91

Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

i) User access for all roles has been validated.

ii) A static analysis tool has been executed for all code.

iii) 100% of the existing regression test suite has passed.

Iv) System is responding In less than 3 seconds, 90% of the time.

v) A new version of Internet Explorer has been included.

SELECT ONE OPTION



Answer : B

The acceptance criteria for a sprint focused on improving the performance of a system, like the one described for Sprint 5, typically include ensuring that the system meets specific performance benchmarks and that the functionality implemented in previous sprints continues to work as expected. Therefore, the most relevant acceptance criteria for such a sprint would be:

iii) '100% of the existing regression test suite has passed.' This criterion ensures that the new performance enhancements have not adversely affected the existing functionalities of the system. It's a common practice in agile projects to maintain the integrity and quality of the system by running regression tests. This is supported by the notion that continuous testing and quality assurance are integral components of agile methodologies, ensuring that each increment of the project maintains and improves the quality of the product (Source: Agile Project Management methodologies).

iv) 'System is responding in less than 3 seconds, 90% of the time.' This criterion directly addresses the goal of the sprint, which is to increase the performance of the system. Setting a specific target for response times is a quantifiable and testable way to measure the improvement in performance. This aligns with agile principles, which emphasize delivering valuable, working software and encourage adaptive planning and continuous improvement. Performance targets like these help the team focus on delivering specific, valuable improvements to the system (Source: Principles behind the Agile Manifesto).

Options i) and v) are less relevant to the specific focus of Sprint 5, which is on performance improvement, and more about user roles and software compatibility, which are not directly tied to the performance objectives of the sprint. Therefore, options iii) and iv) constitute the most appropriate acceptance criteria for Sprint 5, focusing on ensuring that the system's performance meets the set benchmarks without compromising existing functionalities.


Question 92

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 93

Which of the following is a risk that continuous integration introduces?

SELECT ONE OPTION



Answer : A

Continuous integration introduces the risk of having too many builds for testers to evaluate, potentially reducing the quality of testing. With frequent integration of new code and automated builds, testers may face challenges in keeping up with the pace, leading to less thorough testing and the possibility of defects slipping through.


Question 94

You have been asked to execute an exploratory testing session on Park & Ride system. The test charter has been titled as "Buy a bus ticket". As a result, a number of defects were reported, the titles of which are listed below.

Which defect is out of scope for the given test charter?

SELECT ONE OPTION



Answer : D

The defect titled 'Payment for parking ticket is restricted to cash only (no credit card supported)' is out of scope for the given test charter titled 'Buy a bus ticket' because it pertains to a different functionality not covered by the charter. The charter focuses on the process of purchasing a bus ticket, which involves functionality such as selecting a ticket type, choosing a journey, and completing the transaction. A defect related to payment methods for a parking ticket does not relate to these functions and is therefore considered out of scope for the testing session focused on buying a bus ticket.


Question 95

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 96

Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?

SELECT ONE OPTION



Answer : B

Option B is not true regarding the benefits of Agile processes promoting early and frequent feedback. The statement, 'Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems,' overstates the capability of Agile methodologies. While Agile practices such as Scrum and Kanban emphasize continuous feedback and collaboration to improve project outcomes and adapt to changes, they do not claim to eliminate all communication problems.

Communication challenges can arise due to various factors, including but not limited to, differences in stakeholders' perspectives, misunderstandings, and external constraints. Agile methodologies aim to reduce the impact of these challenges by promoting transparency, regular interactions, and adaptive planning. Tools like daily stand-ups, retrospectives, and sprint reviews facilitate ongoing dialogue among team members and stakeholders, helping to identify and address issues promptly. However, these practices enhance communication effectiveness rather than eliminating all potential communication problems.

In contrast, options A, C, and D accurately reflect the principles and benefits of Agile methodologies. Early and frequent feedback helps in identifying and rectifying defects and misalignments with requirements more quickly (A), improves development processes through reflective practices like retrospectives (C), and ensures that the team prioritizes work that delivers the highest value to the customer (D).

Therefore, option B is the verified answer as it presents an unrealistic expectation of Agile processes' impact on communication challenges, contradicting the Agile Manifesto's acknowledgment of the complexity and collaborative nature of software development.


Question 97

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 98

Which ONE of the following is a testable acceptance criterion?

SELECT ONE OPTION



Answer : C

A testable acceptance criterion must be specific, measurable, and verifiable, which makes option C the correct choice. Stating that 'the response time to confirm a customer submission must not exceed 5 seconds' provides a clear, quantifiable measure that can be tested to determine whether the criterion has been met. This contrasts with more subjective criteria, such as the system being 'easy to use,' which cannot be easily quantified or measured in a straightforward manner. The specificity of the response time allows for the creation of test cases that can confirm whether the system meets this particular requirement, thus making it a testable acceptance criterion.


Question 99

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 100

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 101

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customers monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

i) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

ii) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

iii) As a customer assistant I can log in to the system and change my password.

iv) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

v) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

vl) As a bank manager I can log in to the system within 10 seconds.

SELECT ONE OPTION



Answer : B

The acceptance test criteria for the user story should ensure that the system can effectively evaluate loan requests based on the specified conditions. Criteria i) and ii) allow the customer assistant to access and verify customer account history and repayment behaviors, which are essential for assessing loan eligibility as per the user story. Criteria iv) and v) enable the bank manager to review and make decisions on loan requests, aligning with the user story's stipulation that the bank manager is responsible for loan approvals. These criteria ensure the system supports both the customer assistant's preparatory role and the bank manager's decision-making role in the loan approval process.


Question 102

Which ONE of the following is a testable acceptance criterion?

SELECT ONE OPTION



Answer : C

A testable acceptance criterion must be specific, measurable, and verifiable, which makes option C the correct choice. Stating that 'the response time to confirm a customer submission must not exceed 5 seconds' provides a clear, quantifiable measure that can be tested to determine whether the criterion has been met. This contrasts with more subjective criteria, such as the system being 'easy to use,' which cannot be easily quantified or measured in a straightforward manner. The specificity of the response time allows for the creation of test cases that can confirm whether the system meets this particular requirement, thus making it a testable acceptance criterion.


Question 103

Which of the following would provide the MOST independence for testers working with agile teams?

SELECT ONE OPTION



Answer : B

In Agile project environments, embedding testers within the Agile teams promotes close collaboration, immediate feedback, and continuous improvement, essential principles of Agile methodologies. This integration enables testers to be involved in all stages of the development process, from planning and design to execution and review, facilitating early detection of defects, understanding of user requirements, and adherence to quality standards. The Agile Manifesto emphasizes individuals and interactions over processes and tools, advocating for collaborative team environments where business people and developers work together daily throughout the project. This approach contrasts with traditional methods where testing is often conducted in isolation or after development phases, potentially leading to delays and reduced quality due to the late discovery of issues.


Question 104

Which of the following statements about Agile retrospectives is CORRECT?

SELECT ONE OPTION



Answer : B


Question 105

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 106

A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations. Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?

I) A task to design the features planned for the next sprint.

ii) A task to run an acceptance test for a user story.

iii) A task to automate regression tests.

iv) A task to participate in training in preparation for the fourth sprint.

v) A task to produce a daily progress report for the agile team members.

SELECT ONE OPTION



Answer : D


Question 107

You have been asked to execute an exploratory testing session on Park & Ride system. The test charter has been titled as "Buy a bus ticket". As a result, a number of defects were reported, the titles of which are listed below.

Which defect is out of scope for the given test charter?

SELECT ONE OPTION



Answer : D

The defect titled 'Payment for parking ticket is restricted to cash only (no credit card supported)' is out of scope for the given test charter titled 'Buy a bus ticket' because it pertains to a different functionality not covered by the charter. The charter focuses on the process of purchasing a bus ticket, which involves functionality such as selecting a ticket type, choosing a journey, and completing the transaction. A defect related to payment methods for a parking ticket does not relate to these functions and is therefore considered out of scope for the testing session focused on buying a bus ticket.


Question 108

Which of the following would provide the MOST independence for testers working with agile teams?

SELECT ONE OPTION



Answer : B

In Agile project environments, embedding testers within the Agile teams promotes close collaboration, immediate feedback, and continuous improvement, essential principles of Agile methodologies. This integration enables testers to be involved in all stages of the development process, from planning and design to execution and review, facilitating early detection of defects, understanding of user requirements, and adherence to quality standards. The Agile Manifesto emphasizes individuals and interactions over processes and tools, advocating for collaborative team environments where business people and developers work together daily throughout the project. This approach contrasts with traditional methods where testing is often conducted in isolation or after development phases, potentially leading to delays and reduced quality due to the late discovery of issues.


Question 109

Which of the following statements about a test charter are CORRECT?

i) It is used mainly in exploratory tests.

ii) It is used to monitor a test process.

iii) It may make reference to user stories.

iv) It contains notes taken during a test session.

v) It is used to outline the company test policy.

SELECT ONE OPTION



Answer : A

A test charter is primarily used in exploratory testing (i) to guide the test session with a clear mission or objective, which might be related to specific functionalities, user stories, or areas of the application, making reference to user stories (iii) plausible. It also contains notes taken during the test session (iv), which are crucial for documenting observations, anomalies, and insights gained during exploratory testing. This approach aligns with Agile's emphasis on individuals and interactions and responding to change, as exploratory testing is inherently adaptive and relies on the tester's skill, creativity, and intuition. It contrasts with more traditional, documentation-heavy approaches, emphasizing the value of working software and collaboration.


Question 110

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 111

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 112

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION



Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.


Question 113

Which of the following describes the main purpose of a task management tool in agile projects?

SELECT ONE OPTION



Answer : C

In agile projects, task management tools play a crucial role in facilitating project management and team collaboration. Specifically, option C accurately describes the primary function of a task management tool in agile contexts. These tools are designed to manage and track various elements of agile projects, including user stories, tests, tasks, and more, thereby enabling teams to maintain visibility and control over the project's progress.

Agile methodologies prioritize adaptability, customer collaboration, and the delivery of value through iterative development cycles. Task management tools support these principles by providing a platform for organizing work, prioritizing tasks, and ensuring that all team members are aligned on the project's objectives and progress. This alignment is essential for maintaining the agility and responsiveness characteristic of agile projects.

For example, the Scrum framework, a popular agile methodology, involves creating a product backlog that contains all the user stories and tasks needed for the project. The task management tool would be used to track these items through various stages of development, from the backlog to in-progress, testing, and completion. This tracking ensures that the team can adapt to changes, manage workloads effectively, and deliver increments of value to the customer consistently.

In summary, option C is the verified answer as it encapsulates the essential purpose of a task management tool in agile projects, which is to manage and track user stories, tests, and other tasks, thereby supporting the agile principles of adaptability, customer collaboration, and iterative delivery of value.


Question 114

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 115

You are working in a team preparing a bank loan application. Your task is the preparation of acceptance tests for the following user story:

"IF a customer needs a loan for less than 50,000 Euros and they have made repayments regularly (without any delay) and the customers monthly income is more than 3000 Euros for the last year, THEN the bank will accept the loan request; in other cases the bank will not accept the request. A customer assistant is responsible for preparing data for approval but the approval is done by the bank manager."

Which of the following test cases can be treated as acceptance test criteria for the above user story?

i) As a customer assistant I can log in to the system and check the history of the customer account for the last year.

ii) As a customer assistant I can log in to the system and check the history of the customer debts and repayments.

iii) As a customer assistant I can log in to the system and change my password.

iv) As a bank manager I can log in to the system and receive the information of all requests waiting for approval.

v) As a bank manager I can log in to the system and decide whether to approve a loan for a customer.

vl) As a bank manager I can log in to the system within 10 seconds.

SELECT ONE OPTION



Answer : B

The acceptance test criteria for the user story should ensure that the system can effectively evaluate loan requests based on the specified conditions. Criteria i) and ii) allow the customer assistant to access and verify customer account history and repayment behaviors, which are essential for assessing loan eligibility as per the user story. Criteria iv) and v) enable the bank manager to review and make decisions on loan requests, aligning with the user story's stipulation that the bank manager is responsible for loan approvals. These criteria ensure the system supports both the customer assistant's preparatory role and the bank manager's decision-making role in the loan approval process.


Question 116

Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

SELECT ONE OPTION



Answer : B

In Agile projects, the integration of development and testing activities involves close collaboration between developers and testers, but it does not typically involve testers replacing developers in writing unit test automation scripts. Agile methodologies, such as Scrum and XP (Extreme Programming), encourage developers to write their own unit tests as part of the Test-Driven Development (TDD) process. Testers often focus on higher-level testing activities, such as acceptance testing and exploratory testing, and may work alongside developers to enhance test coverage and effectiveness. The incorrect statement about testers replacing developers in writing unit test automation scripts contradicts the Agile principle of developers being responsible for the quality of their code, which includes writing and maintaining unit tests.


Question 117

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 118

Which of the following statements about a test charter are CORRECT?

i) It is used mainly in exploratory tests.

ii) It is used to monitor a test process.

iii) It may make reference to user stories.

iv) It contains notes taken during a test session.

v) It is used to outline the company test policy.

SELECT ONE OPTION



Answer : A

A test charter is primarily used in exploratory testing (i) to guide the test session with a clear mission or objective, which might be related to specific functionalities, user stories, or areas of the application, making reference to user stories (iii) plausible. It also contains notes taken during the test session (iv), which are crucial for documenting observations, anomalies, and insights gained during exploratory testing. This approach aligns with Agile's emphasis on individuals and interactions and responding to change, as exploratory testing is inherently adaptive and relies on the tester's skill, creativity, and intuition. It contrasts with more traditional, documentation-heavy approaches, emphasizing the value of working software and collaboration.


Question 119

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 120

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION



Answer : B


Question 121

Which of the following allows a developer to define accurate unit tests focused on business needs?

SELECT ONE OPTION



Answer : A

Behavior-Driven Development (BDD) allows developers to define accurate unit tests focused on business needs by bridging the communication gap between technical and non-technical team members. BDD uses scenarios in plain language that describe the behavior of the application from the end-user's perspective, ensuring that the development focus remains on delivering features that provide real value to the business.


Question 122

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 123

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 124

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 125

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 126

What is the definition of agile software development?

SELECT ONE OPTION



Answer : A

Agile software development is characterized by its iterative and incremental approach, where development is conducted in cycles, and the work is divided into small, manageable chunks known as iterations or sprints. This approach allows for frequent reassessment of the project's direction, making it easier to incorporate changes and adapt to new information. Self-organizing, cross-functional teams are a hallmark of agile methodologies, emphasizing collaboration, flexibility, and team empowerment. This definition captures the essence of agile as described in various agile methodologies and the Agile Manifesto.


Question 127

Which of the following sentences related to Risk-based testing is CORRECT?

SELECT ONE OPTION



Answer : C

Risk-based testing is a strategic approach to testing that prioritizes testing activities based on the level of risk associated with various features or components of the software. In Agile development, this approach aligns well with the iterative and incremental nature of Agile methodologies. During both release and iteration planning, Agile teams assess and prioritize work based on risk, value, and other factors. This double layer of risk analysis allows teams to focus their testing efforts more effectively on areas that pose the greatest risk to the project's success, thereby enhancing the quality and reliability of the deliverables. This approach is consistent with Agile principles, which emphasize adaptability and the delivery of value to the customer.


Question 128

Which of the following statements is FALSE regarding early and frequent feedback?

SELECT ONE OPTION



Answer : C

Early and frequent feedback is fundamental in Agile methodologies to ensure the product meets customer needs and to identify and resolve issues promptly. However, the statement that early feedback decreases the time needed for system testing (Option C) is misleading. While early feedback helps in identifying and resolving issues at an early stage, it does not necessarily reduce the overall time required for system testing. System testing is a comprehensive phase that assesses the system's compliance with the specified requirements. Agile practices, such as continuous integration and testing, aim to maintain a high quality throughout the development process, but they do not eliminate the need for thorough system testing to validate the product before release.


Question 129

Which of the following would provide the MOST independence for testers working with agile teams?

SELECT ONE OPTION



Answer : B

In Agile project environments, embedding testers within the Agile teams promotes close collaboration, immediate feedback, and continuous improvement, essential principles of Agile methodologies. This integration enables testers to be involved in all stages of the development process, from planning and design to execution and review, facilitating early detection of defects, understanding of user requirements, and adherence to quality standards. The Agile Manifesto emphasizes individuals and interactions over processes and tools, advocating for collaborative team environments where business people and developers work together daily throughout the project. This approach contrasts with traditional methods where testing is often conducted in isolation or after development phases, potentially leading to delays and reduced quality due to the late discovery of issues.


Question 130

You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework. Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?

SELECT ONE OPTION



Answer : D

Cross-functional teamwork is a cornerstone of Agile methodologies, emphasizing the collaboration of team members with diverse expertise to enhance project outcomes. In Agile frameworks like Scrum, teams are encouraged to be self-organizing and multidisciplinary, with each member contributing to all project areas, including testing, regardless of their primary role. This approach promotes a shared responsibility for the project's success, fosters a deeper understanding of the project from multiple perspectives, and enhances the team's ability to respond to changes effectively. It aligns with Agile principles that advocate for the best architectures, requirements, and designs emerging from self-organizing teams, underscoring the value of collective ownership and collaboration in achieving project goals.


Question 131

Which of the following activities are done in release planning?

i. Identifying testable user stories with acceptance criteria.

ii. Elaborating the user stories into tasks.

iii. Prioritizing the user stories.

iv. Creating acceptance tests for the user stories.

v. Analyzing risks for each of the user stories.

vi. Performing high level estimation for the release.

SELECT ONE OPTION



Answer : A

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.


Question 132

Which tasks are typically performed by a tester on an Agile project?

i) Implementing test strategy.

ii) Documenting business requirements.

iii) Measuring and reporting test coverage.

iv) Coaching development team in relevant aspects of testing.

v) Executing test-driven development tests.

SELECT ONE OPTION



Answer : A

In an agile project, testers often perform tasks beyond traditional testing roles, including implementing test strategy (i), measuring and reporting test coverage (iii), and coaching the development team on relevant aspects of testing (iv). Implementing test strategy involves planning how testing will be conducted within the agile framework, ensuring that testing aligns with agile principles and practices. Measuring and reporting test coverage help the team understand the extent to which the codebase is tested, which is crucial for maintaining quality in fast-paced agile environments. Coaching the development team involves sharing knowledge on testing best practices and fostering a quality-centric mindset across the team. These activities contribute to the collaborative and iterative nature of agile projects, where continuous feedback and improvement are emphasized.


Question 133

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 134

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 135

Which ONE of the following is a testable acceptance criterion?

SELECT ONE OPTION



Answer : C

A testable acceptance criterion must be specific, measurable, and verifiable, which makes option C the correct choice. Stating that 'the response time to confirm a customer submission must not exceed 5 seconds' provides a clear, quantifiable measure that can be tested to determine whether the criterion has been met. This contrasts with more subjective criteria, such as the system being 'easy to use,' which cannot be easily quantified or measured in a straightforward manner. The specificity of the response time allows for the creation of test cases that can confirm whether the system meets this particular requirement, thus making it a testable acceptance criterion.


Question 136

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 137

Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

SELECT ONE OPTION



Answer : B

In Agile projects, the integration of development and testing activities involves close collaboration between developers and testers, but it does not typically involve testers replacing developers in writing unit test automation scripts. Agile methodologies, such as Scrum and XP (Extreme Programming), encourage developers to write their own unit tests as part of the Test-Driven Development (TDD) process. Testers often focus on higher-level testing activities, such as acceptance testing and exploratory testing, and may work alongside developers to enhance test coverage and effectiveness. The incorrect statement about testers replacing developers in writing unit test automation scripts contradicts the Agile principle of developers being responsible for the quality of their code, which includes writing and maintaining unit tests.


Question 138

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 139

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 140

During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

SELECT ONE OPTION



Answer : C

Agile retrospectives focus on the process, practices, and tools, rather than personal critiques. The effectiveness of a retrospective lies in its ability to foster a positive, constructive environment where the team can discuss what worked well, what didn't, and how to improve going forward. Focusing on an individual's perceived shortcomings, such as being 'disruptive and lazy' (Option C), does not align with the Agile principle of building projects around motivated individuals and trusting them to get the job done. It could lead to a negative atmosphere, reducing the team's willingness to openly share and collaborate on solutions. Instead, retrospectives should concentrate on actionable items that can lead to process improvements, such as addressing frequent automation test failures, discrepancies in effort estimations, and delays in the build process, as mentioned in options A, B, and D respectively.


Question 141

You have been asked to explain to your client how to define acceptance criteria that are fully testable. Which of the following is the BEST EXAMPLE for testable acceptance criteria?

SELECT ONE OPTION



Answer : B


Question 142

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 143

During a retrospective, which of the following items would be the LEAST effective to generate discussions on process improvement?

SELECT ONE OPTION



Answer : C

Agile retrospectives focus on the process, practices, and tools, rather than personal critiques. The effectiveness of a retrospective lies in its ability to foster a positive, constructive environment where the team can discuss what worked well, what didn't, and how to improve going forward. Focusing on an individual's perceived shortcomings, such as being 'disruptive and lazy' (Option C), does not align with the Agile principle of building projects around motivated individuals and trusting them to get the job done. It could lead to a negative atmosphere, reducing the team's willingness to openly share and collaborate on solutions. Instead, retrospectives should concentrate on actionable items that can lead to process improvements, such as addressing frequent automation test failures, discrepancies in effort estimations, and delays in the build process, as mentioned in options A, B, and D respectively.


Question 144

Which of the following sentences about the integration of development and testing activities in Agile projects is INCORRECT?

SELECT ONE OPTION



Answer : B

In Agile projects, the integration of development and testing activities involves close collaboration between developers and testers, but it does not typically involve testers replacing developers in writing unit test automation scripts. Agile methodologies, such as Scrum and XP (Extreme Programming), encourage developers to write their own unit tests as part of the Test-Driven Development (TDD) process. Testers often focus on higher-level testing activities, such as acceptance testing and exploratory testing, and may work alongside developers to enhance test coverage and effectiveness. The incorrect statement about testers replacing developers in writing unit test automation scripts contradicts the Agile principle of developers being responsible for the quality of their code, which includes writing and maintaining unit tests.


Question 145

What is the definition of agile software development?

SELECT ONE OPTION



Answer : A

Agile software development is characterized by its iterative and incremental approach, where development is conducted in cycles, and the work is divided into small, manageable chunks known as iterations or sprints. This approach allows for frequent reassessment of the project's direction, making it easier to incorporate changes and adapt to new information. Self-organizing, cross-functional teams are a hallmark of agile methodologies, emphasizing collaboration, flexibility, and team empowerment. This definition captures the essence of agile as described in various agile methodologies and the Agile Manifesto.


Question 146

In a sprint planning, the product owner presents a user story written on a card. The team starts having a discussion with the product owner to get an understanding on how the software should work.

The user story written on the card is:

"As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email."

By applying the 3C concept, which ONE of the following statements is CORRECT?

SELECT ONE OPTION



Answer : A

The 3C concept in Agile development refers to Card, Conversation, and Confirmation. This concept emphasizes the collaborative and iterative nature of defining user stories and their acceptance criteria in Agile projects. In the context of the provided user story, 'As a customer, I want to subscribe to the mailing list so that I can receive the latest deal in an email,' option A is correct. The conversation should include the acceptance criteria discussion, which is an integral part of the 3C concept.

The Card represents the user story itself, which is a brief statement describing a feature or requirement from the user's perspective. The Conversation involves discussions between the development team and the product owner (or other stakeholders) to clarify the details and ensure a mutual understanding of the user story. This conversation is crucial for exploring the user story's implications, discussing potential implementation approaches, and agreeing on the acceptance criteria that define when the story is considered complete and satisfactory.

Confirmation involves agreeing on and documenting the acceptance criteria that emerge from the conversation. These criteria serve as a checklist to ensure that the implemented feature meets the user's needs and expectations as defined in the user story.

Option A is the verified answer because it accurately reflects the importance of including acceptance criteria discussions in the conversation phase of the 3C concept. This practice aligns with Agile principles by ensuring clarity, shared understanding, and a focus on delivering value to the customer.


Question 147

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 148

Which ONE of the following is an example of a typical "Business-oriented work product"?

SELECT ONE OPTION



Answer : C

In Agile projects, a 'Business-oriented work product' refers to any deliverable that provides business value or is directly usable by the end users or stakeholders of the project. Among the options provided, a user manual is a typical example of a business-oriented work product because it is designed for end users, helping them understand and use the product effectively. Other options, such as the released product itself, acceptance testing criteria, and usability test results, while important, do not fit the definition of a business-oriented work product in the same direct manner as a user manual does.


Question 149

Which agile development approach incorporates the following practices:

- a project is divided into iterations called sprints

- each sprint results in a potentially releasable/shippable product?

SELECT ONE OPTION



Answer : C

Scrum is the agile development approach that incorporates the practice of dividing a project into iterations called sprints, with each sprint resulting in a potentially releasable/shippable product. Scrum's iterative and incremental approach allows teams to deliver working software frequently, with a focus on delivering tangible value to the customer at the end of each sprint.


Question 150

Which of the following activities are done in release planning?

i. Identifying testable user stories with acceptance criteria.

ii. Elaborating the user stories into tasks.

iii. Prioritizing the user stories.

iv. Creating acceptance tests for the user stories.

v. Analyzing risks for each of the user stories.

vi. Performing high level estimation for the release.

SELECT ONE OPTION



Answer : A

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.


Question 151

You are a tester in an agile team. The user story you are due to test is still under development so your tests are blocked. The main issue holding progress on this user story is that the developer's unit tests are constantly failing.

As an agile tester, which of the following actions should you take?

SELECT ONE OPTION



Answer : C

In Agile teams, collaboration and direct communication are key. When faced with blocked tests due to ongoing development or failing unit tests, an agile tester should collaborate with the developer to identify and resolve the issues. This approach encourages teamwork, knowledge sharing, and problem-solving, leading to more efficient and effective resolution of blocking issues.


Question 152

Which of the following statements about a test charter are CORRECT?

i) It is used mainly in exploratory tests.

ii) It is used to monitor a test process.

iii) It may make reference to user stories.

iv) It contains notes taken during a test session.

v) It is used to outline the company test policy.

SELECT ONE OPTION



Answer : A

A test charter is primarily used in exploratory testing (i) to guide the test session with a clear mission or objective, which might be related to specific functionalities, user stories, or areas of the application, making reference to user stories (iii) plausible. It also contains notes taken during the test session (iv), which are crucial for documenting observations, anomalies, and insights gained during exploratory testing. This approach aligns with Agile's emphasis on individuals and interactions and responding to change, as exploratory testing is inherently adaptive and relies on the tester's skill, creativity, and intuition. It contrasts with more traditional, documentation-heavy approaches, emphasizing the value of working software and collaboration.


Question 153

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 154

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 155

Which of the following is a risk that continuous integration introduces?

SELECT ONE OPTION



Answer : A

Continuous integration introduces the risk of having too many builds for testers to evaluate, potentially reducing the quality of testing. With frequent integration of new code and automated builds, testers may face challenges in keeping up with the pace, leading to less thorough testing and the possibility of defects slipping through.


Question 156

Which of the following statements about the Planning poker test estimate technique are CORRECT?

i) Planning poker is a consensus based technique using a deck of cards.

ii) A low test estimate usually means the story should be broken down into multiple smaller stories.

iii) A high test estimate usually means the story should be broken down into multiple smaller stories.

iv) One poker round is played and then consensus has to be reached.

v) The risk level of each backlog item should be decided before the poker session.

SELECT ONE OPTION



Answer : C

Planning poker, a consensus-based estimation technique used in Agile planning sessions, involves team members making estimates by playing numbered cards face-down to the table, avoiding the influence of other participants. This process promotes a collective understanding and agreement on effort estimations. Statements i, ii, and iii accurately reflect the principles of Planning Poker. It's a consensus-based technique (i), and if the estimates are too high (iii) or too low (ii), it often indicates that the user story is not well understood or is too complex, suggesting it should be broken down into smaller, more manageable pieces. This approach aligns with Agile's preference for small, incremental changes that can be easily managed and adapted, fostering collaboration and collective decision-making within the team.


Question 157

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION



Answer : B


Question 158

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 159

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 160

Which of the following activities are done in release planning?

i. Identifying testable user stories with acceptance criteria.

ii. Elaborating the user stories into tasks.

iii. Prioritizing the user stories.

iv. Creating acceptance tests for the user stories.

v. Analyzing risks for each of the user stories.

vi. Performing high level estimation for the release.

SELECT ONE OPTION



Answer : A

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.


Question 161

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 162

Which of the following statements about Agile retrospectives is CORRECT?

SELECT ONE OPTION



Answer : B


Question 163

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 164

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION



Answer : B


Question 165

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION



Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

These values emphasize the importance of people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.


Question 166

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 167

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 168

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 169

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION



Answer : B

An Agile task board is a visual management tool used by Agile teams to track the progress of work items during an iteration or sprint. It typically includes columns for different stages of work (e.g., To Do, In Progress, Done) and cards or sticky notes representing individual tasks or user stories. The task board provides a detailed visual representation of the whole team's status, allowing team members and stakeholders to quickly see what work is in progress, what has been completed, and what is yet to be started. This visibility supports transparency, one of the core values of Agile, and facilitates communication and collaboration within the team. The task board is updated regularly, often daily during stand-up meetings, to reflect the most current status of the work.


Question 170

Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

i) User access for all roles has been validated.

ii) A static analysis tool has been executed for all code.

iii) 100% of the existing regression test suite has passed.

Iv) System is responding In less than 3 seconds, 90% of the time.

v) A new version of Internet Explorer has been included.

SELECT ONE OPTION



Answer : B

The acceptance criteria for a sprint focused on improving the performance of a system, like the one described for Sprint 5, typically include ensuring that the system meets specific performance benchmarks and that the functionality implemented in previous sprints continues to work as expected. Therefore, the most relevant acceptance criteria for such a sprint would be:

iii) '100% of the existing regression test suite has passed.' This criterion ensures that the new performance enhancements have not adversely affected the existing functionalities of the system. It's a common practice in agile projects to maintain the integrity and quality of the system by running regression tests. This is supported by the notion that continuous testing and quality assurance are integral components of agile methodologies, ensuring that each increment of the project maintains and improves the quality of the product (Source: Agile Project Management methodologies).

iv) 'System is responding in less than 3 seconds, 90% of the time.' This criterion directly addresses the goal of the sprint, which is to increase the performance of the system. Setting a specific target for response times is a quantifiable and testable way to measure the improvement in performance. This aligns with agile principles, which emphasize delivering valuable, working software and encourage adaptive planning and continuous improvement. Performance targets like these help the team focus on delivering specific, valuable improvements to the system (Source: Principles behind the Agile Manifesto).

Options i) and v) are less relevant to the specific focus of Sprint 5, which is on performance improvement, and more about user roles and software compatibility, which are not directly tied to the performance objectives of the sprint. Therefore, options iii) and iv) constitute the most appropriate acceptance criteria for Sprint 5, focusing on ensuring that the system's performance meets the set benchmarks without compromising existing functionalities.


Question 171

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION



Answer : A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Question 172

A calculator application is being developed. The third sprint has been planned to add functionality to the calculator to allow scientific calculations. Which TWO examples below represent activities that would likely be managed on an agile task board for the third sprint?

I) A task to design the features planned for the next sprint.

ii) A task to run an acceptance test for a user story.

iii) A task to automate regression tests.

iv) A task to participate in training in preparation for the fourth sprint.

v) A task to produce a daily progress report for the agile team members.

SELECT ONE OPTION



Answer : D


Question 173

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

SELECT ONE OPTION



Answer : B

Exploratory testing in an agile environment involves the creative and intuitive testing of software without the constraints of predefined test cases. Time-boxed sessions, typically not exceeding 2 hours, are used to maintain focus and efficiency. Test charters guide these sessions, providing direction while still allowing for flexibility and adaptability in testing approaches. This method leverages the skills and experience of testers to uncover issues that might not be identified through traditional scripted testing, aligning with the agile emphasis on individuals and interactions over processes and tools.


Question 174

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 175

You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework. Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?

SELECT ONE OPTION



Answer : D

Cross-functional teamwork is a cornerstone of Agile methodologies, emphasizing the collaboration of team members with diverse expertise to enhance project outcomes. In Agile frameworks like Scrum, teams are encouraged to be self-organizing and multidisciplinary, with each member contributing to all project areas, including testing, regardless of their primary role. This approach promotes a shared responsibility for the project's success, fosters a deeper understanding of the project from multiple perspectives, and enhances the team's ability to respond to changes effectively. It aligns with Agile principles that advocate for the best architectures, requirements, and designs emerging from self-organizing teams, underscoring the value of collective ownership and collaboration in achieving project goals.


Question 176

Which of the following is a risk that continuous integration introduces?

SELECT ONE OPTION



Answer : A

Continuous integration introduces the risk of having too many builds for testers to evaluate, potentially reducing the quality of testing. With frequent integration of new code and automated builds, testers may face challenges in keeping up with the pace, leading to less thorough testing and the possibility of defects slipping through.


Question 177

Which tasks are typically performed by a tester on an Agile project?

i) Implementing test strategy.

ii) Documenting business requirements.

iii) Measuring and reporting test coverage.

iv) Coaching development team in relevant aspects of testing.

v) Executing test-driven development tests.

SELECT ONE OPTION



Answer : A

In an agile project, testers often perform tasks beyond traditional testing roles, including implementing test strategy (i), measuring and reporting test coverage (iii), and coaching the development team on relevant aspects of testing (iv). Implementing test strategy involves planning how testing will be conducted within the agile framework, ensuring that testing aligns with agile principles and practices. Measuring and reporting test coverage help the team understand the extent to which the codebase is tested, which is crucial for maintaining quality in fast-paced agile environments. Coaching the development team involves sharing knowledge on testing best practices and fostering a quality-centric mindset across the team. These activities contribute to the collaborative and iterative nature of agile projects, where continuous feedback and improvement are emphasized.


Question 178

User Story: As a user I want to be able to calculate tax percentage based on amount of income.

What is the best black box test design technique for verifying the accuracy of this user story?

SELECT ONE OPTION



Answer : B

Equivalence partitioning is a black box test design technique suitable for verifying the accuracy of user stories like the one described. It involves dividing input data of a software unit into partitions of equivalent data from which test cases can be derived. For a user story involving tax percentage calculation based on income, Equivalence Partitioning allows the creation of test cases for different income ranges (low, medium, high) to ensure that the system accurately calculates tax percentages for each partition, thus covering various scenarios within the application's functionality.


Question 179

Iteration planning for Sprint 5 of your current project is complete. The plan for the sprint is to increase performance of the system, which of the following acceptance criteria would you expect for Sprint 5?

i) User access for all roles has been validated.

ii) A static analysis tool has been executed for all code.

iii) 100% of the existing regression test suite has passed.

Iv) System is responding In less than 3 seconds, 90% of the time.

v) A new version of Internet Explorer has been included.

SELECT ONE OPTION



Answer : B

The acceptance criteria for a sprint focused on improving the performance of a system, like the one described for Sprint 5, typically include ensuring that the system meets specific performance benchmarks and that the functionality implemented in previous sprints continues to work as expected. Therefore, the most relevant acceptance criteria for such a sprint would be:

iii) '100% of the existing regression test suite has passed.' This criterion ensures that the new performance enhancements have not adversely affected the existing functionalities of the system. It's a common practice in agile projects to maintain the integrity and quality of the system by running regression tests. This is supported by the notion that continuous testing and quality assurance are integral components of agile methodologies, ensuring that each increment of the project maintains and improves the quality of the product (Source: Agile Project Management methodologies).

iv) 'System is responding in less than 3 seconds, 90% of the time.' This criterion directly addresses the goal of the sprint, which is to increase the performance of the system. Setting a specific target for response times is a quantifiable and testable way to measure the improvement in performance. This aligns with agile principles, which emphasize delivering valuable, working software and encourage adaptive planning and continuous improvement. Performance targets like these help the team focus on delivering specific, valuable improvements to the system (Source: Principles behind the Agile Manifesto).

Options i) and v) are less relevant to the specific focus of Sprint 5, which is on performance improvement, and more about user roles and software compatibility, which are not directly tied to the performance objectives of the sprint. Therefore, options iii) and iv) constitute the most appropriate acceptance criteria for Sprint 5, focusing on ensuring that the system's performance meets the set benchmarks without compromising existing functionalities.


Question 180

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION



Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.


Question 181

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION



Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.


Question 182

Which of the following activities are done in release planning?

i. Identifying testable user stories with acceptance criteria.

ii. Elaborating the user stories into tasks.

iii. Prioritizing the user stories.

iv. Creating acceptance tests for the user stories.

v. Analyzing risks for each of the user stories.

vi. Performing high level estimation for the release.

SELECT ONE OPTION



Answer : A

In release planning for Agile project management, activities such as identifying testable user stories with acceptance criteria (i), prioritizing the user stories (iii), and performing high-level estimation for the release (vi) are essential. These activities ensure that the team has a clear understanding of what needs to be delivered, the order of importance of the deliverables, and an estimate of the effort required to achieve the release goals.


Page:    1 / 14   
Total 40 questions