CTFL-PT_D Exam Dumps - ISTQB Certified Tester Foundation Level - Specialist Performance Testing

The correct associations between the aspects and factors to be considered when selecting performance testing tools are:

Compatibility: Protocols. (C)

Scalability: Ability to generate load from multiple points of presence. (D)

Understandability: Level of technical knowledge needed to use the tool. (A)

Monitoring: Correlation of the monitoring with the defined transactions. (B)

References:

ISTQB Performance Testing Syllabus

ISTQB Glossary

The scope of performance testing is established during the test planning phase. During this phase, testers define the objectives, resources, schedule, and scope of the testing activities. This includes identifying the specific performance requirements, determining the test environment, and outlining the test strategy. According to ISTQB guidelines, effective test planning ensures that the performance testing efforts are aligned with the project goals and stakeholder expectations, setting a clear direction for subsequent testing activities.

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.

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 determine how many departing passengers access the front-end per hour, including those reconnecting:

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.

Including Reconnecting Passengers:

30% of departing passengers reconnect for a boarding pass.

Reconnecting passengers: 30% of 937.5 passengers/hour = 0.30 * 937.5 = 281.25 passengers/hour.

Total front-end accesses per hour: 937.5 + 281.25 = 1,218.75 passengers/hour.

Given the available options, the closest correct value isA. 1,425.00 departing passengers / hour.