A project sponsor wants a reliable process for applying system updates while preserving stability and adhering to corporate standards. Which method accomplishes this goal?
Maintain a record of changes in a shared spreadsheet updated by each team
Convene monthly cross-departmental meetings to inform the team of previously implemented modifications
Apply fixes whenever a critical issue is discovered during production
Adopt well-defined guidelines that require review, testing, and authorization for each new update
Adopting well-defined guidelines that require review, testing, and authorization for each new update establishes consistency throughout the lifecycle. That structured approach controls risks by ensuring each change is vetted before implementation. Merely applying fixes in reaction to critical issues or logging them in a spreadsheet offers no mandatory vetting process. A monthly meeting without steps for formal testing and authorization introduces possible oversights.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
Why is it important to have well-defined guidelines for system updates?
Open an interactive chat with Bash
What are some benefits of testing and review before applying a system update?
Open an interactive chat with Bash
What other tools or practices can support a structured update process?