ISTQB Agile Tester Extension Exam Crash Course Part 12
The following user-friendly questions prepared according to different K-Levels are of great help in reviewing your skills before appearing in ISTQB Agile Tester Extension Certification exam as per the latest syllabus.
Set of 10 Questions (Q. 111 to 120) with Explanation in Favour of the Correct Answer
The Correct Answer option has been Hi-lighted in Yellow.
Q. 111: (Level K2) Consider the following user story: “As a bank teller, I would like to be able to view all of my customer’s bank transactions on the screen, so I can answer his/her questions”.
Out of the following which can be considered as relevant acceptance test cases?
i. Login as a bank teller, get the customer’s account balance for all open accounts.
ii. Login as a bank teller, enter a customer account ID, get his transactions history on the screen.
iii. Login as a bank teller, request customer account ID by using name abbreviations, and get his transaction history on the screen.
iv. Login as a bank teller, enter a customer IBAN (international bank account number), get his transaction history on the screen.v. Login as a Bank Teller, enter a customer Account ID, get the transactions history in less than 3 seconds on screen.
A. i, ii, iv
B. i, iii, iv
C. ii, iv, v
D. ii, iii, iv
Explanation in favor of the correct answer:
By the process of elimination of illogical test cases, test cases described in (ii), (iii) & (iv) are true under the scenario.
<<<<<< =================== >>>>>>
Q. 112: (Level K2) Consider the following user story:
“As a bank customer, I can easily view my bank statements for the last 5 years”
“For all customers, the system must display all queries in less than 4 seconds, 90% of the time” And the associated test cases:
Test Case 1: Login as the bank customer. Verify that the customer transaction history is available for the last 5 years.
Test Case 2: Verify in a realistic environment that the customer can view the statement in less than 4 seconds. Which TWO test quadrants would the above test cases be part of?
A. Q1 unit level, technology facing & Q2 system level, business facing.
B. Q2 system level, business facing & Q3 system or user acceptance level, business facing.
C. Q1 unit level, technology facing & Q4 system or operation acceptance level, technology facing.
D. Q2 system level, business facing & Q4 system or operation acceptance level, technology facing.
Explanation in favor of the correct answer:
Q1 is Incorrect – as these test cases are not technology-facing component tests.
Q2 is Correct – as system level is part of the 2nd quadrant.
Q3 is Incorrect – as these test cases are not user acceptance level tests.
Q4 is Correct – as performance testing is part of the 4th quadrant.
<<<<<< =================== >>>>>>
Q. 113: (Level K2) In the release planning session the tester is communicating the test ideas using testing quadrants so that the team understands the purpose of all the test types and test levels included in the development lifecycle.
Out of the following which tester statements about testing quadrants are true?
A. Quadrant Q1 are unit level tests and Quadrant Q4 are functional tests.
B. Quadrant Q1 are unit level tests and Quadrant Q4 are user acceptance tests.
C. Quadrant Q3 are performance tests and Quadrant Q4 are functional tests.
D. Quadrant Q2 are functional tests and Quadrant Q4 are performance tests.
Explanation in favor of the correct answer:
Quadrant Q1 is unit level, technology facing, and supports the developers.
Quadrant Q2 is system/functional level, business facing, and confirms product behavior.
Quadrant Q3 is user acceptance level, business facing, and contains tests that critique the product.
Quadrant Q4 is the system or operational acceptance level, technology facing, and contains tests that critique the product.
<<<<<< =================== >>>>>>
Q. 114: (Level K3) In the New Agile team the testers and developers are sitting together but the product owners are based in a different location though they participate in all daily stand-up and planning meetings and retrospectives.
Some of the testers are new to the Agile project and they are not able to cope with the changes coming during each iteration. The product owner has found a couple of instances where the testing team has not followed the testing strategy agreed to by the team during test execution.
What does organizational and behavioral best practices the team lack?
A. Self-organizing, Empowered, Credible
B. Self-organizing, Resilience, Committed
C. Cross-functional, Empowered, Credible
D. Co-located, Collaborative, Committed
E. Co-located, Resilience, Credible
Explanation in favor of the correct answer:
Co-located: Testers jointly collaborate with the developers and the product owner.
Resilience: Testing must be able to respond to changes.
Credible: The tester must ensure the credibility of the testing strategy.
<<<<<< =================== >>>>>>
Q. 115: (Level K3) Review the Agile team descriptions followed by organization and behavioral practices and then answer the question.
1. Team (A): The team has agreed upon a Test process In the Release planning session but the testers are not following it for some of the testing activities in order to finish all stories included in the sprints.
2. Team (B): The testers actively participate in all daily stand-up and planning meetings but they are not invited to the retrospective meeting happening at the end of each iteration.
3. Team (C): The testers are reporting the testing progress to their Test Manager but the team is not using Agile task board for monitoring the development and testing tasks.
4. Team (D): The testers are new to the Agile methodology and they are not able to keep up with the changes during each iteration.
I. Transparent
II. Open to Feedback
III. Resilience
IV. Credible
Match the teams with the organizational and behavioral practices they are lacking?
A.1-iii, 2-ii, 3-i, 4-iv
B.1-ii, 2-iii, 3-i, 4-iv
C.1-iv, 2-i, 3-ii, 4-iii
D.1-iv, 2-ii, 3-i, 4-iii
Explanation in favor of the correct answer:
1. Testers in Team (A) are missing credibility.
2. Team (B) is not open to feedback as the testers are not participating in the retrospectives.
3. Team (C) is not transparent as the progress of activities is not shared among the team.
4. Team (D) is not resilient as testers are not able to respond to changes.
<<<<<< =================== >>>>>>
Q. 116: (Level K3) There is a new feature in scope for the current sprint which will result in changes to the existing database tables. The testers on the team realize that this change can introduce bugs and it may require major changes in the existing scripts and the automation framework.
What is the best course of action for the testers to take?
A. The testers will calculate the extra time required and update the team that they have to work extra hours in order to update the existing test scripts and automation framework In the existing sprint plan.
B. The testers will notify the team of the issue. A risk analysis is done and the team decides what regression testing must be performed to find the defects introduced by the new changes. The testers will update the sprint plan by adding tasks to modify the framework and scripts to support the new changes.
C. The current testing tasks need to be completed for the sprint. The testers continue with their existing sprint plan and make no changes to the test automation framework or scripts.
D. The testers will stop what they are doing and start working on the automation framework & script modifications and communicate with the team that any other testing work for the sprint will have to be pushed to the next iteration.
Explanation in favor of the correct answer:
Option (A) is False – as risk analysis should be done including the whole team and a collaborative decision should be made.
Option (B) is True – as the decision to modify the test automation framework and scripts should be done collaboratively with the whole team. The tester is then responsible to make changes to the iteration plan as required.
Option (C) is False – as the tester must notify the team who will then decide what to do with the issue.
Option (D) is False – as tester alone must not be made responsible to determine the scope of work. This issue will be addressed by creating a new user story or modifying an existing user story and will be addressed by the entire team during sprint planning.
<<<<<< =================== >>>>>>
Q. 117: (Level K3) Agile team is doing the quality risk analysis for the following user stories selected from the backlog items In an iteration planning session.
Match the stories with their respective quality risk based on the information below:
User Story 1: A program to calculate account interest information for the financial end of year report.
User Story 2: A program to display search results in less than 3 secs.
User Story 3: A program to work on different operating systems.
A. User Story 1: Security, User Story 2: Functional, User Story 3: Recoverability
B. User Story 1: Security, User Story 2: performance, User Story 3: Compatibility
C. User Story 1: Functional, User Story 2: performance, User Story 3: Compatibility
D. User Story 1: Functional, User Story 2: performance, User Story 3: Recoverability
Explanation in favor of the correct answer:
User Story 1: Incorrect calculation (accuracy) in the report is a functional risk.
User Story 2: Storing customer sensitive information is a performance risk.
User Story 3: Working on the different operating system is a compatibility risk.
<<<<<< =================== >>>>>>
Q. 118: (Level K3) Agile team is doing the quality risk analysis for three user stories selected from the backlog during an iteration planning session.
Match the stories with their respective quality risk based on the information below:
User Story 1: Program to calculate the account interest information for the financial end of year report.
User Story 2: Program to store the customer sensitive information.
User Story 3: A front-end screen for the system used by senior citizens.
A. User Story 1: Security, User Story 2: Functional, User Story 3: Usability
B. User Story 1: Functional, User Story 2: Security, User Story 3: Usability
C. User Story 1: Usability, User Story 2: Security, User Story 3: Functional
D. User Story 1: Functional, User Story 2: Usability, User Story 3: Security
Explanation in favor of the correct answer:
User Story 1: Calculation (accuracy) in report is a functional risk
User Story 2: Storing customer sensitive information is a security risk
User Story 3: Difficulty in understanding screens for the users (senior citizens) is a usability risk
<<<<<< =================== >>>>>>
Q. 119: (Level K3) In the quality risk analysis session, of iteration planning, the Agile team identified the quality risk for each story and the level of risk based on the impact and likelihood of defects
# User story 1 (Functional): Likelihood: high, Impact: high
# User story 2 (Security): Likelihood: low, Impact: medium
# User story 3 (Performance): Likelihood: high, Impact: medium
# User story 4 (Functional): Likelihood: low, Impact: low
# User story 5 (Recoverability): Likelihood: low, Impact: medium
How can the team mitigate these risks during the iteration?
Select TWO options.
A. The tasks associated with user story 1 should be started first.
B. The tasks associated with user story 4 should be started last.
C. The tasks associated with user story 3 should be started first.
D. The tasks associated with user story 2 should be started last.
E. The tasks associated with user story 5 should be started last.
Explanation in favor of the correct answer:
Option (A) is correct – as user story 1 has the highest level of risk so it should be started first.
Option (B) is correct – as user story 4 has the lowest level of risk so it should be started last.
Option (C) is incorrect – as user story 3 does not have the highest level of risk.
Option (D) is incorrect – as user story 2 does not have the lowest level of risk.
Option (E) is incorrect – as user story 5 does not have the lowest level of risk.
<<<<<< =================== >>>>>>
Q. 120: (Level K3) Given the following results from a product risk analysis that occurred at the beginning of an iteration:
# User story 1 (Performance): Likelihood: high, Impact: high
# User story 2 (Security): Likelihood: high, Impact: high
# User story 3 (Functional): Likelihood: medium, Impact: high
# User story 4 (Functional): Likelihood: high, Impact: medium
# User story 5 (Compatibility): Likelihood: low, Impact: low
# User story 6 (Recoverability): Likelihood: low, Impact: low
Which out of the following TWO describes best what the team should do with this information?
Select TWO options.
A. Move onto planning poker session to estimate effort for user stories, and determine what can be done in the current iteration, and what needs to be added to the backlog.
B. Remove user stories 5 and 6 from the current iteration and move to a later iteration.
C. Because of the number of high likelihood, high impact risks slotted for this iteration, the team has no choice but to extend the timeframe of the iteration by 2 weeks.
D. The team should collaborate on effective ways to mitigate the high likelihood, high impact risks
E. The team should plan to complete all items in the current sprint, but save the lower risk items for the end of the sprint, and only test these items if there is time.
Continue to Crash Course Part 13
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.