ISTQB® CTFL v4.0 Exam Practice Questions (P. 2)
- Full Access (125 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
Question #6
Which of the following is an advantage of the whole team approach?
- AAny person in the team with the right skills can perform any task
- BTasks are assigned to specific team members who will own that task until completion
- CTesters have clear ownership of quality and this eliminates confusion and overlap
- DBusiness representatives are not included in the team so they can supply independent assessment during UAT
Correct Answer:
A
A
GPT-4o - Answer
The key strength of the whole team approach is its flexibility and collaborative nature, allowing team members, regardless of their role, to perform any task they are skilled at. This adaptability enhances efficiency and supports a more integrated team dynamic, unlike approaches that rigidly assign tasks. It fosters not just personal accountability but collective responsibility, enabling the team to utilize varied expertise efficiently to tackle different tasks as needed. This approach is crucial for rapid adaptations and problem-solving, often leading to more cohesive and successful project outcomes.
Question #7
If you are using test results to learn more about the software and are then creating additional tests based on those results, what type of testing are you doing?
- AExploratory
- BDecision-based
- CChecklist-based
- DControl flow
Correct Answer:
A
A
GPT-4o - Answer
When you perform exploratory testing, you're actively learning about the software by testing it. As you obtain results, this knowledge assists in forming new tests. This iterative process of test creation based on learned outcomes, directly from interacting with the software, is a hallmark of exploratory testing. Essentially, you're continuously adapting your testing strategy in reaction to what is discovered during testing sessions, endorsing a flexible and responsive approach to uncovering defects and validating system behaviors.
Question #8
You are working on calculating the estimation for a project. You have been given the following numbers by your manager, who is considered to be an expert in estimation:
Optimistic = 35 days -
Likely = 40 days -
Pessimistic = 65 days -
Apply the three-point estimation technique, what is the proper expression of the final estimate?
Optimistic = 35 days -
Likely = 40 days -
Pessimistic = 65 days -
Apply the three-point estimation technique, what is the proper expression of the final estimate?
- AE is 46.3 days, SD = 35
- BE is 40 days, SD = 6.67
- CE is 37.3 days, SD = 43.3
- DE is 43.3 days, SD = 5
Correct Answer:
D
D
GPT-4o - Answer
The correct estimation using the three-point technique is calculated as the weighted average: \(E = \frac{(O + 4M + P)}{6}\), where Optimistic (O) = 35 days, Likely (M) = 40 days, and Pessimistic (P) = 65 days, leading to \(E = \frac{(35 + 4 \times 40 + 65)}{6} = 43.3\) days. The standard deviation is estimated as \(SD = \frac{P - O}{6}\), which is \(SD = \frac{65 - 35}{6} = 5\). Therefore, the suitable answer indicating a balanced estimation accounting for best and worst-case scenarios is indeed option D.
Question #9
Which black-box technique should be used to verify different responses of the system, depending on its current conditions or previous history?
- AUse case testing
- BDecision table testing
- CState transition testing
- DEquivalence partitioning
Correct Answer:
C
C
GPT-4o - Answer
For this scenario, we'd lean on state transition testing since it's perfect for checking how an application reacts under varying states or after specific sequences of events. This black-box approach maps out states and transitions clearly, revealing how input sequences and current states influence outcomes. Ideal for systems where the past conditions significantly impact the present behavior!
Question #10
You have been given the following story:
As a help desk worker -
I want to enter a caller’s birth date
So the system can display the caller’s account information
As a team, you have developed the following table of acceptance criteria:
You have developed the following test cases and will execute them in the specified order:
1. Enter a valid date and verify that the account retrieved matches the birth date entered.
2. Enter an invalid date and verify that the error indicates the date is invalid.
3. Verify that the date prompt is already formatted for the date with xx/xx/xx format.
4. Enter a valid date and verify that two pages of account information are readable.
5. Enter a valid date and verify that the response occurs within 2 seconds when the system is under an average load.
What is incorrect about this approach?
As a help desk worker -
I want to enter a caller’s birth date
So the system can display the caller’s account information
As a team, you have developed the following table of acceptance criteria:
You have developed the following test cases and will execute them in the specified order:
1. Enter a valid date and verify that the account retrieved matches the birth date entered.
2. Enter an invalid date and verify that the error indicates the date is invalid.
3. Verify that the date prompt is already formatted for the date with xx/xx/xx format.
4. Enter a valid date and verify that two pages of account information are readable.
5. Enter a valid date and verify that the response occurs within 2 seconds when the system is under an average load.
What is incorrect about this approach?
All Pages