ISTQB CT-TAE Exam - Topic 2 Question 60 Discussion

Actual exam question for ISTQB's CT-TAE exam

Question #: 60
Topic #: 2

You have been asked to determine a TAS for a new release of a SUT, test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.

What would be the BEST Test Automation Solution (TAS) design in this scenario?

AAutomate tests at both Component and System Level. Only do this automation once every interface has been fully developed or amended and manual testing has completed successfully.

BAutomate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.

CAutomate the tests at two levels, Component and System level. Create customized hooks at Component level for interface not yet developed or amended. Only use the newly developed or amended interfaces to test at System level.

DAutomate a test at once level, component level, Create customized interface/test hooks for this level where the interface has not yet been developed or amended.

Show Suggested Answer

Suggested Answer: A

by Rima at Nov 21, 2025, 09:11 PM

Limited Time Offer

25%

Off

Get Premium CT-TAE Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Eladia

1 day ago

B feels too restrictive. We need to test more thoroughly.

upvoted 0 times

...

Cordie

6 days ago

D is interesting, but limiting to one level might miss issues.

upvoted 0 times

...

Ryan

12 days ago

Option A seems too slow. Waiting for everything to be done is risky.

upvoted 0 times

...

Keneth

17 days ago

I agree, C allows for flexibility with the new interfaces.

upvoted 0 times

...

Casandra

22 days ago

Component level only? That’s a hard pass for me.

upvoted 0 times

...

Sylvia

27 days ago

I’m surprised they even considered option B, seems too limiting.

upvoted 0 times

...

Shawnta

2 months ago

Totally agree, we need those customized hooks!

upvoted 0 times

...

Julio

2 months ago

I think option C makes the most sense for thorough testing.

upvoted 0 times

...

Dean

2 months ago

I wonder if the developers will remember to update those "customized hooks" when the real interfaces are ready...

upvoted 0 times

...

Josphine

2 months ago

Option D is a bit too narrow, we should automate at both levels to ensure thorough testing.

upvoted 0 times

...

Germaine

2 months ago

Option B is too limited, we need to test at both the component and system level for a robust TAS.

upvoted 0 times

...

Adaline

2 months ago

I like how Option C suggests using customized hooks at the component level to handle interfaces not yet developed or amended.

upvoted 0 times

...

Arlette

3 months ago

I remember something about focusing on the newly developed interfaces, but I’m not clear if just doing System level automation is enough for this scenario.

upvoted 0 times

...

Giovanna

3 months ago

I feel like option C makes sense because it allows for flexibility with the new interfaces, but I'm uncertain if we should really automate at both levels right away.

upvoted 0 times

...

Rosio

3 months ago

I think we practiced a similar question where automating at both levels was beneficial, but I can't recall if we should create hooks for interfaces that aren't ready yet.

upvoted 0 times

...

Arlean

3 months ago

I'm leaning towards option B. Automating at just the system level and using the new interfaces as-is seems like the simplest and most straightforward approach. We can always add more automation later if we need to.

upvoted 0 times

...

Elmira

3 months ago

I like the idea of option C. Automating at both levels and using customized hooks for the unfinished interfaces will let us get a head start on the automation work. That way, we can hit the ground running once the interfaces are complete.

upvoted 0 times

...

Janessa

3 months ago

Option A sounds like the safest bet to me. Waiting until the interfaces are fully developed and manually tested before automating just seems like the low-risk approach. I don't want to get stuck trying to automate something that's still in flux.

upvoted 0 times

...

Arthur

4 months ago

I think option C is the best. It covers both levels.

upvoted 0 times

...

Terrilyn

4 months ago

I remember we discussed the importance of incremental testing, but I'm not sure if we should wait until everything is fully developed before automating.

upvoted 0 times

...

Alease

4 months ago

Option C seems the most comprehensive approach to handle the incremental release of the new and amended interfaces.

upvoted 0 times

...

Joanna

4 months ago

Not sure about waiting until everything's done, that's risky.

upvoted 0 times

...

Lina

5 months ago

I'm a bit confused by this question. It seems like we have to decide on the test automation strategy before the interfaces are fully developed. Wouldn't it be better to wait until the interfaces are complete before starting the automation?

upvoted 0 times

...

Malcom

5 months ago

I think option C is the best approach here. Automating at both the component and system level will give us the most comprehensive coverage, and using customized hooks for the interfaces that aren't fully developed yet is a smart way to get started on automation early.

upvoted 0 times

Brittani

4 months ago

I like how it allows testing as interfaces are developed.

upvoted 0 times

...