CT-PT Exam Questions & Answers

If multiple virtual users execute the same script while logged in as the same user, it can cause data conflicts, session collisions, or cache interference, leading to inconsistent performance test results.

Option A (Concurrent scripts accessing the same data) may cause data locking issues, but this is a test setup concern rather than an inconsistency issue.

Option B (Sequential scripts accessing the same data) does not typically cause inconsistencies since they execute in order.

Option D (Verification with management) is unrelated to technical inconsistencies.

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.

Load testing assesses a system's ability to handle gradually increasing levels of load and ensures that it meets performance expectations under normal and peak conditions.

Option B (Elevation testing) is incorrect because this term does not exist in ISTQB performance testing terminology.

Option C (Spike testing) focuses on sudden increases in load rather than gradual scaling.

Option D (Endurance testing) examines how a system performs over an extended period, rather than gradual load increases.

A load management console is a tool that helps testers analyze and visualize test results, providing performance reports, graphs, and insights. This aids in understanding bottlenecks, response times, and throughput trends.

Option A (Simulating user behavior) is incorrect; load generators handle simulation.

Option B (Senior management monitoring) is not the primary role of a test console.

Option D (Emulating virtual users) is incorrect; that is the job of load injectors.

One of the key performance risks in mainframe architectures is slow hard disk speed, which can impact transaction processing, batch jobs, and database access times.

Option A (Inconsistent loads via APIs) is more relevant to distributed or cloud architectures rather than mainframes.

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

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