Free Practice Questions for ISTQB CT-PT Exam

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.

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.

Protocol-level scriptsmeasure theactual response times of network requests, making them ideal foranalyzing network latency, bandwidth issues, and server response times.

Option A (GUI scripts)measure user interactions, not network timing.

Option B (API scripts)measure API interactions but do not providedetailed network response time analysis.

Option C (HTTP scripts)measure web requests but lack low-level network insights.

Forbatch processing performance metrics, the two most important factors are:

Throughput– Measures the number of transactions processed over time.

Wait times– Evaluates delays in processing batches.

Option B (Number of records deleted)is irrelevant unless batch processing specifically involves deletions.

Option C (Network latency percentage)applies toreal-time transaction processing, not batch jobs.

Option D (Concurrent virtual users)applies more toload testingrather than batch performance.

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.

Iftimeouts and excessive wait times occur, butthroughput is high, this suggests thatthe system is unable to process requests fast enough. This points toslow processing speeddue toCPU bottlenecks, memory limitations, or inefficient database queries.

Option A (Network infrastructure investigation)would be relevant if throughput wasloworvariable.

Option C (Impatient virtual users)is irrelevant; virtual users followscripted behaviors.

Option D (New test data)does not address the core issue.

One of the keyperformance risks in mainframe architecturesisslow hard disk speed, which canimpact transaction processing, batch jobs, and database access times.

Option A (Inconsistent loads via APIs)is more relevant todistributed or cloud architecturesrather than mainframes.

Option C (Misconfigured host machine)is aconfiguration issue, not a typical performance risk.

Option D (Lack of RAM)is less common in mainframes, which typically useoptimized memory management.

Business stakeholders aremost concerned with risks that affect deployment and production stability. The primary risk in performance testing is that thetest environment may differ from production, leading to misleading test results.

Option A (HTTP response goals)is too technical for abusiness stakeholder audience.

Option B (Hardware specifications)is relevant for technical teams, not business stakeholders.

Option C (Support staff details)is alogistical aspect, not a key performance testing risk for business decision-makers.

Stress testingis designed to evaluate how a system behavesunder extreme conditions, often exceeding its design limitations. The goal is to identify bottlenecks, memory leaks, and failures that occurbeyond normal operating conditions.

Option A is incorrectbecause it refers toresilience testing, which focuses on recovery rather than stress beyond limits.

Option B is incorrectas it describesload testing, which measures performance under expected loads.

Option C is incorrectsincedetermining the maximum transactionsis a feature ofcapacity testing, not stress testing.