CSA - ServiceNow System Administrator Update Sets and Customizations Questions and Answers 1 — Questions and Answers
Question 1: A developer creates a new Business Rule and a system property. For testing, they also create a new user record and several incident records. Assuming all this work occurred while a single custom Update Set was 'In Progress', what will be transferred when this Update Set is moved to another instance?
- The Business Rule and the system property only. (Correct answer)
- The Business Rule, system property, and the user record.
- The Business Rule, system property, and the incident records.
- All changes, including the Business Rule, system property, user, and incident records.
Correct answer: The Business Rule and the system property only.
Update Sets are designed to capture configuration changes, such as Business Rules, UI Policies, and system properties. They do not capture transactional data, which includes records like incidents, users, groups, and CIs.
Question 2: An administrator retrieves a completed Update Set from a development instance to a UAT instance. Before applying the changes, they need to identify any potential conflicts with changes that have been made directly in UAT. What is the mandatory next step in the standard Update Set process?
- Commit Update Set
- Back Out Update Set
- Merge Update Sets
- Preview Update Set (Correct answer)
Correct answer: Preview Update Set
After retrieving an Update Set, the 'Preview Update Set' step is a critical and mandatory action. It compares the changes in the Update Set with the current configuration of the target instance to detect potential conflicts, such as a local record being newer than the one in the update set.
Question 3: Which of the following represents a ServiceNow best practice for managing Update Sets to ensure manageability and ease of troubleshooting?
- Use a single, large Update Set for all development work during a two-week sprint.
- Keep Update Sets small and focused on a single, logical change or feature. (Correct answer)
- Always delete the original Update Sets after merging them.
- Move completed Update Sets back to 'In Progress' to add minor fixes.
Correct answer: Keep Update Sets small and focused on a single, logical change or feature.
ServiceNow best practices recommend that Update Sets should be small and contain a cohesive, logical set of changes related to a specific feature or fix. This approach makes them easier to manage, deploy, troubleshoot, and back out if necessary.
Question 4: A system administrator on a test instance has just committed an Update Set that introduced a critical bug. What is the standard ServiceNow feature designed to revert the instance to the state it was in before the Update Set was applied?
- Re-importing the previous version of the Update Set.
- Deleting the committed Update Set record.
- Backing Out the Update Set. (Correct answer)
- Cloning the instance from a recent backup.
Correct answer: Backing Out the Update Set.
The 'Back Out' functionality is the specific feature designed to revert the changes applied by a committed Update Set. It works by creating a new Update Set that contains the opposite changes, effectively undoing the customizations from the original set.
Question 5: A developer is working on a large feature that involves changes across multiple applications. To manage this complexity, they have created several distinct Update Sets. What is the recommended method for grouping these related Update Sets so they can be retrieved, previewed, and committed as a single unit?
- Update Set Merging
- Update Set Linking
- Batch Update Sets (Correct answer)
- Scoped Update Sets
Correct answer: Batch Update Sets
Batch Update Sets are used to group multiple Update Sets together by creating a parent-child relationship. When the parent (or 'base') Update Set is retrieved and committed, all its child Update Sets are processed together as a single entity, preserving their individual changes.
Question 6: By default, which of the following items would NOT be captured in a custom Update Set?
- A new user role
- A modified form layout
- A new Business Rule
- A new Assignment Group record (Correct answer)
Correct answer: A new Assignment Group record
Assignment Groups (records in the sys_user_group table) are considered data, not configuration. Update Sets do not capture transactional or foundational data records like users, groups, or incidents by default. Changes to roles, form layouts, and Business Rules are all considered configurations and are captured.
CSA - ServiceNow System Administrator Update Sets and Customizations Questions and Answers 1
A developer creates a new Business Rule and a system property.
For testing, they also create a new user record and several incident records.
Assuming all this work occurred while a single custom Update Set was 'In Progress', what will be transferred when this Update Set is moved to another instance?