ISTQB CT-PT Dumps in PDF and Online - Page: 4

QUESTION: 9

Which of the following is an advantage of using performance monitoring tools?

They can prevent malicious behavior.
They proactively compile metrics from server logs.
They more easily identify and report multi-threading problems.
They can proactively detect denial-of-service (DoS) attacks.

Answer(s): B

Explanation:

Performance monitoring tools collect real-time and historical performance data, particularly from server logs, application metrics, and infrastructure monitoring. This allows testers to analyze performance trends efficiently.

Option A is incorrect because monitoring tools do not prevent malicious behavior but may detect it.

Option C is incorrect since identifying multi-threading issues is typically done through profiling tools rather than performance monitors.

Option D is incorrect as DoS attack detection falls under security testing.

Reference:

ISTQB CT-PT Syllabus, Section 3.2: Performance Monitoring Tools.

Reveal Solution Next Question

QUESTION: 10

Which of the following is usually identified by a performance test?

Resource bottlenecks
Suitability issues
Learnability concerns
Failure to meet accessibility requirements

Answer(s): A

Explanation:

Performance tests primarily identify resource bottlenecks such as CPU saturation, memory leaks, network congestion, and database slowdowns.

Option B (Suitability issues) is a functional requirement concern, not a performance issue.

Option C (Learnability concerns) relates to usability testing, not performance.

Option D (Accessibility requirements) falls under compliance and usability testing, not performance testing.

Reference:

ISTQB CT-PT Syllabus, Section 2.5: Identifying Bottlenecks and Performance Issues.

Reveal Solution Next Question

QUESTION: 11

During which of the principal performance testing activities are the building blocks for larger, more complex tests created?

During test completion
During test planning
During test design
During test implementation

Answer(s): D

Explanation:

Test implementation is the stage where smaller test components are created and assembled into larger test scenarios. This phase includes scripting, test data preparation, and configuring load profiles.

Option A (Test completion) involves analyzing results, not building tests.

Option B (Test planning) focuses on strategies and objectives, not test creation.

Option C (Test design) defines test scenarios and cases, but the actual building happens in implementation.

Reference:

ISTQB CT-PT Syllabus, Section 1.4: Performance Testing Process.

Reveal Solution Next Question

QUESTION: 12

When following the principal performance testing activities, when are resources allocated?

During test planning
During test execution
During test evaluation
During test completion

Answer(s): A

Explanation:

Resource allocation happens during the test planning phase, where hardware, tools, and personnel are assigned to the project. This ensures that performance tests are adequately supported.

Option B (Test execution) is when resources are actually used, not allocated.

Option C (Test evaluation) happens after execution to analyze results.

Option D (Test completion) focuses on documentation and reporting.

Reference:

ISTQB CT-PT Syllabus, Section 1.3: Test Planning in Performance Testing.

Reveal Solution Next Question

QUESTION: 13

Which of the following is a typical performance risk associated with distributed architectures?

A local hard disk that has been de-fragmented
Excess computer memory resources
Unreliable or unpredictable remote servers
Inconsistent Bluetooth connectivity

Answer(s): C

Explanation:

A key risk in distributed systems is unreliable remote servers, which can lead to latency, timeouts, and failures in performance testing.

Option A (Hard disk de-fragmentation) is not a significant risk in distributed systems.

Option B (Excess memory) is a positive factor, not a risk.

Option D (Bluetooth connectivity) is unrelated to distributed system performance.

Reference:

ISTQB CT-PT Syllabus, Section 2.7: Performance Risks in Distributed Systems.

Reveal Solution Next Question

QUESTION: 14

Which of the following is a typical performance risk associated with mobile, browser-based, and embedded real-time architectures?

Slow hard disk speed
Misconfigured host machine
Unexpected loads due to API accessibility
Internet connectivity issues

Answer(s): C

Explanation:

Mobile and browser-based applications often rely on APIs for data retrieval and processing. Unexpected API load can cause latency issues, bottlenecks, and system crashes.

Option A (Hard disk speed) is not a major issue in cloud-based or mobile systems.

Option B (Misconfigured host machine) affects on-premise systems, not mobile/browser-based applications.

Option D (Internet connectivity issues) is a user-side issue, not a system performance risk.

Reference:

ISTQB CT-PT Syllabus, Section 2.7.2: Mobile and Web Performance Risks.

Reveal Solution Next Question

QUESTION: 15

Which of the following is a typical performance risk associated with mainframe architectures?

Inconsistent loads when accessed via APIs
Slow hard disk speed
Misconfigured host machine
Lack of RAM

Answer(s): B

Explanation:

One of the key performance risks in mainframe architectures is slow hard disk speed, which can impact transaction processing, batch jobs, and database access times.

Option A (Inconsistent loads via APIs) is more relevant to distributed or cloud architectures rather than mainframes.

Option C (Misconfigured host machine) is a configuration issue, not a typical performance risk.

Option D (Lack of RAM) is less common in mainframes, which typically use optimized memory management.

Reference:

ISTQB CT-PT Syllabus, Section 2.7.3: Performance Risks in Mainframe Architectures.

Reveal Solution Next Question

QUESTION: 16

You are managing a project that is testing a system that manages a newly redesigned jet engine for heavy aircraft. Given the fact that this engine is specifically engineered to reduce noise, it is important that the software maintains enough thrust for lift for a period of 5 minutes without exceeding 87.5dB. The software must achieve this independent of other internal systems such as fuel or navigation management.

Given the risk for the ability of the aircraft to meet the noise abatement regulations while still being able to fly, when is the optimum time in the software lifecycle to apply the performance testing?

Preferably during each phase in the lifecycle
Preferably at the end of system testing
Preferably during system integration testing
Preferably at the end of unit testing

Answer(s): A

Explanation:

Performance testing should be integrated into every phase of the software lifecycle to ensure that critical performance requirements (such as thrust-to-noise ratio) are met early and continuously validated.

Option B (End of system testing) is too late, as issues may be costly to fix at that stage.

Option C (During system integration testing) is useful but not comprehensive enough.

Option D (At the end of unit testing) is incorrect because unit tests do not assess overall system performance.

Reference:

ISTQB CT-PT Syllabus, Section 1.2: When to Conduct Performance Testing.

Reveal Solution Next Question

ISTQB Certified Tester - Performance Testing CT-PT Dumps in PDF

Free ISTQB CT-PT Real Questions (page: 4)

QUESTION: 9

Explanation:

Reference:

QUESTION: 10

Explanation:

Reference:

QUESTION: 11

Explanation:

Reference:

QUESTION: 12

Explanation:

Reference:

QUESTION: 13

Explanation:

Reference:

QUESTION: 14

Explanation:

Reference:

QUESTION: 15

Explanation:

Reference:

QUESTION: 16

Explanation:

Reference: