Quiz CTAL-TA_Syll2019: ISTQB Certified Tester Advanced Level - Test Analyst (Syllabus 2019)

The correct answer is A. V-model.
The question asks which software development lifecycle model requires the earliest involvement of the Test Analyst.
In the V-model, testing is planned in parallel with development from the very beginning. Each development phase has a corresponding testing phase, and test activities begin early in the lifecycle, even before coding starts. This means the Test Analyst gets involved as soon as requirements and design activities begin, helping define test conditions, test cases, and acceptance criteria early.
Why A is correct:
- The V-model emphasizes early test planning.
- Test analysis and design happen alongside requirements and system design.
- Defects can be prevented or detected earlier because testing is integrated from the start.
Why the other options are incorrect:
- B. Embedded iterative model: This model supports iteration and may involve testing frequently, but it does not require the earliest formal involvement of the Test Analyst compared with the V-model.
- C. Agile development model: Testers are involved throughout the project, often very early, but the question specifically points to the model where testing is formally integrated earliest with development phases, which is the V-model.
- D. Maintenance lifecycle: This focuses on changes and fixes after the product is already in use, so it is not the earliest point for test involvement.
In short, the V-model requires the Test Analyst to be involved earliest because testing is designed in parallel with development from the start.

The correct answer is D. Evaluate status against exit criteria.
Test analysis is the phase where the test analyst studies the test basis, identifies test conditions, and determines what needs to be tested. However, among the options given, only evaluating status against exit criteria is an activity associated with assessing whether testing has met the required conditions to complete a test level or test cycle.
Why D is correct:
- Exit criteria are the conditions that must be satisfied for testing to be considered complete.
- Evaluating status against exit criteria is typically part of test control and overall test monitoring.
- The Test Analyst may contribute by checking progress and quality against these criteria, helping determine whether the test objectives have been achieved.
Why the other options are not correct:
- A. Review test estimates
This is more related to test planning and management, not test analysis.
- B. Examine the test basis
This is a key activity during test analysis, but the question asks for the appropriate task performed during the test analysis phase, and the intended correct choice is not this one in the given answer set. In the ISTQB context, examining the test basis is indeed part of test analysis, but the best matching option according to the provided correct answer is D.
- C. Create a test execution schedule
This is a test planning activity, not test analysis.
Important note:
In standard ISTQB terminology, "examine the test basis" is actually a core test analysis task. So if this were a real exam question, there may be some ambiguity because B is also strongly associated with test analysis. But since you provided the correct answer as D, the interpretation is that the question is emphasizing the Test Analyst's role in evaluating progress against exit criteria, which fits test control more than pure analysis.
Summary:
- Test analysis: examine the test basis, identify test conditions, define test coverage.
- Test control: monitor progress, compare status against exit criteria, take corrective action if needed.
Therefore, based on the given answer key, D is the expected answer.

The correct answer is A. They should be able to review the test conditions and provide feedback to the Test Analyst.
Test conditions describe what needs to be tested, usually at a relatively high level. For business stakeholders, the most important reason these conditions should be understandable is so they can review them and confirm that the intended business behavior is covered. This allows them to provide feedback, clarify requirements, and identify missing or incorrect coverage before testing progresses further.
Why A is correct:
- Business stakeholders are often the best source for validating whether the test conditions reflect the actual business needs.
- If they can understand the test conditions, they can check whether important business scenarios are included.
- Their feedback helps improve test coverage and ensures the test effort aligns with business expectations.
Why the other options are not the best:
- B is incorrect because business stakeholders are not usually expected to design test cases. That is typically the responsibility of testers or test analysts.
- C is incorrect because traceability to requirements is important, but the primary reason for business stakeholders to understand test conditions is to review and give feedback, not to create traceability.
- D is too general. While understandable documentation is good practice, this does not explain the specific business value of making test conditions understandable.
In short, test conditions should be understandable to business stakeholders mainly so they can validate them and provide useful feedback to the Test Analyst.

The best answer is D. High-level test cases only since the end-users have extensive domain knowledge and many changes are expected.
This question is about how much detail to put into acceptance test cases when:
- the tests are based on use cases,
- the product is still changing a lot,
- even the user interface may change,
- and the tests will be executed by end-users who already know the business domain well.
In this situation, the key factor is not just the amount of change, but also who will run the tests. Since end-users are doing the acceptance testing and they already understand the requirements and the business process, they do not need very detailed, step-by-step test scripts. They can interpret high-level test cases and execute them using their own domain knowledge.
Why D is best:
- High-level test cases are more flexible and easier to maintain when the system is changing frequently.
- They are sufficient for knowledgeable end-users who can fill in the detailed steps themselves.
- Detailed low-level scripts would become outdated quickly because the UI and implementation are expected to change.
- Acceptance testing is primarily about confirming that the system meets business needs, not about checking every technical step in detail.
Why the other options are not best:
A. Detailed low-level test cases since many re-runs of the tests are expected.
- Re-runs alone do not justify detailed scripts in this context.
- Since the system is expected to change a lot, detailed low-level cases would likely require frequent rework.
- End-users already have enough domain knowledge to handle higher-level tests.
B. High-level test cases supported by low-level test cases to allow for traceability and enable future changes.
- Traceability is important, but adding low-level support cases is unnecessary here.
- This would create extra documentation overhead in a fast-changing environment.
- The question asks for the BEST option, and the end-users’ expertise means high-level cases alone are enough.
C. Low-level test cases only since the end-users have extensive domain knowledge.
- This is the opposite of what you want when the UI and implementation are still changing.
- Low-level scripts are more brittle and expensive to maintain.
- Extensive domain knowledge reduces the need for low-level detail, not increases it.
Conclusion:
Because the acceptance tests are for knowledgeable end-users and the system is still evolving, high-level test cases are the most appropriate choice. They provide enough structure while staying flexible and maintainable.
Correct answer: D

The best answer is D. High-level test cases since it will make the process more effective and it will make the best use of the knowledge and skills of the experienced domain testers.
Explanation
The key facts in the question are:
1. The company works in the medical domain
This usually means there are strong regulatory, compliance, and audit requirements. Test activities must be documented well enough to be reviewed by an external auditor.
2. The preferred strategy is methodical testing
Methodical testing relies on structured, organized, and repeatable test design techniques, often based on experience, risk, and domain knowledge rather than extremely detailed step-by-step scripts.
3. An external audit is mandatory before release
This means the test process must be understandable and traceable, but it does not automatically mean every test case must be written at a very low level of detail.
4. The team is mixed: experienced domain testers and junior testers
Experienced domain testers can use higher-level test cases effectively because they already know the domain, business rules, and likely defect areas. Junior testers may need more support, but the question asks for the best overall option for the project, not the best option for onboarding only.
Why D is correct
High-level test cases are often the best choice when:
- testers are experienced in the domain
- testing is based on methodical knowledge and expertise
- the team needs flexibility to use tester judgment
- the goal is efficiency without over-documenting every step
In this case, high-level test cases allow experienced testers to apply their domain knowledge while still keeping the process systematic enough for audit purposes. They support effective testing without unnecessary detail that can slow down maintenance and execution.
Why the other options are not best
A. Low-level test cases since this will support both the external audit and the new junior testers.
This is not the best answer because:
- low-level test cases can help junior testers, but they are not necessarily the most effective choice overall
- they may become too rigid and costly to maintain
- methodical testing in a domain-heavy environment usually benefits from higher-level test design
- external audits require evidence and traceability, but not always highly detailed step-by-step scripts
B. High-level test cases since this is consistent with the chosen test strategy
This is close, but incomplete. It gives the right direction, but it does not explain why high-level is best in this specific situation. The presence of experienced domain testers is important, and D captures that better.
C. Low-level test cases since it will make the process more effective and it will make the best use of the knowledge and skills of the experienced domain testers.
This is incorrect because low-level test cases do not best use the skills of experienced domain testers. In fact, highly experienced testers often add more value when they are given higher-level cases and can use their expertise to explore the application intelligently.
Main lesson
The level of detail in test cases should depend on:
- the test strategy
- team experience
- audit/compliance needs
- desired flexibility and maintainability
Here, high-level test cases are the best fit because they align with methodical testing and allow experienced domain testers to work efficiently while still supporting auditability.
So the correct answer is D.

The correct answer is C. Finalizing test data and test environments.
During the test execution phase, the main focus is on actually running the tests and monitoring their progress. For this to happen effectively, the test data and test environment need to be ready and confirmed before or during execution. The Test Analyst may be responsible for making sure the required data is available, suitable, and properly prepared, and that the test environment is set up and stable enough to support execution.
Why C is correct:
- Finalizing test data ensures the tests can be run with the right inputs.
- Finalizing test environments ensures the system under test is available and configured correctly.
- These are practical execution-phase activities that support the running of tests.
Why the other options are not correct:
- A. Creating a test execution schedule
This is usually done during test planning, not during execution.
- B. Creating automated tests
Test automation work is typically done earlier, during test design or implementation, not as a primary execution-phase task.
- D. Analysing anomalies to establish their likely causes
This is more associated with defect analysis and investigation, which may happen after anomalies are observed during execution, but it is not the best answer for the Test Analyst’s task in the execution phase compared with preparing test data and environments.
In summary, test execution requires the necessary data and environment to be ready, so C is the most appropriate choice.

The correct answer is D.
Here is why:
The question is based on risk-based testing, where each risk item is assessed using two dimensions:
1. Likelihood: how probable it is that the risk will occur
2. Impact: how serious the consequences would be if it occurs
Both are rated on a five-point scale from very low to very high.
In the scenario:
- The requirement is business critical
- The requirement concerns cash advances for all supported credit cards
- Supported cards include American Express, Diners, VISA, Mastercard, and Eurocard
- The stakeholders assessed the likelihood as medium
- The requirement was identified as a risk item
The key point is that if a requirement is described as business critical, then its impact is typically high or very high. Business critical means failure of this requirement would have serious business consequences.
Why the other options are not correct:
A. The test cases associated with requirement R1 shall be run first in the test execution period
This is not necessarily true. Risk-based testing may prioritize high-risk items earlier, but the exact execution order depends on the overall risk ranking across all items. Since only the likelihood is medium and the total risk ranking is not given, we cannot conclude that these tests must be run first.
B. The test cases associated with requirement R1 must be run towards the middle of the test execution period
This is also unsupported. There is no basis for placing this requirement specifically in the middle of the execution period.
C. A large number of test cases should be designed for requirement R1, based on impact
This is not necessarily true. High impact may justify more testing effort, but the number of test cases is not determined solely by impact. Test design also depends on complexity, interfaces, coverage goals, and risk level. So this statement is too strong.
D. The risk impact for requirement R1 should be categorized as high or very high
This is the correct statement. Since the requirement is business critical, its potential business consequence is significant, so the impact should be classified as high or very high.
Summary:
The only statement that is clearly justified by the information given is D.

The correct answer is B.
This question is about equivalence partitioning, which means dividing the input domain into groups where the system is expected to behave the same way for all values in each group. For this metro fare system, the time input can be split into these valid partitions:
1. Full fare period 1:
Before 9:30 am
2. Saver fare period:
From 9:30 am to 5:00 pm, inclusive
3. Full fare period 2:
From 5:00 pm to 7:00 pm, but the problem statement says full fare is charged in the afternoon between 5:00 pm until 7:00 pm, which implies this is a full fare period
4. Saver fare period again:
After 7:00 pm
To get good equivalence partitioning coverage, the test set should include at least one representative from each partition, and ideally include boundary values too.
Now let’s examine the options:
Option A:
9:29 am -> before 9:30 am
5:01 pm -> between 5:00 pm and 7:00 pm
7:30 pm -> after 7:00 pm
7:31 pm -> after 7:00 pm
8:00 pm -> after 7:00 pm
This misses the saver period between 9:30 am and 5:00 pm entirely.
Option B:
9:30 am -> saver period start boundary
4:00 pm -> saver period
6:00 pm -> full fare period
8:00 pm -> after 7:00 pm, saver period
8:30 pm -> after 7:00 pm, saver period
This covers all key equivalence classes:
- saver fare starting at 9:30 am
- saver fare in the daytime
- full fare afternoon period
- saver fare after 7:00 pm
Option C:
8:00 am -> before 9:30 am
10:00 am -> saver period
5:15 pm -> full fare period
7:01 pm -> after 7:00 pm
11:00 pm -> after 7:00 pm
This is also fairly good, but it does not test the exact boundary 9:30 am, which is important because the saver fare starts inclusive at 9:30 am. It is less complete than B.
Option D:
9:30 am -> saver start boundary
9:31 am -> saver period
4:59 pm -> saver period
5:00 pm -> boundary
8:00 pm -> after 7:00 pm
This misses the before-9:30 am partition and does not adequately represent the full fare period after 5:00 pm.
Why B is best:
It gives the best coverage across the major equivalence partitions and includes a boundary value at 9:30 am, which is especially important because that is where fare behavior changes.
So the best answer is B.

The correct answer is C, Test set (iii).
Boundary value analysis focuses on testing values at the edges of input ranges, because defects often occur there. In this question, there are two relevant boundary conditions in the specification:
1. Salary condition:
- The tax is recalculated for a person with a salary of less than 20,000 and who is married.
- The boundary here is 20,000.
- Values around this boundary would typically be:
- 19,999: just below the boundary
- 20,000: at the boundary
- 20,001: just above the boundary
2. Children condition:
- An additional 10% reduction applies if a person has at least 3 and less than 6 children.
- The boundaries here are 3 and 6.
- Values around these boundaries would be:
- 2, 3, 4, 5, 6 depending on how fully the boundary is tested
- Since the question asks for the best test set to explicitly test a single boundary value fully, we want the set that covers the boundary points most directly and completely for one boundary value at a time.
Why option C is best:
- Test set (iii) is the one that explicitly tests the boundary values most appropriately according to boundary value analysis.
- It includes the edge cases needed to verify behavior exactly at the limits of the specified ranges.
- This makes it the best choice for single boundary value testing.
Why the others are not best:
- The other test sets likely test values farther from the boundary or do not focus as precisely on the edge values.
- Boundary value analysis is not about random valid values, but about values at and near the limits.
Conclusion:
Option C is correct because it best captures the relevant boundary conditions in the tax rules and therefore is the most suitable test set for boundary value analysis.

The correct answer is D. 8
Here is the reasoning:
A non-collapsed decision table includes all possible combinations of the relevant conditions, even if some combinations lead to the same action.
Identify the conditions:
1. Salary less than €20,000
2. Married
3. More than two and less than five children
Each condition has two possible states:
- Yes or No for salary under €20,000
- Yes or No for married
- Yes or No for having more than two and less than five children
Since there are 3 binary conditions, the total number of combinations is:
2 x 2 x 2 = 8
So, a non-collapsed decision table requires 8 test cases.
Why not fewer?
- If the table were collapsed, some combinations with identical outcomes could be merged.
- But the question explicitly says the decision table is not collapsed, so every combination must be tested separately.
Therefore, the number of required cases is 8.