An internal application has been developed to increase the efficiency of an operational process of a global manufacturer. New code was implemented to fix a security bug, but it has caused operations…

Question

Options

• AVersion control
• BAgile development
• CWaterfall development
• DChange management
• EContinuous integration

• A
  13% (4)
• B
  3% (1)
• C
  3% (1)
• D
  73% (22)
• E
  7% (2)

Explanation

Note: The listed answer shows only D, but this 'choose two' question is best answered with A and D. Version control (A) is the most direct technical enabler of rollback - a version control system (such as Git) maintains a complete history of code changes, allowing the team to immediately revert the codebase to the prior working state before the security fix was applied. Change management (D) is the procedural framework that supports rollback: a well-executed change management process documents what was changed, ensures a rollback plan exists before any change is deployed, identifies approvers, and provides the process steps needed to execute a rollback safely and quickly. Together, version control provides the technical mechanism and change management provides the documented procedure. Agile (B) and Waterfall (C) are development methodologies, not rollback mechanisms. Continuous integration (E) helps catch issues during development but does not directly enable production rollbacks.

No community discussion yet for this question.