100+ Free ISTQB CTAL-ATT Practice Questions

Pass your ISTQB Advanced Level Agile Technical Tester (CTAL-ATT) exam on the first try — instant access, no signup required.

✓ No registration✓ No credit card✓ No hidden fees✓ Start practicing immediately

~60-70% Pass Rate

100+ Questions

100% Free

1 / 100

Question 1

Score: 0/0

Which mnemonic represents the criteria for well-formed user stories in Agile projects?

SMART

INVEST

FIRST

DRY

to track

2026 Statistics

Key Facts: ISTQB CTAL-ATT Exam

Exam Questions

ISTQB

65%

Passing Score

ISTQB

60 min

Exam Duration

75 min non-native

$249

Exam Fee

AT*SQA

56%

Testing in Agile

Largest chapter

Lifetime

Cert Valid

No renewal needed

The CTAL-ATT exam has 40 multiple-choice questions worth 64 points in 60 minutes (75 min for non-native English speakers) with a 65% passing score. K-levels span K2-K4 with K3 worth 2 points and K4 worth 3 points. Prerequisites: ISTQB CTFL Foundation Level AND CTFL-AT (Agile Tester) certifications. Four chapters: Requirements Engineering (~19%), Testing in Agile (~56% — largest: TDD, BDD, ATDD, FIRST, experience-based testing), Test Automation (~14%), and Deployment and Delivery (~11% — CI/CD pipelines). Certification is valid for life with no renewal.

Sample ISTQB CTAL-ATT Practice Questions

Try these sample questions to test your ISTQB CTAL-ATT exam readiness. Each question includes a detailed explanation. Start the interactive quiz above for the full 100+ question experience with AI tutoring.

1Which mnemonic represents the criteria for well-formed user stories in Agile projects?

A.SMART

B.INVEST

C.FIRST

D.DRY

Explanation: INVEST is the standard mnemonic for evaluating user stories: Independent, Negotiable, Valuable, Estimable, Small, Testable. Coined by Bill Wake, it ensures stories are sized and scoped for a sprint. SMART applies to goals/objectives, FIRST applies to unit tests, DRY is a coding principle.

2In INVEST, what does the 'I' stand for?

A.Important

B.Independent

C.Iterative

D.Inspectable

Explanation: The 'I' in INVEST stands for Independent. A good user story should be independent of other stories so it can be developed, tested, and delivered in any order without dependencies blocking the team.

3Which is the BEST description of an epic in Agile?

A.A defect found in production

B.A small story completed in one day

C.A large user story too big for a single sprint, broken down into smaller stories

D.A non-functional requirement

Explanation: An epic is a large body of work that cannot fit into a single sprint and must be decomposed into smaller user stories. Epics typically span multiple sprints or releases and represent significant features or initiatives.

4What is the PRIMARY purpose of acceptance criteria attached to a user story?

A.To estimate story points

B.To define when a story is considered done from the user/business perspective

C.To replace test cases

D.To assign the story to a developer

Explanation: Acceptance criteria define the conditions a story must satisfy to be considered complete and accepted by the Product Owner. They make the story testable and form the basis for acceptance tests in ATDD/BDD.

5A story reads: 'As a customer, I want to filter products by price so that I can find items within my budget.' Which user story format does this follow?

A.Connextra (As a/I want/so that)

B.Job Story (When/I want to/So I can)

C.Gherkin (Given/When/Then)

D.Feature Driven (Action-Object-User)

Explanation: This follows the Connextra (also called role-feature-benefit) template: 'As a [role], I want [feature], so that [benefit]'. It's the most common user story format in Scrum/XP and clearly captures who, what, and why.

6During backlog refinement, you identify a story that depends on another team's API and cannot start until that API is delivered. Which INVEST criterion does this violate?

A.Valuable

B.Independent

C.Small

D.Estimable

Explanation: The story violates Independent — it cannot proceed without an external dependency. Resolving this typically means splitting the story, mocking the dependency for development, or sequencing the work to remove the blocker.

7Which technique helps split a large epic into smaller, independently deliverable stories?

A.Story mapping and SPIDR

B.Mob programming

C.Burndown charting

D.Pair rotation

Explanation: Story mapping (Jeff Patton) visualizes user journey to identify slices, and SPIDR (Spike, Path, Interface, Data, Rules) provides patterns for decomposing stories along functional axes. Both produce smaller, INVEST-compliant stories from epics.

8What is the MAIN risk if acceptance criteria are written only after the story is implemented?

A.The team will work faster

B.Tests will confirm what was built rather than what was needed, reducing requirements traceability

C.The Product Owner becomes unnecessary

D.Story points will be more accurate

Explanation: Writing acceptance criteria after implementation creates confirmation bias — tests will validate what was built, not what was originally needed. Pre-implementation criteria drive correct development and enable ATDD/BDD specification by example.

9Which technique uses concrete examples to capture requirements in a form readable by both business and technical stakeholders?

A.Specification by Example (SBE)

B.Cyclomatic complexity analysis

C.Mutation testing

D.Code review

Explanation: Specification by Example (SBE), also called Living Documentation, uses concrete examples (often expressed as Given-When-Then scenarios) to capture requirements unambiguously. Gojko Adzic popularized this approach in BDD/ATDD contexts.

10In Agile, what is the typical maximum size guideline for a user story to be considered 'Small' (the S in INVEST)?

A.At most 1 hour of work

B.Should fit comfortably within a single sprint, typically a few days of effort

C.At most 1 month

D.Always less than 8 story points

Explanation: Small means the story should comfortably fit within a single sprint, typically a few days of effort for the team. Stories larger than half a sprint risk not completing and should be split. Specific story-point thresholds vary by team velocity.

About the ISTQB CTAL-ATT Exam

The ISTQB Advanced Level Agile Technical Tester (CTAL-ATT) certification validates advanced skills in technical testing within Agile teams. It covers requirements engineering (user stories, epics, acceptance criteria, INVEST principles), testing in Agile (test-driven development, behavior-driven development with Gherkin, acceptance test-driven development, unit test characteristics with the FIRST mnemonic, experience-based testing, product backlog analysis), test automation (Mike Cohn's test pyramid, Brian Marick's Agile testing quadrants, automation tool selection, service virtualization), and deployment and delivery (continuous integration, continuous delivery, continuous deployment, build pipelines, DevOps testing practices).

Questions

40 scored questions

Time Limit

60 minutes (75 min non-native)

Passing Score

65%

Exam Fee

$249 USD (ISTQB / AT*SQA / Pearson VUE)

ISTQB CTAL-ATT Exam Content Outline

19%

Requirements Engineering

User stories and epics, INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable), acceptance criteria writing, requirements engineering techniques applied to Agile backlogs

56%

Testing in Agile

Test-driven development (TDD red-green-refactor), unit test characteristics (FIRST: Fast, Independent, Repeatable, Self-validating, Timely), behavior-driven development (BDD with Gherkin Given-When-Then), acceptance test-driven development (ATDD), experience-based testing, product backlog analysis

14%

Test Automation

Mike Cohn's test pyramid (unit/service/UI), Brian Marick's Agile testing quadrants, test level selection, automation tool selection criteria, service virtualization (WireMock, Hoverfly, Mountebank), automated regression

11%

Deployment and Delivery

Continuous integration (CI), continuous delivery (CD), continuous deployment, build pipelines (build/test/deploy stages), DevOps testing practices, blue-green deployments, canary releases, feature toggles

How to Pass the ISTQB CTAL-ATT Exam

What You Need to Know

Passing score: 65%
Exam length: 40 questions
Time limit: 60 minutes (75 min non-native)
Exam fee: $249 USD

Keys to Passing

Complete 500+ practice questions
Score 80%+ consistently before scheduling
Focus on highest-weighted sections
Use our AI tutor for tough concepts

ISTQB CTAL-ATT Study Tips from Top Performers

1Memorize FIRST for unit tests: Fast, Independent, Repeatable, Self-validating, Timely

2Master the TDD cycle: Red (failing test) → Green (minimal code to pass) → Refactor (improve without breaking)

3Memorize INVEST for user stories: Independent, Negotiable, Valuable, Estimable, Small, Testable

4Practice writing Gherkin scenarios: Given (precondition) — When (action) — Then (expected outcome)

5Know the test pyramid: many fast unit tests at base, fewer integration/service tests, very few slow UI tests at top

6Study Brian Marick's Agile testing quadrants: technology-facing/business-facing × supporting/critiquing the team

7Distinguish CI (merge frequently, automated build+test) from CD (always deployable) from continuous deployment (auto-push to prod)

8Get hands-on with key tools: JUnit/pytest (TDD), Cucumber/SpecFlow (BDD), Jenkins/GitHub Actions (CI/CD), WireMock (service virtualization)

Frequently Asked Questions

What is the ISTQB CTAL-ATT exam?

The CTAL-ATT (Certified Tester Advanced Level — Agile Technical Tester) exam validates advanced technical testing skills in Agile teams. It focuses on requirements engineering (user stories, INVEST), test-driven and behavior-driven development (TDD/BDD/ATDD), test automation strategy (test pyramid, automation pyramid), service virtualization, and continuous integration/delivery/deployment pipelines.

What are the prerequisites for CTAL-ATT?

Two ISTQB certifications are required: CTFL (Foundation Level) AND CTFL-AT (Foundation Agile Tester). This dual prerequisite ensures candidates understand both general testing fundamentals and Agile-specific testing principles before tackling advanced technical Agile content. Practical Agile experience (1-2+ years) and coding/automation familiarity are strongly recommended.

How is CTAL-ATT different from CTAL-TAE?

CTAL-TAE (Test Automation Engineer) focuses on automation architecture, test automation strategy across the SDLC, automation framework design, and tooling — applicable to any methodology. CTAL-ATT (Agile Technical Tester) is Agile-specific, emphasizing TDD/BDD/ATDD, Agile testing quadrants, CI/CD, and how technical testing fits into Scrum/Kanban teams. Many testers earn both for comprehensive coverage.

What is the largest topic on CTAL-ATT?

Testing in Agile is the largest chapter at approximately 56% of the syllabus by teaching time. It covers test-driven development (TDD red-green-refactor cycle), unit testing with FIRST principles, behavior-driven development with Gherkin scenarios (Given-When-Then), acceptance test-driven development on the product backlog, and experience-based testing techniques.

How should I prepare for CTAL-ATT?

Plan for 35-60 hours of study over 4-8 weeks. Read the CTAL-ATT syllabus 2-3 times. Practice TDD red-green-refactor with simple coding katas. Write Gherkin scenarios for sample stories. Study test pyramid layers and automation tool fit. Learn CI/CD pipeline stages (build, test, deploy). Complete 100+ practice questions and aim for 75%+. Hands-on Agile experience is essential.

Does the CTAL-ATT certification expire?

No — CTAL-ATT is valid for life with no renewal required. The current syllabus is v1.1 (2019). Once earned, the certification stays on your record. ISTQB does not require continuing education, though staying current with evolving Agile practices, DevOps, and modern test automation tools is recommended for career growth.