Please refer to the exhibit. From a Testing perspective, what are the MAIN purposes of Configuration Management?

Question

Options

• Aii, iv and v.
• Bii, iii and iv.
• Ci, ii and iv.
• Di, iii and v.

• A
  15% (4)
• B
  8% (2)
• C
  73% (19)
• D
  4% (1)

Explanation

Option C (i, ii, and iv) is correct because Configuration Management (CM) in testing primarily serves to: uniquely identify and version-control testware, maintain the integrity of test items throughout the lifecycle, and support traceability between test items, their configurations, and related documentation. These three functions are the core CM responsibilities from an ISTQB/testing perspective.

Why the distractors fail:

• A (ii, iv, v) drops item i - which covers unique identification and version control, a foundational CM purpose - and replaces it with item v, which typically refers to resource management or scheduling (a test management concern, not CM).
• B (ii, iii, iv) includes item iii, which usually represents something like managing people or planning test activities - responsibilities that belong to test management, not configuration management.
• D (i, iii, v) excludes item ii entirely and keeps the two non-CM items (iii and v), making it the furthest from correct.

Memory tip: Think of CM with the acronym "VIT" - Version control, Integrity maintenance, Traceability. Any answer choice that swaps one of these for resource/team management is wrong, because CM controls artifacts, not people or schedules.

No community discussion yet for this question.