New ISTQB ISTQB-Agile-Public Dumps & Questions Updated on 2024
Dumps to Pass your ISTQB-Agile-Public Exam with 100% Real Questions and Answers
NEW QUESTION # 10
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
- A. Acceptance test criteria are i, ii, iii and vi
- B. Acceptance test criteria are ii, iv, v and vi
- C. Acceptance test criteria are i, ii, iv and v
- D. Acceptance test criteria are i, iii, iv and v
Answer: C
Explanation:
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.
NEW QUESTION # 11
Which of the following is a risk that continuous integration introduces?
SELECT ONE OPTION
- A. Developer's workload is increased, which can result in a reduction of output.
- B. Teams no longer have the ability to run manual tests, as all tests must be automated.
- C. Testers sometimes have too many builds to test, which reduces the quality of testing.
- D. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
Answer: C
Explanation:
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.
NEW QUESTION # 12
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
- A. Work together with the developer, suggesting reasons why the tests are failing.
- B. Create a bug report for each of your blocked tests.
- C. Review the design of the problematic user story and improve it where possible.
- D. Use the time to improve and automate existing test cases of other user stories.
Answer: A
Explanation:
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.
NEW QUESTION # 13
Which of the following statements would you expect to be the MOST direct advantage of the whole-team approach?
SELECT ONE OPTION
- A. Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.
- B. Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.
- C. Having at least once a day an automated build and test process that detects integration errors early and quickly.
- D. Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.
Answer: A
NEW QUESTION # 14
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
- A. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
- B. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
- C. ( ) Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
- D. Co located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
Answer: A
Explanation:
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.
NEW QUESTION # 15
What is the definition of agile software development?
SELECT ONE OPTION
- A. A way of developing software where the test cases are developed, and often automated, before the software under test is developed.
- B. A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready.
- C. A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.
- D. Testing carried out informally where no formal test preparation or execution takes place, no recognized test design technique is used and there are no expectations for results.
Answer: C
Explanation:
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.
NEW QUESTION # 16
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
- A. ii, iii, iv
- B. i, ii, iii
- C. ii. iv
- D. i, iii. v
Answer: B
Explanation:
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.
NEW QUESTION # 17
Which of the following statements about the benefits of the Agile processes promoting early and frequent feedback is NOT true?
SELECT ONE OPTION
- A. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
- B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
- C. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
- D. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
Answer: C
Explanation:
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.
NEW QUESTION # 18
Which of the following allows a developer to define accurate unit tests focused on business needs?
SELECT ONE OPTION
- A. Design-Driven Development
- B. Acceptance Test-Driven Development
- C. Behavior-Driven Development
- D. Test-Driven Development
Answer: C
Explanation:
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.
NEW QUESTION # 19
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
- A. ii, iii, iv
- B. ii. v
- C. ii, iv, v
- D. i, iii, iv
Answer: D
Explanation:
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.
NEW QUESTION # 20
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
- A. Work together with the developer, suggesting reasons why the tests are failing.
- B. Create a bug report for each of your blocked tests.
- C. Review the design of the problematic user story and improve it where possible.
- D. Use the time to improve and automate existing test cases of other user stories.
Answer: A
Explanation:
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.
NEW QUESTION # 21
Which of the following is NOT a statement of value from the Agile Manifesto?
SELECT ONE OPTION
- A. software over comprehensive documentation.
- B. Customer collaboration over contract negotiation.
- C. Processes and tools over individuals and interactions.
- D. Responding to change over following a plan.
Answer: C
Explanation:
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.
NEW QUESTION # 22
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
- A. Scrum
- B. Continuous Integration
- C. Kanban
- D. Extreme Programming
Answer: A
Explanation:
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.
NEW QUESTION # 23
Which of the following sentences related to Risk-based testing is CORRECT?
SELECT ONE OPTION
- A. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
- B. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
- C. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- D. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
Answer: D
Explanation:
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.
NEW QUESTION # 24
Which of the following statements is FALSE regarding early and frequent feedback?
SELECT ONE OPTION
- A. Early feedback helps to deliver a product that better reflects what the customer wants.
- B. Early feedback promotes early discovery and resolution of quality problems.
- C. Early feedback decreases the amount of time needed for system testing.
- D. Early feedback provides the Agile team with information on its productivity.
Answer: C
Explanation:
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.
NEW QUESTION # 25
......
Updated Exam ISTQB-Agile-Public Dumps with New Questions: https://www.fast2test.com/ISTQB-Agile-Public-premium-file.html
Today Updated ISTQB-Agile-Public Exam Dumps Actual Questions: https://drive.google.com/open?id=1C43rflBQ6U-YTtUIy4jdftUMv83-Tez3