Users and groups are captured in update sets.

Users and groups are captured in update sets.

• A. True
• B. False
• C. Only users
• D. Only groups

Answer: (B)

Update sets are used to move configuration and customization from one ServiceNow instance to another. They track changes to metadata like fields, tables, scripts, business rules, UI policies, workflows, and installed applications. They are not meant for migrating data records. Users and groups are data records stored in tables such as sys_user and sys_user_group, so changes to who exists or which users belong to which groups are data changes, not configuration changes. Because of this, users and groups aren’t captured by update sets. If you need to migrate those records, you’d use data migration methods (like export/import) rather than an update set.

Update sets are used to move configuration and customization from one ServiceNow instance to another. They track changes to metadata like fields, tables, scripts, business rules, UI policies, workflows, and installed applications. They are not meant for migrating data records. Users and groups are data records stored in tables such as sys_user and sys_user_group, so changes to who exists or which users belong to which groups are data changes, not configuration changes. Because of this, users and groups aren’t captured by update sets. If you need to migrate those records, you’d use data migration methods (like export/import) rather than an update set.