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

iSQI Exam CTFL-PT_D Topic 4 Question 11 Discussion

Actual exam question for iSQI's CTFL-PT_D exam
Question #: 11
Topic #: 4
[All CTFL-PT_D Questions]

If Emily is conducting a performance test to determine that a system exposed to a load can respond to a high number of concurrent users during short periods of time that occur on specific days and at specific times, and then return to a stable state.

What type of performance testing is Emily conducting?

SELECT ONE OPTION

Show Suggested Answer Hide Answer
Suggested Answer: B

Spike testing involves subjecting a system to a significant increase in load for short periods of time to determine if it can handle sudden spikes in traffic. Emily's scenario of testing a system's response to a high number of concurrent users during specific periods and then returning to a stable state fits the description of spike testing.


* ISTQB Performance Testing Syllabus

* ISTQB Glossary

Contribute your Thoughts:

Shonda
2 months ago
I think it's load testing. They're trying to see how the system performs under a heavy load, which sounds a lot like what Aron is describing.
upvoted 0 times
Norah
19 days ago
D) Load testing
upvoted 0 times
...
Filiberto
20 days ago
I agree, it does sound like load testing. The system needs to handle a high number of users at specific times.
upvoted 0 times
...
Teddy
21 days ago
D) Load testing
upvoted 0 times
...
Dana
25 days ago
C) Concurrency testing
upvoted 0 times
...
Kimberlie
1 months ago
B) Spike testing
upvoted 0 times
...
Roxane
1 months ago
A) Endurance testing
upvoted 0 times
...
...
Aron
2 months ago
Ha, that's ironic that I'm the one conducting the test and I'm not even sure which one it is. Maybe I should've paid more attention in class.
upvoted 0 times
Willodean
1 months ago
User 3: I believe it's actually load testing.
upvoted 0 times
...
Edna
1 months ago
I think it might be concurrency testing.
upvoted 0 times
...
Lindsey
1 months ago
It sounds like Emily is conducting spike testing.
upvoted 0 times
...
...
Teddy
2 months ago
I think it's Load testing because she wants to see how the system handles a high number of concurrent users.
upvoted 0 times
...
Georgene
2 months ago
Hmm, I'm not so sure. Wouldn't this be more like concurrency testing, where you're trying to see how the system handles a lot of users at the same time?
upvoted 0 times
Tamar
1 months ago
I see your point, but I still think it's concurrency testing to check how the system handles multiple users at once.
upvoted 0 times
...
Lillian
1 months ago
Actually, I think it's load testing to measure the system's response under normal and peak load conditions.
upvoted 0 times
...
Dalene
1 months ago
I disagree, I believe it's endurance testing to see how the system performs over a long period of time.
upvoted 0 times
...
Adria
2 months ago
I think it's more like spike testing, where you test sudden increases in load.
upvoted 0 times
...
...
Lemuel
3 months ago
Definitely spike testing, that's the one that checks for high concurrent user loads at specific times, right?
upvoted 0 times
Luke
1 months ago
Actually, it's Concurrency testing. This type of testing checks how well the system can handle multiple users accessing it at the same time.
upvoted 0 times
...
Selma
2 months ago
I think it's Load testing. It checks the system's ability to handle a specific load over an extended period of time.
upvoted 0 times
...
Louann
2 months ago
Yes, you're correct! Spike testing is the type of performance testing that checks for high concurrent user loads at specific times.
upvoted 0 times
...
...
Ronnie
3 months ago
I believe it could also be Concurrency testing.
upvoted 0 times
...
Deeanna
3 months ago
I think Emily is conducting Spike testing.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77