220-1102 Operational Procedures Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Instructions for returning the system to its original state

  Why this is correct

  Instructions for returning the system to its original state is correct because a backout plan is a predefined, step-by-step technical procedure to reverse the change if it fails. In the context of a BIOS update, this includes obtaining the previous firmware version (e.g., from a verified backup or vendor repository), using the manufacturer's rollback utility or a bootable USB, and reflashing the old BIOS to restore baseline functionality. It also specifies system checks needed after rollback to confirm the system boots and operates normally, and any conditions where restoration might not be possible (such as an interrupted flash corrupting the boot block). This is the core technical content of a backout plan, distinct from administrative or communication steps.

• ✗

  A list of users to notify if the change fails

  Why it's wrong here

  A list of users to notify if the change fails is wrong for this question because it belongs to the communication plan, not the backout plan. The backout plan is purely a technical troubleshooting and reversal document—it details commands, utilities, hardware steps, and verification methods to revert the BIOS. Notifying stakeholders is a project management or change coordination activity that happens in parallel, and it does not describe how to undo the change. While a full change request may include such a list, it is not part of the ‘return to original state’ procedure that defines a backout plan.

• ✗

  Approximate time required to implement the change

  Why it's wrong here

  The approximate time required to implement the change is wrong because it is a parameter of the implementation plan, not the backout plan. Change windows and downtime estimates help schedule when the BIOS update will occur and how long the servers will be offline, but they say nothing about the steps to restore a previous BIOS version. The backout plan’s focus is the technical sequence of actions—such as booting to a recovery environment, invoking the rollback command, and revalidating firmware integrity—not the duration or schedule. Including time would conflate implementation logistics with the reversal methodology, which is a separate concern in the change management process.

• ✗

  A schedule for post-implementation review

  Why it's wrong here

  A schedule for post-implementation review is wrong because that occurs only after the change—and any necessary rollback—has been executed, and it is a distinct phase in the change lifecycle. A post-implementation review evaluates success, user impact, and process effectiveness, often within a defined period (e.g., one week later), and is not a technical procedure to revert the system. The backout plan is designed to be used *during* the change window if the BIOS update fails, offering immediate reversal guidance, not a future meeting or audit timeline. Therefore, a review schedule cannot substitute for the concrete rollback steps that a backout plan must contain.

Go deeper

Related to this question