In ServiceNow, an Update Set is a mechanism used to capture customizations made in an instance and move them to another instance (e.g., from development to production). However, certain elements are not included in an Update Set by default. Items NOT Included in Update Sets (By Default): Homepages (A) – ✅ Correct Homepages are stored as user-specific or global content, and they are not included in update sets by default. To migrate them, you need to manually export/import them or use the sys_portal_page_set table. Data (B) – ✅ Correct Update Sets do not include actual data, such as incident records, user records, or CMDB data. Only configuration changes (like fields, forms, and workflows) are captured. Data migration must be handled separately using Data Export or Integration methods. Published Workflows (C) – ✅ Correct Once a workflow is published, it is stored as a runtime instance and not automatically included in an Update Set. To capture it, you must manually update the workflow before moving it in an Update Set. Report Definitions (H) – ✅ Correct Reports and their configurations are not automatically included in Update Sets. You must manually include them by marking them as "Captured in Update Set." Items That ARE Included in Update Sets (By Default): D . Business Rules ✅ (Captured in Update Sets) E . Schedules ✅ (Captured in Update Sets) F . Database changes ✅ (Captured in Update Sets) G . Related Lists ✅ (Captured in Update Sets) I . Scheduled Jobs ✅ (Captured in Update Sets) J . Client Scripts ✅ (Captured in Update Sets) K. Views ✅ (Captured in Update Sets) Official Reference from Certified System Administrator (CSA) Documentation: ServiceNow Update Sets Overview: https://docs.servicenow.com/en-US/bundle/utah-applicationdevelopment/page/build/system-update-sets/concept/c_UpdateSets.html ServiceNow Update Set Best Practices: https://docs.servicenow.com/en-US/bundle/utahapplication-development/page/build/system-update-sets/concept/update-set-best-practices.html