51 questions from the Data Migration and Integration domain of the ServiceNow Certified System Administrator (CSA) exam, each with its answer and an explanation. Read them through as revision, then sit the full practice exam to test yourself on them under multiple-choice conditions.
Answer
IntegrationHub handles multiple data formats when integrating with external systems. It can parse XML (common in SOAP APIs and legacy systems) and JSON (standard for REST APIs), which ensures flexibility across diverse integrations.
Answer
Coalesce lets you update existing target table records when transforming import data. A matching record is updated; if none is found, a new record is created.
Answer
ServiceNow supports coalescing on multiple fields and multiple transform maps against a single data source. When several fields coalesce, all values must match an existing record; if one matches but another does not, a new record is inserted.
Answer
Customizations are stored in sys_update_xml (Customer Update), which captures XML records of changes such as new fields, forms, scripts and configurations for use in update sets. sys_update_set only stores metadata about the update set container. Update sets store new and updated choice options as separate records in sys_update_version and sys_update_xml.
Answer
ecc_queue is the central table storing all communication records between the instance and the MID Server, holding both input and output messages. The cmdb-prefixed variants are not valid table names.
Answer
Update sets can be reverted to previous versions; administrators can roll changes back, so the statement is false.
Answer
The Default Update Set only captures changes when no other set is selected; using it for migration causes confusion and incomplete transfers, so named update sets are best practice. The Baseline Update Set captures the original state before customization, instances should be on the same version, and a Complete update set should not be reopened.
Answers
The Import Log details execution errors, warnings and successes; Import Set Runs track each execution with timing and status; Import Set Rows hold the staged source records. Import Maps are configuration objects, the Import Set API is a programmatic mechanism, and concurrent import sets describe system behavior rather than record detail.
Answer
Mapping Assist helps align source fields from the import set table with target fields in the destination table using Field Maps, reducing manual effort. Transform History tracks past transforms, the Import Log records import status, and SLAs are unrelated to data import.
Answer
A spoke is a scoped application containing Flow Designer or IntegrationHub actions or subflows, grouping related actions and supporting files for reuse. IntegrationHub includes baseline spokes, and more can be obtained from the ServiceNow Store or Share, or built in-house.
Answer
Workflows are tracked differently in update sets because workflow information spans multiple tables. Changes to a workflow version are not added to the update set until the workflow is published, at which point the whole workflow is added.
Answer
A transform map is a set of field maps determining the relationships between fields in an import set and fields in an existing ServiceNow table, such as Incident or User. The Transform Maps module lets an administrator define destinations for imported data on any table, often via drag-and-drop field linking.
Answer
To load data from a data source into a staging table, use the Application Navigator to open System Import Sets > Load Data; configuration options vary by data source, and a staging table is created dynamically.
Answer
An import set table acts as a staging location for records imported from a data source prior to transforming them. Fields on these tables are generated automatically and should not be modified manually.
Answer
Coalesce Fields determine whether an incoming record should update an existing record or create a new one, acting as the unique key for matching during import. Sys IDs are system-generated and impractical for external matching, and "Match Fields"/"Key Fields" are not formal ServiceNow terms.
Answer
The Transform Map module lets administrators define destinations for imported data on any table.
Answer
Before importing, verify and clean the data, and avoid loading data in extremely large chunks.
Answers
Smaller update sets reduce the chance of overlapping changes or conflicts when merging into production, and make changes easier to review, test, and validate. It is unrelated to ISO audits, business-hour timing, the default update set, or log length.
Answer
Update sets capture configuration changes like tables, fields, form/list layout, business rules, workflows, system properties, client scripts, and script includes, but they do NOT capture transactional data such as changes to records, users, groups, incidents, configuration items, or email.
Answer
Transform map field mapping scripts (such as onBefore, onAfter, or Script mappings) enable dynamic logic to map source fields to destination fields during data imports. Update sets are unrelated to runtime mapping, and ServiceNow does support scheduled data imports.
Answer
Update sets track customizations to application tables, fields, and records, which are entailed in a form.
Answer
Homepages and dashboards must be manually added to the update set to move between instances; they are not automatically captured.
Answer
The mapping assist utility provides a visually intuitive drag-and-drop environment for specifying mapping between import set fields and production table fields, including mapping a single source field to multiple destination fields.
Answer
The Import Set table acts as a staging location for records prior to transforming them; the standard process is to load data, create a transform map, transform the data, and clean up the import table afterward.
Answer
If no coalesce field is defined, all imported rows are treated as new records; no existing records get updated.
Answer
Coalesce fields determine whether an incoming record matches an existing one; when a match is found, the existing record is updated with the imported data, and if no match is found a new record is created instead.
Answers
All five are valid import set sources: JDBC connects to relational databases, XML and CSV are structured file formats, HTTP enables web service imports, and Excel spreadsheets can also be imported directly.
Answer
Setting the Title field as coalesce causes ServiceNow to check for an existing record with the same Title and update it instead of creating a duplicate. The 'Allow Duplicates' checkbox only affects the import set staging table, not the target table, and a delete-after-insert business rule is inefficient and risky.
Answer
import_admin is specifically designed to allow creating and managing import sets, providing the necessary permissions to load data and configure mappings — the minimum role needed for this task rather than the broader admin role.
Answer
Integration Hub enables executing third-party APIs as part of a flow via spokes, which are easy to configure without scripting. The MID Server instead facilitates data movement between the platform and external systems, not flow integration per se.
Answers
Update sets capture application customizations like client scripts, business rules, and field definitions, enabling consistent deployment across environments. They do not capture transactional data such as modified/new data records or tasks like incidents.
Answers
Update sets capture report definitions, active published workflow versions, custom views (columns/filters), and table/schema changes. Homepages/dashboards require separate export/import, and scheduled jobs are runtime/transactional data excluded from update sets.
Answer
Transform maps can be reused multiple times across different import sets, promoting efficiency and consistency in data mapping.
Answer
Workflows must be published before they are captured in update sets. Only published versions are included for migration between instances.
Answer
System Import Sets > Load Data is where you upload a data file into a staging table, the entry point for initiating an import set process.
Answer
Update sets are containers that capture customizations and configuration changes made in one instance, allowing them to be moved to another instance (e.g., dev to production).
Answer
Only users with the import_set role (or membership in a group with that role) can manage and set up import sets, due to the potential impact on data integrity.
Answer
Update sets bundle and track customizations (scripts, workflows, field/table modifications, UI customizations) made within an instance.
Answer
ServiceNow system upgrades do not automatically update MID Servers. MID Servers require manual upgrade or redeployment to align with the instance version.
Answer
Update sets in ServiceNow can be merged - multiple update sets can be combined into a single new update set, with ServiceNow prioritizing the latest changes.
Answer
Marking the Default update set complete causes ServiceNow to automatically create a new 'Default1' update set and make it the active default.
Answer
An update set must be marked Completed before it can be exported to another instance.
Answer
ServiceNow provides native, out-of-the-box integration with LDAP for authenticating users and importing user/group data from directories like Active Directory.
Answer
Import Set tables are reusable staging tables; once mapped correctly, the same Import Set can be reused for future imports that share the same column structure.
Answer
Update sets are retrieved from a remote instance via All > System Update Sets > Update Sources, which manages connections to other instances for pulling update sets.
Answer
Exporting data as XML from one instance and importing it into another is a common way to migrate records exactly, without needing to build an import set or transform map, for occasional one-time migrations.
Answer
The update set transfer process is: Retrieve the remote update set, Preview it to check for conflicts, then Commit it to apply the changes to the instance.
Answer
UI Actions can be configured with scripts/conditions to trigger outbound SOAP messages when events occur (record created/updated, button clicked, condition met), enabling integration with external systems. UI Policies control visibility/behavior of UI elements, and Data Policies enforce data integrity rules — neither triggers outbound communication.
Answer
ServiceNow supports LDAP integration out of the box, but it is not configured for you. An administrator has to define the LDAP server connection, the OUs to import and the transform maps, and schedule the user and group imports before LDAP authentication and synchronization work.
Answer
Custom roles are configuration records, so creating or changing them is captured in update sets, and they move between instances like any other customization. Assigning a role to a user or group is data, however, and is not captured.
Answers
Update sets capture configuration changes, such as creating or modifying tables, changing form layouts and defining views. User records are data, not configuration, so they are not captured and have to be moved another way, for example by exporting and importing XML.