Astatic performance testis anon-execution-based reviewthat analyzes system architecture, network configurations, and other elements thataffect system performance before execution.
Option A (Usability test)is not a static performance test but rather a functional or UX evaluation.
Option B (Evaluation of testers' skills)is unrelated to performance testing.
Option D (Formal signature approval)is an administrative task and not a static test.
Create a steady and consistent background load on the system
B.
Simulate user behavior in accordance with the defined operational profile
C.
Record and analyze the behavior of the system as it is executing the prescribed tests
D.
Support root cause analysis when performance degradation is encountered
Answer:
B
Explanation:
Aload generatoris responsible forsimulating virtual usersand applyingworkloads to a systemas defined by an operational profile. This allows testers to analyze how the system behaves under different load conditions.
Option A (Background load)is incorrect becauseload generators create simulated user interactions, not just background noise.
Option C (Record and analyze behavior)is the role ofmonitoring tools, not a load generator.
Option D (Support root cause analysis)is incorrect becauseroot cause analysis is done after the load test, using monitoring tools.
When following the principal performance testing activities, when are resources allocated?
Options:
A.
During test planning
B.
During test execution
C.
During test evaluation
D.
During test completion
Answer:
A
Explanation:
Resource allocation happens during the test planning phase, wherehardware, tools, and personnelare assigned to the project. This ensures that performance tests areadequately supported.
Option B (Test execution)is when resources are actually used, not allocated.
Option C (Test evaluation)happensafter executionto analyze results.
Option D (Test completion)focuses on documentation and reporting.
[Reference:ISTQB CT-PT Syllabus, Section 1.3: Test Planning in Performance Testing., ]