Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam CTAL-TTA Topic 2 Question 20 Discussion

Actual exam question for ISTQB's CTAL-TTA exam
Question #: 20
Topic #: 2
[All CTAL-TTA Questions]

You are working on a project that is integrating code from multiple development groups. There have been numerous integration problems, particularly regarding reliability, error recovery and transactional integrity. You are now responsible for planning the performance efficiency testing for this product. There Is a strong feeling among the development managers that some parts of the code are weaker than others and will tend to exhibit problems during the performance efficiency testing. To identify these problematic areas as soon as possible, which type of testing should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Stress testing is the most appropriate method for identifying weak areas in code that may cause performance issues, especially under conditions of extreme load or stress. This type of testing deliberately pushes the system beyond its normal operational capacity to see how it behaves under stress, which can help reveal vulnerabilities in error recovery and transactional integrity that are not apparent under normal conditions. Stress testing can provide early insights into potential failure points and help prioritize areas for improvement before full-scale deployment.


Contribute your Thoughts:

Merlyn
2 months ago
Let's focus on stress testing first, then we can move on to scalability testing if needed.
upvoted 0 times
...
Haydee
2 months ago
Scalability testing is important, but stress testing will help us pinpoint immediate issues.
upvoted 0 times
...
Vinnie
2 months ago
Stress testing is the obvious choice. I'm picturing the developers sweating bullets as the system crumbles under pressure. *chuckles*
upvoted 0 times
Antonette
1 months ago
C) Stress testing
upvoted 0 times
...
Leota
1 months ago
Stress testing is definitely the way to go. We need to see how the system holds up under pressure.
upvoted 0 times
...
Marguerita
1 months ago
D) Scalability testing
upvoted 0 times
...
Tesha
2 months ago
C) Stress testing
upvoted 0 times
...
Agustin
2 months ago
B) Interoperability testing
upvoted 0 times
...
Blondell
2 months ago
A) Load testing
upvoted 0 times
...
...
Dorthy
3 months ago
But what about scalability testing? Shouldn't we consider that too?
upvoted 0 times
...
Malissa
3 months ago
Interoperability testing? Really? That's like trying to fit a square peg in a round hole. We need to focus on the core issues here.
upvoted 0 times
Raul
1 months ago
D) Scalability testing
upvoted 0 times
...
Matthew
1 months ago
C) Stress testing
upvoted 0 times
...
Aleisha
2 months ago
A) Load testing
upvoted 0 times
...
...
Merlyn
3 months ago
I agree with Haydee, stress testing will help us find weak spots.
upvoted 0 times
...
Bettyann
3 months ago
Hmm, I think scalability testing is the way to go. We need to ensure the system can handle increasing workloads without compromising performance.
upvoted 0 times
...
Heidy
3 months ago
I'd go with load testing. We need to simulate real-world conditions and see how the system handles the influx of data and requests.
upvoted 0 times
Hillary
3 months ago
C) Stress testing might also be a good option. We need to push the system to its limits to identify any weak areas.
upvoted 0 times
...
Nettie
3 months ago
A) Load testing sounds like the way to go. We need to see how the system performs under heavy loads.
upvoted 0 times
...
...
Haydee
3 months ago
I think we should do stress testing to identify the problematic areas.
upvoted 0 times
...
Estrella
3 months ago
Stress testing for sure! We need to push the system to its limits and see where it breaks.
upvoted 0 times
Hyman
2 months ago
C) Stress testing
upvoted 0 times
...
Lovetta
3 months ago
A) Load testing
upvoted 0 times
...
...

Save Cancel