Pass the ISTQB Test Manager Advanced CT-PT Questions and answers with ExamsMirror

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.

Crowd-based load generationrelies on real users from different locations, makingtest conditions highly variable. This makes itdifficult to reproduce the same test scenario multiple timesunder identical conditions.

Option B (Less sensitive to changes)is incorrect becausecrowd-based load is highly sensitive to external conditions(network, device types, etc.).

Option C (Suitable for mainframe applications)is incorrect becausecrowd-based load testing is typically used for web and cloud applications, not mainframes.

Option D (More precise than other methods)is incorrect becausecrowd-based load testing lacks precision due to real-world inconsistencies.

Spike testingis a type of performance testing that evaluates how a systemresponds to sudden, extreme increases or decreases in load. It is designed to simulateunexpected surges in user activity or workload, such as flash sales, viral events, or cyberattacks.

Option A (Gradual load increase testing)describesload testing, not spike testing.

Option B (Handling expected peak load)describesstress testing, which pushes the system to or beyond its limits but does not focus on sudden changes.

Option C (Meeting future efficiency requirements)relates tocapacity planningrather than spike testing.

Spike testing helps toidentify system bottlenecks, resource allocation issues, and performance degradationwhen traffic surges unexpectedly.

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.

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.

Astatic performance testis anon-execution-based reviewthat analyzes system architecture, network configurations, and other elements thataffect system performance before execution.

Option A (Usability test)is not a static performance test but rather a functional or UX evaluation.

Option B (Evaluation of testers' skills)is unrelated to performance testing.

Option D (Formal signature approval)is an administrative task and not a static test.

To ensure anaccurate operational profile, it is crucial tovalidate and adjust it with key stakeholders before executing tests. This step ensures that the workloadrealistically represents actual user behavior.

Option A (Executing the test first and adjusting later)is incorrect becauseadjustments should be made before executionto avoid misleading results.

Option C (Aggregating profiles into a single generic profile)removesimportant distinctions between different user types, reducing test accuracy.

Option D (Creating separate profiles and using equal proportions)does not match the actualpower purchaserbehavior, which requires arealistic representation of their higher-volume transactions.

Load testingassesses a system’s ability to handlegradually increasing levels of loadand ensures that it meets performance expectationsunder 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 onsuddenincreases in load rather thangradualscaling.

Option D (Endurance testing)examines how a system performsover an extended period, rather thangradual load increases.

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.

Performance monitoring toolscollectreal-time and historicalperformance data, particularly fromserver logs, application metrics, and infrastructure monitoring. This allows testers to analyze performance trends efficiently.

Option A is incorrectbecause monitoring toolsdo not preventmalicious behavior but may detect it.

Option C is incorrectsinceidentifying multi-threading issuesis typically done throughprofiling toolsrather than performance monitors.

Option D is incorrectasDoS attack detectionfalls undersecurity testing.