CTFL-PT_D ISTQB Certified Tester Foundation Level - Specialist Performance Testing Questions and Answers

To calculate the number of departing passengers accessing the front-end only once to check in per hour, we follow these steps:

Total Departing Passengers in January:

465,000 passengers transported throughout January.

Duration of Operations in January:

Operating hours: 07:00 to 23:00, which equals 16 hours per day.

Total days in January: 31 days.

Total operating hours in January: 31 days * 16 hours/day = 496 hours.

Passengers Per Hour:

Total passengers: 465,000.

Total hours of operation: 496 hours.

Passengers per hour: 465,000 passengers / 496 hours = 937.5 passengers/hour.

Passengers Accessing Only Once for Check-In:

30% of departing passengers reconnect for a boarding pass, which means 70% access only once.

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.

Reproducibility is a fundamental principle of performance testing, ensuring that identical results are obtained when tests are repeated on an unchanged system. This principle is critical for verifying the reliability and consistency of performance test outcomes, allowing testers to confidently identify and address performance issues. ISTQB standards emphasize reproducibility to ensure that performance testing provides accurate and actionable insights.

Generating load through the User Interface (UI) is essential to replicate a real production environment accurately. This approach simulates real user interactions with the system, providing a more realistic assessment of how the system performs under actual usage conditions. According to ISTQB standards, using the UI to generate load helps identify performance issues that users might experience, ensuring that the test results are relevant and actionable.

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.

Ramp-up in performance testing refers to the phase where the number of virtual users is gradually increased to simulate the increase in load on the system. This is essential for determining how the system behaves under varying levels of stress. The correct description of the ramp-up concept aligns with option C, which involves increasing the number of concurrent users to simulate a transition from a steady state to a higher load scenario.

References:

ISTQB Performance Testing Syllabus

ISTQB Glossary

Virtualizing the servers is not typically part of performance test preparation. Performance test preparation generally involves activities such as deploying the test environment, setting up the system under test, and configuring load generation and monitoring tools to ensure accurate data collection. While virtualization can be an aspect of the overall infrastructure setup, it is not a direct step in preparing for performance testing. ISTQB performance testing guidelines emphasize setting up the environment, system, and tools specifically for performance test execution.

In the testing process, specific test conditions for performance testing are identified during the Test Analysis phase. This phase involves reviewing and analyzing the test basis, such as requirements, architecture, and design, to identify the test conditions, which are the items or events of a component or system that could be verified by one or more test cases.

References:

ISTQB Foundation Level Syllabus

ISTQB Glossary

Endurance testing, also known as soak testing, evaluates the stability and performance of a system over an extended period under a significant load. This type of testing is designed to identify issues such as memory leaks, resource depletion, and other long-term stability problems that may not be evident in shorter testing durations. According to ISTQB guidelines, endurance testing is essential for ensuring that the system can maintain performance and stability over time, especially in operational contexts.

Given the scenario of online check-in with peak user activity, the most suitable performance-related business objective would be to ensure that the system can handle a high number of concurrent users within a short period without performance degradation. Option A directly addresses the requirement to support peak loads while maintaining system performance, which aligns with the specified peak of 100 users per minute.

References:

ISTQB Performance Testing Syllabus

ISTQB Glossary