Free ISTQB Certified Tester - Performance Testing CT-PT Exam Questions

For safety-critical software, performance goals must be identified as early as the requirements phase. This ensures that performance constraints are well understood and accounted for throughout development.

Option A (After test readiness but before system testing) is too late, as requirements should be defined before coding begins.

Option C (During the concept stage) is too early, as details may not be concrete.

Option D (During software design) is useful but should be preceded by a proper definition during the requirements phase.

One of the most critical test acceptance criteria in performance testing is to ensure that the hardware in the test environment is comparable to production. Differences in CPU, memory, disk I/O, or network infrastructure can distort performance results.

Option A (Convincing stakeholders to set goals) is a planning activity, not an acceptance criterion.

Option B (Describing the system under test) is important but does not directly affect test acceptance.

Option D (Comparing baselined metrics) is useful, but without a comparable test environment, baseline metrics may be misleading.

A load generator is responsible for simulating virtual users and applying workloads to a system as defined by an operational profile. This allows testers to analyze how the system behaves under different load conditions.

Option A (Background load) is incorrect because load generators create simulated user interactions, not just background noise.

Option C (Record and analyze behavior) is the role of monitoring tools, not a load generator.

Option D (Support root cause analysis) is incorrect because root cause analysis is done after the load test, using monitoring tools.

During performance testing, it is crucial to define failure handling procedures to ensure that failures do not introduce additional errors into the test execution process. This helps maintain test accuracy and avoid misleading results.

Option A (Meeting stakeholder expectations) is important but not the primary reason for defining failure handling.

Option C (Capturing all defects) is a general testing principle, not specific to failure handling in performance tests.

Option D (Minimizing distractions) is not a valid reason for defining failure handling.

Crowd-based load generation involves using distributed users (e.g., cloud-based testers or real users). The main challenge is that the load generation can be difficult to reproduce consistently due to variations in network conditions, device types, and user behavior.

Option B is incorrect because load generation methods should adapt to system changes.

Option C is incorrect since mainframe applications typically do not rely on crowd-based testing.

Option D is incorrect because crowd-sourced load testing is generally less precise than scripted load testing.

REST (Representational State Transfer) is a widely used web service protocol that enables client-server communication over HTTP. It is commonly used in modern APIs and web applications for performance testing.

Option A (SOAK) refers to soak testing, which evaluates performance over an extended period.

Option C (HTTP) is a transport protocol, but REST is the actual web service architecture built on HTTP.

Option D (RTE) is not a web service protocol but may refer to Real-Time Enterprise systems.