In which of the following situations should a Problem Record be created?

A failed redundant network segment with no user impact is handled by Event Management and does not automatically require a Problem Record unless systemic root cause investigation is warranted.

Escalating an incident to second-level support is an Incident Management activity and does not by itself satisfy the criteria for creating a Problem Record.

When a Technical Management team identifies a permanent resolution to recurring incidents, it confirms that root cause analysis has been completed, which is the central purpose of Problem Management. Creating a Problem Record at this point formally documents the known error and its resolution, enabling a Request for Change to be raised to implement the fix and permanently close the problem.

Implementing a workaround remains within the scope of Incident Management, as it restores service without identifying or resolving the underlying root cause.