What is true about rollback plan for migration phases? (Select two)

Question

Options

• AStaff members can't be included in rollback dependency
• BDon't give a timeframe for the rollback as this might affect customer confidence in your solution
• CArchive Last known good configuration (state)
• DDetermine maximum time for rollback

• A
  4% (1)
• B
  4% (1)
• C
  93% (26)

Explanation

Archiving the last known good configuration (C) ensures you have a verified restore point before migration begins - without it, rollback has nothing to revert to. Determining the maximum rollback time (D) is equally critical because it sets a hard decision boundary: if recovery isn't complete within that window, the team escalates rather than guessing indefinitely.

Why the distractors are wrong:

• A is incorrect - staff and personnel are valid rollback dependencies. Human resources (DBAs, network engineers, approvers) are often essential to executing a rollback and must be accounted for.
• B is the opposite of best practice - you should define a rollback timeframe. It drives decision-making under pressure and is part of what option D correctly requires.

Memory tip: Think "Save and Set" - Save the last good state (C) and Set a time limit (D). These two actions make a rollback executable, while the distractors either exclude real dependencies (A) or hide critical information (B).

No community discussion yet for this question.