When movinghomepagesordashboardsbetween ServiceNow instances (e.g., from development to production), they arenot automatically includedin an update set. Instead, they must bemanually addedto the update set before migration.
C). Manually add them to the update set
Homepages and dashboards donotget included in update sets by default.
To move them, you must:
Navigate toSystem UI > Homepage Admin > PagesorPerformance Analytics > Dashboards Select the homepage or dashboard you want to move.
Use theAdd to Update Setfunction to include them in your active update set.
Once added, move the update set to another instance and commit it.
A). Create a separate update set for them
While it's a good practice to keep UI elements in separate update sets, it isnot a requirement.
Homepages/dashboards can be added toany active update setmanually.
B). They are automatically added to the update set
Incorrect-ServiceNowdoes notautomatically add homepages or dashboards to update sets.
D). They cannot be moved via update set
Incorrect-Theycanbe moved via update sets, but they must bemanually added.
References:ServiceNow Documentation:Moving Homepages and Dashboards Between Instances ServiceNow Best Practices:Working with Update Sets

InServiceNow,System Import Setsis the primary application used toimport and transform datafrom external sources into the platform. It provides a structured way toload data into tableswhile allowingdata transformation and mappingbefore final insertion.
Data Loading from External Sources:
Supports imports fromCSV, Excel, XML, JSON, and JDBC databases.
Allows data fromexternal systemsto be brought into ServiceNow.
Staging Area for Data Processing:
Imported data first enters atemporary staging table(Import Set Table).
Data can then betransformedbefore being committed to the target table.
Data Mapping and Transformation:
UsesTransform Mapsto map fields from theImport Set Tableto theTarget Table.
Supportsautomatic field mappingandscripted transformations.
Data Cleansing and Validation:
Duplicate records can bedetected and removed.
Invalid or missing data can becorrected before insertion.
Navigate to System Import Sets(All # System Import Sets # Load Data).
Upload the data file(CSV, XML, JSON, etc.).
Create a Transform Mapto define how data is mapped to the target table.
Run the transformationto move data from the Import Set Table to the final table.
Verify the datain the target table.
A company importsemployee recordsfrom an externalHR system (CSV file).
TheSystem Import Setsmodule loads this data into astaging table.
ATransform Mapmoves the data into theUser [sys_user]table.
Key Features of System Import Sets:Steps to Load Data Using Import Sets:Example Use Case:
Why Option C (System Import Sets) is Correct?System Import Sets is the primary tool for loading data into ServiceNow from external sources.
Why Other Options Are Incorrect?A. Service Level Management# Incorrect
Service Level Management (SLM)is used to trackService Level Agreements (SLAs), not to import data.
B: Configuration# Incorrect
Configuration Management (CMDB)helps trackconfiguration items (CIs)but does not handle data imports.
D: System Update Sets# Incorrect
Update Setsare used tomove configurations and customizationsbetween instances,not to import data.
ServiceNow Docs - Importing Data with System Import Setshttps://docs.servicenow.com ServiceNow Learning - Data Import & Transformation Best Practices ServiceNow Developer Portal - Using Import Sets Efficiently References from Certified System Administrator (CSA) Documentation:

InServiceNow,Create Incident, Password Reset, and Report Outageare examples ofService Catalog itemsthat guide users through submitting requests. These services are commonly implemented usingRecord Producers.
What is a Record Producer?ARecord Produceris a special type ofcatalog itemthat:
Creates recordsin a table (e.g., Incident, Change, or Request).
Provides auser-friendly interfacein the Service Catalog.
Maps user input fields to corresponding fieldsin the target table.
For example:
" Create Incident " uses a Record Producer to create a record in theIncident [incident]table.
" Password Reset " can create a record in acustom password reset tableor trigger a workflow.
" Report Outage " may create a record in theProblem or Incident table.
Why is Option A Correct? " They direct the user to a record producer. " These catalog servicesdo not create Service Requests (REQs) like normal catalog items.
Instead, theyuse Record Producers to generate records directly in specific tables (e.g., Incident, Change, Problem).
This allowscustom form fields, pre-filled values, and direct mappingto the target table.
Why Are the Other Options Incorrect?B. " They direct the user to a catalog property. " Incorrect:Catalog properties aresystem settingsthat control Service Catalog behavior, not user-facing forms.
Example:Catalog properties controlcart behavior, request approval rules, etc.
C). " They direct the user to a catalog UI policy. "
Incorrect:UI Policies controlfield behavior (e.g., hiding, showing, making fields mandatory) on the formbut do not determine how the request is processed.
D). " They direct the user to a catalog client script. "
Incorrect:Catalog Client Scripts controlform logic (such as auto-filling fields) but do not create records directly.
Reference from Certified System Administrator (CSA) Documentation:# ServiceNow Docs - Record Producers in the Service Catalog
# ServiceNow Record Producers Documentation
" A Record Producer is acatalog itemthat lets users create records in a table instead of generating a standard request. " Conclusion:The correct answer isA. They direct the user to a record producer.
# Record Producers are widely used in ServiceNow ' s Service Catalog to simplify and streamline user requests, ensuring data is properly captured and processed.

In ServiceNow, when a user wants topersonalize the layout of the columnsin arelated list, they need to click theGear icon (##).
Navigate to a record that contains arelated list.
Look at the top-right corner of the related list for theGear icon.
Click theGear iconto open the "Personalize List Columns" interface.
From there, the user canadd, remove, or rearrange columnsin the related list.
A). Magnifier- A magnifying glass is typically used forsearch functionsbut not for column customization.
B). Context Menu- The context menu (right-click) providesother actionsbut does not allow column layout changes.
C). Pencil- A pencil icon typically representseditingbut not column layout customization.
ServiceNow Personalizing List Views
ServiceNow CSA Training Module:"Personalizing Lists and Forms"
How It Works:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Reference: https://www.servicenowelite.com/blog/2016/8/7/update-sets
When moving multipleupdate setsat once, ServiceNow allows users to move them in abatch. This makes it easier to handle large numbers of updates efficiently.
Key Benefits of Using Batch for Update Sets:Saves Time- Instead of moving update sets one by one, you can transfer multiple at the same time.
Reduces Errors- Ensures all related update sets are moved together, preventing dependency issues.
Improves Deployment Efficiency- Helps when deploying updates across development, test, and production instances.
How to Move Multiple Update Sets in a Batch:Navigate toSystem Update Sets > Update Set Batches.
Create a new batch and select multiple update sets.
Move the batch to the target instance.
Preview and commit the update sets together.
Why Other Options Are Incorrect:B. Verify# While it is important to verify updates before committing," Verify" is not a functionfor moving update sets.
C: Test# Update sets should be tested, but "Test" is not a feature for moving them.
D: Preview# The preview function checks for conflicts or missing dependencies before committing update sets, but it does not facilitate moving them.
Reference:ServiceNow Docs: Managing Update Sets
ServiceNow CSA Official Study Materials