Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
Identify the correspondences between performance measures and metrics (1 -6) and the different environments (A C) in which performance evaluation is needed.
1. Alerts and warnings.
2. Concurrency of usage.
3. Operational processes.
4. Resource utilization.
5. Response time.
6. Throughput of data, transactions, and other units of work performed.
1. Operating environment.
2. Business environment.
3. Technical environment.
SELECT ONE OPTION
* 1A: Alerts and warnings are typically part of the operating environment to monitor and respond to issues in real-time.
* 2B: Concurrency of usage is critical in the business environment where multiple users interact with the system simultaneously.
* 3A: Operational processes are key aspects of the operating environment, ensuring the smooth running of day-to-day activities.
* 4C: Resource utilization is a technical concern, focusing on how effectively system resources are used.
* 5C: Response time is a technical metric that directly affects user experience and system efficiency.
* 6B: Throughput of data, transactions, and other units of work performed is relevant to the business environment where the volume of operations impacts overall performance.
This categorization aligns with the ISTQB framework for performance evaluation across different environments, ensuring comprehensive coverage of performance metrics.
(REFER TO BASE SCENARIO 2): When you refer to Base Scenario 2, you are referring to the description and only the description, without any modification.
Question specific constraints: (specific constraints are not part of the Base Scenario and are specific to this question).
Throughout the month of January (31 days), the company performed 3,100 departure operations from the Capital City Airport. These departure operations transported 465,000 passengers during the hours of operation, from 07:00 to 23:00.
The departing passengers (one of the most relevant operational profiles) will access the front-end of the application to check in for their flight. It is known that 30% of departing passengers reconnect after checking in to request the boarding pass to be resent or printed.
Question
How many departing passengers access the front-end only once to check in per hour?
SELECT ONE OPTION
To calculate the number of departing passengers accessing the front-end only once to check in per hour, we follow these steps:
1. Total Departing Passengers in January:
o 465,000 passengers transported throughout January.
2. Duration of Operations in January:
o Operating hours: 07:00 to 23:00, which equals 16 hours per day.
o Total days in January: 31 days.
o Total operating hours in January: 31 days * 16 hours/day = 496 hours.
3. Passengers Per Hour:
o Total passengers: 465,000.
o Total hours of operation: 496 hours.
o Passengers per hour: 465,000 passengers / 496 hours = 937.5 passengers/hour.
4. Passengers Accessing Only Once for Check-In:
o 30% of departing passengers reconnect for a boarding pass, which means 70% access only once.
o Passengers accessing only once: 70% of 937.5 passengers/hour = 0.70 * 937.5 = 656.25 passengers/hour.
Given the available options, the closest correct value is C. 625.00 departing passengers / hour.
If Emily is conducting a performance test to determine that a system exposed to a load can respond to a high number of concurrent users during short periods of time that occur on specific days and at specific times, and then return to a stable state.
What type of performance testing is Emily conducting?
SELECT ONE OPTION
Spike testing involves subjecting a system to a significant increase in load for short periods of time to determine if it can handle sudden spikes in traffic. Emily's scenario of testing a system's response to a high number of concurrent users during specific periods and then returning to a stable state fits the description of spike testing.
* ISTQB Performance Testing Syllabus
* ISTQB Glossary
Given the following list of approaches to load generation, select the load generation approach that is LEAST reproducible and accurate.
SELECT ONE OPTION
Load generation using crowds (crowdsourcing) is the least reproducible and accurate approach. This method involves using a large number of real users to generate load on the system. The variability in network conditions, user behavior, and device capabilities makes it difficult to reproduce the exact same load conditions consistently.
* ISTQB Performance Testing Syllabus
* ISTQB Advanced Level Test Automation Engineer Syllabus
Select the ONE option that describes the mechanism used to extract metrics associated with deadlocks and multi threading problems
SELECT ONE OPTION
Direct measurement through a performance monitoring tool is the most effective mechanism for extracting metrics associated with deadlocks and multithreading problems. These tools can provide real-time insights into the system's performance, highlighting issues such as thread contention, deadlocks, and resource bottlenecks. ISTQB performance testing principles advocate the use of specialized monitoring tools to capture detailed performance metrics, facilitating the identification and resolution of complex multithreading issues.
Identify the correspondences between the communication protocols used most frequently (listed from 1 to 5) in performance testing and the categories to which they belong to (A to C).
1.REST.
2. HTTP.
3. JDBC.
4. SOAP.
5. HTTPS.
1. Web service.
2. Database.
3. Web.
SELECT ONE OPTION
* 1A: REST - Web service
* 2C: HTTP - Web
* 3B: JDBC - Database
* 4A: SOAP - Web service
* 5C: HTTPS - Web
This mapping accurately categorizes each protocol according to its common use in performance testing. REST and SOAP are typically used for web services, JDBC for database connectivity, and HTTP/HTTPS for web communications. Understanding these correspondences helps testers select the appropriate protocols for performance testing scenarios, as outlined in ISTQB guidelines.
Exam domains verified against: Official iSQI CTFL-PT_D exam guide, last checked October 2026.
This section covers the core concepts of software testing and the fundamental principles that underpin effective testing practices. It explores why testing is a crucial component of software development and tests the ability of learners to gain insight into the primary objectives of testing.
This section covers integrating testing practices across different software development methodologies and how testing adapts to various development approaches. It ensures quality at every stage of the software lifecycle and explores how testing fits into the DevOps collaborative framework.
This section covers software quality assurance that occurs without executing code. It explores the basics of static testing techniques, including code reviews and static analysis tools that identify defects early in development.
This section covers various techniques for deriving effective test cases including black-box testing methods that focus on functionality and white-box testing that examines code internal structure. It also covers experience-based techniques for test design.
This section addresses effective test management for successful software quality assurance. It covers the essentials of test planning and techniques for estimating test effort accurately to support project delivery.
This section addresses effective test management for successful software quality assurance. It covers the essentials of test planning and techniques for estimating test effort accurately to support project delivery.
This section focuses on testing tools and automation with a framework for classifying different types of testing tools and their applications. It covers tool selection criteria and integration into testing processes.
Common questions about the exam itself
