Which one of the following statements is a recommendation from ServiceNow about Update Sets?
Avoid using the Default Update set as an Update Set for moving customizations from instance to instance
Before moving customizations from instance to instance with Update Sets, ensure that both instances are different versions
Use the Baseline Update Set to store the contents of items after they are changed the first time
Once an Update Set is closed as “Complete”, change it back to “In Progress” until it is applied to another instance
Update Setsin ServiceNow are used tocapture customizations and configurationsmade in an instance, allowing these changes to be moved between instances (e.g., from development to test or production). ServiceNow provides best practices to ensure smooth migration and avoid issues with missing or conflicting updates.
What is an Update Set?
AnUpdate Setis a collection of customizations (e.g., changes to forms, scripts, workflows, business rules) that can be moved from one instance to another.
Ittracks changesin a controlled way, preventing accidental loss of configurations.
Why Avoid Using the Default Update Set?
TheDefault Update Setis automatically used when no other update set is selected.
It captures changesbut should never be used for instance-to-instance migrationsbecause:
Itcannot be exported.
It contains system changes that arenot logically grouped.
It can causeinconsistencies and missing dependencieswhen moving updates.
Instead, administrators shouldcreate a named Update Setfor specific development work.
Understanding Update Sets in ServiceNow:
Why Answer " A " is Correct:✔️ " Avoid using the Default Update Set as an Update Set for moving customizations from instance to instance. "
This follows ServiceNow’sbest practicesfor managing Update Sets.
Using theDefault Update Setcan lead tomissing updates, conflicts, and untracked changes, making migrations unreliable.
Why the Other Answers Are Incorrect:B. " Before moving customizations from instance to instance with Update Sets, ensure that both instances are different versions. "
Incorrectbecause ServiceNowrecommends that instances be on the same versionbefore applying Update Sets.
If instances are ondifferent versions, the Update Set may includeincompatible changes, causing failures.
C. " Use the Baseline Update Set to store the contents of items after they are changed the first time. "
Incorrectbecause there is no such thing as a " Baseline Update Set " in ServiceNow.
ServiceNowdoes not automatically create a backup of original configurations—administrators should manually create an Update Set before making changes.
D. " Once an Update Set is closed as ' Complete, ' change it back to ' In Progress ' until it is applied to another instance. "
Incorrectbecausea completed Update Set should not be reopened.
Once markedComplete, an Update Set isready for export and migration. Reopening it can causedata integrity issuesand confusion in version control.
ServiceNow CSA Study Guide – Update Sets & Configuration Management
ServiceNow Docs: Best Practices for Update Sets(ServiceNow Documentation)
ServiceNow Docs: Moving Customizations with Update Sets
References from the Certified System Administrator (CSA) Documentation:
What are the two aspects to LDAP Integration?
Data Population
Data formatting
Authorization
Authentication
LDAP (Lightweight Directory Access Protocol) Integrationin ServiceNow enables organizations to connect theircorporate directory services (such as Microsoft Active Directory)with their ServiceNow instance. This integration helps manageuser authentication and data synchronizationefficiently.
There aretwo key aspectsof LDAP Integration in ServiceNow:
Authentication
LDAP is commonly used foruser authentication, allowing users to log in to ServiceNow using theircorporate credentials.
Instead of storing passwords in ServiceNow, authentication requests are sent to theLDAP serverto verify the user ' s identity.
This helps in maintainingcentralized identity managementacross the organization.
Data Population
LDAP can be used toimport user and group informationinto ServiceNow.
This process is known asdata synchronization, where attributes such asusernames, email addresses, department details, roles, and group membershipsare pulled from LDAP and stored in ServiceNow.
This ensures that user information in ServiceNow isalways up-to-datewith the organization ' s directory.
B. Data Formatting–
While ServiceNow does process data from LDAP, " Data Formatting " isnotan aspect of LDAP integration.
Formatting refers to structuring or modifying data but is not a core function of LDAP integration.
C. Authorization–
Authorizationdetermines what a user can doafter authentication, such as assigning roles and permissions.
While ServiceNow can use LDAPgroupsto assign roles, the integration itselffocuses on Authentication and Data Populationrather than defining permissions within ServiceNow.
ServiceNow Docs: LDAP Integration
ServiceNow CSA Official Training Guide (LDAP Integration & User Authentication)
Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that the two main aspects of LDAP Integration in ServiceNow areAuthentication and Data Population.
Which statement is true about business rules?
A business rule must run before a database action occurs
A business rule can be a piece of Javascript
A business rule must not run before a database action occurs
A business rule monitors fields on a form
Abusiness rulein ServiceNow is a server-side script written inJavaScriptthat executes when a record is inserted, updated, deleted, or queried. Business rules allow for automation and enforcement of business logic without requiring manual intervention.
Business rules arenot tied to formsbut instead runon the server-sidewhen a database operation occurs. They can be configured to execute:
Beforea record is saved (Before Business Rule)
Aftera record is saved (After Business Rule)
Asynchronously(Async Business Rule)
Before a query is run on the database(Query Business Rule)
Explanation of the Correct Answer:B. A business rule can be a piece of JavaScript(Correct)
Business rules are written inJavaScript, allowing administrators to define custom logic that executes on the server.
These scripts can modify data, enforce rules, validate fields, or trigger other workflows.
Example JavaScript snippet for a business rule:
if(current.state== ' 3 ' & & current.priority!= ' 1 ' ) {
current.priority= ' 1 ' ;
gs.addInfoMessage( " Priority set to High because state is Resolved. " );
}
This rule ensures that if an incident ' s state is changed toResolved, its priority is automatically set to High.
Why the Other Options Are Incorrect:A. A business rule must run before a database action occurs (Incorrect)
Business rulescan run before a database action occurs, but they can also executeafterorasynchronously.
Business rules have four execution types:
Before– Runs before the record is inserted/updated in the database.
After– Runs after the record is committed to the database.
Async– Runs in the background after the transaction completes.
Query– Runs before data is returned to a user (modifies query results).
C. A business rule must not run before a database action occurs (Incorrect)
This is false because some business rulesdo run beforea database action (e.g., aBefore Business Rulecan validate data before saving).
D. A business rule monitors fields on a form (Incorrect)
Business rulesdo not monitor form fields directly. Instead, they execute based on database operations.
If real-time monitoring of form fields is needed,Client Scripts(not Business Rules) are used for this purpose.
Automaticallyassigning prioritybased on ticket severity.
Preventing updates to certain records if a condition is not met.
Sending email notifications when a record changes.
Modifying data before it is saved to enforce business policies.
Example Use Cases for Business Rules:
How are Workflows moved between instances?
Workflows are moved using Update Sets
Workflows are moved using Transform Maps
Workflows are moved using Application Sets
Workflows cannot be moved between instances
Workflows inServiceNoware typically moved between instances usingUpdate Sets. Update Sets serve as a mechanism for capturing customizations and migrating them across different environments, such asDevelopment (Dev) → Test → Production (Prod).
Recording Customizations:
When a workflow is modified or created, its changes are recorded in an Update Set if theUpdate Set is active.
Capturing Related Records:
Workflows consist of multiple components (e.g., activities, conditions, transitions).
Update Sets capture theWorkflow Versionand associatedWorkflow Activities.
Exporting and Importing:
The Update Set containing the workflow is exported from the source instance (e.g., Dev).
It is then imported into the target instance (e.g., Test or Prod).
Commit the Update Set:
After import, the Update Set must be reviewed and committed to apply the changes in the target instance.
B. Workflows are moved using Transform Maps
Incorrect: Transform Maps are used forimporting and mapping datafrom external sources into ServiceNow tables, not for migrating configurations like workflows.
C. Workflows are moved using Application Sets
Incorrect: There is no such thing as " Application Sets " in ServiceNow. However,Applications (Scoped Apps)can be moved usingApplication Repositories (App Repo)orUpdate Sets, but this is different from standard Workflow migration.
D. Workflows cannot be moved between instances
Incorrect: Workflowscanbe moved usingUpdate Sets, and in scoped applications, they can also be packaged with the application.
How Update Sets Work for Workflows?Why Other Options Are Incorrect?
ServiceNow Product Documentation - Update Sets
Update Sets Overview
Moving Customizations Using Update Sets
ServiceNow Workflows
Workflow Management
References from ServiceNow CSA Documentation:
Copyright © 2021-2026 CertsTopics. All Rights Reserved