# Free CTFL-AT practice questions

> 10 free CTFL-AT practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/istqb-agile-tester-ctfl-at/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/istqb-agile-tester-ctfl-at/

### Question 1 of 10

A team lead keeps citing the Agile Manifesto when the company's quality group demands a 60-page requirements specification before any coding. Which value statement from the Manifesto best supports the team lead's position?

- A. Working software over comprehensive documentation
- B. Responding to change over following a plan
- C. Individuals and interactions over processes and tools
- D. Customer collaboration over contract negotiation

**Answer:** A

**Explanation:** Preferring working software over comprehensive documentation is the value that speaks directly to delaying coding in favour of a large specification. Individuals and interactions over processes and tools concerns how people collaborate rather than document volume. Responding to change over following a plan concerns plan rigidity, and customer collaboration over contract negotiation concerns the relationship with the customer, not the amount of upfront documentation.

### Question 2 of 10

An agile team is co-located with its business representative, developers and testers, and all three are jointly responsible for quality. Which concept from the Agile Tester syllabus does this describe?

- A. Independent testing by a separate test team
- B. The whole-team approach
- C. Pair programming as defined in Extreme Programming
- D. Session-based test management

**Answer:** B

**Explanation:** The whole-team approach means everyone with the necessary skills works together, ideally co-located, and the whole team shares responsibility for quality. Independent testing by a separate team is the opposite organisational choice. Pair programming involves two people at one workstation writing code, and session-based test management is a way of structuring exploratory testing, so neither describes shared team ownership of quality.

### Question 3 of 10

In the 'power of three' (three amigos) concept, which three perspectives come together to discuss a feature before and during its development?

- A. Tester, test manager and a quality assurance lead
- B. Architect, operations engineer and project sponsor
- C. Business representative, developer and tester
- D. Product owner, Scrum Master and an external auditor

**Answer:** C

**Explanation:** The power of three brings together the business representative, a developer and a tester so that business needs, implementation and testability are considered together. A Scrum Master and external auditor do not bring the developer and tester views. Three test roles miss the business and development perspectives, and an architect, operations engineer and sponsor leave out both the tester and the business view of the story.

### Question 4 of 10

How much documentation should agile test work products have according to the syllabus?

- A. No documentation at all, because the tests are the only documentation
- B. Full IEEE-style documents for every test, regardless of context
- C. Exactly the same amount as in the organisation's existing sequential projects
- D. As little as possible, but enough for the team's and stakeholders' needs

**Answer:** D

**Explanation:** Agile teams aim for lightweight documentation: as little as possible while still meeting the needs of the team and stakeholders, with the balance shaped by context such as regulation. Full formal documents for every test contradict that aim, no documentation at all ignores real needs, and copying sequential-project volume ignores the agile value of working software over comprehensive documentation.

### Question 5 of 10

A tester has been in the same agile team for three years and now accepts the developers' explanations for odd behaviour without questioning them. Which organisational risk from the syllabus does this illustrate?

- A. The tester is failing to keep pace with incoming changes
- B. The product owner is over-specifying stories
- C. The tester has lost the appropriate tester mindset
- D. The team has too many independent test teams

**Answer:** C

**Explanation:** The syllabus warns that testers working closely with developers can lose the appropriate tester mindset and become too accepting of the team's views. Failing to keep pace with changes is a separate risk about time pressure, an excess of independent test teams is not the situation described, and over-specified stories would not explain the tester's uncritical acceptance.

### Question 6 of 10

An organisation wants to keep testers in its agile teams but is worried about lost independence on long-term topics such as performance and automated regression. Which organisational option from the syllabus BEST addresses this?

- A. Keep embedded testers and add an independent test team for long-term work
- B. Move all testers into a separate team that tests only after each release is integrated
- C. Ask developers to review each other's tests so no testers are needed
- D. Rotate testers between teams every day so nobody gets too familiar

**Answer:** A

**Explanation:** The syllabus describes having an independent, separate test team that supports agile teams on long-term work such as automated test development, non-functional testing and environments, while testers remain in the teams. Testing only after releases loses in-iteration feedback, removing testers reduces independence further, and daily rotation would destroy domain knowledge and team continuity.

### Question 7 of 10

Which item belongs in a definition of done for an iteration?

- A. The product vision has been rewritten for the next quarter
- B. Every defect ever found in the product has been closed
- C. The release has been deployed to all customers in the production environment
- D. All iteration features are ready and individually tested

**Answer:** D

**Explanation:** Definition of done for an iteration includes that all features for the iteration are ready and individually tested, non-critical defects that cannot be fixed are added to the backlog and prioritised, and integration of all features is completed and tested. Deployment to all customers is a release activity, rewriting the vision is product strategy, and closing every defect ever found is unrealistic and not required.

### Question 8 of 10

A team writes: 'Given a cart with items worth 95 EUR, When the customer adds an item worth 10 EUR, Then free shipping is applied.' The business rule is free shipping for orders of 100 EUR or more. Which additional scenario would add the MOST value?

- A. A cart of 500 EUR with ten identical items in it
- B. A cart reaching exactly 100 EUR, and one ending at 99.99 EUR
- C. A cart of 105 EUR where the customer pays part of it with a gift card
- D. A cart of 95 EUR where the customer removes an item

**Answer:** B

**Explanation:** Boundary value analysis applied to the 100 EUR threshold suggests testing exactly 100 EUR and the value just below it, where defects in the comparison are most likely. A 500 EUR cart is in the same partition as the existing scenario, a gift card adds an unrelated payment condition, and removing an item from 95 EUR stays below the threshold and tests nothing new about the rule.

### Question 9 of 10

A story says: 'As a customer, I want to export my invoices so that I can file my taxes.' Its only acceptance criterion is 'Export works.' What is the BEST improvement a tester can propose?

- A. Criteria for file format, date range rules, data fields and a time limit
- B. A criterion requiring the developer to write unit tests for the export
- C. A single criterion stating 'Export works correctly in all cases'
- D. A criterion that the product owner must approve the export in the sprint review

**Answer:** A

**Explanation:** Good acceptance criteria are specific and testable, covering functional behaviour, data definitions, business rules and quality characteristics such as performance. Rewording 'works' to 'works correctly' stays untestable, unit tests are part of the definition of done rather than story acceptance criteria, and product owner approval does not define what to verify.

### Question 10 of 10

In planning poker, the tester shows a 13 and the developers show 3 for the same story. What should happen next?

- A. The tester's estimate is discarded because developers know the code best
- B. The highest and lowest estimators explain, then the team re-estimates
- C. The Scrum Master chooses the estimate because the team cannot agree
- D. The team takes the average of all cards and records it as the estimate

**Answer:** B

**Explanation:** Planning poker aims for consensus: large differences are discussed, typically by the people with the highest and lowest estimates, and the team estimates again. Averaging hides valuable information such as testing complexity, the Scrum Master does not decide estimates, and discarding the tester's view ignores test effort the developers may have overlooked.

Ready for a timed run? Take the free 15-question CTFL-AT mini exam: https://devopscodelab.com/app/exams/istqb-agile-tester-ctfl-at/mini/

DevOpsCode Lab is not affiliated with ISTQB. CTFL-AT and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
