Important iSQI CTAL-ATT Exam Questions

CertPrep • iSQI • CTAL-ATT Exam Questions

Select Certification Providers

Select Certification Exam

Get Full Version

iSQI Certified Tester Advanced Level Agile Technical Tester CTAL-ATT Exam

Attempt the ISTQB Certified Agile Technical Tester practice test and solve real exam-like CTAL-ATT questions to prepare efficiently and increase your chances of success. Our iSQI CTAL-ATT practice questions match the actual Certified Tester Advanced Level Agile Technical Tester exam format, helping you enhance confidence and improve performance. With our CTAL-ATT practice exam software, you can analyze your performance, identify weak areas, and work on them effectively to boost your final ISTQB Certified Agile Technical Tester exam score.

Vendor:	iSQI
Exam Name:	Certified Tester Advanced Level Agile Technical Tester
Registration Code:	CTAL-ATT
Related Certification:	iSQI ISTQB Certified Agile Technical Tester Certification
Exam Audience:	Experienced software testers, test analysts,

Total Questions

Last Updated

25-05-2026

Exam Duration

90 MINUTES

Upgrade to Premium

GET FULL PDF

Question: 1

Which of the following is the preferred way to solicit information from the product owner to better understand what will be ''acceptable''?

APropose the following acceptance criteria:
Purchase below the limit for free delivery
Purchase above the limit for free delivery
Request store pickup

BExplain boundary value analysis to the product owner and have them indicate the appropriate boundaries to test

CWork with the product owner to elicit examples of how they would use the software. Combine their examples with testing techniques to flesh out the set of acceptance criteria.

DCreate the following acceptance criteria and review them with the product owner:
Login
Verify password reset
Verify account details
Update account details
Browse and select food
Add to cart, etc.

Answer: C

Explanation:

Preferred Approach for Acceptance Criteria:

Collaboratively eliciting examples from the product owner ensures that the acceptance criteria reflect real-world usage and expectations.

Combining these examples with testing techniques ensures coverage of edge cases and system behavior.

Analyzing Options:

A: Proposes specific criteria but does not involve the product owner in the process.

B: Boundary value analysis is useful but does not address broader acceptance criteria.

D: Lists numerous acceptance criteria without first understanding the product owner's expectations.

Aligned with ISTQB Agile Technical Tester syllabus emphasizing collaboration with stakeholders to define robust acceptance criteria.

Question: 2

The following user story has been written:

As a paying hotel guest

I want to see the charges that have been added to my bill

So that I can monitor my expenditure and know In advance how much I will have to pay when I check out

The notes that have been added to It mention that It must be possible for the guest to get a printout of the bill, see It In a variety of currencies and set a flag in the hotel's billing system against any Item that they wish to challenge.

The following acceptance criteria have been defined:

1. The user shall be able to choose from the most commonly-used currencies.

2. The application must be accessible on most mobile platforms as well as on the hotel room's smart TV.

3. The hotel manager must be notified whenever a bill item is flagged by a hotel guest.

4. End-to-end response time for any individual request submitted by a user must not exceed 7 seconds.

Applying the INVEST technique to this user story, including its acceptance criteria, which of the following statements is correct?

SELECT ONE OPTION

AThe Testable and Negotiable criteria of INVEST have not been satisfied

BThe Testable and Small criteria of INVEST have not been satisfied

CThe INVEST criteria have all been satisfied by this epic

DThe Negotiable and Small criteria of INVEST have not been satisfied

Answer: D

Explanation:

The user story provided is quite broad and encompasses multiple functionalities, which suggests it is more of an epic than a small, deliverable user story. The INVEST criteria for Agile user stories require that stories be Independent, Negotiable, Valuable, Estimable, Small, and Testable. In this case:

Independent: This user story seems to have dependencies, as the ability to print the bill, view it in different currencies, and flag items are likely interconnected functionalities.

Negotiable: The user story provides specific solutions rather than outlining the problem to solve, which limits the negotiation on how to implement the solutions.

Valuable: The story does provide value to the hotel guest, which is clear.

Estimable: With the information provided, the development team can likely estimate the effort required.

Small: The story is not small; it covers multiple features that probably cannot be delivered in a single iteration.

Testable: The acceptance criteria are testable, although they are quite detailed and prescriptive.

Reference= The explanation is based on the INVEST criteria as described in Agile methodologies1234. The criteria are used to assess the quality of a user story, ensuring it is well-defined and suitable for Agile development practices. The user story in question does not fully meet the 'Negotiable' and 'Small' criteria, which is essential for maintaining flexibility and delivering incremental value in Agile projects.

Question: 3

You are testing a new feature in the current iteration. The feature is supposed to take the input of a name and return the number of characters in the name. This information is used by another feature that will determine the size needed on a form. The acceptance criteria state the following

1) a name of up to 30 characters should be accepted

2) standard error processing should be in place to limit user errors

The developers are using TDD and you have asked to see their tests. This is what they gave you

Exam Question 3 Exhibit 1

When you run your manual tests you are finding that when you use the following inputs you get the associated results:

From these results what can you conclude about the TDD process?

AThe developers are not running the tests prior to releasing the code

BThe tests cannot be passing

CThe tests are insufficient and need to include more options

DThe story needs to be enhanced to include the capabilities that are causing errors

Answer: C

Explanation:

The TDD process, as described, seems to lack comprehensive testing that covers all the acceptance criteria. Specifically, the tests provided by the developers do not address the full range of input validation, such as ensuring that names with up to 30 characters are accepted and that standard error processing is in place to limit user errors. This indicates that the tests are insufficient and need to include more options to fully validate the feature against its acceptance criteria.The ISTQB Advanced Level Agile Technical Tester syllabus emphasizes the importance of creating testable acceptance criteria within an Agile team and implementing various Agile test approaches using appropriate techniques12.It also highlights the need for supporting and contributing to test automation activities in an Agile project12, which includes ensuring that all acceptance criteria are met and that tests are sufficiently robust to catch potential errors.

ISTQB Advanced Level Agile Technical Tester Syllabus1

ISTQB Advanced Level Agile Technical Tester Learning Objectives2

Question: 4

A developer has implemented a class that calculates if a given date is a leap year. The definition

for the leap year is given:

Every year that is exactly divisible by four is a leap year, except for years that are exactly

divisible by 100, but these centurial years are leap years if they are exactly divisible by 400.

- divisible by 4

- but not by 100

- years divisible by 400 are leap anyway

You have already thought about it and started with the first test class; the test class looks like

(pseudo JavaScript used here):

// LeapYear.spec.js

describe('Leap year calculator', () => {

it('should consider 1996 as leap', () => {

expect(LeapYear.isLeap(1996)).toBe(true);

});

What would now be your next step to proceed as efficient as possible, to validate the correctness

of the class above?

AFirst write additional test classes to test also other relevant aspects of the leap year
calculation

BFirst write code that covers other relevant aspects of the leap year calculation

CFirst write code that makes this test case fail

DFirst write code that makes this test case pass

Answer: D

Explanation:

In the context of test-driven development (TDD), the next step after writing a failing test is to write the minimum amount of code necessary to make the test pass. This approach encourages simple designs and inspires confidence that the system is functioning as expected. Once the test passes, you can then refactor the code to improve its structure without changing its behavior.

Question: 5

Refactoring of test cases is needed in agile projects for many reasons.

Which of the following statements about the refactoring of test cases is correct?

ARefactoring of test cases is done to match and evolve the test cases due to changing
functionality. The main benefits include improving the regression test cases and the
continued alignment of the tests with the code base and product functionality

BRefactoring of test cases is needed because we cannot write and maintain detailed test
cases in the short iterations associated with agile. The main benefits include aligning the
pace of testing with development and the ability to quickly create new test cases

CIn general, in the agile world refactoring is a way to clean up test cases by making them
shorter. The main benefits include the ability to write test cases quickly, being able to test
faster using short test cases, and being able to automate them quickly

DRefactoring of test cases is done as a process with the following steps: Identification,
Refactor, Re-run, and Identify again. The main benefits include improving the regression
test cases and maintaining the alignment of tests with the code base and product
functionality

Answer: A

Explanation:

Refactoring of test cases in agile projects is primarily done to ensure that the test cases remain relevant and effective as the functionality of the product evolves. This process involves updating and improving the test cases to match the current state of the product's functionality. The main benefits of this practice include enhancing the quality and effectiveness of regression test cases and ensuring that the tests continue to align with the code base and product functionality. This alignment is crucial for maintaining the integrity of the testing process and ensuring that the tests accurately reflect the product's requirements and behavior.

SAVE TIME & QUICKLY PREPARE WITH REAL QUESTIONS

GET FULL ACCESS

Other iSQI Certification Exams

CT-AI Exam

Certified Tester AI Testing

CTFL_Syll_4.0 Exam

ISTQB Certified Tester Foundation Level (CTFL) v4.0

CTFL-AT Exam

ISTQB Certified Tester - Agile Tester

TMMi-P_Syll2.1 Exam

TMMi Test Maturity Model Integration Professional

CTFL-PT_D Exam

ISTQB Certified Tester Foundation Level - Specialist Performance Testing

CTFL_Syll2018 Exam

ISTQB Certified Tester Foundation Level