ServiceNow Certified System Administration Practice

Should you include few or many changes in one Update Set?

1. Few

2. Many

3. Only significant changes

4. No changes at all

The correct answer is: Few

Including a few changes in one Update Set is considered best practice in ServiceNow for several reasons. Firstly, smaller Update Sets are easier to manage and track. When you bundle too many changes together, it can become complicated to identify which change caused an issue if problems arise during a migration or deployment. This makes troubleshooting more challenging, as pinpointing errors in a larger set of changes can be time-consuming and confusing. Secondly, smaller Update Sets allow for more focused testing. Each change can be validated individually, ensuring that they work as intended before being moved to another instance, such as from development to production. When there are only a few changes, the testing process can be thorough without overwhelming the testing phase. Thirdly, if a particular change needs to be rolled back or modified, having fewer changes in an Update Set allows you to isolate and manage the specific change without affecting others. This modular approach enhances the flexibility and stability of your deployment process. Therefore, using fewer changes in an Update Set is a sound strategy to maintain clarity and efficiency in your ServiceNow development and deployment process.