Important ISTQB CT-PT Exam Questions

Answer: C

Explanation:

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.

Answer: D

Explanation:

Test implementation is the stage where smaller test components are created and assembled into larger test scenarios. This phase includes scripting, test data preparation, and configuring load profiles.

Option A (Test completion) involves analyzing results, not building tests.

Option B (Test planning) focuses on strategies and objectives, not test creation.

Option C (Test design) defines test scenarios and cases, but the actual building happens in implementation.

Answer: B

Explanation:

Wait time is the period a transaction spends waiting for resources, database responses, or external services before completing. It is critical for understanding real-world transaction durations.

Option A (Think time) refers to user delays, not system delays.

Option C (Action time) focuses on execution time only.

Option D (User time) is not a standard performance metric.

Answer: C

Explanation:

A key risk in distributed systems is unreliable remote servers, which can lead to latency, timeouts, and failures in performance testing.

Option A (Hard disk de-fragmentation) is not a significant risk in distributed systems.

Option B (Excess memory) is a positive factor, not a risk.

Option D (Bluetooth connectivity) is unrelated to distributed system performance.

Answer: A

Explanation:

Before running the next set of performance tests, it is crucial to understand the differences (delta) between the previous test results and the expected improvements. This ensures that:

The changes made by developers are properly validated.

Performance objectives are aligned with measurable improvements.

Option B (Adjust stakeholder expectations) is incorrect, as performance testing should focus on real data rather than adjusting expectations.

Option C and D (Realign objectives for milestones or time-to-market goals) are incorrect because test objectives should focus on technical accuracy rather than schedule constraints.