You have now also been given the task to identify the key fields for logging the incident reports. So far the following fields have been in use in the Excel sheet: Incident description Date Author…

Question

Options

• APriority, version of software under test, incident identification
• BDate to be fixed, priority, incident identification
• CDeveloper assigned to the fix, version of software under test, incident identification
• DPriority, version of software under test, date to be fixed

• A
  87% (55)
• B
  8% (5)
• C
  3% (2)
• D
  2% (1)

Explanation

Option A is correct because it adds the three most essential missing fields for a complete incident tracking system. Incident identification provides a unique ID so incidents can be referenced, tracked, and cross-linked - without it, communication breaks down. Priority is needed to triage and schedule fixes, and version of software under test establishes the context needed to reproduce and verify the defect.

B is wrong because "date to be fixed" is a planning/commitment field that often isn't known at logging time and can change - it's not a core incident attribute. C is wrong because "developer assigned to the fix" is a workflow assignment that may change repeatedly and belongs to project management, not the incident record itself; priority is more fundamentally important than assignment. D is wrong because it omits incident identification entirely - a unique identifier is non-negotiable for any tracking system, making this combination incomplete despite having two good fields.

Memory tip: Think of the three pillars a new incident always needs - "What is it called? How urgent is it? Where was it found?" - mapping to Identification, Priority, and Version. If an option is missing any of these three, it's likely wrong.

No community discussion yet for this question.