CTFL-PT_D Questions Bank

When preparing a presentation for business stakeholders, it is essential to focus on high-level objectives and outcomes that align with business goals. In the context of performance testing, the stakeholders are primarily concerned with ensuring that the system can handle peak loads and maintain operational integrity.

Option Atalks about the setup of the test environment and the logistics of passenger data, which is too technical for business stakeholders.

Option Bfocuses on budget and timeline, which are relevant but do not directly address the performance test's purpose and objectives.

Option Cclearly states the purpose of the performance test (spike test) and its objective, which is to verify that the system can support concurrent request peaks, directly aligning with business interests.

Option Dagain focuses on technical details about the test environment setup, which is not the primary concern for business stakeholders.

Therefore, Option C is the most appropriate choice as it succinctly communicates the performance test's objective and its relevance to business operations.

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.

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 isC. 625.00 departing passengers / hour.

Correlation is a critical step in preparing performance test scripts, especially when they are generated from protocol-level recordings. It involves handling dynamic values (such as session IDs or tokens) that change with each user session or transaction. Without correlation, the script fails to handle these dynamic values correctly, leading to playback errors. According to ISTQB principles, ensuring scripts are properly correlated is essential for accurate and functional test execution.