iSQI CTFL-PT_D Exam - Topic 5 Question 13 Discussion

Actual exam question for iSQI's CTFL-PT_D exam

Question #: 13
Topic #: 5

Base Scenario 1: This Base Scenario 1 is used for 2 questions throughout this exam. When you refer to Base Scenario 1, you are referring to this description and only this description, without any modification.

k given project for the development of a management software that will have a multilayer architecture will enable Its users to Install it in multiple locations, nationally and internationally - each installation can operate Independently and communicate with other instances in a selective way. Each installation shall have a high processing capacity.

Question specific constraints: (specific constraints are not part of the Base Scenario and are specific to this question).

* The project follows a sequential development life cycle model.

Question

Which is the right moment in the project to analyze and evaluate the performance risks?

SELECT ONE OPTION

AAfter design but before coding.

BDuring the requirements activities and again before running the performance test.

CDuring the analysis and design activities as well as, again, before each performance test cycle.

DRepeatedly throughout the development phases (including requirements activities) and the performance test itself.

Show Suggested 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

by Jovita at Oct 20, 2024, 07:02 AM

Limited Time Offer

25%

Off

Get Premium CTFL-PT_D Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Luz

3 months ago

I like option A, it’s a clear point to assess before coding.

upvoted 0 times

...

Louis

4 months ago

Option B seems too limited, we need more checks.

upvoted 0 times

...

Bong

4 months ago

Wait, can we really analyze performance risks during design?

upvoted 0 times

...

Deangelo

4 months ago

I disagree, option D is better for ongoing evaluation.

upvoted 0 times

...

Desiree

4 months ago

I think option C makes the most sense.

upvoted 0 times

...

Truman

4 months ago

I lean towards option C because it mentions both analysis and design, which seems like a logical time to address performance risks.

upvoted 0 times

...

Tricia

5 months ago

I feel like performance risks should be assessed repeatedly, but I'm uncertain if that means throughout all phases or just specific ones.

upvoted 0 times

...

Winifred

5 months ago

I think we practiced a question similar to this, and I recall that analyzing risks during requirements might be crucial.

upvoted 0 times

...

Edwin

5 months ago

I remember discussing performance risks during the design phase, but I'm not sure if that's the best time to evaluate them.

upvoted 0 times

...

Krystina

5 months ago

Okay, I think I've got it. Since the project follows a sequential development life cycle, we need to analyze performance risks during the analysis and design activities, and then again before each performance test cycle. That way we can catch any issues early on and make adjustments as needed.

upvoted 0 times

...

Andrew

5 months ago

Hmm, this is a tricky one. I'm leaning towards the option that says to analyze performance risks repeatedly throughout the development phases and the performance test itself. That seems like the most comprehensive approach to me.

upvoted 0 times

...

Jody

5 months ago

I'm a bit confused on this one. The question mentions a sequential development life cycle, so I'm not sure if that means we should only analyze performance risks at certain phases or if it needs to be done repeatedly. I'll have to think this through carefully.

upvoted 0 times

...

Winifred

5 months ago

This question seems straightforward - I think the right answer is to analyze and evaluate performance risks during the analysis and design activities, as well as before each performance test cycle.

upvoted 0 times

...

Oneida

10 months ago

Hey, I hear ya on the performance risks. Gotta keep a close eye on that like a hawk watching its prey. Or maybe more like a ninja, sneaking up on those issues before they even know what hit 'em!

upvoted 0 times

Ryan

9 months ago

C) During the analysis and design activities as well as, again, before each performance test cycle.

upvoted 0 times

...

Freeman

9 months ago

B) During the requirements activities and again before running the performance test.

upvoted 0 times

...

Donette

10 months ago

C) During the analysis and design activities as well as, again, before each performance test cycle.

upvoted 0 times

...

Arlette

10 months ago

A) After design but before coding.

upvoted 0 times

...

Paris

10 months ago

B) During the requirements activities and again before running the performance test.

upvoted 0 times

...

Hermila

10 months ago

A) After design but before coding.

upvoted 0 times

...

Rory

11 months ago

D all the way! Performance is critical for this multi-layer, globally-deployed software. Gotta be on top of those risks from start to finish. Anything less would be like trying to defuse a bomb with your eyes closed.

upvoted 0 times

Helga

9 months ago

Repeatedly throughout the development phases (including requirements activities) and the performance test itself.

upvoted 0 times

...

Yolande

10 months ago

upvoted 0 times

...

Shaunna

11 months ago

Hmm, I'm torn between B and D. I like the idea of evaluating risks during requirements and before tests, but repeatedly throughout the whole project is also a good call. Guess I'll have to flip a coin on this one!

upvoted 0 times

Louis

10 months ago

User 2: I see your point, but I'm leaning towards option D for a more thorough approach.

upvoted 0 times

...

Jutta

10 months ago

User 1: I think option B is the way to go.

upvoted 0 times

...

Vivan

11 months ago

I believe analyzing performance risks during the analysis and design activities, as well as before each performance test cycle, is crucial for the success of the project.

upvoted 0 times

...

Sage

11 months ago

I'm going with C. Analyzing performance risks during analysis, design, and before each test cycle seems like a more comprehensive approach than just doing it once or twice.

upvoted 0 times

Fabiola

10 months ago

Tammy: Definitely, it's better to be proactive than reactive when it comes to performance risks.

upvoted 0 times

...

Jaclyn

10 months ago

User 3: I agree, it ensures that any potential issues are caught early on.

upvoted 0 times

...

Tammy

10 months ago

User 2: Yeah, analyzing performance risks multiple times throughout the project is crucial.

upvoted 0 times

...

Nobuko

11 months ago

User 1: I think C is the best option too.

upvoted 0 times

...

Emerson

11 months ago

I agree with Kendra. It's important to assess risks before moving on to coding.

upvoted 0 times

...

Wynell

11 months ago

I think the answer is D. Performance risks should be analyzed and evaluated repeatedly throughout the development process, not just at specific points. Waiting until after design or just before testing seems too late to catch potential issues.

upvoted 0 times

...

Kendra

11 months ago

I think the right moment to analyze performance risks is after design but before coding.

upvoted 0 times

...