ISTQB-Agile-Public Exam Practice Test Instant Access

Question 1

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

AState transition testing. Test the transitions between the following states: logging In. inserting the power of the vehicle, making payment, logging out

BUse case testing.
Test the following use case (Actor=registered user):
Pre-condition=registered user logged in
Scenario=registered user inserts the power of the vehicle, making payment and logs out
Post-condition=car tax paid and registered user logged out

CDecision table testing. Test the following conditions:
Condltions=reglstered user logged In; inserted power of the vehlcle=20kW;
Action=Car tax paid

DEquivalence partitioning. Test the annual car tax value for the following partitions: [power of the vehicle<20 kW; 20 kW ?power of the vehicle?! 50 kW; power of the vehicle>150 kW]

Answer : C

Question 2

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

Aiv, v

Bi. iv

Ci. v

Dii, iii

Answer : D

Question 3

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

SELECT ONE OPTION

AEnsuring the appropriate testing tasks are scheduled during iteration planning.

BEnsuring all project status meetings are held according to the plan.

CSuggesting improvements in team retrospectives.

DWorking with business stakeholders to clarify requirements.

Answer : B

Question 4

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

SELECT ONE OPTION

AReducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.

BHaving at least once a day an automated build and test process that detects integration errors early and quickly.

CAvoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

DCapitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

Answer : C

Question 5

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

AAction 'Reopen' must be available only for a user with a specific authorization level.

BThe ID field must accept input value of a length between 2 and 10 characters.

CThe interface to External System shall be specified.

DThe program's icon should be clear and attractive.

Answer : B

Question 6

Which statement about an Agile task board is CORRECT?

SELECT ONE OPTION

AIt is updated once at the end of each iteration.

BIt provides detailed visual representation of the whole team's status.

CIt is a detailed visual representation of the status of testing.

DOnly ''in progress' tasks are shown on the task board.

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 7

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

SELECT ONE OPTION

AIn Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.

BIncreasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.

CFeedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.

DEarly and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.

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.

ISTQB Agile Public Sector Exam Practice Test