Pass the ServiceNow Certified System Administrator CSA Questions and answers with CertsForce

In ServiceNow Knowledge Management, the ability to create, edit, or import articles into a specific Knowledge Base is governed by User Criteria , specifically the Can Contribute criteria.

1. User Criteria vs. Roles:

While ServiceNow heavily utilizes Roles (like itil or admin) for general platform security, Knowledge Bases use a more granular, criteria-based approach. On a Knowledge Base definition record, administrators define who can interact with it using two primary related lists:

Can Read: Who is allowed to see the articles.

Can Contribute: Who is allowed to author, edit, and import articles.

2. The Import Process:

ServiceNow allows users to import Word documents directly into a Knowledge Base to automatically generate HTML articles. To utilize this feature for a given KB, the user must meet the conditions defined in that KB ' s " Can Contribute " User Criteria (which could be based on their department, group, role, or individual user record).

3. Why the other options are incorrect:

A & B: sn_knowledge_contribute and sn_knowledge_import are not standard out-of-the-box base platform roles dedicated specifically to the single action of importing.

C: There is no distinct " Can import " User Criteria related list. The right to import is bundled into the general right to author/contribute.

InServiceNow Table Inheritance, tables can be categorized asBase, Parent, or Childdepending on how they relate to other tables.

Task Table:

Base Table:Since it isnot extended from any other table, it serves as the foundation for other tables.

Parent Table:Because theIncident tableextends from Task, Task acts as aParenttable.

Incident Table:

Parent Table:BecauseSuper Incident extends from Incident, it becomes aParentto Super Incident.

Child Table:Since it extends fromTask, it is aChildtable to Task.

Super Incident Table:

Child Table:Because it extends fromIncident, it is aChildtable.

Not a Parent or Base Tablebecause no other table extends from it.

Understanding Table Relationships in the Given Scenario:Final Table Classification:Table

Base Table?

Parent Table?

Child Table?

Task

Yes

Yes

No

Incident

No

Yes

Yes

Super Incident

No

No

Yes

A. Incident table is a Base table →Incorrect

TheTask tableis the Base table, not Incident.

E. Super Incident table is a Parent table →Incorrect

No table extends from Super Incident, so itcannot be a Parent table.

F. Super Incident table is a Base table →Incorrect

It is extended fromIncident, meaning itis not a Base table.

I. Task table is a Child table →Incorrect

Sinceno other table extends to Task, it isnot a Child table.

Table Inheritance in ServiceNow

Extending Tables

Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

Detailed Explanation:

To assign a task to themselves, users in ServiceNow can:

Option A:Use the check box to select the record, then click the Person icon to assign it.

Option B:Select the Task number and use theAssign to meUI action available on the form. These methods provide quick ways for users to take ownership of tasks directly from the list view. (Reference: ServiceNow Documentation - Task Assignment and List Actions)

Predictive Intelligence (PI)in ServiceNow is anAI-powered frameworkthat helpsautomate classificationanddecision-makingbased on historical data. It canautomatically populate values for fields like Priority and Categorybased on theShort Descriptionfield value.

D. Predictive Intelligence

Usesmachine learning modelsto analyze patterns in previous records.

Automaticallysuggests or assigns valuesfor fields likePriority, Category, and Assignment Group.

Example:

If a user submits anincident with " Email not working " in theShort Description, Predictive Intelligence can:

SetCategorytoEmail

SetPrioritytoMedium

Assign the ticket to the appropriateSupport Group

A. UI Policy

UI Policiescontrolform behavior(e.g., showing/hiding fields) butdo notdynamically assign values based on machine learning.

B. Assignment Rule

Assignment Rulesdeterminewho gets assigneda record based on conditions butdo not populate Priority or Category automatically.

C. Action

" Action " is not a framework—it refers toFlow Designer actions, which require manual configuration.

E. CSDM (Common Service Data Model)

CSDMis adata frameworkfor managing CIs and services, but it doesnot handle automatic field population.

In ServiceNow, a useronlysees modules and records they have permission for, based onroles and group memberships. If an IT user can only seeSelf-Service, it ' s likely because theylack the required rolesfor IT tasks.

B. His user account does not belong to any groups that contain the ITIL role

TheITIL roleis assigned viauser groups(e.g., " Service Desk, " " IT Support " ).

If the user is not in anITIL role group, theywill notsee IT-related modules.

D. His user account does not have the ITIL role

TheITIL role (itil)is required to accessIncidents, Changes, Tasks, and Service Catalog Management.

Without it, the useronlyseesSelf-Serviceoptions (e.g., requesting services, reporting issues).

A. His user account failed LDAP authentication

If LDAP authentication failed, the userwould not be able to log in at all.

The issue here isrole-based access, not authentication.

C. His user account was not approved by his manager

User approval may be required for account creation, butit does not affect role permissions.

E. His user account is not logged in properly

If the user was not logged in properly, theywould not see any homepage at all.

The issue here islimited access due to missing roles.

InServiceNow, by default, the " Save " button is not displayedon the form header. Instead, users typically use the " Submit " or " Update " buttons.

To enable the " Save " buttonon the form header, you mustenable theglide.ui.advancedsystem property.

Enables the " Save " Button in the Form Header

Theglide.ui.advancedpropertyactivates additional UI options, including theSave button on forms.

Once enabled, users will see the " Save " button alongside " Submit " and " Update " in the form header.

Allows Partial Record Saves Without Submitting

Unlike " Submit " (which creates a new record) or " Update " (which modifies an existing record), " Save " allows users toretain changes without submitting the form.

Useful fordrafts or in-progress edits.

Controlled via System Properties

The " Save " buttonisnot a field or UI actionthat can be manually added through Form Design or Layout.

It is enabledat the system levelviaSystem Properties > UI Properties.

Why is " Turning onglide.ui.advanced " the Correct Answer?

Navigate toAll > System Properties > UI Properties

Find theglide.ui.advancedproperty

Set it to " true "

Save the changes

Refresh theIncident form→ The " Save " button will now appear

How to Enable the Save Button in ServiceNow?

B. Context Menu > Form Design > Add the " Save " buttonIncorrect– The " Save " button isnot a UI actionthat can be added via Form Design. It must beenabled through system properties.

C. All > System Properties > UI Properties > Turn on the " Save " buttonIncorrect– No suchspecific " Save " button settingexists in UI Properties. The correct setting isglide.ui.advanced.

D. Context Menu > Form Layout > Add the " Save " buttonIncorrect–Form Layout only controls fields, not form buttons. The " Save " button is controlled viaUI Properties.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Enabling the Save Button???? Configuring UI Properties

ServiceNow Docs – Using the glide.ui.advanced Property???? Understanding glide.ui.advanced

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

A. All > System Properties > UI Properties > Turn on theglide.ui.advancedproperty

Thisenables advanced UI options, including the " Save " button, allowing users tosave records without submitting them.

In ServiceNowFlow Designer, when an action is executed within a flow, it generates aruntime valuethat remains consistent throughout the flow execution. This value is known as adata pill runtime value.

???? Understanding Data Pill Runtime Values:

Definition:A data pill represents dynamic data retrieved from a trigger, action, or step in a flow.

Behavior:When a flow runs an action, it produces adata pillthat stores the generated value. This value remains unchanged for the duration of the flow’s execution.

Usage:These values can be used in conditions, other actions, or as inputs to subsequent steps.

???? Key Features of Data Pills in Flow Designer:

Persistency:The data pill’s value remains the same throughout the flow’s execution.

Accessibility:Data pills can be referenced throughout different actions in the flow.

Dynamic Population:Data pills dynamically capture runtime values, eliminating the need for hardcoding.

???? Example Scenario:

Suppose a flow is triggered when a new incident is created. The incident’ssys_idis stored as adata pilland can be referenced in subsequent actions, such as sending an email notification or updating the record.

???? Reference:

ServiceNow Docs: Understanding Data Pills in Flow Designer

ServiceNow Flow Designer Training: Flow Designer Basics

TheCI Dependency View Mapin ServiceNow is a graphical representation of therelationshipsanddependenciesbetween Configuration Items (CIs) within theConfiguration Management Database (CMDB). Right-clicking on a CI in the Dependency View provides additional options for analyzing its impact and history.

A. View Affected CIs

Shows all CIsimpactedby the selected CI.

Example: If adatabase servergoes down, this option lists all applications and services affected.

B. View Related Tasks

Displays tasks (e.g.,Incidents, Changes, Problems) associated with the selected CI.

Example: Viewing allopen Incidentsrelated to aserver CI.

C. View Recent Outages

Showsrecently reported outageslinked to the selected CI.

Useful for analyzing recurring issues or identifying historical failures.

D. View Cases

Casesare used inCustomer Service Management (CSM), not in CMDB CI dependency maps.

E. View Knowledge

WhileKnowledge Articlesmay reference a CI, this is not an option in theCI Dependency View Map.

When transferringlarge amounts of databetween ServiceNow instances, the mostefficient and recommended methodisExport to Data Package. This method allows for bulk data transfer, ensuring that relationships, dependencies, and data integrity are maintained.

Optimized for Large Data Transfers

Data Packages are designed toefficiently handle large datasetswithout performance degradation.

They maintain relationships between records, unlike simple XML exports.

Preserves Data Integrity

Ensures that allreferenced records(e.g., related tables) are included in the export.

Prevents data loss by preserving dependent records.

Faster and More Reliable than XML or Update Sets

XML exports areless efficientfor large datasets.

Update Setsdo nottransfer actual table records, only configurations (metadata).

Supports Complex Data Structures

Useful for movingentire tablesor a large subset of records while maintaining relationships.

Why " Export to Data Package " is the Best Choice?

B. Export to XMLIncorrect– XML exports arenot efficient for large data transfersbecause:

It does not manage relationships between records.

Importing large XML filescan cause performance issues.

More suitable for movingindividual recordsrather than large datasets.

C. Update SetsIncorrect–Update Sets do NOT transfer actual data, only configurations (e.g., fields, forms, workflows).

They aremeant for customization changes, not for moving large data records.

D. Export to ZipIncorrect– There is no " Export to Zip " option for large data transfers in ServiceNow.

This is likely adistractor option.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Data Export and Import Best Practices???? Data Export and Import

ServiceNow Docs – Moving Data Between Instances???? Exporting and Importing Data Packages

Official ServiceNow Documentation References:

Conclusion:The correct answer isA. Export to Data Packagebecause it is themost efficient and scalableway to transfer large amounts of data between ServiceNow instances whilemaintaining relationships and data integrity.

InServiceNow, aMany-to-Many (M2M) relationshipexists whenrecords in one tablecan be associated withmultiple records in another table, and vice versa.

A classic example of anM2M relationshipis:

✔Vendors can sell multiple products

✔Products can be sold by multiple vendors

Vendors oftensell multiple productsacross different categories.

A single product can beavailable from multiple vendors.

This requires anintermediary (join) tableto track the many-to-many relationship.

A. Requests & Items

Incorrectbecause eachRequest (REQ#)can havemultiple requested items (RITM#), but anitem does not belong to multiple requests. This is aone-to-many (1:M) relationship.

C. Tasks & Workflows

Incorrectbecause workflows are associatedat an individual task level, and while multiple workflows may be involved, they do not create a trueM2M relationship.

D. Configuration Items & Classes

Incorrectbecause a Configuration Item (CI)belongs to only one class, making this aone-to-many relationship, not M2M.

When importing spreadsheet data into ServiceNow using theImport Setprocess, data is transferred in multiple stages. The step where data getswritten to the receiving tableis called " Run Transform. "

Load Data:The spreadsheet or data file is uploaded to a temporary table (Import Set table).

Run Transform:The system processes the import set data andwrites it to the target table.

Verify Data:After transformation, the data is checked for accuracy.

Load Data:

The spreadsheet or external data is first imported into astaging table (Import Set table)in ServiceNow.

At this stage, the data is not yet written to the actual destination table.

Run Transform (Correct Answer):

TheTransform Mapapplies field mappings and business logic.

The data is processed and written from the import set table to the target table (e.g., Incident, CMDB, or any other receiving table).

Any data transformation (such as field mappings, lookups, or script-based modifications) happens here.

Verify Data:

After transformation, users shouldvalidate the imported recordsto ensure that data was written correctly.

B. Run Import:

This steponly loads the data into a temporary Import Set table.

It does not write data to the receiving table.

C. Import Dataset:

" Import Dataset " isnot an actual stepin the ServiceNow data import process.

D. Execute Transform:

There is no " Execute Transform " step in ServiceNow.

The correct term is " Run Transform. "

E. Schedule Transform:

While youcanschedule transforms, this is not the step where data gets written to the final table.

The actual transformation and writing occur during " Run Transform. "

Import Set Process in ServiceNow:Explanation of Each Step:Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:For more details, refer to the official ServiceNow documentation:

Importing Data into ServiceNow

Transform Maps in Import Sets