CT-PT Exam Dumps - ISTQB Certified Tester - Performance Testing

Forsafety-critical software, performance goalsmust be identified as early as the requirements phase. This ensures thatperformance constraints are well understood and accounted for throughout development.

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

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

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

One of thebest practices in performance test scriptingis tovalidate that correct data is recorded in the databaseafter execution. This ensures thatperformance issues do not impact data integrity.

Option A (Increasing the number of scripts)may providemore coverage but does not verify accuracy.

Option C (Adding transaction timers)is useful for performance monitoring but does not ensurecorrect data entry.

Option D (Holding the development team accountable)is amanagement responsibility, not a scripting best practice.

Nested transactionsallow performance tests to capture bothindividualandaggregatedelements bygrouping multiple related transactionsand measuring their cumulative impact.

Option A (Aggregated metrics)provides summaries but lacks insight into individual elements.

Option B (Process optimization tracking)focuses onbusiness process improvement, not test metrics.

Option C (Measuring underlying transactions)focuses only onindividualtransactions.

Akey risk in distributed systemsisunreliable remote servers, which can lead tolatency, timeouts, and failuresin performance testing.

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

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

Option D (Bluetooth connectivity)is unrelated todistributed system performance.

One of the mostcritical test acceptance criteriain performance testing is toensure that the hardware in the test environment is comparable to production. Differences inCPU, memory, disk I/O, or network infrastructurecandistort 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, butwithout a comparable test environment, baseline metrics may be misleading.