The affected metrics are Mean Time to Respond and Mean Time to Resolve because both can depend on the expected lifecycle of a notable beginning in the default New state and progressing through subsequent analyst-handling states.
If Testing is accidentally configured as the default, newly generated notables no longer begin with the status value expected by searches or reports that identify sequences such as:
New → In Progress
or
New → ... → Resolved
As a result, the timestamp used to establish the beginning of the response or resolution interval may be missing from the expected status-change sequence, producing inaccurate, incomplete, or excluded metric calculations.
Dwell Time is different. It measures how long malicious activity remains present or undetected in the environment and is not fundamentally calculated from Enterprise Security notable-status transitions. That eliminates options C and D. Option B is also incorrect because changing a status value relied upon by existing SOC metric searches can directly alter their results.
The supplied guide explicitly emphasizes notable status and ownership as operational SOC measurement fields , supporting the importance of preserving lifecycle-state consistency.
Study Guide topics: notable-event lifecycle, status transitions, Mean Time to Respond, Mean Time to Resolve, SOC metrics, reporting consistency.
