I85PREP
⌘ K
ISTQB CTAL-ATT study materials
ISTQB CTAL-ATT study resources

ISTQB CTAL-ATT practice questions

One question at a time. Build your ISTQB CTAL-ATT understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Requirements Engineering

In a technical test analysis for a system with a REST API, which work product most directly supplies the input and output data constraints needed to design API-level test conditions?

  1. The interface specification describing endpoint parameters, payload schemas and status codes Correct answer.
  2. The test summary report from the previous release
  3. The project risk register listing business-level schedule risks
  4. The configuration management plan for the test environment

Explanation

Technical test analysis derives test conditions from specifications of the interfaces under test, so the interface specification with its parameters, schemas and response codes is the primary source. Risk registers and plans guide prioritisation and logistics rather than data constraints.

Question 2Requirements Engineering

Which statement best describes the difference between test analysis and test design in a technical testing context?

  1. Analysis produces the exit report; design produces the entry criteria
  2. Analysis executes tests; design records the results in the incident log
  3. Analysis defines what to test as test conditions; design defines how to test them as test cases and procedures Correct answer.
  4. Analysis selects tools; design approves the test strategy

Explanation

Test analysis identifies and prioritises test conditions (what to test), while test design turns those conditions into concrete test cases and procedures (how to test). Execution and reporting are later activities in the test process.

Question 3Requirements Engineering

A team must decide how rigorously to review a requirements specification for an embedded braking controller. Which factor most strongly justifies a formal, documented review process?

  1. The reviewers are geographically distributed across time zones
  2. The project uses an agile delivery model with short iterations
  3. The requirements are safety-related and defects escaping to later phases carry high cost and risk Correct answer.
  4. The requirements document exceeds fifty pages in length

Explanation

Review rigour should be driven by risk: safety-related, high-consequence requirements justify formal, documented reviews with defined roles and records. Document size, distribution or delivery model may influence logistics but not the fundamental need for formality.

Question 4Requirements Engineering

When reviewing a requirement written as 'The system shall respond quickly to user requests', which review type is most appropriate as the first step?

  1. A technical review focused on verifiability and measurability of the requirement Correct answer.
  2. A walkthrough led by the author to explain the design
  3. A management review focused on budget allocation
  4. An audit verifying compliance with statutory regulations

Explanation

The defect is ambiguity and lack of measurability, which is a technical content issue best found in a technical review examining verifiability. Management reviews, audits and design walkthroughs address different objectives.

Question 5Requirements Engineering

Which characteristic of a good requirement is violated by the statement 'The system shall allow login using a username and password or a fingerprint'?

  1. Necessity, because authentication is not needed for the system
  2. Traceability, because no stakeholder is named
  3. Atomicity, because it combines two distinct authentication options in one requirement Correct answer.
  4. Feasibility, because fingerprint readers do not exist

Explanation

A good requirement should be atomic, expressing a single verifiable condition; combining two alternative authentication mechanisms in one statement makes it non-atomic and harder to test and trace. The other listed characteristics are not the primary defect here.

Question 6Requirements Engineering

A requirements engineer uses a perspective-based reading technique on an interface specification. What is the main benefit of this technique?

  1. It removes the need for a review moderator
  2. It replaces the need for test analysis
  3. It guarantees that all defects are found in a single review pass
  4. Different reviewers apply different stakeholder viewpoints to find defects that a single viewpoint would miss Correct answer.

Explanation

Perspective-based reading assigns reviewers distinct viewpoints (for example user, designer, tester) so that each finds different classes of defects, increasing coverage. It does not guarantee completeness or remove roles such as the moderator.

Question 7Requirements Engineering

During test analysis of a requirements specification, a tester identifies a missing requirement for handling timeouts on a payment gateway. What is the most appropriate action?

  1. Ignore it because requirements are the business analyst's responsibility
  2. Silently design a test based on an assumed timeout value
  3. Raise it as a defect or question against the requirements specification and record it for traceability Correct answer.
  4. Log it as a product incident after release

Explanation

Test analysis explicitly includes evaluating the test basis for defects and gaps, so missing requirements should be raised and recorded rather than assumed or deferred. Acting on assumptions risks testing the wrong behaviour.

Question 8Requirements Engineering

Which item is the most appropriate output of the test analysis activity for a technical system?

  1. A fully executed test log with pass and fail statuses
  2. A defect report describing a production outage
  3. A signed-off test strategy document
  4. A prioritised list of test conditions with traceability to the requirements and risks Correct answer.

Explanation

Test analysis produces prioritised test conditions, typically traceable to their sources such as requirements and risks. Execution logs, strategies and incident reports arise from other activities.

Question 9Requirements Engineering

A tester applies equivalence partitioning to a requirement stating that an API accepts an integer port number from 1 to 65535. Which set of test conditions best reflects the partitions?

  1. Only the value 1 and the value 65535
  2. Valid values within 1 to 65535; invalid values below 1; invalid values above 65535 Correct answer.
  3. Random values across the full integer range
  4. Only the value 32768 as a representative

Explanation

Equivalence partitioning divides the input domain into classes treated as equivalent: one valid range and two invalid ranges (below and above). Testing boundary values alone or a single representative does not cover all partitions.

Question 10Requirements Engineering

For the same port-number requirement (1 to 65535), which boundary value analysis test conditions are most complete?

  1. 0, 1, 2 and 65534, 65535, 65536 Correct answer.
  2. 32767 and 32768 only
  3. 1 and 65535 only
  4. 0 and 65536 only

Explanation

Two-value and three-value boundary analysis around each boundary gives 0, 1, 2 and 65534, 65535, 65536, covering the boundary and its neighbours on both sides. Testing only the boundaries or only the outside values leaves gaps.

Question 11Requirements Engineering

A requirement states that a discount applies when the order total is greater than 100 and the customer is a member. Which test design technique most directly targets the combinations of these conditions?

  1. Pairwise testing of configuration parameters
  2. State transition testing
  3. Use case testing
  4. Decision table testing Correct answer.

Explanation

Decision table testing systematically models combinations of conditions and their resulting actions, which suits the conjunction of order total and membership. State transition testing targets sequences of states, not condition combinations.

Question 12Requirements Engineering

A tester is designing tests from a state machine for a vending machine with states Idle, AcceptingCoins, Dispensing and OutOfService. Which technique is most appropriate and why?

  1. Decision table testing, because conditions combine into actions
  2. Equivalence partitioning, because inputs fall into valid and invalid ranges
  3. Boundary value analysis, because coin values have limits
  4. State transition testing, because behaviour depends on the current state and the triggering event Correct answer.

Explanation

State transition testing is chosen when system behaviour depends on its current state and the events that trigger transitions, which is exactly the vending machine scenario. The other techniques address input domains or condition combinations rather than state-dependent behaviour.

Question 13Requirements Engineering

Which activity in requirements engineering most directly enables bidirectional traceability between requirements and test conditions?

  1. Estimating the testing effort using function points
  2. Assigning a unique, stable identifier to each requirement and recording links in a traceability matrix Correct answer.
  3. Rewriting all requirements as user stories
  4. Holding a kick-off meeting with stakeholders

Explanation

Bidirectional traceability requires unique, stable requirement identifiers and recorded links, typically in a traceability matrix, so each requirement maps to test conditions and back. Meetings, story formats and estimation do not themselves create traceable links.

Question 14Requirements Engineering

A requirement is written as 'The report module shall generate reports.' Which review finding is most specific and actionable?

  1. The requirement lacks a priority field
  2. The requirement is too short to be a real requirement
  3. The requirement is ambiguous and unverifiable because report content, format and trigger are unspecified Correct answer.
  4. The requirement should be split into a user story with story points

Explanation

The defect is that the requirement is ambiguous and cannot be verified because the content, format and trigger of the report are undefined. This finding names the specific quality characteristic violated and guides the author to add measurable detail.

Question 15Requirements Engineering

In a review of an interface specification, a reviewer records a defect stating that the error response for an invalid token is not defined. Which review role is responsible for ensuring this defect is tracked to closure?

  1. The moderator Correct answer.
  2. The manager
  3. The author
  4. The scribe

Explanation

The moderator plans the review, ensures defects are recorded and follows up until they are resolved. The author fixes the defect, the manager may allocate resources, and the scribe records findings during the meeting.

Question 16Requirements Engineering

Which statement about the entry criteria for a formal requirements review is most accurate?

  1. Entry criteria confirm that the document is available, version-controlled and meets defined quality thresholds before the review starts Correct answer.
  2. Entry criteria replace the need for exit criteria
  3. Entry criteria are defined after the review meeting to reflect the findings
  4. Entry criteria are only relevant to management reviews

Explanation

Entry criteria define preconditions such as document availability, correct version and quality thresholds that must be satisfied to start a formal review. They are defined in advance and are distinct from, not a replacement for, exit criteria.

Question 17Requirements Engineering

A tester must design tests for a requirement describing a complex algorithm with many interdependent parameters where no reliable model exists. Which approach is most appropriate?

  1. Waiting until a formal model is produced before any testing
  2. Exhaustive boundary value analysis of every parameter
  3. Strict decision table testing of all parameter combinations
  4. Exploratory testing guided by test charters, combined with experience-based techniques Correct answer.

Explanation

When the test basis is weak or the system is complex with no reliable model, experience-based approaches such as exploratory testing guided by charters are appropriate and can be combined with other techniques. Exhaustive combination testing is impractical, and blocking all testing is not justified.

Question 18Requirements Engineering

Which of the following best characterises a requirement that is 'testable' in the context of technical test analysis?

  1. The requirement has been approved by the product owner
  2. The requirement has a unique identifier
  3. The requirement is written in natural language
  4. An independent tester can determine objectively, from defined inputs and expected results, whether the requirement is met Correct answer.

Explanation

Testability means an objective, repeatable determination of whether the requirement is satisfied is possible from defined inputs and expected results. Approval, language and identifiers support process but do not make a requirement testable.

Question 19Requirements Engineering

A team uses a traceability matrix and finds a test condition with no linked requirement. What is the most likely interpretation and appropriate action?

  1. The requirement must be rewritten to match the test condition
  2. The test condition is automatically invalid and must be deleted
  3. The traceability matrix is corrupt and should be discarded
  4. The test condition may be an orphan; check whether it derives from a missing or implicit requirement and raise it for clarification Correct answer.

Explanation

An unlinked test condition is a potential orphan that may indicate a missing or implicit requirement, so it should be investigated and clarified rather than deleted. Traceability gaps are signals to examine, not automatic proof of error.

Question 20Requirements Engineering

Which statement about the relationship between risk analysis and requirements-based test analysis is correct?

  1. Risk analysis eliminates the need to analyse requirements
  2. Risk analysis applies only to non-functional requirements
  3. Risk analysis helps prioritise which requirements and test conditions receive the most rigorous testing Correct answer.
  4. Requirements analysis replaces risk analysis entirely

Explanation

Risk analysis informs prioritisation, so test conditions derived from high-risk requirements receive more rigorous and earlier testing. It complements rather than replaces requirements analysis and applies across functional and non-functional requirements.

Question 21Requirements Engineering

A specification contains the phrase 'the system shall be user-friendly'. Which review comment is most useful to the author?

  1. Remove the requirement because usability cannot be tested
  2. Replace it with 'the system shall be very user-friendly'
  3. State measurable usability criteria such as task completion time or error rate so the requirement can be verified Correct answer.
  4. Move the requirement to the design document without change

Explanation

The defect is non-measurability; the fix is to express usability in verifiable terms such as task completion time or error rate. Strengthening the adjective, deleting the requirement or relocating it does not make it testable.

Question 22Requirements Engineering

Which technique best supports designing test conditions for a requirement describing a business process with multiple alternative paths and exception flows?

  1. Use case testing Correct answer.
  2. State transition testing
  3. Boundary value analysis
  4. Equivalence partitioning

Explanation

Use case testing derives test conditions from the main flow, alternative flows and exception flows of a business process, giving coverage of realistic end-to-end paths. Boundary and equivalence techniques address data domains, and state transition testing targets state-dependent behaviour.

Question 23Requirements Engineering

During a review, two reviewers disagree about whether a requirement is a defect. What is the most appropriate moderator action?

  1. Remove the finding to keep the review on schedule
  2. Close the review immediately and reconvene later
  3. Accept the opinion of the most senior reviewer without discussion
  4. Facilitate a focused discussion to reach consensus and, if unresolved, record it as an open issue for follow-up Correct answer.

Explanation

The moderator's role is to keep the review focused and constructive, facilitating consensus and recording unresolved items as open issues for later resolution. Deferring to seniority, dropping findings or abruptly closing the review undermines the review's purpose.

Question 24Requirements Engineering

Which of the following is the best example of a test condition derived during technical test analysis for a message-queue integration?

  1. The test lead owns the integration test plan
  2. Messages are processed in order when the consumer restarts after a failure Correct answer.
  3. The queue component uses version 3.2 of the broker
  4. The integration test will run in the staging environment

Explanation

A test condition states something to be verified, such as ordered processing after a consumer restart following failure. Tool versions, environment choices and ownership are planning and logistics details, not test conditions.

Question 25Requirements Engineering

Which statement best explains why requirements reviews are more cost-effective than finding the same defects during system testing?

  1. Defects found in requirements can be corrected before design and code are built on the faulty requirement, avoiding rework across later phases Correct answer.
  2. Reviews are cheaper because they require no preparation
  3. Reviews guarantee that no defects reach later phases
  4. Reviews replace the need for any dynamic testing

Explanation

Early defect detection avoids the cascading rework of design, code and tests built on a faulty requirement, which is why reviews are cost-effective. Reviews still require preparation, cannot guarantee zero escapes, and do not replace dynamic testing.

Question 26Requirements Engineering

In requirements engineering for a technical system, which characteristic distinguishes a functional requirement from a non-functional requirement?

  1. A functional requirement describes a behaviour or function the system must perform, while a non-functional requirement constrains qualities such as performance or reliability. Correct answer.
  2. A functional requirement is written by testers, while a non-functional requirement is written by business stakeholders.
  3. A functional requirement always concerns the user interface, while a non-functional requirement always concerns the database layer.
  4. A functional requirement can be verified by testing, while a non-functional requirement cannot be verified by testing.

Explanation

Functional requirements specify what the system does, i.e., behaviours and transformations of inputs to outputs. Non-functional requirements specify quality attributes and constraints such as performance, security, usability, and reliability. Both types must be verifiable, and authorship is not what separates them.

Question 27Requirements Engineering

A requirement reads: 'The gateway shall process incoming orders within an acceptable time.' Which review finding best identifies the defect in this requirement?

  1. The term 'acceptable time' is not measurable, so the requirement is not verifiable and needs a quantified threshold. Correct answer.
  2. The requirement mixes functional and non-functional concerns and should be split into two documents.
  3. The requirement uses 'shall', which is discouraged in technical specifications.
  4. The requirement is too detailed and should be generalized to allow implementation flexibility.

Explanation

A verifiable requirement must state a criterion that can be checked objectively, such as a maximum latency in milliseconds. 'Acceptable time' leaves the threshold undefined, so no test can determine pass or fail. Quantifying the threshold resolves the defect.

Question 28Requirements Engineering

Which requirements engineering activity establishes the link that lets a tester confirm every requirement is covered by at least one test?

  1. Requirements prioritization
  2. Requirements validation
  3. Requirements traceability Correct answer.
  4. Requirements elicitation

Explanation

Traceability records relationships between requirements and downstream artifacts such as test conditions and test cases. Testers use these links to confirm coverage and to detect gaps. The other activities do not by themselves create requirement-to-test links.

Question 29Requirements Engineering

During technical test analysis, a tester must derive test conditions from a requirements specification. Which statement best describes a test condition in this context?

  1. An aspect of the system or requirement that could be verified by one or more test cases. Correct answer.
  2. A defect found while reviewing the requirements specification.
  3. A specific set of input values and expected results executed as one test case.
  4. A tool configuration used to automate regression tests.

Explanation

A test condition is an item or aspect identified as worth testing, derived from requirements, risks, or other sources. Test cases are then designed to cover each condition. It is not itself the executable test case, a defect, or a tool setting.

Question 30Requirements Engineering

A requirement states that a login form locks the account after three consecutive failed attempts. Which test condition is most directly derived from this requirement during test analysis?

  1. The account is locked after the third consecutive failed attempt. Correct answer.
  2. The login page loads within two seconds.
  3. The system supports at least ten thousand concurrent users.
  4. The password field masks entered characters.

Explanation

The derived test condition must correspond to the behaviour the requirement specifies, namely account locking after three consecutive failures. The other options describe unrelated behaviours or quality attributes not stated in this requirement.

Question 31Requirements Engineering

Which characteristic makes a requirement suitable as a basis for designing test cases in a technical system?

  1. It is unambiguous and states observable, measurable expected results. Correct answer.
  2. It is approved by the project manager before analysis begins.
  3. It is written using formal mathematical notation.
  4. It is brief and leaves implementation details to the developer.

Explanation

Testable requirements must be clear and state outcomes that can be observed and measured, so a tester can determine pass or fail. Formal notation can help but is not required, and brevity that introduces ambiguity undermines testability.

Question 32Requirements Engineering

A tester finds that a requirement for a payment service omits what should happen when the external payment provider times out. Which type of requirements defect does this represent?

  1. Inconsistency between two requirements
  2. Missing requirement Correct answer.
  3. Incorrect requirement
  4. Ambiguous requirement

Explanation

The specification fails to state behaviour for a defined scenario, which is a missing requirement. Inconsistency would require two conflicting statements, ambiguity requires unclear wording, and incorrectness requires a stated but wrong behaviour.

Question 33Requirements Engineering

In a formal review of a requirements specification, which role is responsible for deciding whether a potential finding is a genuine defect and how it should be handled?

  1. The scribe
  2. The author of the requirement
  3. The moderator Correct answer.
  4. The manager who commissioned the review

Explanation

The moderator leads the review meeting, manages discussion, and rules on whether items are recorded as defects and their severity. The author explains and later fixes, the scribe records, and the manager typically does not adjudicate technical findings.

Question 34Requirements Engineering

A requirements specification describes a batch job that must reject files larger than 50 MB. Which test condition set best reflects boundary value analysis for this requirement?

  1. Files of 25 MB and 100 MB only
  2. Files of 1 MB, 10 MB, and 50 MB
  3. Files of 0 MB, 50 MB, and 1000 MB
  4. Files of 49 MB, 50 MB, and 51 MB Correct answer.

Explanation

Boundary value analysis targets values at and adjacent to the boundary, so 50 MB (the threshold) plus the values just below and just above are most informative. The other sets miss the immediate neighbourhood of the boundary.

Question 35Requirements Engineering

Two requirements in the same specification state that a report must be generated within five seconds and that the same report must be generated within thirty seconds. Which review finding is most appropriate?

  1. The requirements are missing because no error handling is described.
  2. The requirements are not testable because performance cannot be measured.
  3. The requirements are ambiguous because 'generated' is undefined.
  4. The requirements are inconsistent because they specify conflicting performance thresholds. Correct answer.

Explanation

Two statements impose conflicting limits on the same behaviour, which is a consistency defect that the author must resolve. Ambiguity, missing content, and testability are different defect classes not matching this situation.

Question 36Requirements Engineering

A tester applies decision table testing to a requirement with three independent boolean conditions that jointly determine an action. How many condition combinations must the complete decision table consider?

  1. 6
  2. 3
  3. 8 Correct answer.
  4. 9

Explanation

Three independent boolean conditions produce 2^3, that is eight, distinct combinations. A complete decision table must cover all of them to ensure every rule is tested. Options such as 3 or 6 undercount the combination space.

Question 37Requirements Engineering

A requirements engineer uses perspective-based reading during a specification review. What is the primary purpose of assigning different reviewer perspectives?

  1. To reduce the number of reviewers needed to complete the review.
  2. To ensure each reviewer examines the specification from a distinct viewpoint such as tester, designer, or user, increasing defect detection. Correct answer.
  3. To replace the need for a moderator during the review meeting.
  4. To guarantee that no defects remain after a single review pass.

Explanation

Perspective-based reading gives reviewers defined viewpoints so they search for different defect classes, which improves coverage and detection. It does not reduce staffing, replace moderation, or guarantee defect-free output.

Question 38Requirements Engineering

A tester must verify a requirement describing an order discount that depends on order total, customer membership, and coupon presence. Which technique is most suitable for deriving test conditions from this requirement?

  1. Decision table testing Correct answer.
  2. Exploratory testing without documentation
  3. Boundary value analysis on the order total alone
  4. Statement coverage

Explanation

Decision tables model combinations of conditions and their resulting actions, which fits multiple interacting business rules. Boundary analysis on one factor ignores interactions, and statement coverage is a white-box measure.

Question 39Requirements Engineering

Which statement correctly describes the relationship between requirements risk and the depth of test analysis?

  1. Risk analysis is performed only after testing is complete and does not influence analysis.
  2. All requirements receive identical analysis depth regardless of risk to keep effort fair.
  3. Risk level determines only the number of testers assigned and never the test conditions.
  4. Higher-risk requirements typically warrant more thorough analysis and more test conditions than low-risk ones. Correct answer.

Explanation

Risk-based testing directs effort toward requirements whose failure would have the greatest impact or likelihood. Higher-risk requirements therefore receive deeper analysis and more test conditions. Uniform depth wastes effort, and risk analysis occurs before and during test design.

Question 40Requirements Engineering

A specification states that an API returns error code 400 for invalid input. During test analysis, a tester notices the specification never defines which inputs are considered invalid. Which action is most appropriate?

  1. Design test cases that assume any non-numeric input is invalid.
  2. Raise the gap with the author to clarify the invalid-input criteria before finalizing test conditions. Correct answer.
  3. Skip testing the error path because it is undefined.
  4. Test only the valid-input path and document the omission in the test report.

Explanation

When a requirement lacks the information needed to derive precise test conditions, the tester should raise it for clarification rather than assume. Assumptions may produce tests that do not match intended behaviour, and skipping the path leaves a risk unaddressed.

Question 41Requirements Engineering

Which item is the most appropriate output of test analysis performed on a requirements specification?

  1. A finalized project schedule
  2. A signed-off release note
  3. A set of prioritized test conditions with associated traceability to requirements Correct answer.
  4. A fully executed test log with pass and fail results

Explanation

Test analysis identifies what to test, producing test conditions that trace back to requirements and are prioritized by risk. Execution results, release notes, and schedules belong to later activities or other disciplines.

Question 42Requirements Engineering

A requirements specification uses the phrase 'the interface shall be intuitive'. Which review comment is most actionable for the author?

  1. Replace 'intuitive' with measurable criteria such as task completion time or error rate targets. Correct answer.
  2. Leave the requirement as is because intuitiveness is subjective by nature.
  3. Remove the requirement because usability cannot be tested.
  4. Rewrite the requirement to say the interface shall be modern.

Explanation

An actionable comment converts a subjective term into measurable acceptance criteria so the requirement can be verified. Usability is testable when quantified, and substituting another subjective adjective does not help.

Question 43Requirements Engineering

A tester must design test conditions for a requirement describing a workflow with several sequential stages and allowed transitions between them. Which technique is most suitable?

  1. Pairwise combination of configuration parameters
  2. State transition testing Correct answer.
  3. Equivalence partitioning on a single input field
  4. Statement coverage of the source code

Explanation

State transition testing models states, events, and transitions, which matches a staged workflow with allowed transitions. The other techniques target input partitions, parameter combinations, or code structure rather than sequence-dependent behaviour.

Question 44Requirements Engineering

A traceability matrix shows a test condition that is linked to no requirement. What is the most likely interpretation for the test analyst?

  1. The test condition may cover an implicit need or risk, so the analyst should confirm whether a requirement is missing or the condition is out of scope. Correct answer.
  2. The test condition is unnecessary and should be deleted immediately.
  3. The matrix is corrupted and should be rebuilt from scratch.
  4. The requirement was already tested and the link was removed intentionally.

Explanation

An orphan test condition can indicate either an unstated requirement or an unnecessary test. The analyst should investigate before deciding, rather than deleting it or assuming corruption.

Question 45Requirements Engineering

Which statement best explains why reviewing requirements early is usually cheaper than finding the same defects during system testing?

  1. Defects found in requirements can be corrected before design and code depend on them, avoiding costly rework across artifacts. Correct answer.
  2. Reviews eliminate the need for any later testing.
  3. Reviews are cheaper because they require no documentation.
  4. System testing is always performed by less experienced staff.

Explanation

Requirements defects propagate into design, code, and tests, so early correction avoids reworking multiple artifacts. Reviews complement rather than replace testing, and cost differences do not stem from documentation or staff seniority.

Question 46Requirements Engineering

A specification contains a requirement that a sensor reading be transmitted every 100 ms with a tolerance of plus or minus 5 ms. Which test conditions best target the timing boundary?

  1. Readings at 0 ms and 1000 ms intervals
  2. Readings at 50 ms and 200 ms intervals only
  3. Readings at exactly 100 ms only
  4. Readings at 95 ms, 100 ms, and 105 ms intervals Correct answer.

Explanation

The tolerance defines an interval from 95 ms to 105 ms, so boundary values at and just outside the limits best test the timing rule. Testing only the nominal value or far-off values misses boundary defects.

Question 47Requirements Engineering

During test analysis of a requirement for a message-queue consumer, which is the best example of a derived test condition?

  1. The consumer acknowledges a message only after successfully persisting it. Correct answer.
  2. The development team uses a particular coding standard.
  3. The queue broker is version 3.2.
  4. The test environment runs on virtual machines.

Explanation

A test condition states a behaviour to verify, such as acknowledgement ordering relative to persistence. Version numbers, coding standards, and environment details are context, not conditions to be tested against the requirement.

Question 48Requirements Engineering

A requirement states: 'The system shall allow an administrator to delete a user account, and the system shall not allow any user account to be deleted.' Which defect class is present?

  1. Inconsistent requirement Correct answer.
  2. Ambiguous requirement
  3. Missing requirement
  4. Untestable requirement

Explanation

The two clauses directly contradict each other about whether account deletion is permitted, which is an inconsistency. The statements are otherwise clear and testable, and no behaviour is absent.

Question 49Requirements Engineering

A tester is analyzing a requirement for a safety-critical braking controller where the specification uses continuous input ranges and precise timing constraints. Which approach to test analysis is most appropriate?

  1. Combine boundary value analysis, equivalence partitioning, and review of timing constraints, prioritizing conditions by risk. Correct answer.
  2. Rely on exploratory testing alone because the domain is complex.
  3. Test a single nominal scenario and assume the rest behaves similarly.
  4. Apply only statement coverage once code is available.

Explanation

Safety-critical continuous behaviour requires systematic techniques that target boundaries, partitions, and timing, with risk-based prioritization. Exploratory testing alone or single nominal scenarios cannot provide the needed rigor, and code coverage is a later structural measure.

Question 50Requirements Engineering

A review team debates whether a requirement's reference to an external standard is acceptable without restating the standard's content. Which moderator response best applies review principles?

  1. Defer the decision to the developer who will implement the requirement.
  2. Accept the reference because external standards are always authoritative.
  3. Record it as a finding and ask the author to confirm the referenced clause is unambiguous, current, and accessible to testers. Correct answer.
  4. Reject the requirement outright because references are never allowed.

Explanation

Referencing a standard can be acceptable if the clause is identifiable, current, and available to those who must verify it. The moderator should ensure this is checked and recorded rather than assuming validity or banning references.