What are common steps in incident response during deployment?

What are common steps in incident response during deployment?

• A. Deploy, monitor, rollback
• B. Plan, code, test
• C. Detect, assess, contain, eradicate, recover, communicate; post-incident review
• D. Ignore, pretend nothing happened

Answer: (C)

Incident response during deployment relies on a clear, structured lifecycle that guides how teams handle disruptions fast. The best choice matches that lifecycle: detect, assess, contain, eradicate, recover, communicate, and then conduct a post-incident review. Detecting the incident starts the process and triggers awareness. Assessing determines how severe and widespread the issue is, which informs the next moves. Containing the incident stops it from spreading and causing more damage. Eradicating removes the root cause so the problem can’t recur in the same way. Recovering brings services back to normal operation with minimal downtime. Communicating keeps engineers, stakeholders, and users informed about status and next steps. Finally, a post-incident review looks at what happened, why it happened, and how to prevent similar events in the future. The other options describe activities that aren’t about managing an incident. Planning, coding, and testing relate to building software rather than responding to disruptions. A deployment-focused sequence like deploy, monitor, rollback covers typical rollout steps but omits the containment, eradication, recovery, and learning phases essential to incident resolution. Ignoring an incident is never acceptable.

Incident response during deployment relies on a clear, structured lifecycle that guides how teams handle disruptions fast. The best choice matches that lifecycle: detect, assess, contain, eradicate, recover, communicate, and then conduct a post-incident review. Detecting the incident starts the process and triggers awareness. Assessing determines how severe and widespread the issue is, which informs the next moves. Containing the incident stops it from spreading and causing more damage. Eradicating removes the root cause so the problem can’t recur in the same way. Recovering brings services back to normal operation with minimal downtime. Communicating keeps engineers, stakeholders, and users informed about status and next steps. Finally, a post-incident review looks at what happened, why it happened, and how to prevent similar events in the future.

The other options describe activities that aren’t about managing an incident. Planning, coding, and testing relate to building software rather than responding to disruptions. A deployment-focused sequence like deploy, monitor, rollback covers typical rollout steps but omits the containment, eradication, recovery, and learning phases essential to incident resolution. Ignoring an incident is never acceptable.