CSA Sample Questions Answers

In ServiceNow, theApplication Navigatorallows users to browse and accessApplications and Modules. Toexpand or collapsethe Application Navigator, users interact with theApplication Menu icon (☰), commonly known as the "Hamburger" menu.

Locate thethree-line "Hamburger" icon (☰)at the top-left of theApplication Navigator.

Double-clickorsingle-clickto expand/collapse the list of applications and modules.

A. Star(Incorrect)

TheStar icon (⭐)representsFavorites, allowing users to mark frequently used modules for quick access.

B. Clock(Incorrect)

TheClock icon (⏱️)is forRecently Viewed Items, showing the user's most recent navigations.

D. Funnel(Incorrect)

TheFunnel icon (????)is afilterused to refine search results or application lists, not to expand/collapse the navigator.

Navigating the Application Menu:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html

How to Expand/Collapse Applications & Modules:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

Flow Designeris ano-code/low-codeautomation tool in ServiceNow that enables users toorchestrate business processes across different serviceswith minimal technical knowledge. It allowsnon-technical usersto build complex workflows using drag-and-drop functionality.

No-Code/Low-Code Automation

Users candesign, test, and managebusiness processeswithout coding skills.

Actions can be executedsequentially or conditionallybased on logic.

Integration with ServiceNow Applications

Flow Designer works withIntegrationHub, allowing ServiceNow to interact with external systems like Slack, Microsoft Teams, and Jira.

Trigger-Based Execution

Flows can be triggeredby conditions, schedules, or user actions.

Prebuilt Spokes & Actions

ServiceNow providesprebuilt "Spokes"with reusable actions that simplify workflow automation.

A. Flow Manager(Incorrect)

No such module called "Flow Manager" exists in ServiceNow.

C. Flow Editor(Incorrect)

The term "Flow Editor" is not used in ServiceNow; the correct name isFlow Designer.

D. Workflow Editor(Incorrect)

Workflow Editoris part of the olderLegacy Workflow Engine, which requires scripting and is not recommended for no-code automation.

E. Workflow Designer(Incorrect)

This is not an official ServiceNow tool; Flow Designer has replaced older workflow tools for modern automation needs.

Flow Designer Overview:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/concept/flow-designer.html

Building Flows in Flow Designer:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/task/t_CreateFlow.html

Key Features of Flow Designer:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

Access Control Rules (ACLs) are a fundamental security feature in ServiceNow that protect applications by identifying and restricting access to files and data. ACLs define which users or roles have permissions to create, read, write, or delete data within an application.

Understanding Access Control Rules (ACLs)ACLs in ServiceNow operate based on three key elements:

Object Type– Defines what is being secured (table-level or field-level access).

Operation– Specifies the type of access (Create, Read, Write, Delete, Execute, etc.).

Condition & Script– Determines when access is granted (role-based permissions or specific conditions).

Data Security:Ensures that only authorized users can access specific data.

Granular Access:Controls permissions at the table and field level.

Regulatory Compliance:Helps organizations maintain security standards and data protection laws.

ServiceNow applies ACLs from the most specific to the most general (Field-level → Table-level → Global-level).

If no ACL explicitly allows access, the system denies it by default (Deny by Default Policy).

ACLs can be role-based, condition-based, or script-based for advanced security configurations.

A. Application Configuration– This refers to application settings but does not control access to data.

B. Verbose Log– Logging helps in debugging but does not secure applications or restrict access.

D. Application Scope– Defines application boundaries but does not control data access permissions.

ServiceNow CSA Documentation: Access Control Rules (ACLs)

ServiceNow Security Best Practices: Security and Access Control

Why Access Control Rules are Important?How ACLs Work in ServiceNow?Incorrect Answer Choices Explanation:Official CSA Documentation Reference:

InServiceNow, theService Catalogis the primary module where users canorder services and productsoffered by various departments. The Service Catalog provides acentralized portalfor users to browse and requestIT, HR, Facilities, Finance, and other departmental servicesin a structured and automated way.

TheService Catalogis aself-service interfacewhere users can request predefined services, products, and resources.

It acts as adigital storefrontfor an organization's internal and external services.

Each service request follows aworkflowthat may includeapprovals, task assignments, and fulfillment processes.

Service Offerings:

Users can requesthardware (laptops, mobile devices, monitors), software, access permissions, or HR-related services (e.g., PTO requests, onboarding).

Structured Request Fulfillment:

Each request follows aworkflowwith assigned tasks to the appropriate fulfillment teams.

Example: A request for anew laptopis routed toIT Supportfor approval and processing.

Automation and Approvals:

Some catalog items requiremanagerial or departmental approvalsbefore fulfillment.

Example: Requesting access torestricted applicationsmight need approval from anIT admin.

Integration with Incident, Change, and Asset Management:

The Service Catalog can triggerchange requests, incidents, and asset updatesas part of the fulfillment process.

Access Through the Self-Service Portal:

Users can access theService Catalogvia theSelf-Service Portalfor quick and easy navigation.

What is the Service Catalog?Key Features of the Service Catalog:

Why Option A (Service Catalog) is Correct?TheService Catalogis the correct place toorder services and productsoffered by different departments in ServiceNow.

It provides astructured and automatedway to request, approve, and fulfill service requests.

Why Other Options Are Incorrect?B. Self-Service– TheSelf-Service Portalprovides access to the Service Catalog but is not where services are ordered directly.

C. Service Department– No such module exists in ServiceNow. Departments use theService Catalogto provide services.

D. Customer Service– TheCustomer Service Management (CSM)module is forexternal customers, not internal service requests.

ServiceNow Docs – Service Catalog Overviewhttps://docs.servicenow.com

ServiceNow Learning – Self-Service & Service Catalog Best Practices

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Import Setsallow administrators toimport and transform datafrom external sources into ServiceNow tables. The platform supports multiple file formats for importing data, includingXML, CSV, and Excel.

XML (Extensible Markup Language)

Used for structured data exchange between systems.

ServiceNow canimport XML filescontaining records formatted according to its schema.

CSV (Comma-Separated Values)

One of the most common formats for bulk data imports.

ServiceNow can processCSV filesand map them to target tables.

Excel (XLS/XLSX)

ServiceNow allows direct imports fromMicrosoft Excel spreadsheets.

Users can upload Excel files via the Import Set UI.

Supported Data Formats for Import Sets:

Import Data:The user uploads a supported file (XML, CSV, or Excel) into an Import Set table.

Mapping:The imported data is mapped to target tables using aTransform Map.

Transformation & Processing:Data is transformed, validated, and inserted into the correct destination tables.

How Import Sets Work in ServiceNow:

A. CSS, SOAP, and Excel→CSS is a styling language, and SOAP is a protocol, not a data format.

C. SOAP, REST, and XML→SOAP and REST areweb service protocols, not file formats used for import sets. XML is valid but alone is insufficient.

D. XML, SOAP, and CSS→SOAP and CSS are incorrect as they are not standard import file formats.

Why Other Options Are Incorrect:

ServiceNow Documentation:Importing Data into ServiceNow

CSA Exam Guide:Coverssupported data formats for Import Sets (XML, CSV, and Excel).

TheCommon Service Data Model (CSDM)is a framework provided by ServiceNow that ensures your application's data correctly maps to theConfiguration Management Database (CMDB)tables. It standardizes howconfiguration items (CIs), services, and relationshipsare structured within the CMDB.

Standardized Data Model:Ensures consistent and correct CMDB data structuring.

Alignment with CMDB Best Practices:Helps businesses align their IT assets, services, and business functions effectively.

Better Service Mapping:Provides structured relationships between business services and their technical components.

Compliance & Governance:Ensuresdata integrityby enforcing best practices for CMDB population.

Key Functions of CSDM:

Incorrect Answer Choices Explanation:B. Service Mapping Utility (SMU)– Service Mapping is used fordiscovering and mapping dependenciesbut is not a data model framework.

C. Service Schema Map (SSM)– No such official term exists in ServiceNow documentation.

D. CMDB Class Manager (CMDBCM)– This is a tool used tomanage CI classesbut does not define a data model framework like CSDM.

E. CI Class Manager (CICM)– Incorrect term; CMDB Class Manager is used for CI class hierarchy management, not for mapping applications to CMDB tables.

ServiceNow Documentation: Common Service Data Model (CSDM)CSDM Overview

ServiceNow CMDB Best PracticesCMDB and CSDM Alignment

Official CSA Documentation Reference:

Thekey differencebetweenReportingandPerformance Analytics (PA)is how they handle data over time.

Showsreal-time datafrom tables.

Runs queries on dataat the momentthe report is generated.

Cannot analyze historical trendsunless data is manually stored.

Used forstatic reports, lists, charts, or dashboards.

Capturessnapshotsof data at scheduled intervals (e.g., daily, weekly).

Tracks trends and KPIs (Key Performance Indicators)over time.

Helps organizationsforecast and analyze historical patterns.

Used forbusiness intelligence and proactive decision-making.

ReportingPerformance Analytics (PA)

Incorrect Answer Choices Explanation:B. Performance Analytics can show trends; Reports cannot.

Reporting can show trends usingaggregated data(e.g., grouped by date), butPA is specifically designedfor tracking trends over time.

C. Reports can be run on a scheduled basis; Performance Analytics cannot.

BothReports and PA can be scheduledto run at regular intervals.

D. Performance Analytics data can be published to Dashboards; Reports cannot.

Reportscanbe published todashboards, just like Performance Analytics.

E. Performance Analytics shows KPIs; Reporting does not.

Reports candisplay KPIsusing calculated metrics and aggregations, butPA is optimizedfor KPI tracking over time.

Performance Analytics vs. Reporting

ServiceNow Reporting Overview

Official CSA Documentation Reference:

TheFilter Navigatorin theApplication Navigatoris a powerful search tool inServiceNowthat allows users toquickly find applications and modulesby typing keywords instead of manually browsing through the navigation menu.

Quick Navigation:

Users can type thename of an application or moduleto locate it instantly.

Example: Typing"incident"in the Filter Navigator will show links to"Create New Incident," "All Incidents," "Open Incidents," etc.

Dynamic Filtering:

The list of applications and modulesdynamically updatesas you type.

Helps users findrelevant sectionswithout scrolling through the full menu.

Keyboard Navigation Support:

Users canuse the keyboard (arrow keys and Enter)to navigate through the filtered results.

Time-Saving Feature:

Reduces the need toexpand and collapse menus manually.

Especially useful fornew users or users working across multiple modules.

Key Functions of the Filter Navigator:Why Option B is Correct?The Filter Navigator is specifically designed to help users quickly search and navigate to applications and modules.

Why Other Options Are Incorrect?A. Filter applications in order of use→ Incorrect

The Filter Navigatordoes not sort applications by usage; it simply filters based on text input.

C. Collapse and expand applications→ Incorrect

Expanding/collapsing applications is donemanually, but the Filter Navigator is purely forsearching and filtering.

D. List applications in order of Top Requests→ Incorrect

The Filter Navigatordoes not rank applicationsby usage or requests. It onlyfiltersbased on search input.

ServiceNow Docs – Using the Filter Navigatorhttps://docs.servicenow.com

ServiceNow Learning – Application Navigator and UI Features

References from Certified System Administrator (CSA) Documentation:

AConfiguration Item (CI)is any component thatneeds to be managed to deliver IT services. In ServiceNow, CIs are stored in theConfiguration Management Database (CMDB)and can include servers, applications, databases, network devices, and more.

Tracking & Management: Helps organizations track IT assets and their relationships.

Service Impact Analysis: Identifies how an issue with one component can affect related services.

Change Management Support: Ensures changes to IT assets are controlled and well-documented.

Incident & Problem Resolution: Provides insights into troubleshooting and root cause analysis.

Hardware: Servers, network devices, storage systems.

Software: Applications, databases, operating systems.

Services: Business services, IT services.

Documentation: Policies, SLAs, knowledge articles.

Why Are Configuration Items Important?Examples of Configuration Items (CIs):

Incorrect Answer Choices Explanation:A. CSDM Items– TheCommon Service Data Model (CSDM)is a framework for structuring CMDB data, but individual components in the CMDB are calledConfiguration Items (CIs).

B. CMDB– TheCMDB (Configuration Management Database)is thedatabasethat stores Configuration Items, but it is not a CI itself.

D. Service Offerings– AService Offeringrepresents a set of capabilities available to customers but is not the same as a CI.

E. Asset– AnIT Assetrefers to aphysical or virtual resourceowned by the organization, butnot all assets are CIs(e.g., a computer mouse may be an asset but not a CI).

ServiceNow CMDB Overview

Configuration Items (CIs)

Official CSA Documentation Reference:

When youimpersonatea user in ServiceNow for testing, you temporarily assume their permissions and role-based access. Toreturn to your own user session, thebestway is toEnd Impersonation.

Click on theUser Menu (top right corner).

Select"End Impersonation".

You will immediately return to your original user session.

A. Turn your computer off and on again→ Unnecessary and does not affect session management.

B. Clear browser cache→ Cache clearing is not required; impersonation is session-based.

D. Log out and back in→ While this works, it isnot the bestmethod becauseEnd Impersonationis a faster and direct solution.

InServiceNow, thepersonal_listrole allows users toadd or remove fields from a list viewwithout requiring full administrator privileges.

Modify List Layout (Columns & Fields)

Users canadd, remove, or rearrange columnsin list views.

Save Personal List Preferences

Customizations applyonly to the user, unless they have additional permissions to modify system-wide settings.

Does NOT Allow System-Wide Changes

Unlike theadminrole,personal_listonly affectspersonal viewsof lists, not global configurations.

A. personalize.control(Incorrect)

No such role exists in ServiceNow.

C. ui_page_admin(Incorrect)

This role allows users tomanage UI Pages, but it does not provide list customization permissions.

D. ui_action_admin(Incorrect)

This role is used tomanage UI Actions(buttons, links, and client-side scripts), not list view configurations.

Key Capabilities of thepersonal_listRole:Why Other Options Are Incorrect?

Role-Based List Customization

ServiceNow List Personalization

User Roles and Permissions

ServiceNow User Roles

References from ServiceNow CSA Documentation:

In ServiceNow,list filtersallow users to define and apply specific conditions to refine data displayed in a list view. If an administrator or user wants to make alist filter available to everyone, they need to:

Assign a Name→ The filter must be named so users can identify and reuse it.

Set Visibility→ The filter’s visibility needs to be adjusted to“Everyone”, a specificgroup, or anindividual user.

Save→ The filter must be saved for it to be accessible in future sessions.

Apply a filterin a list view using the filter conditions.

Click theSavebutton.

Provide anamefor the filter.

UnderVisibility, select one of the following:

Me (Private)→ Only the creator can use the filter.

Everyone (Public)→ All users can access the filter.

Group→ Assign the filter to a specific group.

ClickSaveto store the filter.

Steps to Make a List Filter Available to Everyone:

Why "B. Assign a Name, Set Visibility, and Save" is Correct:Assign a Name→ The filter needs an identifiable name for users.

Set Visibility→ Determines whethereveryone, a group, or just the creatorcan see the filter.

Save→ Saves the filter for future use.

A. Make active, set visibility, and save→Filters do not have an "Active" state; they just need to be saved with the correct visibility settings.

C. Assign a group, set visibility, and save→Assigning a group isoptionalbut does not apply to everyone.

D. Make active, assign a name, and save→"Make active" is not required; visibility settings control availability.

Why Other Options Are Incorrect:

ServiceNow Documentation:Creating and Sharing List Filters

CSA Exam Guide:CoversList Filters and visibility settings.

Reference from CSA Documentation:Thus, the correct answer is:

B. Assign a Name, Set Visibility, and Save

InServiceNow, Favorites allow users to quickly access frequently usedmodules, records, lists, or reports. Favorites can be customized, including renaming them, changing their icons, or modifying their colors.

Changing the Label of a FavoriteTorename or edit a Favorite, you must use thePencil icon (✏️), which indicatesedit mode.

Navigate to theApplication Navigatoron the left-hand side.

Locate theFavoritessection.

Hover over the favorite item you want to rename.

Click on thePencil icon(✏️) to open the edit menu.

Update thelabel(name) and other properties like color or icon.

ClickSaveto apply changes.

A. Clock(Incorrect)

TheClock icontypically representsrecently accessed items, not Favorites.

B. Hamburger(Incorrect)

TheHamburger menu (☰)represents navigation menus but is not used to edit Favorites.

D. Three dots(Incorrect)

TheThree dots (⋮)often indicate a menu with additional options but do not specifically edit Favorites.

E. Triangle(Incorrect)

NoTriangle iconis used for renaming Favorites.

F. Star(Incorrect)

TheStar icon (⭐)is used toadd or removeFavorites, but not to rename them.

ServiceNow Favorites Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/task/t_CreateFavorites.html

Steps to Change the Label of a Favorite:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

InServiceNow, aTemplateis a tool used topre-fill commonly used fieldsin a form, saving time and ensuring consistency in data entry.

ATemplateis a predefined set offield valuesthat can be applied to a form toautomatically populate fields.

Users can create and apply templates tospeed up form completionandreduce errors.

Templates are especially useful forstandardized requests, such asincident logging, change requests, or task assignments.

Create a Template:

Navigate toSystem UI → Templates.

Define thefieldsand their default values.

Assign the template to aspecific table(e.g.,incident,change_request).

Apply a Template to a Form:

When filling out a form, users canselect a templatefrom theTemplate Bar.

The templateautomatically populatesthe pre-configured fields.

Example Use Case:

Scenario:A Service Desk agent frequently logs incidents forpassword resets.

Solution:A"Password Reset"template can be created with:

Short Description:"Password reset request"

Category:"Access"

Assignment Group:"IT Support"

When an agent applies this template, these fields areautomatically populated, saving time.

What is a Template in ServiceNow?How to Use a Template?

Why Option A (Template) is Correct?Templates are the official ServiceNow tool for pre-filling commonly used fields in a form.

Why Other Options Are Incorrect?B. Reference Qualifier→ Incorrect

Reference Qualifierscontrolwhich values appear in a reference field(e.g., filtering available users in theAssigned Tofield).

They donot populate fields automatically.

C. Formatter→ Incorrect

AFormatteris a UI component thatdisplays additional information(e.g., anActivity Formattershows an activity log).

It doesnot populate form fields.

D. Assignment Rule→ Incorrect

Assignment Rulesautomaticallyassign recordsto users or groups based on conditions.

They donot populate multiple fieldsin a form.

ServiceNow Docs – Creating and Using Templateshttps://docs.servicenow.com

ServiceNow Learning – Templates and Data Population

ServiceNow Best Practices – Using Templates for Efficiency

References from Certified System Administrator (CSA) Documentation:

Thecorrect answer is "Flows", which refers toFlow Designerin ServiceNow.

Flow Designeris ano-code/low-code automation toolthat allows users to automatebusiness logicfor a specific application or process, such as:

Approvals

Task creation

Notifications

Record operations(such as updating or deleting records)

AFlowis a sequence of automated actions that are triggered by specific events.

It ispart of Flow Designer, which is themodern alternative to the legacy Workflow Engine.

It providestrigger-based execution, meaning it can run when a record is created, updated, or upon a specific condition.

B. Action Sequences(Incorrect)

No such term exists in ServiceNow.

C. Action Sets(Incorrect)

No such feature exists in ServiceNow.

D. Task Flows(Incorrect)

This is not a term used in ServiceNow automation.

E. Flow Diagrams(Incorrect)

While Flow Designervisually representsflows, there isno feature named "Flow Diagrams"in ServiceNow.

Flow Designer Overview:https://docs.servicenow.com/bundle/utah-automation/page/administer/flow-designer/concept/flow-designer.html

How to Create and Use Flows:https://docs.servicenow.com/en-US/bundle/utah-automation/page/administer/flow-designer/task/t_CreateFlow.html

Why "Flows" is the Correct Answer:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

If a user reports that theycannot see certain modulesin theApplication Navigator, the best way to troubleshoot is toimpersonate the user. Impersonation allows an administrator to see exactly what the user seeswithout needing their password.

Click on your profile icon (top-right corner).

SelectImpersonate User.

Search for and select theuser’s name.

The instance will reload, and you will see the UI as the user experiences it.

Navigate to theApplication Navigatorand check for missing modules.

Once done, clickStop Impersonation.

Ensures security(no need to reset or look up passwords).

Speeds up troubleshootingby allowing admins to replicate user issues.

Helps verify role-based access permissions.

Steps to Impersonate a User in ServiceNow:Why is Impersonation Useful?

Incorrect Answer Choices Explanation:A. Look up their password, so you can login with their account

This is asecurity violationand not an acceptable practice.

B. Initiate a Connect Chat session

Chatting with the user can help gather information, but it does not allow you to see what they see.

C. Install the Bomgar plug-in

Bomgaris a remote support tool, but impersonation is thebuilt-inand recommended method for troubleshooting in ServiceNow.

E. Launch a NowChat window

NowChat is used forcustomer support and collaboration, not for verifying module visibility.

Impersonate Users in ServiceNow

User Roles and Permissions

Official CSA Documentation Reference:

TheCMDB Builderis the primary tool used inServiceNow’s Configuration Management Database (CMDB)for creating and managingdependencies between Configuration Items(CIs). It provides agraphical interfacethat allows administrators and CMDB managers to visualize and define relationships between CIs efficiently.

Visual Representation of CI Dependencies:

CMDB Builder provides agraphical interfacethat allows users tocreate, modify, and deleterelationships between Configuration Items (CIs).

It helps in identifyingimpact analysisandservice dependenciesby mapping CIs and their relationships.

Supports Complex CI Relationships:

Allows definingparent-child,peer, anddependencyrelationships between CIs.

Helps in ensuring the accuracy ofservice mapsandIT asset relationships.

Drag-and-Drop Functionality:

Users candrag and dropCIs onto the builder canvas andconnect them using predefined relationships.

Integration with CMDB Relationship Rules:

CMDB Builder adheres toCMDB relationship rulesto ensure that onlyvalidrelationships are created.

Impact and Root Cause Analysis:

Helps introubleshooting IT incidentsby showing thedependencies between services.

Useful inchange managementto predict potentialimpactson downstream services before making changes.

Key Features of CMDB Builder:

A. CI Relationship Editor:

TheCI Relationship Editorallows users toview and edit relationshipsbetween CIs in atabular formatbutdoes not provide a graphical dependency visualizationlike CMDB Builder.

It is moremanual and less interactivecompared to CMDB Builder.

C. CI Service Manager:

CI Service Manageris used for managingCI service mappingsbut isnot primarily a tool for creating dependencies between CIs.

It is more focused ondefining service-level relationshipsrather thanbuilding CMDB dependency models.

D. CI Class Manager:

CI Class Manageris used formanaging CI classes, attributes, and extending CMDB class structures.

It is not used forcreating dependencies between configuration items.

Why Other Options Are Incorrect:

ServiceNow CMDB Guide:CMDB Builder Overview

ServiceNow Best Practices for CMDB:CMDB Relationship Management

ServiceNow Admin Documentation:Understanding CMDB Dependency Management

References from the Certified System Administrator (CSA) Documentation:

Final Answer:CMDB Builder (Option B) is the correct answer, as it is the primary tool used to create, manage, and visualize dependencies between CIs in ServiceNow's CMDB.

InServiceNow (and databases in general), data is stored intables, which consist of:

Columns (Fields):Representindividual data attributes(e.g., Name, Email, Status).

Rows (Records):Representindividual entriesin the table (e.g., a specific Incident or User).

Key Concepts:Table

Columns (Fields)

Rows (Records)

Incident

Number, Caller, Priority, Description

Each unique incident entry

User

Name, Email, Role, Department

Each individual user record

A column represents a single field (data attribute), such as "Priority" or "Short Description."

A row represents a record (entry in the table), such as an individual incident or user.

A. A column is a field in the database and a record is one user→Incorrect

Records are not limited to users; a record could be an Incident, Change, or any other entry.

C. A column is one field and a record is one column→Incorrect

Arecord is not a single column; a record consists of multiple fields (columns).

D. A column contains data from one user and a record is one set of fields→Incorrect

Columns contain data for all users/records, not just one user.

A record is one row, not just a set of fields.

Why is "B. A column is one field and a record is one row" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Understanding Tables and Fieldshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/metadata/concept/c_TablesAndFields.html

References from Certified System Administrator (CSA) Documentation:

To translateService Catalog itemsinto multiple languages in ServiceNow, theTranslation Framework plugin (com.glide.translation_framework)must be activated. This plugin enablesautomatic translation of text fields, including:

Service Catalog items

Knowledge Base articles

Field labels

UI components

Providesmulti-language supportfor catalog items.

Usesmachine translation or manual translation mapping.

Works with theServiceNow Language Packsto provide localized experiences.

Key Features of the Translation Framework Plugin:

TheTranslation Framework plugin (com.glide.translation_framework)is specifically designed to supportmulti-language content translationfor the Service Catalog.

It allows translation of catalog item descriptions, labels, and options without custom scripting.

Why "B. Translation Framework Plugin" is the Correct Answer?

A. Localization Framework Plugin (com.glide.localization_framework) – Incorrect

This plugin helps withlocalization settingsbut is not specifically for catalog item translation.

C. Multiple Language Framework Plugin (com.glide.multiple.language_framework) – Incorrect

No such plugin exists in ServiceNow.

D. Language AI Framework Plugin (com.glide.language.ai_framework) – Incorrect

This is not a valid ServiceNow plugin.

Explanation of Incorrect Options:

ServiceNow Docs: Translation Framework Plugin

ServiceNow CSA Study Guide – Multi-language Support

ServiceNow Product Documentation: Translating Service Catalog Items

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Data Sourcesdefine external data that can be imported into the platform. These sources feed data intoImport Sets, which are then transformed into ServiceNow tables.

Why These Options Are Correct?A. Local Sources (i.e. XML, CSV, Excel)

Allows importingstructured data filesstored locally or uploaded manually.

Commonly used forone-time data migrationsor periodic imports.

D. JDBC Connection

JDBC (Java Database Connectivity)allows ServiceNow to connect directly toexternal databases(e.g., MySQL, Oracle, SQL Server).

Useful forreal-time integrationswith legacy systems.

E. Network Server

Allows importing data from afile stored on a remote serverviaSFTP/FTP.

Common forautomated batch data imports.

F. LDAP Connection

LDAP (Lightweight Directory Access Protocol)allows ServiceNow to syncuser and group datafrom enterprise directories (e.g., Active Directory).

Used forHR, ITSM, and Identity Management.

Why Are the Other Options Incorrect?B. Implementation Spoke

Incorrectbecause "Implementation Spoke" isnot a data sourcebut aServiceNow IntegrationHub componentused for automating ITSM tasks.

C. DataHub

Incorrectbecause "DataHub" isnot a ServiceNow data source.

ServiceNow usesIntegrationHub, JDBC, REST, and SOAP APIsfor data ingestion.

ServiceNow Data Sources - Importing External Data

ServiceNow LDAP Integration - Best Practices

ServiceNow JDBC and File-Based Data Import Methods

References to Official Certified System Administrator (CSA) Documentation:

Afilter conditionin ServiceNow consists of three essential components that define how data is filtered in lists, reports, and queries. These components determine which records meet specific criteria.

Column (D)– Represents thefieldin the table that is being filtered (e.g., "Priority" in theincidenttable).

Operator (A)– Defines the comparison method, such asis, contains, starts with, greater than, etc.

Value (C)– Specifies thecriteriaused for filtering (e.g., "High" for Priority).

Components of a Filter Condition:Example of a Filter Condition in an Incident Table:PriorityisHigh

Column:Priority

Operator:is

Value:High

B. Match Criteria→ Not a defined component; filtering is based on column, operator, and value.

E. Field→ While "Field" is a general term,ServiceNow officially uses "Column"in filter conditions.

Access Control rules in ServiceNow define who cancreate, read, write, or deleterecords in a table or specific fields. These rules are applied at thetable or field leveland follow a specificnaming convention:

TableName.FieldName

Naming Convention for Access Control Rules:

If an Access Control rule applies to a specifictable, its format isTableName(e.g.,incident).

If it applies to a specificfield, it followsTableName.FieldName(e.g.,incident.major_incident).

Major Incident is a field in the Incident table:

Theincidenttable represents the ITSMIncident Management module.

Major Incidentis aspecific fieldwithin theincidenttable.

To apply anAccess Control Ruleto this field, the rule name must beincident.major_incident.

A. Incident.Major_Incident:Incorrect because ServiceNow Access Control rulesdo not use uppercase table or field names—they are alwayslowercase.

B. incident=>major_incident:Incorrect syntax—ServiceNow does not use=>in Access Control names.

C. incident<=>major_incident:Incorrect syntax—ServiceNow does not use<=>in rule naming conventions.

D. incident||major_incident:Incorrect syntax—ServiceNow does not use||(logical OR) in Access Control naming.

ServiceNow Access Control Rules Guide:ServiceNow Docs

How to Create and Manage Access Control Rules in ServiceNow

Why is the Correct Answer "incident.major_incident"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:By usingincident.major_incident, we correctly definefield-level securityfor theMajor Incidentfield in theIncident table.

Virtual Agentis ServiceNow’sAI-powered chatbotthat provides assistance via amessaging interface. It helps users obtain information, make decisions, and complete common tasks without human intervention.

Conversational Interface→ Users interact through chat to get information and perform tasks.

Automated Responses→ Uses predefinedtopicsandnatural language understanding (NLU)to provide relevant answers.

Integration with ServiceNow Applications→ Can create incidents, reset passwords, check order statuses, etc.

Available on Multiple Channels→ Works with Microsoft Teams, Slack, and the ServiceNow portal.

A. Agent Workspace→ A unified interface for agents to manage cases, not an AI chatbot.

B. Chat bot→ A generic term; Virtual Agent is the official chatbot in ServiceNow.

D. Knowledge Chat→ No such feature exists; however, Virtual Agent can integrate with the Knowledge Base.

E. Now Support→ ServiceNow’s customer support portal, not an AI-driven assistant.

InServiceNow's System Import Sets, administrators canimport data from external sources(such as CSV, Excel, or databases) intoany tablewithin the platform usingTransform Maps.

ATransform Mapdefines how data from an Import Set table is mapped to fields in atarget table (destination table).

Administrators can select any tablein the system as the destination, including bothstandard and custom tables.

Thedestination table is not limitedto Task-related tables (Incident, Problem, Change, etc.).

Users can also applycoalesce rulesto determine if records should be updated or inserted during the transformation.

ServiceNowallows administrators to select any tableas the destination when setting up a Transform Map.

This includes standardITSM tables (Incident, Problem, Change, Task, Service Catalog)as well ascustom tablescreated by administrators.

There areno restrictionson which table can be a destination.

A. "The Task table is the only table that can be a destination"→Incorrect

TheTasktable is widely used, but it isnot the only tablethat can receive imported data.

B. "Only Incident, Problem, Change, Task, and Service Catalog tables can be destinations"→Incorrect

These are common ITSM tables, butany table in the systemcan be selected as a destination.

C. "Only the Incident, Problem, and Change tables can be destinations"→Incorrect

This istoo restrictivebecause other tables, including custom ones, can also be used.

Navigate to:System Import Sets > Create Transform Map

Select the Import Set Tableas thesource.

Choose any available tablein ServiceNow as thedestination.

Definefield mappingsbetween the source and target table.

Configurecoalesce rulesto update or insert records.

ServiceNow Docs: Creating and Using Transform Mapshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/import-sets/concept/c_TransformMap.html

ServiceNow CSA Official Training Guide (Import Sets & Data Management)

Key Points About Transform Maps & Data Import:Why is "D. Any ServiceNow table" the Correct Answer?Why the Other Options Are Incorrect?How to Configure a Transform Map in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms thatany ServiceNow tablecan be adestination tablefor imported data when using Transform Maps inSystem Import Sets.

InServiceNow, theTask [task]table is acore tablethat provides aset of standard fieldsused by multiple tables that extend it, including:

Incident [incident]

Problem [problem]

Change Request [change_request]

Service Request [sc_request]

These tablesinherit fieldsfrom theTasktable, ensuring consistency inassignments, state management, and workflows.

Standard Fields:

Assigned To

Assignment Group

Priority

State

Created By / Updated By

Short Description / Description

Extensibility:

TheIncident, Problem, and Change tablesallextendthe Task table, inheriting its fields.

Developers canadd additional fieldswhile keeping core task properties intact.

TheTask table is the primary tablefor work-related records in ServiceNow.

Itstandardizes fieldsacross multiple ITSM modules.

B. Assignment [assignment]→Incorrect

There isno standard "Assignment" tablein ServiceNow.

Assignments are managed through theTask tablevia theAssigned To and Assignment Group fields.

C. Service [service]→Incorrect

There isno generic "Service" tablethat acts as a core table for ITSM processes.

Service-related items are stored in different tables, such ascmdb_ci_service(for service records).

D. Workflow [workflow]→Incorrect

TheWorkflow tableis used for managing automated workflows anddoes not store task-related records.

Key Features of the Task Table:Why is "A. Task [task]" the Correct Answer?Why the Other Options Are Incorrect?

ServiceNow Docs: Task Table Overviewhttps://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/incident-management/concept/task-table.html

References from Certified System Administrator (CSA) Documentation:This confirms thatthe Task table is the core table that extends to Incident, Problem, and other related tables.

TheFlow Designermodule in ServiceNow is used to create and manageautomationsthat involve business logic such asapprovals, tasks, notifications, and integrations. It provides ano-code/low-codeenvironment where users can define automated workflows without needing to write scripts.

Automates Processes– Handles approvals, notifications, and task assignments.

No-Code Interface– Users can build workflows using adrag-and-dropinterface.

Replaces Legacy Workflows– Flow Designer is themodernalternative to Workflow Editor.

Integrates with Spokes– Can connect to other systems usingIntegration Hub.

Triggers– Define when a flow starts (e.g., record changes, schedules, API calls).

Actions– Define what happens (e.g., create a task, send an email, update a record).

Conditions– Add logic to control execution paths.

B. Process Automation > Flow Administration→ Used formanaging existing flows, not creating new ones.

C. Process Automation > Workflow Editor→ This is thelegacyworkflow automation tool, replaced by Flow Designer.

D. Process Automation > Process Flow→ No such module exists in ServiceNow.

E. Process Automation > Active Flows→ Displaysalready running flows, but does not allow new flow creation.

AReference fieldin ServiceNow allows you tolook up values from another table, effectively creating a relationship between two tables. When a user selects a value in a reference field, they are selecting a record from the referenced table.

Stores asys_id(unique identifier) of a record from another table.

Displays a user-friendly label from the referenced record.

Allowsdot-walking, enabling access to related fields from the referenced table.

Incident Table (source table)→ Contains a"Caller"field that references theUser Table(sys_user).

TheCallerfield allows users to select a user from theUser Table.

B. Verity→ Not a valid field type in ServiceNow.

C. Options→ Options are typically used in choice lists, not for referencing another table.

D. Selections→ No such field type exists in ServiceNow.

E. Dot Walk→ Dot-walking is afeaturethat allows accessing related fields but is not a field type itself.

F. Lookup→ While "Lookup Select Box" exists, it functions differently by filtering choices rather than directly referencing another table.

In ServiceNow, every record in a table has a unique 32-character identifier calledsys_id. This ID uniquely identifies a record and is stored in thesys_id fieldfor every table.

sys_id is a globally unique identifierassigned to every record in ServiceNow.

It is a 32-character hexadecimal string, ensuring uniqueness across instances.

It remains constant for a record, even if other fields in the record are modified.

sys_id is used in API calls, reference fields, and update setsto track records across environments.

A. sn_rec_id:No such field in ServiceNow.

B. rec_id:Not a valid field in ServiceNow.

C. u_id:Not a standard ServiceNow field. Custom fields may use "u_" prefix butu_id is not a system field.

E. sn_gu_id:No such field in ServiceNow.

F. sn_sys_id:No such standard field in ServiceNow.

G. id:Generic term, but not a standard field in ServiceNow.

ServiceNow Data Model and sys_id Explained: ServiceNow Docs

sys_id Best Practices for Data Management

Why is the Correct Answer "sys_id"?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:Thesys_idis crucial for tracking and managing records efficiently in ServiceNow and plays a key role in integrations, workflows, and automation.

InServiceNow, you can add additional fields to a form using either:

Form Layout(for quick field additions)

Form Designer(for a drag-and-drop UI approach)

Context Menu > Configure > Form Layout (B)

This allows administrators toadd or remove fieldsin a simplelist-based interface.

Used when only minor modifications are needed.

Context Menu > Configure > Form Design (C)

Opens theForm Designer, adrag-and-drop UI editorfor configuring forms.

Allows users torearrange fields, sections, and tabseasily.

A. Context Menu > Form > Layout(Incorrect)

The correct path isConfigure > Form Layout, not "Form > Layout."

D. Right-click on header > Add > Field(Incorrect)

Right-clicking the form headerdoes not provide an option to add fields directly.

E. Context Menu > Form > Designer(Incorrect)

The correct option isConfigure > Form Design, not "Form > Designer."

F. Right-click on header > Configure > UX Dashboard(Incorrect)

UX Dashboards areused for analytics and reporting, not form configuration.

Form Layout in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/task/t_ConfigureFormLayout.html

Form Designer Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/form-administration/concept/c_FormDesigner.html

Correct Methods:Explanation of Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

AService Level Agreement (SLA)in ServiceNow is a tracking mechanism that ensures tasks are completed within a specified time frame. SLAs help inmonitoring and enforcing deadlinesfor various tasks, such as incidents, changes, or service requests.

Tracks Task Duration

SLAs calculate theelapsed timesince a task was created and determine if it meets or breaches the defined resolution targets.

Ensures Timely Completion

SLAs definestart, pause, and stop conditionsbased on specific criteria (e.g., an incident must be resolved within 8 hours).

Visual Indicators

SLAs includeprogress bars, warning alerts, and breach notificationsto help users track deadlines.

Works with Business Rules and Workflows

SLAs can triggerescalations, notifications, or automated actionsif a task is at risk of breaching the SLA.

A. Task Escalation Clock(Incorrect)

No such feature called "Task Escalation Clock" exists in ServiceNow. Escalations are handled usingSLA workflows and escalation rules.

C. Inactivity Monitor(Incorrect)

TheInactivity Monitoris used to detect when a task has not been updated for a specific period, but it does not enforce time-bound completion.

D. Response Time Clock(Incorrect)

No specific "Response Time Clock" exists in ServiceNow.Response SLAstrack thetime taken to acknowledge a task, but this is part of the broader SLA system.

E. Business Time Remaining(Incorrect)

This isnot a specific featurebut rather a calculated field within SLAs that shows the time remaining before an SLA breaches.

Service Level Agreements (SLA) Overview:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-level-management/concept/c_ServiceLevelAgreements.html

How SLAs Work in ServiceNow:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/service-level-management/concept/slas-how-work.html

Key Features of SLAs in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

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:

InPerformance Analytics (PA),long-term signalsarekey performance indicators (KPIs) that help organizations make data-driven decisions for sustained workflow stability. These KPIs providetrends over time, allowing businesses to analyze patterns, predict future performance, and optimize workflows for efficiency.

Track Trends Over Time→ Identify slow-moving changes and patterns.

Support Predictive Analysis→ Help in making data-driven strategic decisions.

Reduce Unplanned Changes→ Avoid reactive decisions by monitoringhistorical data.

Incident Backlog Over Time→ Measures incident accumulation to prevent delays.

Change Success Rate→ Analyzes how well changes are implemented without failures.

Mean Time to Resolution (MTTR)→ Tracks how long it takes to resolve incidents.

How Long-Term Signals Help in Workflow Stability:Example KPIs Used in Performance Analytics:

Why "A. Long-term signals" is Correct:Long-term signals provide historical trends that help organizations maintain stable workflows.

B. Non-signals→No such term exists in Performance Analytics.

C. Anti-signals→Not a recognized Performance Analytics term.

D. Stability signals→Misleading term; long-term signalsare what provide stability insights.

Why Other Options Are Incorrect:

ServiceNow Documentation:Performance Analytics Overview

CSA Exam Guide:Coverslong-term KPI tracking for workflow stability.

Reference from CSA Documentation:Thus, the correct answer is:

A. Long-term signals

InServiceNow, agroupis acollection of userswho share common responsibilities, such as handling incidents, approvals, or service requests.

Groups are stored in thesys_user_grouptable

Eachgroupis arecord in thesys_user_grouptable, which manages user access and permissions.

Example: The "Service Desk" group (sys_user_grouprecord) may contain multiple IT support users.

Groups are used for role assignments

Instead of assigning roles directly to users,roles are assigned to groupsfor easier access management.

Groups can be used for approvals and task assignments

Groups are often assigned to handleapproval workflows, incident resolution, and change management tasks.

A. A group is one record stored in the Group Type [sys_user_group_type] table(Incorrect)

Thesys_user_group_typetable is used for categorizing groups,not storing actual group records.

C. A group defines a set of users that share the same location(Incorrect)

Incorrect: Groups arenot location-based; they are used fortask assignments, approvals, and permissions.

D. A group defines a set of users that share the same job title(Incorrect)

Incorrect: Users with the same job titlemay belong to different groupsbased on their responsibilities.

Key Details About Groups in ServiceNow:Why Other Options Are Incorrect?

Groups in ServiceNow

Managing User Groups

User and Group Management

ServiceNow User and Group Administration

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

InServiceNow, administrators canreuse the same notification contentacross multiple channels (such asemail, SMS, and push notifications) by usingCommon Notification Content.

Consistency Across Channels

Ensures that the same message format is used acrossemail, SMS, and push notifications.

Easier Maintenance

Instead ofcreating separate contentfor each channel, administrators can manage all notification content from one place.

Dynamic Content

Supports variables and dynamic placeholders to customize messages based on recipient data.

A. Configure Default notification content

Incorrect: There is no "default notification content" feature in ServiceNow.

B. Enable Actionable notification content

Incorrect: Actionable notifications allow users totake actions directly from the notification, but they do not manage common content.

D. Set up Related notification content

Incorrect: No such feature as "Related notification content" exists in ServiceNow.

Key Features of Common Notification Content:Why Other Options Are Incorrect?

Common Notification Content Overview

ServiceNow Notification Management

Setting Up Common Notification Content

Creating Reusable Notification Content

References from ServiceNow CSA Documentation:

ABusiness Rulein ServiceNow is aserver-side scriptthat executes when records are inserted, updated, deleted, or queried in a specified table. Business Rules allow automation and customization of workflows by defining logic that runs under specific conditions.

Table (B) –Correct

ABusiness Rulemust be associated with aspecific tablewhere it will execute (e.g., Incident, Change, Task).

This determineswhich recordsthe rule applies to.

Script to Run (E) –Correct

A script must be provided when defining advanced logic in a Business Rule.

Business Rules useserver-side JavaScriptto perform various actions, such as setting field values, enforcing validation, or triggering workflows.

Timing (H) –Correct

The execution timing of a Business Rule determineswhenit runs relative to a database transaction.

Business Rules can run:

Before(before record is saved)

After(after record is saved)

Async(after the transaction completes)

Display(when a form loads)

Condition to Evaluate (I) –Correct

Conditions definewhen the Business Rule should executebased on specific criteria.

Example: A Business Rule might runonly when the priority is set to High.

A. UI Action(Incorrect)

UI Actions (buttons, links, context menus) are separate from Business Rules and are used for UI customization.

C. Fields to update(Incorrect)

While Business Rules can update fields,you do not specify "fields to update" as a required setting. Instead, updates are made via scripts within the rule.

D. Who can run(Incorrect)

Business Rulesalways run on the server-sideand do not require user-specific execution settings.

F. Application Scope(Incorrect)

Although Business Rules belong to an application scope, this isautomatically determinedbased on the current application.

G. Update Set(Incorrect)

Business Rules arecaptured in an Update Set, but this is not a configuration setting while creating the rule.

ServiceNow Business Rules Overview:https://docs.servicenow.com/bundle/utah-application-development/page/script/server-scripting/concept/business-rules.html

Creating Business Rules:https://docs.servicenow.com/en-US/bundle/utah-application-development/page/script/server-scripting/task/t_CreateABusinessRule.html

Key Elements to Specify When Creating a Business Rule:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

In ServiceNow, the"Service Desk > My Groups Work"module is designed to display tasks assigned to a groupbut not yet assigned to an individual user.This means that even if an IT manager oversees theNetworkandHardwareassignment groups, they will not see any tasks in this listif all tasks have already been assigned to specific individualswithin the group.

Let’s break down whyoption Ais the correct answer and why the other options are incorrect:

The"My Groups Work"list only shows tasks that are assigned to thegroupbut have not been assigned to a specificindividualwithin the group.

If all tasks are assigned to specificteam members, then the manager will not see any tasks in this list.

The IT manager can verify this by navigating to theTask List(e.g., Incidents, Changes, or Requests) and filtering by theNetworkandHardwareassignment groups.

Explanation for Correct Answer (A):

Theitil roleallows users toview, create, update, and resolve incidents, changes, problems, and other ITSM tasks.

However, not having this role wouldrestrict accessto various ITSM functionalities, but itdoes notimpact whether tasks appear inMy Groups Work.

If the manager lacks theitilrole, they might have trouble accessing or modifying tasks, but this wouldn't explain why they don’t see anything in the list.

TheService Desk groupis a separate entity in ServiceNow, typically associated with incident handling and user support.

TheMy Groups Workmodule isnot restricted to the Service Desk group—it displays work assigned toany groupthe user belongs to.

Since the manager is responsible for theNetwork and Hardwaregroups, being part of theService Deskgroup is irrelevant.

If the manager wasnot a memberof these groups, they wouldn't seeany group-related tasksat all.

However, the question states that the manager isresponsible for these groups, so it’s reasonable to assume they are either a member or at least agroup managerwith visibility.

Even if they were just a manager and not an officialgroup member, they would still be able to see the tasks assigned to the groups.

TheAssignment Group managerfield is an informational field that indicates who manages a group.

This fielddoes not controlwhat is displayed in theMy Groups Workmodule.

Even if this field were empty, it wouldn’t prevent a manager (who is a group member) from seeing unassigned tasks.

Explanation for Incorrect Answers:(B) The manager does not have the itil role.(C) The manager is not a member of the Service Desk group.(D) The manager is not a member of the Network and Hardware groups.(E) The Assignment Group manager field is empty.

ServiceNow CSA Guide - User Interface and Navigation

ServiceNow ITSM Fundamentals - Incident and Task Management

ServiceNow Role-Based Access Controls and Group Management

ServiceNow KB Articles - My Groups Work Module

References to Official Certified System Administrator (CSA) Documentation:

AUI Policyis the preferredno-codeapproach in ServiceNow to dynamically control themandatory, read-only, or visibilitystate of form fields based on specified conditions. Unlike Client Scripts, which require JavaScript coding, UI Policies provide aneasy-to-configure, rule-based solution.

They allow administrators tocontrol form behaviorwithout scripting.

They arefaster and more efficientthan Client Scripts.

Theyrun on the client-side, meaning changes occur dynamically as users interact with the form.

Defineconditions(e.g., "Priority is High").

Setactions(e.g., make "Due Date" mandatory, read-only, or hidden).

Apply the UI Policy to the form automatically when the condition is met.

A. UI Action→ UI Actions create buttons, links, or context menu items; they do not control form fields.

B. Client Script→ While Client Scripts can achieve similar functionality, they require JavaScript coding, making them alow-coderather than ano-codesolution.

C. UI Script→ UI Scripts are reusable JavaScript libraries, not designed for controlling form fields.

D. UI Rule→ No such feature exists in ServiceNow.

In computing and networking, aclientrefers to anapplication or system that accesses a remote service or another computer system (known as a server). The client-server model is a fundamental concept in computing, where:

A client sends requeststo a server.

The server processes the requestand sends back a response.

This architecture is widely used inweb applications, databases, and ServiceNowitself, whereclients interact with the ServiceNow platform (server) via a web browser or API requests.

In ServiceNow, theclienttypically refers toa user’s browser or an external system making requests via API calls.

Theserveris the ServiceNow instance, which processes requests and returns responses.

Client-side scripts(such asClient ScriptsorUI Policies) run on the user's browser, whileserver-side scripts(such as Business Rules and Script Includes) execute on the ServiceNow server.

How This Relates to ServiceNow:

A. Server→ A serverreceives requestsand processes them but is not the requesting entity.

C. Script→ A script is apiece of codethat executes certain actions but does not represent an entire system accessing a service.

D. Policies→ Policies definerules or behaviors(e.g., UI Policies, Data Policies) but do not access a remote service.

Why Other Options Are Incorrect:

ServiceNow Documentation:Client and Server in ServiceNow

CSA Exam Guide:CoversClient and Server architecturein ServiceNow.

Reference from CSA Documentation:

Coalescing is a crucial concept in ServiceNow's data import process. When a set of fields are marked as "coalesce" in aTransform Map, they act as unique identifiers to determine if an existing record should be updated rather than creating a new one.

If a match is found based on the coalesce field(s):

The system updates the existing record with the new data from the import.

If no match is found:

A new record is created.

How Coalescing Works in ServiceNow Imports:This means that coalescing helps maintain data integrity by preventing duplicate records while ensuring existing records receive updates when necessary.

When a record in the target table matches the value(s) in the coalesce field(s),ServiceNow updates that existing recordinstead of creating a new one.

This ensures that data is synchronized correctly rather than creating duplicate entries.

Option B (Incorrect):"If a match is not found using the coalesce fields, the system does not create a Transform Map."

The Transform Map isalways createdbefore the import process even starts. The presence or absence of a match has no impact on the Transform Map itself.

Option C (Incorrect):"If a match is found using the coalesce fields, the system creates a new record."

If a match is found, the existing record is updated,not replaced or duplicated.

Option D (Incorrect):"If a match is not found using the coalesce fields, the existing record is updated with the information being imported."

If a match isnotfound, anew recordis created, not an update to an existing one.

Why is Option A Correct?Why Are the Other Options Incorrect?

ServiceNow CSA Official Documentation on Data Import & Transform Maps:

ServiceNow Docs - Transform Maps

"If a field is coalesced, the system checks for matching records before inserting new ones. If a match is found, the existing record is updated; if no match is found, a new record is created."

Reference from Certified System Administrator (CSA) Documentation:

Conclusion:The correct answer isA. If a match is found using the coalesce fields, the existing record is updated with the information being imported.

????Understanding coalescingis vital for any ServiceNow administrator to ensure data integrity, avoid duplicates, and maintain system efficiency when handling data imports.

n ServiceNow, theList Editorallows users to edit field values directly within a list without opening the record in a form. This feature is particularly useful for making quick modifications to multiple records without the need to open each one individually.

Users navigate to a list view of records (e.g., an incident list).

If a field is editable via the List Editor, clicking on it will allow inline editing.

After making changes, users can pressEnteror click outside the field to save.

Inline Editing:Users can modify fields directly from the list.

Multi-Row Editing:Certain fields support bulk updates.

Security Controls:Admins can control which fields are editable via List Editor through dictionary settings.

Audit and History Tracking:Changes made via List Editor are logged for tracking purposes.

A. Data Editor:No such term as "Data Editor" exists in ServiceNow.

B. Edit Menu:This does not refer to inline editing; instead, it's a general menu for editing options.

D. Form Designer:Used for configuring form layouts, not for inline editing.

ServiceNow Product Documentation → Lists and List Editing

ServiceNow CSA Exam Guide → Covers List Editor as a core feature of instance configuration.

How List Editor Works:Key Features of List Editor:Why Other Options Are Incorrect:Reference from CSA Documentation:This verifies thatList Editoris the correct answer.

InServiceNow Flow Designer, aTriggeris used toinitiateaflow. Triggers define the conditions under which a flow starts and can be based on various system events, schedules, or user actions.

(A) A Trigger – Correct

Triggers are the starting point of a flowin Flow Designer.

A flow will not execute unless a trigger condition is met.

Types of triggers include:

Record-based triggers(e.g., when a record is created, updated, or deleted)

Scheduled triggers(e.g., run at a specific time or interval)

Application-specific triggers(e.g., Service Catalog request submission)

(B) Core Action – Incorrect

Core Actionsare predefined actions that execute tasks within a flow, such as:

Sending notifications

Updating records

Calling APIs

They aresteps within a flow,notwhat initiates it.

(C) A Spoke – Incorrect

A spokein Flow Designer is a collection of actions and subflows related to a specific application or integration (e.g., ServiceNow ITSM Spoke).

Spokescontain actionsbut donotinitiate flows.

(D) An Event – Incorrect

Eventsin ServiceNow trigger Business Rules, Notifications, and Script Actions, but they arenot directly used to initiate flowsin Flow Designer.

However, aflow can be triggered based on an event, but the event itself is not the trigger—the flow’s trigger is configured to listen for the event.

Explanation of Each Option:

Triggers should be well-definedto prevent unnecessary flow executions that might impact performance.

Use Scheduled Triggersfor time-based workflows (e.g., daily reports).

Record Triggersare commonly used for automation within ITSM processes.

Debugging Triggers: Use theFlow Execution Detailspage to troubleshoot trigger execution.

Additional Notes & Best Practices:

ServiceNow Docs: Flow Designer Triggers

https://docs.servicenow.com

ServiceNow Community: Best Practices for Flow Designer Triggers

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,Favoritesallow users to quickly accessapplication menus and modulesthat they frequently use. By marking an application menu or module as a favorite, it appears under theFavorites tab in the Application Navigator, making navigation faster and more efficient.

(A) Breadcrumb – Incorrect

Breadcrumbs in ServiceNow show thenavigation pathwithin a list view or form.

They help users filter data quickly but donotstore shortcuts for quick access.

(B) Favorite – Correct

TheFavorite featurein ServiceNow allows users to save frequently used menus and modules for quick access.

Users canadd, remove, and reorderfavorites for better personalization.

Located in theApplication Navigator, favorites appear at the top for easy access.

Favorites can include forms, records, reports, or dashboards.

(C) Tag – Incorrect

Tagsare used toorganize and categorize records(e.g., incidents, problems, change requests).

Tags help users group related records but donotcreate direct menu shortcuts.

(D) Bookmark – Incorrect

ServiceNow doesnotuse the term "Bookmark" for quick access to menus and modules.

While users can bookmark URLs in a web browser, this is different from ServiceNow’s built-inFavoritesfeature.

Explanation of Each Option:

Users cancustomize Favoritesby renaming them or selecting an icon for better visibility.

Admins canpre-configure favoritesfor users based on roles to improve productivity.

Favorites improveuser efficiencyby reducing the number of clicks needed to reach frequently used items.

ServiceNow Docs: Using Favorites in the Application Navigator

https://docs.servicenow.com

ServiceNow Community: Personalizing the Application Navigator with Favorites

https://community.servicenow.com

Additional Notes & Best Practices:References from Certified System Administrator (CSA) Documentation:

ServiceNow follows asingle-instance, single-tenant architecture,nota multiple-tenant architecture. This means:

Single-Instance:

Each ServiceNow instance is aunique, independent environmentfor a customer.

All customers have their own dedicated instance with their owncustom configurations, data, workflows, and applications.

ServiceNow instances are hosted in amulti-instance cloud modelrather than a multi-tenant model.

Single-Tenant Model (Multi-Instance Architecture):

Unlikemulti-tenant architectures(where multiple customers share the same application and database), ServiceNow provideseach customer with a separate, isolated instance.

Thisensures data security, performance isolation, and customization flexibility.

Each instance has its owndata storage, configuration, and upgrade schedule, reducing risks associated with shared environments.

Why ServiceNow Uses Multi-Instance Instead of Multi-Tenant:

Security & Data Isolation:Since each customer has an independent instance, there isno risk of data leakagebetween tenants.

Customization & Flexibility:Customers cancustomizetheir instance freely without affecting others.

Performance & Scalability:Each instance can bescaled independently, ensuring optimal performance.

ServiceNow does NOT use a multiple-tenant architecture.

ServiceNow follows a single-instance, single-tenant (multi-instance) model.

Each customer has a dedicated instance with isolated resources and configurations.

A multi-tenant architecturemeans multiple customerssharethe same application/database with logical separation, which is NOT the case in ServiceNow.

ServiceNow instead provides separate instancesfor each customer, meaning it isnota true multi-tenant system.

ServiceNow Product Documentation – Multi-Instance Cloud Modelhttps://docs.servicenow.com

ServiceNow Community – Single-Tenant vs. Multi-Tenant Explained

ServiceNow Best Practices – Security & Instance Architecture

Why Option B (False) Is Correct?Why Option A (True) Is Incorrect?References from Certified System Administrator (CSA) Documentation:

InServiceNow Role Management, aroleis a collection ofpermissionsthat control what users can see and do within the platform.

Role Hierarchy (Role Inheritance)

Rolescan contain other roles(known asnested roles).

When a user is assigned aparent role, theyinherit all child roleswithin it.

Example:

TheITIL roleincludesincident_managerandproblem_managerroles.

AssigningITILto a userautomatically grants them all the permissions of the included roles.

Roles Are Assigned by Administrators

Typically, roles are assigned by aSystem Administratoror an authorized user.

Role-Based Access Control (RBAC)

ServiceNow usesRBACto control access to applications, records, and actions.

B. Users can click on the Personalize Role feature to try different roles

Incorrectbecause userscannot manually switch rolesunless they have theimpersonation privilege.

C. A role is granted to a user by the System Administrator

Partially correct, butnot the best answerbecause rolescan also be assigned via groupsor automated processes, not just by a System Administrator.

D. Each user has a role in the ServiceNow platform

Incorrectbecause not all usersmust have a role.

Example:A self-service user can access the systemwithouthaving any specific role.

ServiceNow Docs: Role-Based Access Control (RBAC)https://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/roles/reference/r_RBAC.html

ServiceNow CSA Official Training Guide (User & Role Management)

Key Characteristics of Role Assignment:Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatroles can contain other roles, and when a user is assigned a role, they inherit all roles within it.

InServiceNow, the best practice for managingusers, groups, and rolesis based onrole-based access control (RBAC).

Assign Roles to Groups (Correct)

Instead of assigning roles directly to users, it is abest practice to assign roles to groups.

This ensuresbetter role management, easier administration, and scalability.

Example:

The"IT Support"group has the"itil"role.

All users in this group automatically get theitilrole.

Add Users to Groups (Correct)

Users should be assigned togroupsrather thanroles directly.

Groups inherit roles, so when a user is added to a group, they automatically receivethe appropriate access.

Example:

A new Service Desk agent joins the"Service Desk"group and immediately gets the associated roles (itil,incident_manager, etc.).

A. You should never assign roles to groups(Incorrect)

Incorrect: Assigning roles to groups is therecommended best practice.

Managing roles at thegroup levelmakesaccess control more efficient and scalable.

B. You should assign roles to users(Incorrect)

Incorrect: Assigning roles directly to users isnot a best practicebecause it becomes difficult to manage as the organization grows.

Instead, users should beadded to groupsthat have the necessary roles.

Best Practices for Users, Groups, and Roles:Why Other Options Are Incorrect?

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

References from ServiceNow CSA Documentation:

InServiceNow, anImport Set Tableis atemporary staging areawhere raw data is storedbefore it is transformed and moved into a target table. It is primarily used indata import processesto ensure data integrity and allow transformation before committing data to production tables.

Stores incoming data from external sources(e.g., CSV files, Excel files, APIs, LDAP, etc.).

Acts as a temporary staging areabefore records are mapped and transformed into atarget table(e.g.,incident,cmdb_ci,problem).

Allows validation and error handlingbefore final data migration.

Uses Transform Mapsto determine how fields in the import set relate to fields in the target table.

Key Functions of an Import Set Table:

Data is importedinto anImport Set Tablefrom an external source.

TheImport Set Table temporarily stores the datawithout affecting existing records.

ATransform Mapis applied to move and modify the data before inserting it into the correct table.

Once transformation is complete, the data is transferred to thetarget table, and the Import Set Table can be cleared.

Example Workflow of an Import Set:

(A) A table where data will be placed, post-transformation – Incorrect

Thetarget table(e.g.,incident,cmdb_ci,problem) holds the dataaftertransformation.

TheImport Set Table is only a temporary staging areabefore transformation occurs.

(B) A table that determines relationships – Incorrect

Relationship tables(e.g.,cmdb_rel_ci) definedependencies between recordsbut are not used for data import.

Import Set Tables do not determine relationships between records.

(C) A staging area for imported records – Correct

Import Set Tables temporarily store incoming recordsbefore processing.

The data is transformed and mappedbefore being inserted into the final target table.

This ensuresdata integrity and consistency.

(D) A repository for Update Set information – Incorrect

Update Sets (sys_update_set) store changes to configurations, such as scripts, workflows, and UI policies.

Import Set Tables are used for data imports, not Update Sets.

Explanation of Each Option:

Always review data in the Import Set Table before applying transformationsto avoid incorrect data entry.

Use Transform Mapsto define field mappings between Import Set Tables and target tables.

Monitor Import Logs(sys_import_set_run) for errors or incomplete data.

Delete old Import Set dataperiodically to improve performance and avoid unnecessary storage usage.

Additional Notes & Best Practices:

ServiceNow Docs: Import Set Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for Import Set Management

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), which can includeboth tangible and intangible business assets.

Tangible assets: Physical devices like servers, network components, and workstations.

Intangible assets: Software, applications, cloud services, licenses, and business services.

Relationships and Dependencies: CMDB maintains the relationships between CIs to help with impact analysis, change management, and troubleshooting.

What is Stored in the CMDB?CMDB plays a crucial role inIT Service Management (ITSM), ensuring that organizations haveaccurate and up-to-dateasset data for better decision-making.

(A) The CMDB contains data about tangible and intangible business assets – Correct

TheCMDB tracks and manages both physical (tangible) and virtual (intangible) assets.

Examples oftangible assets: Servers, routers, desktops, mobile devices.

Examples ofintangible assets: Cloud services, software applications, business services.

(B) The CMDB contains the Business Rules that direct the intangible, configurable assets used by a company – Incorrect

Business Rules are not stored in the CMDB.

Business Rules in ServiceNow are part of the platform’s automation framework and control system behavior but donotdefine configuration items.

(C) The CMDB archives all Service Management PaaS equipment metadata and usage statistics – Incorrect

TheCMDB does not function as an archive; it maintains real-time, active data about CIs.

Usage statistics are stored in performance analytics and reporting tools, not in the CMDB.

(D) The CMDB contains ITIL process data pertaining to configuration items – Incorrect

While CMDBsupports ITIL processes, it doesnot store ITIL process datadirectly.

ITIL process data (e.g., incident, problem, change records) is stored inITSM modules, not in the CMDB itself.

CMDBdoes contain CI relationshipsthatsupportITIL processes likeIncident, Problem, and Change Management.

Explanation of Each Option:

CI Classes & Hierarchy: ServiceNow CMDB uses a hierarchical structure with variousCI Classes(e.g.,cmdb_ci,cmdb_ci_server,cmdb_ci_database).

CMDB Health Dashboard: Ensures data accuracy withcompleteness, compliance, and correctnessmetrics.

Relationship Management: CIs in the CMDB are linked to show dependencies, which iscrucial for impact analysisin change and incident management.

Discovery & Service Mapping: ServiceNow’sDiscovery and Service Mappingtools helpautomate CI data collection.

Additional Notes & Best Practices:

ServiceNow Docs: CMDB Overview

https://docs.servicenow.com

ServiceNow Community: Best Practices for CMDB Data Accuracy

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

ARelated Listin ServiceNow is used to display records from other tables that are related to the current record. It helps users view and manage associated records without navigating away from the main record they are working on.

Related Lists appear at the bottom of a form view.

They display records from tables that have a relationship (via reference fields, many-to-many relationships, or database joins) with the current table.

Users can add, remove, or modify related records directly from the Related List, depending on their permissions.

Key Features of Related Lists:Why "D. To present related records" is the correct answer?Related Lists show records from another table that have a relationship with the current record. For example:

AnIncidentrecord may have a Related List showing allTasksassociated with it.

AUserrecord may have a Related List displayingGroup Memberships.

AChange Requestrecord may have a Related List displaying all relatedCI (Configuration Items).

Option A: "To create a one-to-many relationship"– Incorrect. While Related Lists often display one-to-many relationships, they do not create them. Relationships are defined throughreference fields,many-to-many tables, ordatabase joins.

Option B: "To dot-walk to a core table"– Incorrect. Dot-walking allows users to access related fields from referenced records, but it is not the purpose of a Related List.

Option C: "To present related fields"– Incorrect. Related Lists display related records, not just individual fields. Related fields can be accessed using dot-walking or reference fields but are not the same as Related Lists.

ServiceNow Product Documentation - Related Lists

ServiceNow CSA Study Guide - Configuring Forms and Lists

ServiceNow Docs: Relationships in Tables

Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

In ServiceNow, every table has a uniqueplatform name(also known as thedatabase nameorsys_id). The table that stores user records in ServiceNow is called"sys_user".

Table Name:sys_user

Purpose:Stores user records, including their roles, group memberships, and personal details.

Location in ServiceNow:You can access this table by navigating to:All → Users and Groups → Users

Key Fields in sys_user Table:

User ID (user_name)– Unique identifier for the user.

Name (name)– Full name of the user.

Email (email)– Email address of the user.

Roles (roles)– Defines user permissions in the system.

Active (active)– Indicates if the user is active in the system.

A. u_users– Incorrect. The prefixu_is typically used forcustom tablescreated by administrators. This is not a default system table.

B. sys_users– Incorrect. The correct name issys_user(singular), notsys_users. ServiceNow follows a singular naming convention for system tables.

C. x_users– Incorrect. The prefixx_is reserved forScoped Applicationscreated within an instance. The User table is a core system table, not a scoped one.

ServiceNow Product Documentation → User Administration → sys_user Table

ServiceNow Tables Reference → sys_user

ServiceNow CSA Study Guide → User and Data Administration

Understanding the sys_user Table:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

In ServiceNow, knowledge articles can bemarked for reviewusing the"Flag article"feature. This allows users toindicate issuessuch as outdated content, incorrect information, or necessary updates.

Users can flag an articleif they believe it needs review or corrections.

The flagged article appears in theKnowledge Management Dashboard, where knowledge managers can track flagged articles.

Knowledge managers or owners canreview flagged articlesand make necessary updates or retire them if needed.

How the "Flag Article" Feature Works:

B. Review→ No such option exists in ServiceNow for marking an article for review. However, knowledge managers can schedule article reviews manually.

C. Bookmark→ Used tosavefrequently accessed articles for personal reference but does not indicate that the article needs a review.

D. On Hold→ Applies to workflows or approvals but is not a method for marking an article for review.

Why Other Options Are Incorrect:

ServiceNow Documentation:Flagging a Knowledge Article

CSA Exam Guide:Covers theFlag Articlefunction as a key feature in Knowledge Management.

Reference from CSA Documentation:Thus, the correct answer is:

A. Flag article

InServiceNow Knowledge Management, knowledge articles must be in a specificstatebefore they can be visible to end users. The correct state that allows users to view the article isPublished.

Understanding Knowledge Article StatesKnowledge articles in ServiceNow go through alifecyclethat includes the following states:

Draft– The article is being created or edited and isnot visibleto end users.

Review– The article is under internal review by approvers before publication. It remainshiddenfrom users.

Published– The article isapproved and publicly availableto users who have access to the Knowledge Base.

Retired– The article is no longer relevant or has been replaced. It isnot visibleto end users.

OnlyPublishedarticles appear in the Knowledge Base and can be accessed by users.

Articles inDraft, Review, or Retiredstates arenot visibleto the general audience.

B. Drafted– Articles inDraftare still being written or edited andcannot be accessed by users.

C. Retired– Retired articles are considered obsolete and areno longer displayedin the Knowledge Base.

D. Reviewed– Articles inRevieware under approval butare not yet visibleto users.

ServiceNow Docs: Knowledge Article Stateshttps://docs.servicenow.com/en-US/bundle/utah-servicenow-platform/page/product/knowledge-management/concept/knowledge-article-states.html

ServiceNow CSA Official Training Guide (Knowledge Management Lifecycle & Publishing Workflow)

Why is "Published" the Correct Answer?Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms that aknowledge article must be in the "Published" stateto be visible to users in the Knowledge Base.

In ServiceNow,all tablesin the database are recorded in amaster tablecalled[sys_db_object]. This table stores metadata about each table in the system, including itsname, label, and other attributes.

Stores a record for every table in the ServiceNow instance.

Tracks essential table properties, such as thetable name, label, and whether it is an extension of another table.

Helps administratorsview, modify, or create new tablesin ServiceNow.

Used inTable Administration and Custom Table Development.

A. [sys_master_db]–

This tabledoes not existin ServiceNow.

C. [sys_master_object]–

There is no such table named "sys_master_object" in ServiceNow.

D. [sys_object_db]–

This tabledoes not existin ServiceNow.

The correct name issys_db_object.

Navigate toSystem Definition→Tables.

Search for the tablesys_db_object.

Open the table to see records representing all tables in the instance.

ServiceNow Docs: Understanding Tables and Fieldshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/metadata/concept/c_TablesAndFields.html

ServiceNow CSA Official Training Guide (System Data and Tables Overview)

Key Functions of [sys_db_object]:Why the Other Options Are Incorrect?How to View the [sys_db_object] Table in ServiceNow?References from Certified System Administrator (CSA) Documentation:This confirms that[sys_db_object]is themaster tablethat contains a record for every table in the ServiceNow database.

InServiceNow,Client Scriptsare used to execute JavaScript codeon the client-side (browser)to control form behavior, validate data, or enhance user interaction.

Types of Client Scripts in ServiceNow:There arefourtypes of Client Scripts supported in ServiceNow:

onLoad (Option D)

Runswhen a form loads.

Used to pre-fill fields, hide/show elements, or set default values.

Example: Automatically setting the "Priority" field toHighwhen a new incident is created.

onChange (Option F)

Runswhen a specific field value changes.

Used for dynamic form behavior, such as making fields mandatory based on another field's value.

Example: If "Category" is changed to "Hardware," then show the "Hardware Type" field.

onSubmit (Option A)

Runswhen the form is submitted.

Used for final validation before allowing submission.

Example: Preventing submission if a mandatory field is left empty.

onCellEdit (Option C)

Runswhen a cell value is edited inline in a list view.

Used to trigger immediate validation or updates without opening the full form.

Example: Displaying an alert when a user directly changes an incident's priority from a list view.

Why Are the Other Options Incorrect?B. onUpdate

No "onUpdate" client script type exists in ServiceNow.

"onUpdate" is relevant inBusiness Rules, not Client Scripts.

E. onEdit

No "onEdit" client script type exists.

Similar functionality can be achieved with "onChange" or "onCellEdit" scripts.

G. onSave

No "onSave" client script type exists.

"onSubmit" handles validation before saving a record.

Reference from Certified System Administrator (CSA) Documentation:????ServiceNow Docs – Client Scripts

????ServiceNow Client Scripts Documentation

"Client Scripts can beonLoad, onChange, onSubmit, or onCellEditdepending on when they execute."

Conclusion:The correct answers are:

A. onSubmit(Runs when submitting a form)

C. onCellEdit(Runs when editing a list cell)

D. onLoad(Runs when a form loads)

F. onChange(Runs when a field value changes)

AService Catalog workflowin ServiceNow is a structured sequence of automated activities designed to manage and fulfill catalog requests. These workflows are essential in handlingapprovals, tasks, notifications, and process automationfor requests submitted through theService Catalog.

Drives Complex Fulfillment Processes:

When a user submits a catalog request, the workflow determines how it should be processed.

It automates the required steps, such asapprovals, task assignments, and record updates.

Different items in the catalog may require different workflows based on the request type.

Sends Notifications to Defined Users or Groups:

Service Catalog workflows includeemail and in-platform notificationsto keep users informed.

Notifications can be triggered at different stages, such as request submission, approval, fulfillment, and closure.

Example:If an item requires managerial approval, the workflow sends an approval request notification to the designated approver.

Approval and Task Automation:

Workflows can createapproval stepsfor request items before they proceed to fulfillment.

They can also generatetasksfor fulfillment teams based on predefined conditions.

Integration with Flow Designer and Other Automation Tools:

In newer ServiceNow versions,Flow Designeris often used instead of traditional workflows, but the core purpose remains the same.

Workflows can integrate withSLA (Service Level Agreements), script actions, and record updates.

Key Functions of a Service Catalog Workflow:Why Option C is Correct?"Drives complex fulfillment processes"→ Correct, as workflows automate and manage Service Catalog request fulfillment.

"Sends notifications to defined users or groups"→ Correct, since notifications are an integral part of ServiceNow workflows.

Why Other Options Are Incorrect?Option A:Incorrect – While workflows include tasks and approvals, they do not "generate item variable types." Variables are defined within catalog items, not workflows.

Option B:Incorrect – Workflowscan send notifications, making this statement false.

Option D:Incorrect – Similar to Option A, workflows do not generate "item variable types." Instead, they focus on fulfillment processes and notifications.

ServiceNow Product Documentation – Service Catalog Workflowshttps://docs.servicenow.com

ServiceNow Learning – Service Catalog and Workflow Automation

ServiceNow Developer Portal – Flow Designer & Workflow Automation

References from Certified System Administrator (CSA) Documentation:

In ServiceNow, ataskis a record that represents work that needs to be completed. It follows a lifecycle where it is:

Created– A task is generated, either manually or automatically (e.g., an incident, change request, or problem record).

Worked Upon– Users perform necessary actions, update statuses, and progress the task towards resolution.

Closed– Once completed, the task reaches a closed state, indicating that no further action is needed.

Tasks in ServiceNow are derived from theTask [task]table.

Common task-based records includeIncidents, Change Requests, Problems, and Service Requests.

Tasks follow a defined workflow and state transitions (e.g., New → Work in Progress → Resolved → Closed).

Key Features of a Task:

A. Report:

A report is a visualization of data and does not follow a lifecycle involving work or closure.

B. Workflow:

A workflow definesprocess automationand the movement of tasks, but it is not something that gets "worked upon" directly like a task.

C. Event:

Events are system-generated triggers that notify or automate actions, but they do not have a structured lifecycle like a task.

Why Other Options Are Incorrect:

ServiceNow Documentation:Task Management in ServiceNow

CSA Exam Guide:Coverstask recordsas fundamental entities that go through a lifecycle.

Reference from CSA Documentation:Thus, the correct answer isD. Task.

In ServiceNow, administrators can check whichrelease versionis running on an instance by navigating to theStats module. This module provides various system statistics, including the current release name, build number, and other important system details.

Navigate toSystem Diagnostics→Stats(or simply type “Stats” in the navigation filter).

Scroll down to find theBuild nameandVersionfields.

The displayed version follows the standard ServiceNow naming convention (e.g., "Washington DC Patch 2 Hotfix 1").

How to Check the Release Version via Stats Module:

A. Memory Stats module:

This module provides memory consumption details and performance-related information, but it does not show the instance version.

C. System.upgraded table:

While this table records upgrade history and past version changes, it does not display the current version running on the instance.

D. Transactions log:

This log captures user activities and system transactions but does not provide release version details.

Why Other Options Are Incorrect:

ServiceNow Documentation:View system version details

Certified System Administrator (CSA) Study Guide: CoversSystem Diagnostics → Stats Moduleas a key method to verify the running release version.

Reference from CSA Documentation:

Thesix methods available for user authenticationin ServiceNow are:

Local Database– The user authenticates using a username and password stored in theinstance database.

Multifactor Authentication (MFA)– The user provides their username, password, and apasscode(e.g., from Google Authenticator).

LDAP (Lightweight Directory Access Protocol)– The user authenticates using credentials stored in a corporateLDAP directory.

SAML 2.0 (Security Assertion Markup Language)– The user is authenticated via an externalSAML Identity Provider (IdP).

OAuth 2.0– The user authenticates via anOAuth identity provider(such as Google, Microsoft, or Facebook).

Digest Token Authentication– The user authenticates using anencrypted tokenrather than directly submitting a password.

Thus, the correct answer is:

A, B, C, D, E, F

ServiceNow supports multiple authentication methods to provideflexibility, security, and integration capabilitieswith external identity providers.

Local Database Authentication:

ServiceNow storesusernames and passwordsin the internal database.

Users authenticate directly with the instance.

This method is commonly used when no external authentication provider is configured.

Multifactor Authentication (MFA):

Enhances security by requiringtwo authentication factors:

Username and password(stored in the database).

Passcodefrom a registered device (such as Google Authenticator, Microsoft Authenticator).

MFA helpsprevent unauthorized accesseven if credentials are compromised.

LDAP Authentication:

Allows users toauthenticate against an external LDAP directory(such as Microsoft Active Directory).

The user must have amatching record in the ServiceNow user table ([sys_user]).

ServiceNowdoes not store passwordswhen using LDAP; it only validates credentials against the directory.

SAML 2.0 Authentication:

Users authenticate via aSAML Identity Provider (IdP)such asOkta, Microsoft Azure AD, or Ping Identity.

ServiceNow acts as aService Provider (SP)and does not store passwords.

ProvidesSingle Sign-On (SSO)capabilities.

OAuth 2.0 Authentication:

Allows authentication viaOAuth providers(Google, Facebook, Microsoft, etc.).

Users do not need to store passwords in ServiceNow; instead, authentication is delegated to theOAuth identity provider.

Digest Token Authentication:

Uses anencrypted token(instead of a plaintext password) to authenticate users.

Often used forAPI-based authenticationor scenarios where passwords should not be transmitted over the network.

Each method aligns with ServiceNow's authentication mechanisms as per official documentation.

ServiceNow supports a hybrid authentication approach, allowing multiple methods to coexist.

ServiceNow Docs – Authentication Methodshttps://docs.servicenow.com

ServiceNow Security Best Practices – Authentication & Access Controls

ServiceNow Developer Portal – SSO & OAuth Authentication

Why These Are the Correct Methods?References from Certified System Administrator (CSA) Documentation:

When a user places an order for an item or service from theService Catalogin ServiceNow, the system generates aRequest (REQ). This is a core component ofRequest Managementwithin the IT Service Management (ITSM) module.

User Places an Order:

The user selects an item from theService Catalog(e.g., a laptop, software, or an access request).

The order may consist of multiple items, depending on the selection.

ServiceNow Generates a Request (REQ):

ThisRequest (REQ#)acts as the umbrella record that tracks the order as a whole.

It is stored in thesc_requesttable.

Creation of Requested Items (RITM#):

Each item within the request generates aRequested Item (RITM#), stored in thesc_req_itemtable.

For example, if the user orders a laptop and a software license, two RITM records are created under the same Request.

Tasks (SCTASK#) Are Created:

Each Requested Item (RITM) may trigger one or moreCatalog Tasks (SCTASK#)in thesc_tasktable.

These tasks define the steps required to fulfill the request (e.g., procurement, approval, and configuration).

A. A Change Request– Incorrect. AChange Request (CHG#)is created only if the requested item involves changes to the infrastructure, such as a server upgrade. Not all catalog items require a change request.

B. An Order Guide– Incorrect. AnOrder Guideis a tool within the Service Catalog that helps users order multiple related items at once. However, it does not get generated when an order is placed.

D. An SLA– Incorrect. AService Level Agreement (SLA)may be associated with the request or tasks, but it is not automatically generated when a request is placed.

ServiceNow Product Documentation → Service Catalog → Request Fulfillment

ServiceNow CSA Study Guide → Service Catalog and Request Management

ServiceNow Tables Reference → sc_request, sc_req_item, sc_task

Understanding the Request Process in ServiceNow:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

ServiceNow supports multiple authentication methods to verify user identities before granting access to an instance. The three valid authentication methods from the given options are:

Local Database Authentication

This is the default authentication method used in ServiceNow.

User credentials (username and password) are stored in the ServiceNow database.

Authentication is handled directly by ServiceNow without relying on external identity providers.

This is useful for small implementations or instances where external authentication is not required.

LDAP (Lightweight Directory Access Protocol)

LDAP allows ServiceNow to integrate withcorporate directory services, such as Microsoft Active Directory, to authenticate users.

Users authenticate using theircorporate credentials, reducing the need to maintain separate user accounts in ServiceNow.

ServiceNow connects to an LDAP server and verifies credentials without storing passwords in the ServiceNow database.

SSO (Single Sign-On)

Single Sign-On enables users to log into ServiceNow using an external identity provider (IdP).

ServiceNow supports various SSO protocols, including:

SAML 2.0 (Security Assertion Markup Language)

OAuth 2.0

OpenID Connect

Kerberos

This allows users to authenticate once and gain access to multiple applications, improving security and user experience.

A. XML feed–

XML feeds are used for data exchange,not authentication.

ServiceNow can consume XML feeds for integrations but does not use XML feeds to authenticate users.

E. FTP authentication–

FTP (File Transfer Protocol) is used for transferring files between systems and isnot a valid authentication methodin ServiceNow.

ServiceNow Docs: User Authentication Methodshttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/security/concept/user-authentication-methods.html

ServiceNow CSA Official Training Guide (User Authentication & Security)

Why the Other Options Are Incorrect?References from Certified System Administrator (CSA) Documentation:These references confirm thatLocal Database, LDAP, and SSOare valid authentication methods in ServiceNow.

InServiceNow,UI Policiesallow administrators todynamically control form fieldsbased on conditions without using scripts. With UI Policies, you can change thebehaviorof a field by making it:

Read-only→ The user canviewthe field butcannot edit it.

Mandatory→ The field becomesrequired, and the usermustfill it out before submitting the form.

Hidden→ The field isremoved from visibilityon the form.

Explanation of Each Option:A. Read-only–Correct

A UI Policy can make a fieldread-only, meaning users canseethe field butcannot modifyits value.

Example: A field likeRequest Number (REQ0001)is typicallyread-onlyafter submission.

B. Write-only–Incorrect

ServiceNowdoes nothave a "write-only" field setting in UI Policies.

If a field iseditable, users canboth read and write; if it’s hidden or read-only, writing is not possible.

C. Necessary–Incorrect

There isno "Necessary"field state in ServiceNow UI Policies.

If the intent is to make a field required, the correct term is"Mandatory".

D. Mandatory–Correct

UI Policies can make a fieldmandatory, requiring the user toenter a valuebefore submitting the form.

Example: AnIncident Descriptionfield might be mandatory before an incident is submitted.

E. Empty–Incorrect

UI Policiescannot directly enforce an "empty" state. However, adefault valuecould be cleared using aclient script, but this isnot a UI Policy feature.

F. Hidden–Correct

UI Policies canhide a field, making it invisible on the form.

Example: A"Manager Approval"field may be hiddenuntila certain condition (e.g., request cost > $1000) is met.

Final Answer:Read-only

Mandatory

Hidden

ServiceNow Docs – UI Policies and UI Policy Actionshttps://docs.servicenow.com

ServiceNow Learning – Form Configuration & UI Policies

ServiceNow Developer Portal – Controlling Form Behavior with UI Policies

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Access Control rules (ACLs)are used torestrict or grant accessto data. Each Access Control rule consists of:

Table-level (Row-Level) ACLs– Control access to the entire record (row).

Field-level ACLs– Control access to specific fields within a record.

Access Control rules are evaluated in a specific orderto determine whether a user has the necessary permissions to perform an action (Read, Write, Create, Delete, etc.).

If both a row-level and a field-level ACL exist for the same table, BOTH must evaluate to "true"before access is granted.

The system checks conditions, scripts, and roles defined in the ACLsto decide whether the user meets the access requirements.

Access Control Rule Evaluation Process:Why is Option C Correct?If both a row-level rule and a field-level rule exist, both must evaluate to "true" for a user to perform an action.

Row-Level ACLscheck if a user can access the record itself.

Field-Level ACLscheck if a user can access specific fields within that record.

If a user failseitherACL check, access is denied.

Why Are the Other Options Incorrect?A. "Rules are evaluated using roles. The role with the most permissions evaluates the rules first."

Access Control rulesare not evaluated based on roles with the most permissions.

Roles are just one factorin ACL evaluation, along with conditions and scripts.

B. "If more than one rule applies to a row, the older rule is evaluated first."

ServiceNow does not prioritize ACL rules based on their creation date.

Instead, ACLs follow a structured evaluation order (general-to-specific).

D. "Rules are evaluated from the general to the specific, so a table rule must be active to continue."

This is partially true but misleading.

ServiceNow evaluates ACLs fromspecific to general(Field → Table).

However,a table-level rule does NOT need to be activefor a field-level ACL to be evaluated.

Reference from Certified System Administrator (CSA) Documentation:????ServiceNow Docs – Access Control Rules (ACLs) Evaluation

????ServiceNow ACL Evaluation Documentation

"If a field-level rule and a row-level rule exist,both must evaluate to truefor the operation to be allowed."

Conclusion:The correct answer isC. If a row-level rule and a field-level rule exist, both rules must be true before an operation is allowed.

????Understanding ACL rule evaluation is critical for managing security in ServiceNow, ensuring that users have the appropriate access while maintaining data integrity.

InServiceNow,Rolesare used to control access toApplications and Moduleswithin the platform. ARoleis a set of permissions that define what actions a user can perform and which records they can access.

Grant Access to Applications and Modules:

If a userdoes not have the required role, theycannot see or accessan application/module.

Control Record-Level and Field-Level Access:

SomeAccess Control Rules (ACLs)depend on roles topermit or restrictdata visibility.

Assign Multiple Roles to a User:

A user can havemultiple rolesbased on job responsibilities.

Example Roles in ServiceNow:

admin– Full access to all system features.

itil– Can manage incidents, problems, and changes.

catalog_admin– Manages the Service Catalog.

asset– Manages assets and CI records.

Key Functions of Roles in Access Control:

Navigate to:All → Users and Groups → Users

Open a user record

Scroll to the Roles related list

Click Edit and add roles

How to Assign Roles to Users:

A. Access Control Rules– Incorrect.

Access Control Rules (ACLs)definerecord-level and field-levelsecurity, but they donot control access to applications and modulesdirectly.

B. UI Policies– Incorrect.

UI Policiescontrol the visibility and behavior of form fields,not module or application access.

D. Assignment Rules– Incorrect.

Assignment Rulesautomatically assigntasks(e.g., Incidents, Requests) to groups or users, but theydo not control access.

Explanation of Incorrect Answers:

ServiceNow Product Documentation → Roles and Permissions

ServiceNow CSA Study Guide → User and Role Management

ServiceNow Knowledge Base → Controlling Access to Applications and Modules

References from Certified System Administrator (CSA) Documentation:

When creating filters inServiceNow, the elements should be specified in the following order:

Field– The database field (column) that is being filtered.

Operator– The comparison method, such as "is", "contains", "greater than", etc.

Value– The specific data that the filter should match.

Example of a Properly Structured Filter:Imagine filtering a list ofIncidentswhere the priority is high. The filter would be structured as:

Field:Priority

Operator:is

Value:High

is– Matches an exact value

is not– Excludes a specific value

contains– Looks for a partial match

greater than– Finds records with a value greater than the specified one

less than– Finds records with a value less than the specified one

B. Field, Operator, then Condition– Incorrect.

"Condition" is not an individual filter element in ServiceNow; theoperatoralready defines the condition (e.g., "is", "contains").

C. Operator, Condition, then Value– Incorrect.

The field must comefirstto define what data is being filtered. The operator follows next.

D. Value, Operator, then Field– Incorrect.

This is completely reversed; you must specifywhat fieldyou are filtering first before applying conditions.

ServiceNow Product Documentation → Filters and Condition Builder

ServiceNow CSA Study Guide → Data Management and List Filters

ServiceNow List Views → Using Filters and Operators

Common Operators in ServiceNow Filters:Explanation of Incorrect Answers:References from Certified System Administrator (CSA) Documentation:

Column Context Menusin ServiceNow provide options for interacting with list columns in a table. These menus allow users to customize list views, generate quick reports, export data, and configure list settings.

When users right-click on acolumn headerin a list view, they see a context menu with several actions. The correct answer,Option A, correctly describes these capabilities.

Create Quick Reports

Users can generatebar charts, pie charts, or other visual reportsbased on column data.

Example: Right-clicking on the "State" column in anIncidentslist allows users to create a report showing the count of incidents per state.

Configure the List

Users can modify the list layout, display additional columns, or customize fields.

Options includePersonalize List, Show / Hide Columns, and Sortfeatures.

Export Data

Data can be exported in various formats, such asExcel, CSV, PDF, or XML.

Example: Exporting all incidents assigned to a particular group.

Key Features of Column Context Menus:

Why the Other Options Are Incorrect:B. It displays actions related to filtering options, assigning tags, and search (Incorrect)

Filtering options are part of theFilter Navigator and List Context Menu, not theColumn Context Menu.

Assigning tags and performing searches happen within the list view but are not primary functions of theColumn Context Menu.

C. It displays actions related to viewing and filtering the entire list (Incorrect)

While column menus allow sorting and filtering, filtering theentirelist is mainly done via theList Context Menu(right-clicking the entire list or using the filter option at the top).

D. It displays actions such as view form, view related task, and add relationship (Incorrect)

Viewing forms, related tasks, and adding relationships are functions available when interacting withrecord-levelactions (right-clicking a row), not a column.

These actions are available via theList Context MenuorRelated Lists, not theColumn Context Menu.

Navigate toIncident > All.

Right-click on thePrioritycolumn header.

A menu appears with options such as:

Sort (Ascending/Descending)

Group By This Field

Create Report

Export Data

Configure List Layout

Example of Using a Column Context Menu in ServiceNow:

ARecord ProducerinServiceNowis atype of Catalog Itemthat allows users to create records intables(such as Incidents, Change Requests, or HR Cases) from theService Catalog. It provides asimplified and user-friendly interfacefor users to submit structured data without needing direct access to the actual form or database tables.

Key Features of a Record Producer:✔Creates task-based recordsin the appropriate table (e.g.,incident,sc_task,problem).

✔Uses a simplified forminstead of the standard form view of a record.

✔Can trigger workflows and business ruleswhen submitted.

✔Maps user inputs to table fieldsviaVariable Mappings.

An employee wants toreport a broken laptopbut does not need to see the fullIncident form.

The IT team creates aRecord Producernamed "Report an IT Issue" in theService Catalog.

The Record Producercollects user input(e.g., issue description, urgency, contact information).

Upon submission, itcreates an Incident record (incidenttable)in ServiceNow.

Example Use Case:

Why the Correct Answer is D:D. A Record Producer is a type of a Catalog Item that allows users to create task-based records from the Service Catalog(Correct)

This is the most accurate description of aRecord Producer.

It allows users tocreate recordsin a specifiedtask table (Incident, Change, Request, etc.)through theService Catalog.

Why the Other Options Are Incorrect:A. A Record Producer is a type of Catalog Item that is used for Requests, not Services (Incorrect)

Record Producers are not limited to Requests.

They can create various types of records, including Incidents, Change Requests, and HR Cases.

B. A Record Producer creates user records (Incorrect)

A Record Producerdoes not create user records(users are managed in thesys_usertable).

Instead, itcreates task-based recordsin other tables likeincidentorsc_task.

C. A Record Producer is a type of Catalog Item that provides easy ordering by bundling requests (Incorrect)

Order Guides, not Record Producers, handlebundling multiple Catalog Items into a single request.

ARecord Producer creates a single recordin a defined table.

Comparison: Record Producer vs. Other Catalog ItemsFeature

Record Producer

Standard Catalog Item

Order Guide

Creates a record in a ServiceNow table

Yes

No

No

Used to order physical/digital goods

No

Yes

Yes

Can bundle multiple requests

No

No

Yes

Uses a form-based submission

Yes

Yes

Yes

In ServiceNow, theService Catalogapplication allows administrators to create, configure, and manage catalog items that users can request. To create a new catalog item, administrators must access the correct module within theService Catalogapplication.

Maintain Categories (Option A)

This module is used to create and managecategorieswithin the Service Catalog.

Categories are used to organize catalog items into logical groups but do not allow the creation of actual catalog items.

Maintain Items (Option B)(Correct Answer)

This module is used tocreate, edit, and manage catalog itemsin the Service Catalog.

It provides options to define the item name, description, fields, workflows, and pricing details.

Administrators use this module when they want tobegin creating a new catalog item.

Content Items (Option C)

This module is related toContent Management System (CMS) and Knowledge Basebut is not used for creating standard Service Catalog items.

It allows administrators to create links to external content rather than actual requestable catalog items.

Items (Option D)

TheItemsmodule displays catalog items but does not allow an administrator to create new ones.

It is primarily forviewingitems rather than maintaining them.

Explanation of the Available Options:

The"Maintain Items"module is theonlymodule where administrators can create, edit, and manage catalog items in ServiceNow.

Other options either relate to categories, content management, or viewing existing items, making them incorrect choices.

Why is "B. Maintain Items" the Correct Answer?

ServiceNow Product Documentation - Service Catalog Administration????https://docs.servicenow.com/bundle/tokyo-it-service-management/page/product/service-catalog-management/concept/service-catalog-management.html

ServiceNow CSA Exam Guide - Service Catalog & Request Fulfillment

ServiceNow Fundamentals Training - Creating and Managing Catalog Items

References from Official CSA Documentation:

InServiceNow Knowledge Management,flagging an articleis a feature that allows users toreport errors or issueswithin a knowledge article. This helps maintain article accuracy and ensures that outdated or incorrect information is addressed by knowledge managers.

Error Reporting

Users can flag an article if they findincorrect, outdated, or misleading information.

Knowledge managers receive anotificationabout flagged articles and can review them for updates.

Article Quality Control

Helps improve knowledge base content by allowing users topoint out inaccuracies.

Ensures that knowledge articles remainrelevant and useful.

Notifying Knowledge Managers

Flagged articles appear in theKnowledge Base Administration module, allowing managers totrack and resolve flagged issues.

A. To mark an article to read later

Incorrect: There isnobuilt-in "read later" feature in ServiceNow Knowledge Management.

Instead, users canbookmarkan article for quick access.

B. Allow a user to submit feedback about an article

Incorrect:

Feedback is submitted through theFeedback feature, which allows users to rate articles and provide comments.

Flaggingis specifically forerror reporting, not general feedback.

Key Purposes of Flagging an Article:Why Other Options Are Incorrect?

Flagging Knowledge Articles

Flagging an Article for Review

Managing Flagged Articles

Knowledge Management Administration

References from ServiceNow CSA Documentation:

In ServiceNow,Table Access Control (ACL) rulesdefine the permissions for accessing records within a table. When a user attempts to access a record, ServiceNow processesACL rules in a specific orderto determine if the user has the necessary permissions.

Specific Table Name ACLs

ServiceNowfirst checks ACL rulesthat are defined for the exact table being accessed.

If there are multiple ACL rules for the same table, ServiceNow evaluates themfrom most specific to least specific(i.e., field-level ACLs before table-level ACLs).

Parent Table Name ACLs(If applicable)

If the table inherits from another table (e.g.,Incident inherits from Task), ServiceNownext checks ACL ruleson theparent table.

This ensures that inherited rules are properly applied.

Wildcard ACLs (*)(Any table)

If no explicit ACL rule is found for the table or its parent, ServiceNow checkswildcard ACL rules (*), which apply toall tables.

Wildcard ACLs act as alast resortwhen no table-specific rules exist.

Order of Processing ACL Rules:

(A) any table name (wildcard), parent table name, table name – Incorrect

Wildcard rules (*) areprocessed last, not first.

(B) table name, parent table name, any table name (wildcard) – Correct

This follows the correctprocessing order:

First:ACLs for the specific table

Second:ACLs for the parent table (if applicable)

Third:Wildcard ACLs (*)

(C) parent table name, table name, any table name (wildcard) – Incorrect

Parent table ACLs arechecked aftertable-specific ACLs, not before.

(D) any table name (wildcard), table name, parent table name – Incorrect

Wildcard ACLs (*) arealways processed last, so this order is incorrect.

Explanation of Each Option:

Field-level ACLs(column-specific) take precedence overtable-level ACLs.

If multiple ACL rules apply,all must evaluate totruefor access to be granted.

Explicit Deny:If an ACL rule explicitlydenies access, the user is denied, even if another ACL grants access.

Always Test ACLs:Use the "Security Debugging" feature (/sys_security_acl_list.do) to verify how ACLs are applied.

Additional Notes & Best Practices:

ServiceNow Docs: How Access Control Rules Work

https://docs.servicenow.com

ServiceNow Community: Understanding ACL Processing Order

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

InServiceNow, theNumber Maintenanceapplication is used toconfigure and modify numbering formats for specific tables. This application allows administrators to control how records are numbered across different modules.

Customization of Number Formats

Administrators can defineprefixes, number sequences, and suffixesfor records in different tables.

Example:INC0001001forIncidents,REQ0002001forRequests.

Resetting or Adjusting Number Sequences

You can manually adjust the numbering sequence if needed.

Example: Resetting incident numbering to start from a specific value.

Supports Multiple Tables

Works for standard tables likeIncidents, Problems, Requests, Change Requests, etc.

Can also be configured forcustom tables.

Application Navigation

Path:

Go toAll → System Definition → Number Maintenance

Locate the table and modify its numbering settings.

Key Features of Number Maintenance:Why Option A (Number Maintenance) is Correct?"Number Maintenance" is the official ServiceNow application for managing number formats per table.

Why Other Options Are Incorrect?B. System Maintenance– Incorrect; no such module in ServiceNow manages numbering formats.

C. Table Maintenance– Incorrect; this does not exist as an application in ServiceNow.

D. Record Maintenance– Incorrect; not a valid ServiceNow feature for modifying number formats.

ServiceNow Docs – Number Maintenance Configurationhttps://docs.servicenow.com

ServiceNow Learning – Customizing Numbering Schemes

ServiceNow System Definition – Number Format Best Practices

References from Certified System Administrator (CSA) Documentation:

In ServiceNow,User Criteriadefine conditions that determinewhich userscancreate, read, write, and retireknowledge articles in aKnowledge Base (KB). User Criteria help enforceaccess controland ensure that only authorized users can interact with specific knowledge bases.

Control who canread, contribute, edit, or retireknowledge articles.

Based onroles, groups, departments, locations, or custom conditions.

Applied at theKnowledge Base level, affecting all articles within that KB.

Can be combined using"Must match all"or"Match any"logic.

Example 1: Restricting Read Access

A knowledge base for IT Support should be accessibleonly to IT employees.

User Criteria:Department = IT, OR Role = itil

Only IT employees or ITIL users can read articles in this KB.

Example 2: Controlling Who Can Contribute

OnlyHR staffshould be allowed to create or update HR-related knowledge articles.

User Criteria:Group = HR Team, OR Role = knowledge_manager

Only HR Team members and Knowledge Managers can contribute.

User Criteriais the official term in ServiceNow for defining access control conditions for knowledge articles.

It allows precise control over who canread, create, write, or retirearticles.

It is a feature within theKnowledge Management application.

A. User Conditions – Incorrect

No such concept exists in ServiceNow. User Criteria, not "User Conditions," determine knowledge article access.

B. User Info – Incorrect

"User Info" refers to details stored in thesys_usertable (e.g., name, email) but does not define knowledge permissions.

D. User Permissions – Incorrect

While permissions exist in ServiceNow (via roles and ACLs),User Criteriaspecifically manageKnowledge Baseaccess.

ServiceNow Docs: User Criteria for Knowledge Management

ServiceNow CSA Study Guide – Knowledge Management Permissions

ServiceNow Product Documentation: Configuring Knowledge Base Access

Key Features of User Criteria:Examples of User Criteria:Why "C. User Criteria" is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

InServiceNow, aRecordrepresents all thedata saved within a particular form. Each record corresponds to a single entry in atableand contains multiplefieldsstoring different pieces of information.

ARecordis asingle instanceof data stored in a ServiceNowtable.

When a user fills out and submits aform, arecord is createdor updated in the respective table.

Each record has a uniqueSys ID(a 32-character identifier).

Example:

AnIncidentrecord contains fields such asNumber,Caller,Short Description, andPriority.

AChange Requestrecord contains fields likeChange Number,Requested By, andAssignment Group.

A. Fields

Fieldsare individualdata pointswithin a record.

Example: TheCallerandPriorityfields in anIncidentrecord.

B. Form

AFormis auser interfaceto enter and display data, but it does not store data itself.

It is just a way tointeract with records.

D. Lists

AListdisplaysmultiple recordsfrom a table, but each row in a list represents asingle record.

Lists are used for filtering, sorting, and searching records but do not represent a single data entry.

Key Concepts:Why Other Options Are Incorrect?

ServiceNow Data Model - Records and Tables

Understanding Records and Forms

Forms vs. Records vs. Fields

ServiceNow Forms and Records

References from ServiceNow CSA Documentation:Final Verification:Answer is 100% correct and aligned with official ServiceNow Certified System Administrator (CSA) documentation.

Service Catalog variables in ServiceNow are used to capture user input when they request catalog items, record producers, or order guides. These variables help customize user interactions and drive automation within Service Catalog workflows.

Key Characteristics of Service Catalog Variables:

Global by Default:

When a Service Catalog variable is created, it isglobal by default, meaning it can beused across multiple catalog itemsunless scoped to a specific item.

This helps inreusabilityof variables across different catalog items, reducing redundancy.

However, administrators candisable the "Global" checkboxif they want the variable to be specific to one catalog item.

Types of Service Catalog Variables:

Variables can besingle-line text, choice lists, reference fields, checkbox, multi-line text, and more.

They allow administrators to collect structured data from users during item requests.

Reusability Across Catalog Items:

Global variables can be used across multiple catalog itemswithout creating duplicate variables.

This is useful when multiple items require the same type of user input (e.g., location, department).

Visibility and Dependency:

ServiceNow allowsUI policiesandcatalog client scriptsto control the behavior of these variables dynamically.

Admins can configurevisibility, mandatory status, or dependenciesbased on user selections.

Explanation of Other Options (Why They Are Incorrect):

Option A (Service Catalog variables can only be used in Record Producers) – Incorrect

While Service Catalog variablescanbe used in Record Producers, they arenot limitedto them.

Variables can also be used inCatalog Items, Order Guides, and Requested Items (RITM).

Option B (Service Catalog variables can only be used in Order Guides) – Incorrect

Service Catalog variablescanbe used in Order Guides, but they arenot restrictedto them.

Order Guides allow multiple items to be ordered together, but variables can be used independently in Catalog Items and Record Producers as well.

Option C (Service Catalog variables cannot affect the order price) – Incorrect

Service Catalog variablescan affect pricingthroughVariable Price Mapping.

If configured, variables (like dropdowns or checkboxes) can be linked to aprice adjustment, impacting the total cost of the request.

For example, selecting "Additional Storage" in a cloud server request could add extra costs dynamically.

Official Reference from ServiceNow Certified System Administrator (CSA) Documentation:

ServiceNow Documentation – Service Catalog Variables: ServiceNow Variables Guide

ServiceNow CSA Exam Guide: Covers Service Catalog fundamentals, including variable behavior and reusability.

In ServiceNow, reports can be created from multiple locations within the platform. Reports provide insights into data stored within the system and help visualize trends, patterns, and key performance indicators (KPIs). The two correct locations from which reports can be created are:

ServiceNow allows users to create a report directly from a list view.

This feature is useful when working with records in a table, as it enables quick reporting based on the visible columns.

To generate a report from a list view:

Navigate to a list view (e.g., Incidents, Requests, etc.).

Click on acolumn headingto access the context menu.

SelectBar Chart, Pie Chart, or other visualization optionsto generate an instant report.

If needed, refine the report using the reporting interface.

TheView / Run moduleis the primary location for creating and managing reports in ServiceNow.

It allows users tocreate new reports, modify existing reports, and run pre-built reports.

Users can access theReport Designerfrom this module, where they can configure:

Data sources (tables)

Report type (bar chart, pie chart, trend, etc.)

Filters and conditions

Visualization settings

To access it:

Navigate toReports > View / Runin the Application Navigator.

ClickCreate a Reportto start building a new report.

1. List Column Heading (Correct)2. View / Run Module (Correct)Why the Other Options Are Incorrect:B. Metrics module (Incorrect)

TheMetrics modulein ServiceNow is used to track and measure the performance of records over time, but it isnot used to create reports.

Metrics focus on data such astime to resolution, SLA compliance, and process efficiency, but reporting is handled separately in the Reports module.

C. Statistics module (Incorrect)

ServiceNow does not have a dedicatedStatistics modulefor report creation.

While reports can generate statistical insights, this is done within theView / Run moduleand not a standalone "Statistics module."

In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.

Definition of a Role:

Aroleis a collection ofpermissionsthat grant access to different parts of the system.

Example:Theadminrole grants full access, while theitilrole allows incident management access.

sys_user_role Table:

This tablestores role recordsand their associated metadata.

Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).

Users are linked to roles through thesys_user_has_roletable.

How Roles Work in ServiceNow:

A user assigned a role gainsall the permissionsassociated with that role.

Roles can behierarchical(one role can inherit permissions from another).

Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.

Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.

Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.

B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.

C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.

ServiceNow Docs – Roles and Role Managementhttps://docs.servicenow.com

ServiceNow Table Schema – sys_user_role

ServiceNow Developer Portal – Role Hierarchy & Best Practices

References from Certified System Administrator (CSA) Documentation:

InServiceNow,User Impersonationallows anadmin or a user with the appropriate roleto temporarily act as another userwithout needing their password. This is mainly used fortesting and visibility, helping administrators and developers verify user permissions, role-based access, and UI experiences.

Testing Permissions & Roles

Ensures thatusers have the correct access rights(e.g., verifying ITIL user permissions for incident management).

Helps testUI Policies, Business Rules, and ACLs (Access Control Rules)by viewing the system from the perspective of different roles.

Debugging & Troubleshooting

Identifies why a usercannot access certain records or modules.

Helps inresolving permission-related issueswithout affecting live users.

Experience Validation

Ensures userssee the correct menus, fields, and optionsbased on their assigned roles.

Useful when developingnew applications, workflows, or Service Catalog items.

Admins and authorized userscan impersonate by clicking on their name in the top-right corner and selectingImpersonate User.

Once impersonated, all actions are logged for security and compliance.

Primary Functions of User Impersonation:How to Use Impersonation:

(A) Testing and visibility – Correct

The primary function ofuser impersonationis totest and verify what different users can see and doin the system.

It helps withdebugging UI, role-based access, ACLs, and workflow execution.

(B) Activate verbose logging – Incorrect

Verbose loggingis used fordetailed debugging and performance monitoring, butimpersonation does not enable logging features.

(C) View custom perspectives – Incorrect

ServiceNow doesnotuse the term "custom perspectives" in the context of impersonation.

Impersonationshows what a specific user sees based on their roles, but it doesnot create custom perspectives.

(D) Unlock Application master list – Incorrect

There isno such featureas an "Application Master List" that requires impersonation to unlock.

Application access is controlled byroles and permissions, not impersonation.

Explanation of Each Option:

Never impersonate a user without permission, especially in production environments.

All impersonation actions are loggedin the system for security and auditing purposes.

Use impersonation in a sub-production (development or test) instancebefore making changes to production.

Admins should use impersonation instead of logging in with test user accountsto maintain security and accountability.

Additional Notes & Best Practices:

ServiceNow Docs: Impersonating Users

https://docs.servicenow.com

ServiceNow Community: Best Practices for User Impersonation

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

InServiceNow,Access Control Rules (ACLs)define thepermissionsrequired for users to interact with records, fields, or UI actions. ACLs are enforced at thedatabase leveland are evaluatedbefore granting accessto a user.

Access Control rules can be configured usingthree primary permission requirements:

Rolesdefine aset of permissionsassigned to users.

Access Control rules canrequire users to have a specific role(e.g.,admin,itil,catalog_admin) to perform an action on a table, field, or record.

Example:

A rule might state:Only users with theitilrole can read theIncidenttable.

Conditional expressionsallow access based on a specified condition.

These conditions areevaluated at runtime, and access is granted if they are met.

Example:

A condition could be:"Allow access if the record's 'State' field is 'New'".

This would mean that users can only modify records if their state is "New".

Scriptsallow advanced, custom logic to determine access.

ACLs supportserver-side scripts(written in JavaScript) that use thegs.hasRole(),currentobject, or other logic to evaluate whether a user should have access.

Example:

1. Roles (Correct -)2. Conditional Expressions (Correct -)3. Scripts (Correct -)javascript

CopyEdit

// Allow access only if the user is the requester of the record

answer = current.requested_for== gs.getUserID();

Scripts provideflexibilityby allowing complex access conditions beyond simple roles or expressions.

C. Assignment Rules(Incorrect)

Assignment Rulesare used toautomatically assign recordsto users or groups based on conditions.

They do not defineaccess control permissions.

E. User Criteria(Incorrect)

User Criteriais used inService CatalogandKnowledge Base (KB)to control access to catalog items or knowledge articles.

It isnot usedfor ACLs at the table/field level.

F. Groups(Incorrect)

Groupsare collections of users but cannot be directly used in ACLs.

Instead,roles(which are often assigned to groups) are used to define ACL permissions.

Why Other Options Are Incorrect?

ServiceNow Product Documentation - Access Control Rules

Access Control Rules Overview

Defining Access Control Rules

ServiceNow Security Model

Role-Based Access

Scripted ACLs

References from ServiceNow CSA Documentation:

In ServiceNow, afilter conditionconsists of three primary components:

Field– The specific column (attribute) in a table that you want to filter by.

Example:State,Priority,Category,Created Date

Operator– Defines the comparison condition between theFieldand theValue.

Example:is, is not, contains, starts with, greater than, less than

Value– The actual data that the filter is looking for.

Example:High (for Priority), New (for State), IT Support (for Category)

Example of a Filter Condition in ServiceNow:If you want to filter Incident records where theStateisNew, the filter condition would be:

Field:State

Operator:is

Value:New

A. Table–

A table is where data is stored, but it isnota component of a filter condition.

Filters are appliedona table but do not include the table itself in the condition.

ServiceNow Docs: Filtering Data in Lists and Reportshttps://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/use/using-lists/concept/filtering-lists.html

ServiceNow CSA Official Training Guide (Filtering and Searching Data)

Why the Other Option is Incorrect?References from Certified System Administrator (CSA) Documentation:This confirms thatField, Operator, and Valueare the three core components of a filter condition.

InServiceNow Service Catalog, anOrder Guideis a feature that allows users toorder multiple, related catalog items in a single request, simplifying the ordering process.

Helps usersrequest multiple items togetherinstead of submitting separate requests.

Ensures that related items are grouped logically (e.g., when onboarding a new employee, an Order Guide can include a laptop, software licenses, and access to required applications).

Usesvariables and rulesto pre-fill certain values and guide users through the ordering process.

Reduces the number of individual requests and makes fulfillment more efficient.

Purpose of an Order Guide:

(A) Order Guides restrict the number of items in an order to only one item per request – Incorrect

This isnot truebecause Order Guides allow users to requestmultiple itemsat once.

Asingle request (REQ#) is generatedthat contains multiple Requested Items (RITMs).

(B) Order Guides provide a list of guidelines for Administrators on how to set up item variables – Incorrect

Order Guides are forusers, not just administrators.

Theydo not provide setup guidelines; instead, they simplify ordering for end-users.

(C) Order Guides provide the ability to order multiple, related items as one request – Correct

This is theprimary functionof an Order Guide.

Instead of placing separate orders for different catalog items, a user can add allrelateditems to asingle request.

Example:Employee Onboarding Order Guide

Laptop

Email account

VPN access

Software (e.g., Microsoft Office, Adobe Suite)

(D) Order Guides take the user directly to the checkout without prompting for information – Incorrect

Order Guidescan include user prompts(variables, conditions) before checkout.

Users may be asked for specific detailsbeforesubmitting the request (e.g., laptop specifications, software preferences).

Explanation of Each Option:

Use dynamic variables: Order Guides can ask questions that determine which items should be included in the request.

Improve user experience: Order Guides streamline ordering, ensuring users request all necessary items without forgetting anything.

Enhance fulfillment efficiency: Since multiple items are grouped in one request, IT and fulfillment teams can process them together, reducing delays.

Example Use Cases:

New Hire Onboarding(laptop, software, security badge, phone)

Office Setup Request(desk, chair, monitor, accessories)

Additional Notes & Best Practices:

ServiceNow Docs: Order Guides Overview

https://docs.servicenow.com

ServiceNow Community: How to Configure an Order Guide

https://community.servicenow.com

References from Certified System Administrator (CSA) Documentation:

ServiceNow uses a hierarchical structure to manageService Catalog requests:

REQ (Request Record)

TheRequest (REQ#)is theparent recordthat represents the entire service request submitted by a user.

It groups all requested items and their associated tasks.

Found in thesc_requesttable.

RITM (Requested Item Record)

TheRequested Item (RITM#)is the specificcatalog itemordered by the user within a request.

A singleREQcan have multipleRITMsif the user ordered multiple items in a single request.

Found in thesc_req_itemtable.

TASK (Catalog Task Record)

TheTask (TASK#)is the individual fulfillment action required to complete the requested item.

A singleRITMcan have multipletasks, each assigned to different fulfillment teams.

Found in thesc_tasktable.

Why Answer "C" is Correct:✔️REQ (Number) > RITM (Number) > TASK (Number)

This is thecorrect pathbecause it follows theServiceNow fulfillment structure:

REQ (Request)– Tracks the entire request.

RITM (Requested Item)– Tracks individual items within the request.

TASK (Catalog Task)– Tracks the specific tasks needed to complete the requested item.

This path allows an administrator to drill down from the overallRequest (REQ#)to individualRequested Items (RITM#)and finally to theTasks (TASK#)assigned to fulfill those items.

Why the Other Answers Are Incorrect:A. RITM (Number) > REQ (Number) > PROCUREMENT (Number)

Incorrectbecause theREQ# (Request) comes firstbefore the RITM# (Requested Item).

Also,PROCUREMENT#is not always part of the fulfillment flow unless the item requires procurement (e.g., purchasing hardware).

B. REQ (Number) > RITM (Number) > PROCUREMENT (Number)

Incorrectbecausenot all requests involve procurement.

The last step should beTASK (sc_task), notPROCUREMENTunless it's a procurement-related request.

D. FULFILLMENT (Number) > RITM (Number) > TASK (Number)

Incorrectbecause"FULFILLMENT" is not a standard record typein ServiceNow.

The correct hierarchy starts withREQ# (sc_request), not "FULFILLMENT."

ServiceNow CSA Study Guide – Service Catalog & Request Fulfillment

ServiceNow Docs: Request Fulfillment Process(ServiceNow Documentation)

ServiceNow Tables & Data Model (sc_request, sc_req_item, sc_task)

References from the Certified System Administrator (CSA) Documentation:

InServiceNow Reporting, when modifying a report, users can preview the resultswithout savingby clicking the"Run"button. This executes the report with the current settings and displays the updated resultsbefore committing any changes.

C. Run

The"Run"button allows users toexecute the report immediatelyto see updated results.

It helps users verify if filters, conditions, or visualizations are correctbefore saving the report.

Example: If a user changes thedate rangeon anincident report, clicking"Run"updates the chartwithout saving the report permanently.

A. Execute

There isno "Execute" buttonin ServiceNow Reporting.

"Execute" is used in scripting (e.g., Business Rules, Scheduled Jobs), not for reports.

B. Try it

Not a valid option in ServiceNow Reporting.

Possibly confused with"Try It" in Flow Designeror Catalog Items.

D. Test

"Test" is used inWorkflows, Business Rules, and Flow Designer, not in reports.

E. Preview

There isno "Preview" buttonfor running reports.

"Preview" is typically used inUI Policies and Forms.

TheActivity Streamin ServiceNow records allupdates, comments, work notes, and system eventsrelated to a record.

Tofilter the Activity log to show only Work Notes, follow these steps:

Locate theActivity Streamsection on the form.

Click theFunnel (Filter) icon.

SelectWork Notesto display only the relevant updates.

This allows thesubject matter expertto focus only onwork notesleft by other users, ensuring quick access to important information.

A. Click Context menu > Work Notes View

There isno default "Work Notes View" optionin the context menu for filtering the Activity log.

B. Click Personalize icon and select Activity Stream

ThePersonalize iconis used forUI preferences, not for filtering work notes.

C. Right-click form header > Form Layout > Add Work Notes Section

Adding a "Work Notes" field to the formdoes not filterthe existing activity log.

E. Click Context menu > History

TheHistory optiontracks user navigation and doesnot filter Work Notesin the Activity log.

InServiceNow, when acustom tableis created, the systemautomatically generates four Access Control Rules (ACLs)to control the basic operations on that table. These rules define who cancreate, read, update, and delete recordsin the table.

Read (ACL: table_name.*.read)Allows users to view (read) recordsin the table.

Without this ACL, userscannot see any recordsin the table.

Create (ACL: table_name.*.create)Allows users to insert new recordsinto the table.

Without this ACL, userscannot add new records.

Update (ACL: table_name.*.update)Allows users to modify (edit) existing recordsin the table.

Userscannot edit recordsif this ACL is missing.

Delete (ACL: table_name.*.delete)Allows users to remove (delete) recordsfrom the table.

Userscannot delete recordswithout this ACL.

Default Access Control Rules Created for a New Table:

C. executeIncorrect– Theexecutepermission applies toScripts or UI Actions, not table records.

NoexecuteACL is automatically created for tables.

F. writeIncorrect–"Write" is NOT an ACL permission in ServiceNow.

Instead,"update"is the correct term for editing records.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Rules (ACLs)????Access Control Best Practices

ServiceNow Docs – Creating Custom Tables????Custom Tables and Security

Official ServiceNow Documentation References:

InServiceNow List Views, users cancustomize and personalizethe displayed columns to fit their needs.

Open anylist view(e.g., Incidents, Requests).

Click theGear icon (⚙)in the top-right corner of the list.

ThePersonalize List Columnswindow appears.

Select or remove columns as needed.

ClickSaveto apply changes.

Steps to Personalize List Layout (Columns):This customization isuser-specific, meaning it only affects the logged-in user’s view.

B. Select the column to be personalized > Click Edit icon (Penal) > Choose options to personalize

NoEdit icon (Pencil) for column customizationexists in List Views.

C. Context Menu > View > Personalize

TheContext Menu (right-click menu)allows you to filter or sort data but doesnot customize columns.

D. Select the column to be personalized and right-click the header > Choose options to personalize

Right-clicking the column header providessorting and grouping options, not full column customization.

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.

In ServiceNow, anUpdate Setis a mechanism used to package and transfer customizations from one instance to another. TheDefault Update Setis automatically created for every instance and captures all unassigned configuration changes. However, it is considered abest practice not to use the Default Update Set for moving customizations between instances.

Lack of Organization & Traceability

The Default Update Set collects all modifications automatically, making it difficult to track specific changes related to a particular project or feature.

If multiple administrators or developers work in an instance, their changes will all be mixed together in the Default Update Set, leading to confusion and conflicts.

Risk of Losing Changes

Default Update Sets are not automaticallycomplete. Since users can forget to mark their customizations explicitly for an update set, some changes might not get captured.

If a system admin forgets to move a customization into a named update set, those changes may not be included in the migration process.

Cannot Be Moved Between Instances

The Default Update Setcannot be retrieved or movedbetween instances because it is system-managed. This makes itimpossibleto use it for transferring customizations effectively.

Named Update Sets, on the other hand, allow developers to package only the required changes for controlled migration.

Best Practice: Use Named Update Sets

It is highly recommended to create anamed Update Set(e.g., "Incident_Enhancements_Q1_2025") for each set of related changes.

This provides a structured way to track, test, and promote configurations fromdevelopment → test → production environmentsin a controlled manner.

A. Merge Default Update Sets before moving between instancesIncorrect – The Default Update Set cannot be moved between instances, so merging it would not serve any purpose.

B. Submit Default Update Set to Application RepositoryIncorrect – The Application Repository is used forScoped Applications, not for update sets. The Default Update Set is system-managed and should not be used for structured deployments.

D. Keep Default Update Set to a maximum of 20 records, for troubleshooting purposesIncorrect – While keeping the Default Update Set small might be useful for tracking small changes, there is no such best practice limit of "20 records." It is still not recommended for migrations.

ServiceNow Product Documentation – Update Sets Best Practices????Update Set Best Practices

ServiceNow Community Best Practices – Managing Update Sets????Managing Update Sets

Reasons Why You Should Not Use the Default Update Set for Moving Between Instances:Incorrect Answer Choices Analysis:Official ServiceNow Documentation References:Conclusion:The correct answer isC. You should not use the Default Update Set for moving between instances.The best practice is to always createnamed Update Setsto ensure controlled, traceable, and reliable migrations of customizations between ServiceNow instances.

InServiceNow Knowledge Management,User Criteriais used to control access toknowledge bases (KBs)andarticlesbased on user attributes such ascompany, department, group, and roles.

Understanding the Given Criteria:Criteria

Value

Companies

ACME North America

Department

HR

Groups

ACME Manager

Match All

Yes

TheMatch All: Yessetting means thatonly users who meet ALL the specified criteriawill have access.

Who Gets Access?Users must be:

Amember of the ACME Manager group

Part of the HR department

An employee of ACME North America

B. Employees of ACME North America, who are members of HR Department or the ACME Manager group →Incorrect

The"OR" conditionis incorrect becauseMatch All: Yesrequires users to meetALL conditions.

C. Users which are members of either ACME North America, or HR Department, or ACME Manager Group →Incorrect

Again,Match All: Yesmeans usersmust meet all criteria, not just one.

D. Member of the ACME Manager group, and HR department, regardless of geography →Incorrect

Company (ACME North America) is part of the criteria, so itcannot be ignored.

Why Other Options Are Incorrect?

User Criteria for Knowledge Bases

Managing Knowledge Base Access

Official ServiceNow Documentation Reference:

InServiceNow’s Configuration Management Database (CMDB), thecmdbtable is thebase tablefrom which allConfiguration Item (CI) tablesinherit.

cmdbis the Parent Table of All CMDB-Related Tables

Thecmdbtablecontainsbasic attributesshared by allConfiguration Items (CIs).

Every CI in ServiceNowinherits fromcmdbor one of its child tables.

Hierarchy of CMDB Tables in ServiceNow:

cmdb(Base Table)→ Stores general CI data.

cmdb_ci(Stores specific CI details)→ Extendscmdbto storedevices, applications, and services.

cmdb_rel_ci(Stores relationships between CIs)→ Used totrack dependencies.

Why iscmdbthe Correct Answer?

A.cmdb_dIncorrect– No such standard table exists in ServiceNow’s CMDB.

B.ucmdbIncorrect–uCMDB (Universal CMDB)is anHP product, not part of ServiceNow’s CMDB.

C.cmdb_rel_ciIncorrect–This table stores CI relationships, but it isnot the base table.

Incorrect Answer Choices Analysis:

ServiceNow Docs – CMDB Core Tables????CMDB Table Structure

ServiceNow Docs – CMDB Best Practices

Official ServiceNow Documentation References:

UI Policiesin ServiceNow dynamically control form field behaviorswithout scripting. They help maintaindata consistencyand improve user experience.

B. Setting fields hidden

UI Policies canhideform fields based on conditions.

Example: Hide the"Resolution Notes"field unlessState = Resolved.

D. Setting fields read-only

UI Policies canmake fields read-onlyto prevent users from modifying certain data.

Example: Set"Requested For"fieldread-onlyafter submission.

E. Setting fields mandatory

UI Policies canenforce mandatory fieldsbased on conditions.

Example: Make the"Justification"field mandatory ifPriority = High.

A. Setting fields to accept the data with ‘n’ number of characters

Field length restrictions are set in theDictionary Definition, not UI Policies.

C. Setting fields to accept the data in an expected format

Data formatting (e.g., date, phone number) is controlled byField Types and Data Policies, not UI Policies.

InServiceNow Service Catalog, the best practice for handling accessory selections is to usevariables or variable setswithin asingle catalog itemrather than creating multiple separate catalog items.

A. Create a Catalog Item for the tablet and add a checkbox variable for each accessory option.Correct– Addingcheckbox variablesfor accessories allows users to select multiple options within a single request.

Example variables:

[✓] Carrying Case

[✓] Screen Cleaner

[✓] Tablet Stand

[✓] Screen Protector

This makes orderingsimpler and more user-friendly.

B. Create a Catalog Item for the tablet, and add a variable set to the form for accessory options.Correct– AVariable Setis a reusable collection of variables that can be applied to multiple catalog items.

This approach is beneficial if multipledevices (e.g., laptop, phone, tablet)sharethe same accessory options.

The Variable Set can includecheckboxesfor selecting accessories.

E. In Shopping Cart configuration, select the option to show the "Add Accessories" button.Correct– Enabling the"Add Accessories"button in theShopping Cartallows users to add related products as separate items in their order.

This works well when accessories areseparate items in the catalogbut need to be linked for convenience.

Best Practices for Configuring the Tablet and Accessories:

C. Create one Catalog Item for each: tablet, carrying case, screen cleaner, tablet stand, and screen protector.Incorrect – Thisforces users to order accessories separately, making the processless efficient.

Best practice is to keep accessorieswithin the same formunless they are standalone items.

D. Create a Record Producer, and on the form, add a checkbox variable for each accessory option.Incorrect –Record Producerscreate records intables (e.g., Incident, Request, HR Case)but arenot used for Service Catalog ordering.

Thecorrect approachis to use aCatalog Item with variablesinstead.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Creating and Managing Catalog Items????Creating Service Catalog Items

ServiceNow Docs – Variable Sets????Service Catalog Variable Sets

ServiceNow Docs – Shopping Cart Configuration????Shopping Cart Configuration

Official ServiceNow Documentation References:

Conclusion:The correct answers are:

A. Create a Catalog item for the tablet and add checkbox variables for accessories.

B. Use a Variable Set for the accessory options.

E. Enable the "Add Accessories" button in Shopping Cart configuration.

This approachenhances user experience, ensures flexibility, and aligns with ServiceNow Service Catalog best practices.

In ServiceNow, role-based access control (RBAC) determines what a user can see and do within the platform. If a user can see an application and its module but encounters a blank page when attempting to create a new record, the most likely reason is insufficient permissions.

Understanding the Issue:

The usercan see the application and module, which indicates they have at leastreadaccess.

The blank page appears when they attempt to create a new record, which suggests a lack ofwriteaccess.

Role-Based Access Control in ServiceNow:

Every table in ServiceNow can haveACLs (Access Control Rules)that define what users can do based on their roles.

If a user hasonly read accessto the Inventory table (x_inventory), they can view records butcannot create new ones.

AwriteorcreateACL is required to allow the user to insert new records into the table.

Why Other Answers Are Incorrect:

A. Create New module has a broken link→ If the module had a broken link, the user would likely get an error or a "Page not found" message rather than a blank page.

B. Known intermittent issue with U115→ No such known issue exists in official CSA documentation.

C. User should be using Chrome instead of Explorer for their browser→ While browser compatibility issues can exist, they do not typically result in a blank page specifically when trying to create a new record.

E. User session has timed out→ If the session had expired, the user would be redirected to the login page rather than seeing a blank page.

Best Practice Solution:

Verify the ACLson the Inventory table (x_inventory) to check if the user haswriteandcreatepermissions.

Check the roles assignedto the user underUser Administration → Usersand ensure they have the appropriate roles for Inventory management.

Review the Application Menu and Module settingsto confirm proper configuration.

Assignment Rulesin ServiceNow automaticallyassign tasks(such as incidents, service requests, or change requests) to theappropriate group or individualbased on predefined criteria.

Acritical, high-priority service requestis created.

TheAssignment Rulechecks conditions (e.g., priority, category, requester, etc.).

The systemassignsthe request to the correctassignment group or individual.

How Assignment Rules Work:Example Scenario:

If an incident isPriority 1 (P1)and the category isNetwork, an assignment rule canautomatically route it to the "Network Support" group.

A. User Policy

No such feature exists in ServiceNow for task assignments.

B. UI Policy

UI Policies controlform behavior (visibility, field conditions, etc.), not assignment logic.

C. Predictive Intelligence

Predictive Intelligence usesmachine learningto suggest assignments, butAssignment Rulesare the primary mechanism for automatic task allocation.

Detailed Explanation:

Business Rulesin ServiceNow are server-side scripts that execute in response to database operations, such as when a record is displayed, inserted, updated, deleted, or queried. They are critical for automating processes, ensuring data integrity, and performing backend operations without user intervention. Business Rules can be set to run at different times, such as before or after the database action, depending on the requirement. (Reference: ServiceNow Documentation - Business Rules and Server-side Scripting)

=================

In ServiceNow’sConfiguration Management Database (CMDB), threekey tablesform the foundation for storing and managingConfiguration Items (CIs)and theirrelationships.

cmdb_ci (E) - CI Base Class Table

This is thebase classfor allConfiguration Items (CIs)in the CMDB.

Every CI (e.g., servers, applications, network devices) extends from this table.

Stores general attributes like name, serial number, and asset tag.

cmdb (G) - CMDB Parent Table

This is theparent tablefor all CMDB-related tables.

Itdoes not store CI records directlybut serves as a reference structure.

All CMDB tables, includingcmdb_ci, inherit from this table.

cmdb_rel_ci (C) - CMDB Relationship Table

This tablestores relationshipsbetween different CIs.

Example: Aserver hosts an application, or adatabase is dependent on a storage unit.

Helps withimpact analysis and dependency mapping.

A. sn_cmdt_bak

No such table in standard ServiceNow CMDB.

B. sh_emdb_ci

Typo or incorrect table name—not part of the ServiceNow CMDB model.

D. cmdb_bak

"bak" suggests abackup table, but there isno standard "cmdb_bak"in ServiceNow.

F. sh_eomdb

Not a recognized CMDB table in ServiceNow.

Tofilter a long list of recordsand find those whereShort Description contains "email", the best practice is to use thecolumn searchfeature:

Click the List Magnifier (????)to open thecolumn searchoptions.

In the "Short Description" column search box, type:

Steps to Filter a List by "email" in Short Description:email

Press Enterto apply the filter.

This methodautomatically applies a "contains" filter, meaning it will showany records where "email" appears anywhere in the Short Description field.

A. Click List Magnifier to expand column search, on Short Description, type %email, click enter →Incorrect

% (percent sign) is not a valid wildcardin ServiceNow's list filters.

C. On Search box, select text, type email, click enter →Incorrect

Theglobal search box searches across multiple tables, not just the Short Description field.

D. Click List Magnifier to expand column search, on Short Description type 'email, click enter →Incorrect

Single quotes ('email') are not requiredin column searches.

Why Other Options Are Incorrect?

Using List Filters in ServiceNow

ServiceNow Search Operators

Official ServiceNow Documentation Reference:

In ServiceNow, new tables can be created using theTables & Columnsmodule or theTablesmodule.

Navigation:System Definition > Tables & Columns

Allows admins tocreate and modify tables, including:

Adding columns (fields)

Setting relationships

Defining attributes

Navigation:System Definition > Tables

A simpler interface for creating tableswithout managing columns immediately.

B. Schema Map →Incorrect

Schema Mapvisualizestable relationships but does not allow table creation.

C. Dictionary →Incorrect

TheSystem Dictionary (sys_dictionary)is used tomanage fields and attributes, not create tables.

Creating Tables in ServiceNow

Understanding Tables & Columns

1. Tables & Columns Module(Correct Answer)2. Tables Module(Correct Answer)Why Other Options Are Incorrect?Official ServiceNow Documentation Reference:

In ServiceNow, when defining afilter condition, theelement being filteredis called aField.

Afieldis an individual piece of data within atable(e.g.,Caller,State,Priorityin theIncidenttable).

The available fields in a filter depend on:

The table being filtered

User access rights (roles and permissions)

The columns (fields) available on the table

Understanding Fields in Filter Conditions:Example of a Filter Condition:css

CopyEdit

[ State ][ is ][ In Progress ]

State→ This is aFieldin the table.

is→ This is theOperatorused for filtering.

In Progress→ This is theValuebeing compared.

A. Attribute– Attributes aremetadataabout a field but do not define filter conditions.

B. Label– The label is thedisplay nameof a field but is not used in filtering.

D. Column– While fields arestored as columnsin a database, in filtering, they are referred to asFields.

E. Data Element– This is a general term, not specific to filter conditions.

ServiceNow Filtering and Conditions

ServiceNow CSA Training Module:"Using Filters and Queries in ServiceNow"

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

When working with along list of records, users canfilter dataquickly using theShow Matchingfeature.

C. On the list, locate and right-click on the value Hardware, select Show Matching

Right-clickingon the"Hardware"value and selecting"Show Matching"filters the list toonly show records where the Category is Hardware.

This is thefastestway to apply aquick filter.

A. On Breadcrumb, click the > icon, type Hardware and click enter

Breadcrumbsdo not support direct text inputfor filtering.

Breadcrumbs showexisting filtersbut are not used to type new values.

B. On the Category column header, right-click and select Show > Hardware

Incorrect menu option—There is no "Show > Hardware" selection.

Instead, users would need to use"Show Matching"(Correct Answer C).

D. Right-click on magnifier, type Hardware, and click enter

There isno "magnifier" optionfor filtering in list view.

E. Click Funnel icon, type Hardware and click enter

TheFunnel (Filter) iconis used to createadvanced filters, but it doesnotsupport direct text input like this.

The correct way to use theFilterwould be:

Click theFunnel icon

SetCategory = Hardware

ClickRun

InServiceNow,Access Control Rules (ACLs)determine whether auser can access a specific record, table, or field.

When evaluatingtable ACLs, ServiceNow follows aspecific-to-generalapproach:

First, it checks the most specific ACL (Table ACL)

Example: If the table isincident, ServiceNow first checks ACLs forincident.

Then, it checks the Parent Table ACL(if the table is inherited)

Example: Sinceincidentextendstask, it will check ACLs fortask.

Finally, it checks the Wildcard ACL (*ACL)

If no specific or parent table ACL is matched, ServiceNow checks for awildcard ACL(*.read,*.write, etc.).

Specific Table ACL(e.g.,incident.read)

Parent Table ACL(e.g.,task.read)

Wildcard ACL(e.g.,*.read)

Order of ACL Evaluation:Thisensures granular access control, giving priority tomore specific rules before applying broader permissions.

*A. Specific to general: Table.Field ACL, Parent Table.Field ACL, .Field ACLIncorrect– Field ACLs are evaluatedaftertable ACLs. This option confuses table and field evaluation.

B. Bottom to top: Table ACL, Table.Field ACL, Parent Table.Field ACLIncorrect– The correct order isTable ACL → Parent Table ACL → Wildcard ACL, not Table.Field ACL order.

C. General to specific: Table ACL, Table.Field ACL, Parent Table, Field ACLIncorrect– ServiceNow appliesspecific ACLs first, not general ones.

D. Top to bottom: Wildcard Table ACL, Parent Table ACL, Table ACLIncorrect– Wildcard ACLs are evaluatedlast, not first.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Access Control Evaluation Order????Access Control Rules

ServiceNow Community – ACL Best Practices????Understanding ACL Processing

Official ServiceNow Documentation References:

To customize thebanner image, text, and colorsof your instance in ServiceNow, you use theSystem Properties > Brandingmodule. This module allows administrators to control variousUIaspects, including thebrandingof the system.

Banner Image: Change the header image seen across the UI.

Text: Customize the text displayed in the header or other branding areas.

Colors: Modify the colors of various UI elements to match your company's branding.

Key Customizations Available in Branding:This is typically applied to bothUI16 (desktop)andUI11 (classic)interfaces, ensuring a consistent experience across the instance.

A. Homepage Admin > Pages > Branding– This is used forhomepagesrather than global instance branding.

C. System Properties > Basic Configuration UI16– This section allows configuration of theUI layout and elementsbut does not specifically manage branding elements like banner image and colors.

E. Service Portal > Portals > Branding– This is specific toService Portal branding, not for global instance customization.

ServiceNow Branding Configuration

ServiceNow CSA Training Module:"System Properties and Branding"

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

When importingspreadsheet datainto ServiceNow, thefirst stepis toDefine a Data Source.

AData Sourcedefineswhere the data is coming from(e.g., Excel, CSV, JDBC connection).

It establishes theformatandstructureof the incoming data before it can be processed by anImport Set.

Without defining theData Source, the system does not know how to handle the incoming data.

Define Data Source– Identify where the data is coming from.

Create Import Set– Temporarily store the imported data.

Set Coalesce– Define unique identifiers to prevent duplicate records.

Transform Data– Map fields to the target table.

Run the Import– Move data into the actual ServiceNow tables.

A. Create Import Set– Import Sets store the data, but they are createdafterdefining the data source.

B. Run Data Scrubber– No such step exists in ServiceNow's import process.

C. Set Coalesce– Coalescing ensuresno duplicate records, but it happensafter data is loaded into the import set.

E. Select Import Set– The Import Set is selected after defining the data source and loading the data.

ServiceNow Data Import Process

ServiceNow CSA Training Module:"Importing Data into ServiceNow"

Why Defining a Data Source is the First Step?Steps in the Data Import Process:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Access Control Rules (ACLs)in ServiceNow define security rules thatcontrol user permissionsforviewing, creating, updating, and deletingrecords in the system. These rules ensure that users can onlysee and interact with the data they are authorized to access.

D. Access Control Rules

ACLsdefine security restrictionsat thefield, table, and record level.

These rules useconditions, scripts, and role-based permissionsto enforce security.

Example: A user with theitilrole may view incidents, but only users with theadminrole can delete them.

A. Role Assignment Rules

ServiceNowassigns roles to users, butroles alone do not define security rules.

ACLs controlwhat users can do, whilerolesonly grant potential access.

B. CRUD Rules

CRUD (Create, Read, Update, Delete)definespermission types, butnot security rules.

ACLs enforce CRUD operations based on roles and conditions.

C. Scripted User Rules

No such term as"Scripted User Rules"in ServiceNow security.

Possibly confused withScripted ACLs, which are part of Access Control Rules.

E. User Authentication Rules

Authentication rules controluser login mechanisms(LDAP, SSO, OAuth) but donot define access to data.

ACLs managedata security, while authentication ensuresusers are who they claim to be.

To monitor which users are performing impersonations in a ServiceNow instance, administrators can activate thesystem propertyglide.sys.log_impersonation. When enabled, this property logs impersonation activities in the system logs, providing full traceability of who is impersonating whom.

Here’s how it works:

By default, impersonation is not loggedunless this system property is explicitly activated.

Once enabled, all impersonation activities are recordedin thesyslogtable (System Log > All), making it easy to track when and by whom impersonations were performed.

This helps in security audits and compliance tracking, ensuring that only authorized users impersonate others in the system.

????Steps to Enable Logging of Impersonations:

Navigate toSystem Definition > System Properties.

In the filter navigator, search forglide.sys.log_impersonation.

Set the value totrue.

Save the changes.

????Alternative Verification Methods:

Check logs manually: Navigate toSystem Logs > Alland filter logs bymessagecontaining"impersonation".

Audit the impersonation role assignments underSystem Security > Roles.

????Reference:

ServiceNow KB Article:KB0717055 – How to Log Impersonations

ServiceNow Docs: Logging and Monitoring in ServiceNow

When using theData Pill Pickerin Flow Designer,dot-walkingis used to access fields inrelated tables.

The shortcut fordot-walkingin theData Pill Pickeris:????Ctrl

Dot-walkingallows users toaccess fields in referenced records.

For example, if you have anIncidentrecord with aCallerfield (which references thesys_usertable), you candot-walkto theCaller’s emailusing:

What is Dot-Walking?CopyEdit

incident.caller.email

This is useful whenbuilding conditions, flows, and reportsin ServiceNow.

A. Arrows– Arrow keys are used for navigation, but they do not support dot-walking.

B. Plus, Minus– These keys arenot used for dot-walkingin ServiceNow.

C. Ctrl C, Ctrl– These are copy-paste shortcuts, unrelated to dot-walking.

E. Shift F4, Shift F5– These do not have any function related to dot-walking.

ServiceNow Dot-Walking & Data Pill Picker

ServiceNow CSA Training Module:"Using Dot-Walking in Flow Designer and Reporting"

Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Detailed Explanation:

In ServiceNow,User Presencefeatures provide real-time visibility into record collaboration. This includes:

Option B:An icon that appears beside fields updated by other users, indicating recent changes.

Option E:A user presence icon showing initials of users currently viewing the record. These real-time indicators improve collaboration and prevent conflicts during data entry. (Reference: ServiceNow Documentation - Real-time Collaboration and User Presence)

=================

In theServiceNow Service Catalog module, tables have aOne-to-Many (1:M) relationship, meaning a single record in one table can relate to multiple records in another table. This is especially important for handling Service Catalog requests, as multiple items, approvals, and tasks may be associated with a single request.

One Request can have many Requested Items (REQ → RITM)

ARequest (REQ)is a container for multipleRequested Items (RITM).

When a user submits a catalog request, multiple items (such as a laptop and a phone) can be ordered in the same request.

Table Relationship:sc_request(Request) →sc_req_item(Requested Item)

One Requested Item can have many Approvals (RITM → Approval)

SomeRequested Items (RITM)require approval before being fulfilled.

For example, a laptop purchase might need approvals from both the IT department and a manager.

Table Relationship:sc_req_item(Requested Item) →sysapproval_approver(Approval)

One Requested Item can have many Catalog Tasks (RITM → SCTASK)

ARequested Item (RITM)can generate multipleCatalog Tasks (SCTASK)for different fulfillment teams.

For example, if an employee requests a new laptop, one task might go to IT to set it up, while another goes to finance for cost approval.

Table Relationship:sc_req_item(Requested Item) →sc_task(Catalog Task)

Breakdown of Correct Answers:Incorrect Answers Explanation:A.One Approval can have many Requests

Approvals do not relate to multiple requests. Instead, a request may contain multiple approvals.

E.One Cart can have many Requests

TheCartis only a temporary storage of items before checkout. Once submitted, it generates asingle Request (REQ), not multiple requests.

ServiceNow Product Documentation→ "Understanding Service Catalog Tables and Relationships"

ServiceNow Data Model→ "Request, Requested Item, and Catalog Task Relationships"

References from Certified System Administrator (CSA) Documentation:

In aServiceNow list view, eachrowrepresents asingle recordfrom the table being viewed.

For example:

In theIncident table (incident), each row representsone Incident record.

In theUser table (sys_user), each row representsone User record.

Each row = A single record

Each column = A field from the record

A. A filter

Filters are used tonarrow down resultsbut do not define what each row represents.

C. A table

The table contains multiplerecords, but eachrow only represents one record.

D. A field

Fields representindividual attributesof a record (e.g., "Priority" or "Category"), but a rowcontains multiple fieldsthat make up a record.

UI Actions related to Listsin ServiceNow provide ways to interact with and modify list data through differentUI elements.

A. List Links

Appear at thebottom of listsand provide actions such as"Create New"or"Save as Template."

B. List Control

Located in thelist title bar, allowing users to configure views, export data, and refresh lists.

C. List Buttons

Buttons added to a list form thattrigger specific actions, such as"Approve"or"Reject."

D. List Context Menu

Right-click menuon list records providing actions likeEdit, Delete, Assign, and Export.

E. List Override

No such feature called "List Override" exists in ServiceNow.

F. List Choices

This term is not a recognized UI Action for lists in ServiceNow.

In ServiceNow, toimport articlesinto aKnowledge Base (KB), a user must have thesn_knowledge_importrole.

sn_knowledge_import→ Required to import articles into a knowledge base.

sn_knowledge_contribute→ Allows users tocreate, edit, and publishknowledge articles butnot importthem.

sn_knowledge_admin→ Grantsfull administrative accessto manage the knowledge base, including permissions, categories, and workflows.

B. sn_knowledge_contribute– This role allowscontributing and editing articlesbut doesnot grant import capabilities.

C. Can contribute– Not a valid ServiceNow role; the correct role issn_knowledge_contribute.

D. Can import– Not a recognized role in ServiceNow. The correct role issn_knowledge_import.

ServiceNow Knowledge Management Roles

ServiceNow CSA Training Module:"Managing Knowledge Bases and Importing Articles"

Key Knowledge Management Roles:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

Natural Language Query (NLQ)in ServiceNow allows users tofilter a list by typing a natural language phrase, making it easier to search and retrieve data without manually building filters.

For example, users can type:

➡️"Show me all open incidents assigned to John Doe"

➡️"Incidents created this week"

The platforminterprets the phraseand automaticallyapplies the correct filterto the list.

A. Automatically select a filter, based on keywords–NLQ does not automatically select filters based on keywords; instead, itprocesses full phrasesinto a filter.

C. Predict the filter desired by the user–NLQ does not predict filters but rather converts typed queries into list filters.

D. Speak to the condition builder–NLQ does not interact with the condition builder directly; it translates text queries into filters.

E. Set list filter, using audible commands–NLQ does not supportvoicecommands, onlytypedqueries.

TheApplication Navigatoris the primary navigation panel in ServiceNow. It provides access to allapplications and modules, includingIncident Management, Change Management, Service Catalog, and more.

It is found on theleft-hand sideof the ServiceNow interface.

Users cansearch, expand, and collapseapplications for easy navigation.

Common applications includeIncident, Problem, Change, and CMDB.

A. Self-Service Module– This module is forend usersto submit requests but does not provide access to all applications.

C. Service Desk Homepage– This is adashboard, not a navigation tool.

D. Favorites– TheFavorites sectionstores frequently accessed modules but does not list all applications.

ServiceNow Navigation – Application Navigator

ServiceNow CSA Training Module:"Navigating the ServiceNow Platform"

Where is the Application Navigator Located?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

When working withHigh Security Settingsin ServiceNow (such assecurity_admin role), the systemtemporarily elevates your security privileges. To return tonormal admin security levels, the most effective way is tolog out and log back in.

Resets Elevated Security Permissions

Thesecurity_adminrole istemporarily assignedand will beremoved upon logout.

Logging out ensures that you return todefault admin security levels.

Prevents Unintended Access

If you remain inHigh Security Mode, you might makeunauthorized changes.

Logging outensures security compliance.

Best Practice in ServiceNow Security Administration

ServiceNow recommendslogging out after making security changestoavoid accidentally altering critical configurations.

Why Logging Out and Back In is the Correct Answer?

A. Use System Administration > Normal Security moduleIncorrect– No such module exists in ServiceNow.

B. Select Normal roleIncorrect– Youcannot manually remove thesecurity_adminrole. It expires uponsession logout.

D. Select Global Update SetIncorrect– TheUpdate Set selection does not affect security roles.

E. End impersonationIncorrect–Ending impersonation only applies when using the "Impersonate User" feature. It doesnot affect elevated security roles.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Managing High Security Settings????Elevating Security Roles in ServiceNow

ServiceNow Docs – Logging Out to Reset Security Roles????Best Practices for Security Admin Role

Official ServiceNow Documentation References:

Conclusion:The correct answer is:

C. Log out and back in

Logging outremoves elevated security roles, restoringnormal admin security levels.

In ServiceNow, aGroupis acollection of userswho share common responsibilities and access rights within the system. Groups are primarily used to facilitate:

Role-Based Access Control (RBAC):Assigning roles and permissions collectively to a set of users.

Task Assignment:Groups can be assigned to handle incidents, change requests, and approvals.

Notification Management:Groups can be used for sending system notifications to multiple users at once.

C. A collection of users

Agroupin ServiceNow consists of multiple users who work together on tasks, approvals, or system activities.

Groups simplify user administration by allowing permissions and responsibilities to be assigned collectively instead of individually.

Examples of groups:

Service Desk(handles incident tickets)

Change Advisory Board (CAB)(approves change requests)

HR Team(manages HR cases)

A. An escalation pod

ServiceNow doesnotuse the term"escalation pod"to define a group.

Escalations are handled through priority rules and workflows, not groups.

B. A department

Adepartmentis an organizational unit (e.g., HR, IT, Finance), while agroupis a functional collection of users.

Departments and groups are separate entities in ServiceNow.

D. A collection of subject matter experts

While some groupsmayconsist of SMEs, this isnot the definitionof a group.

Groups can have users of different expertise levels, not just experts.

E. A team of users

Although groups may act as "teams," the officialServiceNow definitionof a group isa collection of users, which is more precise.

"Team" is a more informal term, while "group" is the structured term used in the platform.

Thesecurity_adminrole in ServiceNow is required to make changes toHigh Security Settings(now part ofSystem Security Settings).

Modify high-security settingsin ServiceNow.

Elevate privilegesto make changes to sensitive security configurations.

Manage Access Control Lists (ACLs)to define security rules.

Users with theadminrole alonecannot modify high-security settings.

Thesecurity_adminrole requireselevationvia the"Elevate Role" optionin the user menu.

This ensures thatonly authorized administratorscan modify security-related configurations.

B. sn_ad_admin– No such role exists in ServiceNow.

C. high_sec_admin– This is not a valid ServiceNow role.

D. admin– Theadmin role alonedoesnot grant access to high-security settingswithoutelevating to security_admin.

ServiceNow Security Admin Role and Elevated Privileges

ServiceNow CSA Training Module:"Managing Security Settings and Access Controls"

What Can the security_admin Role Do?Why Elevation is Required?Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow, aBreadcrumbis thestring of filter criteriadisplayed at the top of a list when filters are applied. Breadcrumbs help usersnavigate and refine filterswithout having to manually edit conditions.

Navigate to a list view(e.g., Incidents, Requests).

Apply a filter (e.g., "Priority is High" AND "State is New").

Abreadcrumb stringappears, displaying the filter conditions.

Users canclick on different parts of the breadcrumbto adjust or remove filter conditions dynamically.

A. Topic

Topics are used inKnowledge Management and Virtual Agentbut do not represent filter criteria.

B. Choice

A Choice refers todropdown optionsin ServiceNow fields, not filters.

D. Menu

Menus provide navigation options, but they do not display filters.

Detailed Explanation:

In ServiceNow, list views can be customized to group records by specific fields to enhance data organization. To group records by theCategorycolumn:

Option Aallows administrators to use the list context menu to group records by category, providing easy data visualization based on the selected column.

Option Dinvolves using the Group icon (usually located in the column header) and selecting the category for grouping. These grouping options simplify navigating and analyzing data by sorting records based on relevant columns, like Category. (Reference: ServiceNow Documentation - List Controls and List Context Menu)

=================

When designing Service Catalog items,Variable Setsallow you toreuse common fields across multiple catalog items.

Instead ofcreating the same four fields(Requested for, Requested by, Approving manager, Delivery instructions)80 times,

You candefine them once in a Variable Setand apply it to all catalog items.

Best Approach (Correct Answer: A)Advantages of Using a Variable Set:Reusability– The same Variable Set can be added to multiple catalog items.

Consistency– Ensures the four mandatory fields are always included.

Easier Maintenance– Changes to these fields only need to be made inone place.

B. Create a Record Producer that contains the four fields →Incorrect

ARecord Produceris used to create records in a specific table (e.g., Incident, Request, Change).

It isnot designed for defining reusable fieldsacross multiple catalog items.

C. Create a Flow Designer Action with Variable Set Data Pill →Incorrect

Flow Designeris for process automation, not fordefining form variables.

It does not allow you to create reusable fields for catalog item forms.

D. Create an Order Guide and hide variables as needed →Incorrect

Order Guidesare used for ordering multiple catalog items together.

They do not provide a structured way to manage common fields across different catalog items.

E. Create a Variable Set Template →Incorrect

There is no concept of a"Variable Set Template"in ServiceNow.

Variable Setsthemselves act as templates.

Why Other Options Are Incorrect?

Using Variable Sets in Service Catalog

Building Service Catalog Forms

Official ServiceNow Documentation Reference:

TheConfiguration Management Database (CMDB)inServiceNowstores information aboutconfiguration items (CIs)and theirrelationships.

cmdb (Configuration Management Database)The main parent table for all CMDB-related data.

Storescore configuration item (CI) data.

Other CMDB-related tables inherit from this table.

cmdb_ci (Configuration Items Table)Stores individual configuration items (CIs).

Every CI (e.g., servers, network devices, software) is stored in this table or one of its child tables.

This tableextendscmdb.

cmdb_rel_ci (CI Relationships Table)Stores relationships between CIs.

Defines how CIsconnect to each other(e.g., "server hosts application").

Helps withService Mapping and Impact Analysis.

The Three Key CMDB Tables:

A. omadb_rel_ciIncorrect– Not a standard ServiceNow CMDB table.

B. sn_emdbIncorrect–sn_emdbisnot a CMDB tablein ServiceNow.

C. sn_emdb_ciIncorrect– No such table inServiceNow CMDB architecture.

E. sn_emdb_bakIncorrect– No suchbackup tablein ServiceNow CMDB.

G. emdb_bakIncorrect– No suchServiceNow CMDB tableexists.

Incorrect Answer Choices Analysis:

ServiceNow Docs – CMDB Core Tables????CMDB Tables Overview

ServiceNow Docs – Understanding CI Relationships????CMDB Relationship Tables

Official ServiceNow Documentation References:

Tochange the default layout of a task listin ServiceNow, you shouldright-click on any column headerand selectConfigure > List Layout.

Navigate to the Task list view(e.g., Incident, Change, or another task-based list).

Right-click on any column header(e.g., "Number" or "Short Description").

SelectConfigure > List Layout.

Add, remove, or reordercolumns as required.

ClickSaveto apply changes.

B. Right-click List Gear icon > Configure > Columns

TheGear icon(⚙) allowspersonalizing columns for an individual user, butdoes not change the default list layout for all users.

C. Click List Context Menu > Personalize List

Personalization only affects the user’s view, not theglobal list layout.

D. Click List Context Menu > Configure Columns

There isno "Configure Columns" optionin the list context menu; the correct path is"Configure > List Layout".

ServiceNow List Layout Configuration

ServiceNow CSA Training Module:"Working with Lists and Configuring Layouts"

Steps to Modify the Task List Layout:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

TheAutomated Test Framework (ATF)is thebuilt-in testing frameworkin ServiceNow used totest applications, including Server-side scripts and logic.

Enablesautomated testing of ServiceNow applicationswithout manual effort.

Can testserver-sidescripts (e.g., Business Rules, Script Includes, and Workflows).

SupportsUI testingfor forms, lists, and portals.

Reduces testing time and enhancesrelease reliability.

ServiceNow is alow-code/no-codeplatform, so ATF provides aplatform-specifictesting tool.

ATF allowstest creation without coding, making it easy for administrators and developers to use.

Integrates with Continuous Integration (CI/CD) pipelinesto ensuresmooth updates.

Key Features of ATF:Why ATF is Used for Testing ServiceNow Applications?

A. Selenium →Incorrect

Seleniumis used forweb UI automation, but it isnot built into ServiceNow.

ATF is thepreferredtesting framework for ServiceNow applications.

B. Test Driven Framework (TDF) →Incorrect

No such frameworkcalled "Test Driven Framework" in ServiceNow.

TDD (Test-Driven Development)is asoftware development methodology, not a testing tool.

C. JUnit →Incorrect

JUnit is a Java-based testing frameworkused for Java applications.

ServiceNow scripts useJavaScript, not Java.

Why Other Options Are Incorrect?

Automated Test Framework (ATF)

Official ServiceNow Documentation Reference:

Understanding CMDB and Use Case Modeler:

TheCMDB (Configuration Management Database)contains information aboutConfiguration Items (CIs)and their relationships.

CMDB Use Case Modeleris a tool within ServiceNow that helps users visualize and analyzeCIs and tablesrelated to a specific business use case.

Why CMDB Use Case Modeler is the Correct Answer:

Itmaps tables and CIsto specific use cases, providing an organized view ofhow different components interact.

It helpsanalyze dependenciesandunderstand the impactof changes on IT services.

It assists withtroubleshooting and compliance checksby offering agraphical representation of CIs.

Why Other Answers Are Incorrect:

A. Scenario Dashboard→ Not a recognized ServiceNow tool for viewing CIs or tables related to a use case.

B. CI Use Case Modeler→ No such feature exists; it may be confused with the correct answer (CMDB Use Case Modeler).

D. Common Service Data Model (CSDM) product view→ TheCSDMprovides a standardized framework for organizing CMDB data but doesnot specifically offer a toolfor viewing tables and CIs related to a use case.

Best Practice Solution:

To access CMDB Use Case Modeler in ServiceNow:

Navigate toCMDB Workspace→Use Case Modeler

Select the relevant use case and analyze the relatedCIs and tables

Ensure that your CMDB isproperly populated and maintainedto get accurate results.

TheCatalog Admin [catalog_admin]role:

Inherits permissions from both:catalog role(Basic Service Catalog access)user_criteria_admin role(User Criteria management)

Has additional permissions to:Create and manage Catalog Items and ServicesConfigureCatalog Categories, Order Guides, and Variables

A. Item Admin [sn_item_admin] →Incorrect

This role does not inherituser_criteria_adminpermissions.

It isspecific to managing Catalog Itemsbut does not have full Catalog Admin permissions.

B. Sys Admin [sys_admin] →Incorrect

Thesys_adminrole has full system access but is notService Catalog-specific.

D. Catalog Author [sn_catalog_write] →Incorrect

TheCatalog Authorrole canedit catalog itemsbutcannot create new ones.

Why the Other Options Are Incorrect?

ServiceNow Catalog Roles

Official ServiceNow Documentation Reference:

To rename a field label in ServiceNow (such as changing "Priority" to "PValue"), you must eitherupdate the dictionary definitionorchange the field label.

Right-click on the "Priority" field labelin the form.

Select"Configure Dictionary".

Update the"Label" fieldto "PValue".

Save the changes.

The new label will now be reflected across the system where applicable.

Right-click on the "Priority" field labelin the form.

Select"Configure Label".

Update thelabel textto "PValue".

Save the changes.

This methodonly changes the field labelfor display purposeswithout affecting the underlying database structure.

B. Right-click on Priority and select Configure Display Settings

There isno "Configure Display Settings"option when right-clicking on a field label in ServiceNow.

D. Right-click on Priority and select Configure Column

"Configure Column" is used forlist views, not for changing field labels on forms.

ServiceNow Field Labels and Dictionary

ServiceNow CSA Training Module:"Configuring Forms and Fields"

Option 1: Configure Dictionary (Recommended for Full Customization)Option 2: Configure Label (Quick Change for Display Purposes)Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation: