In ServiceNow, users can quickly generate a report from a list view without needing to navigate to the Reports module. The two main ways to do this are:

Steps:

Open any list view (e.g., Incident, Change, or any table-based list).

Click thethree-line (hamburger) context menuon the top-left of the list.

SelectCreate Reportto generate a basic report based on the current list view.

Modify report settings (e.g., visualization type, filters, groupings).

Save the report for future reference.

Steps:

Apply the necessary filters to refine the list view.

Right-click on acolumn header(e.g., Priority, State, Category).

SelectCreate Reportfrom the context menu.

Configure the report visualization and save it if needed.

1. Using the Context Menu (Option C)2. Right-click on a Column Header (Option E)

Incorrect Answer Choices Explanation:A. Click on filter breadcrumb, drag and drop on the Report > Create New module

There is no such drag-and-drop functionality for report creation in ServiceNow.

B. Click Funnel, define filter conditions, click Create Report

TheFunnel iconis used to filter list views but does not directly generate reports.

D. Apply filter, right-click on column header, select Bar Chart

There is no direct " Bar Chart " option available when right-clicking on a column header.

Creating Reports from List Views

ServiceNow KB Article: KB0014148

Official CSA Documentation Reference:

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:

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, users can log into theService Portalusingcertificate-based authentication methods. The two commonly supported methods are:

ACACis a smart card issued by theU.S. Department of Defense (DoD).

It is used by military personnel, contractors, and government employees for secure authentication.

ServiceNow supportsCAC authenticationby integrating with external identity providers.

APIV cardis used byU.S. federal agenciesfor authentication.

It followsFederal Information Processing Standard (FIPS) 201for identity verification.

ServiceNow allows users to log in using PIV authentication, ensuringsecure accessto government and enterprise systems.

1. Common Access Card (CAC) – (Correct Answer)2. Personal Identity Verification (PIV) – (Correct Answer)

Both CAC and PIV are widely recognized certificate-based authentication methodsused in ServiceNow for secure user authentication.

They provide multi-factor authentication (MFA)and meet federal security standards.

Why " C. CAC " and " E. PIV " are the Correct Answers?

A. Extended Validation Access (EVA) – Incorrect

No such authentication method exists in ServiceNow.Extended Validation (EV) certificatesare used for website security, not user authentication.

B. Organization Verification Card (OVC) – Incorrect

Not a recognized ServiceNow authentication method.

D. Domain Authentication Card (DAC) – Incorrect

No such authentication method exists in ServiceNow.

Explanation of Incorrect Options:

ServiceNow Docs: Common Access Card (CAC) Authentication

ServiceNow Docs: Personal Identity Verification (PIV) Authentication

ServiceNow CSA Study Guide – Authentication Methods in ServiceNow

References from 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.

TheServiceNow platformprovides variousinterfacesfor users to interact with the system based on their role and requirements. These interfaces cater to different use cases, such as web-based, mobile, and portal-based access.

Now Mobile Apps (A) –Correct

ServiceNow providesNow Mobile applicationsfor bothiOS and Android.

These apps allow users to access self-service options, request services, check approvals, and complete tasks from mobile devices.

Apps includeNow Mobile, Field Service Mobile, and Mobile Agent.

Service Portals (D) –Correct

Service Portalsprovide auser-friendly web interfacethat allows users tosubmit requests, search for knowledge, and interact with catalog itemsin a simplified way.

Service Portals are customizable and used forself-service and customer-facing interactions.

Now Platform® User Interfaces (E) –Correct

This includes the standardUI16 (Current Web Interface), UI Builder for custom interfaces, and theClassic UIfor legacy systems.

Users can access ServiceNow throughdesktop web browsers, mobile web interfaces, and UI frameworks.

B. Agent Control Center(Incorrect)

No such predefined interface exists in ServiceNow as " Agent Control Center. "

C. Back Office Dashboard(Incorrect)

This is not a standard ServiceNow interface but may be a custom-built dashboard.

F. Field Service Taskboard(Incorrect)

This is afeaturewithinField Service Management (FSM), not a platform-wide interface.

ServiceNow User Interfaces Overview:https://docs.servicenow.com/en-US/bundle/utah-platform-user-interface/page/administer/navigation-and-ui/concept/c_NavigationAndTheUserInterface.html

Now Mobile App:https://docs.servicenow.com/en-US/bundle/utah-now-mobile/page/administer/service-now-mobile/concept/now-mobile-overview.html

Types of Interfaces in ServiceNow:Incorrect Options:Official References from Certified System Administrator (CSA) Documentation:

TheBasic Configuration UI 16 modulein ServiceNow allows administrators to make basic UI customizations without needing to modify code or system properties manually. These settings apply to theoverall look and feelof the instance.

Banner Image (Option A)

Allows admins to change theServiceNow banner logoat the top of the page.

This is useful for branding the instance with a company’s logo.

Browser Tab Title (Option C)

Changes thetitle displayed on the browser tabwhen accessing the ServiceNow instance.

Helps customize the instance’s branding for different user environments (e.g., " IT Service Portal " instead of " ServiceNow " ).

System Date Format (Option D)

Allows admins toset the date formatdisplayed across the instance.

Helps standardize date display based on organizational or regional preferences (e.g.,MM/DD/YYYY vs. DD/MM/YYYY).

Customizable Elements via Basic Configuration UI 16:

Why Are the Other Options Incorrect?B. Record Number Format

Incorrect:The format of record numbers (such asINC0010001 for incidents) is controlled viaSystem Definition → Number MaintenanceandNOTin Basic Configuration UI 16.

E. Form Header Size

Incorrect:The form header size isnot directly customizable through Basic Configuration UI 16.

Form layout and styling changes are managed throughUI Policies, Client Scripts, or custom CSS configurations.

Reference from Certified System Administrator (CSA) Documentation:???? ServiceNow Docs – Basic Configuration UI 16

???? ServiceNow UI Customization Documentation

" Basic Configuration UI 16 provides a simple way to modifybanner images, browser titles, and system-wide date formats. "

Conclusion:The correct answers are:

A. Banner Image(Customizes the instance’s logo)

C. Browser Tab Title(Changes the browser tab text)

D. System Date Format(Sets the instance-wide date format)

???? Understanding Basic Configuration UI 16 is important for ServiceNow administratorsto quickly apply branding and instance-wide display settings without modifying system properties manually.

ServiceNow providesfive primary rolesthat define access and permissions within the platform. These roles help structure user responsibilities and ensure that users only have access to the necessary functions.

Thehighest level of accessin ServiceNow.

Can manage all platform features, applications, data, and configurations.

Has control overusers, security settings, system properties, and scripting capabilities.

Example: A ServiceNow admin configuring new workflows, modifying tables, or setting up instance-wide settings.

Manages specific applications or functionalities within ServiceNow.

Includes roles such as:

knowledge_admin(Manages Knowledge Base)

report_admin(Manages Reports)

catalog_admin(Manages Service Catalog)

Example: A Knowledge Base Administrator controlling access to articles and updating knowledge categories.

Users with theITIL rolewho perform IT Service Management (ITSM) tasks.

Cancreate, update, and resolve recordssuch as incidents, problems, changes, and requests.

Example: A service desk agent handling incidents and requests.

Users with theApprover rolecanapprove or reject requests, such as change requests or access requests.

Can view or modify approval records directed to them but cannot fulfill other ITIL tasks.

Example: A manager approving a new software installation request.

Basic userswith no assigned roles.

Cansubmit requests, view their own tickets, and access public pages(e.g., Knowledge Base, Catalog).

Example: An employee submitting a request for laptop repair via the ServiceNow portal.

1. System Administrator (admin)2. Specialized Administrator3. Fulfiller (ITIL Role)4. Approver5. Requester (Employee Self-Service - ESS)

These roles form thefoundation of role-based access control (RBAC)in ServiceNow.

They ensure that usersonly access the data and functions relevant to their job responsibilities.

Additional roles can be assigned based on business needs, but these five cover the core platform functionalities.

Why These Are the Provided Roles in ServiceNow:

ServiceNow Documentation:User Roles in ServiceNow

CSA Exam Guide:CoversSystem Administrator, Specialized Administrator, Fulfiller, Approver, and Requesteras the standard user roles.

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

A. System Administrator, B. Specialized Administrator, C. Fulfiller, D. Approver, E. Requester

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:

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:

TheApplication Navigator (App Navigator) search fieldin ServiceNow allows users to quickly findapplications, modules, and favoritesby typing relevant keywords. It helps in easy navigation by filtering available options as the user types.

Thefour correct answersdescribe what the App Navigator search field can return:

The search field can return bothapplicationsand their respectivemodulesin the left navigation panel.

Example: Searching for " Incident " will return:

Application: " Incident "

Modules: " All " , " Open " , " Resolved " , " Create New "

Modulesare specific functionalities within an application.

Searching by a module name directly will display results that match the keyword.

Example: Searching for " Create New " will return modules like:

" Create New Incident "

" Create New Change Request "

The search field supports findingfull applicationsby their name.

Example: Typing " Change " will display theChange Managementapplication and its related modules.

If a user has marked specific modules or applications asFavorites, they will appear in search results.

This helps users quickly access commonly used features.

1. Names of Applications and Modules (Correct)2. Names of Modules (Correct)3. Names of Applications (Correct)4. Favorites (Correct)

Why the Other Options Are Incorrect:E. History Records (Incorrect)

TheHistory tabin the navigation panel showsrecently accessed records, but it isnot searchable through the App Navigator.

Instead, users can find history under:

History Module(System Settings > History)

Recent History Tabin the left navigation

F. Titles of Dashboard Gauges (Incorrect)

Dashboard Gaugesare visual elements onPerformance Analytics or Reporting Dashboardsand arenot searchablein the App Navigator.

Instead, dashboards and reports are found under:

Self-Service > Dashboards

Performance Analytics > Dashboards

A ServiceNow user wants toquickly access the " All Incidents " module.

They type " incident " into the App Navigator search.

The search results return:

Incident (Application)

All (Module)

Assigned to Me (Module)

Resolved (Module)

Example Use Case:This allows for quick navigation without manually expanding application menus.

TheConfiguration Management Database (CMDB)in ServiceNow is a centralized repository that stores information aboutConfiguration Items (CIs), their attributes, and relationships. It plays a crucial role in IT Service Management (ITSM), helping organizations track assets, dependencies, and service impacts.

Thefour correct concepts associated with the CMDBare:

The CMDB is structured usingtablesandfieldswithin the ServiceNow database.

Different tables store different types ofConfiguration Items (CIs)such as servers, applications, and network devices.

Example CMDB Tables:

cmdb_ci(Base CMDB Table)

cmdb_ci_server(Stores server-specific CIs)

cmdb_ci_database(Stores database-related CIs)

Each table hasfieldsthat store attributes (e.g.,Serial Number, IP Address, Location).

The CMDB is essentially adatabasethat holds detailed information about IT assets and their relationships.

It enables organizations to maintain an accurate inventory of IT infrastructure.

The database helps withincident management, change management, and asset tracking.

Dependency Viewprovides agraphical representationof how Configuration Items (CIs) are related.

This visualization helps IT teamsunderstand dependencies, impact analysis, and root cause analysis.

Example:

If adatabase servergoes down, theDependency Viewcan show which applications and services will be affected.

The CMDB supports variousIT Service Management (ITSM) processes, such as:

Incident Management(linking incidents to affected CIs)

Change Management(analyzing the impact of changes on CIs)

Problem Management(identifying root causes of recurring issues)

The CMDB ensures that these processes operate with accurate and updated asset data.

1. Tables and Fields (Correct)2. A Database (Correct)3. The Dependency View (Correct)4. Service Processes (Correct)

Why the Incorrect Option is Wrong:B. User Permissions (Incorrect)

Whileuser permissions(such as roles and access controls) exist in ServiceNow, they arenot a fundamental concept of the CMDB itself.

Permissions (likecmdb_readoradmin) controlwho can access and modify the CMDB, but they are notcore CMDB components.

AnIT administratorwants to checkwhich business services depend on a specific database serverbefore performing maintenance.

Using theCMDB Dependency View, they see that the database server is linked to anemail serviceand acustomer portal.

This insight helps them plan achange requestto notify impacted users before the server is taken offline.

Example Use Case:

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:

TheUser Menuin ServiceNow is accessible from the top-right corner of the interface by clicking on the user’s avatar or name. This menu provides various options that allow users to manage their sessions, roles, and impersonation settings.

The three correct actions a user can select from the User Menu are:

TheLog Outoption allows users to end their session and securely exit ServiceNow.

It is an essential feature for security and session management.

Location:User Menu > Log Out

Users with appropriate privileges (such as administrators) canelevate their rolesto gain temporary access to higher permissions.

This is primarily used when a user needs elevated access (e.g.,security_admin) to perform specific administrative actions.

Location:User Menu > Elevate Roles

Example:

A system administrator can elevate their role tosecurity_adminto access security-related configurations.

TheImpersonate Userfeature allows an administrator to act as another user without needing their credentials.

This is useful for troubleshooting, testing permissions, and verifying user-specific configurations.

Location:User Menu > Impersonate User

Example:

An admin impersonating a regular user can verify that the correct permissions and UI settings are applied.

1. Log Out ServiceNow (Correct)2. Elevate Roles (Correct, for Admin Users)3. Impersonate Users (Correct, for Admin Users)

Why the Other Options Are Incorrect:A. Send Notifications (Incorrect)

The User Menudoes notinclude an option to send notifications.

Notifications (emails, push notifications, SMS) are managed through:

System Notification > Email > Notifications

Outbound SMS or Messaging Settings

E. Order from Service Catalog (Incorrect)

Users can order items from theService Catalog, butthis action is not available from the User Menu.

Instead, users access the Service Catalog through:

Self-Service > Service Catalog

Requests and Catalog Items pages

F. Approve Records (Incorrect)

Users canapprove recordsif they have approval roles (e.g.,approver), but this action is not directly available from theUser Menu.

Approvals are managed through:

My Approvalsin Self-Service

The Approvals module in theServiceNow application navigator

In ServiceNow,tablesare fundamental components of the platform ' s database structure. A table consists ofrecords (rows)andfields (columns)that store data.

Arecordis an individual entry in a table, similar to a row in a traditional database.

Each record represents a single entity (e.g., an incident, a user, a request).

Records are stored uniquely in the system and are identified by aSys ID(a globally unique identifier).

Afieldis an attribute of a record, like a column in a database.

Each field has a specificdata type(e.g., string, integer, date, reference).

Fields define what type of information can be stored in a record.

1. Records (Rows) – Correct Option2. Fields (Columns) – Correct OptionExample:TheIncident [incident]tableSys ID

Number

Short Description

Caller

State

123abc

INC001

System crash

John D

New

456def

INC002

Network issue

Jane S

Open

Records:INC001, INC002 (each row is a record).

Fields:Number, Short Description, Caller, State (each column is a field).

B. Lists – Incorrect

Listsare aviewof table data but are not a part of the table itself.

A list displays multiple records from a table but does not define the structure of a table.

C. Forms – Incorrect

Formsare user interfaces used to view or edit single records.

A form allows users to interact with the data stored in a table but is not part of the table structure itself.

ServiceNow Docs: Tables and Records

ServiceNow CSA Study Guide – Understanding Tables, Records, and Fields

ServiceNow Product Documentation: List and Form Views

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

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. "

InServiceNow,Related Listsdisplayrecords that are linked to the current recordthrough relationships. Tomanage records within a Related List, the following buttons are commonly used:

1. " New " ButtonCreates a new record in the related list

Example: In theUser Form, the " Groups " related list has a " New " button toadd a new Group membership.

2. " Add " ButtonAdds an existing record to the related list

Example: In theIncident Form, the " Affected CIs " related list has an " Add " button toassociate existing CIswith the incident.

3. " Edit " ButtonModifies existing relationships

Opens amulti-record selection view, allowing users toadd or remove multiple related records at once.

Example: EditingUser Rolesin theUser Formallows selectingmultiple rolesat once.

A. PublishIncorrect– " Publish " is used inKnowledge Managementfor articles, not related lists.

D. ManageIncorrect– There isno standard " Manage " buttonin Related Lists.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Related Lists Overview???? Using Related Lists

ServiceNow Docs – Configuring Related Lists???? Configuring Related Lists

Official ServiceNow Documentation References:

In ServiceNow,rolesdetermine what users can see and do within the platform.

The IT useronly sees the Self-Service homepageinstead of the full ServiceNow interface, including task records.

This suggests that their accountdoes not have the necessary role(s) to access task records.

Issue:Why the Correct Answers?D. Their user account does not have the itil role

Theitil roleis required to work with ITSM task records (e.g., Incidents, Problems, Changes).

Without this role, usersonly have access to the Self-Service portal.

E. Their user account does not belong to any groups, which contain the itil role

Even if a user is not directly assigned theitil role, they can inherit itthrough a group membership.

If theiruser account is not part of an ITSM-related groupthat has theitil role, they will not be able to access tasks.

A. Their user account failed LDAP authentication →Incorrect

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

In this case, theyare logged in but only see Self-Service, meaning authentication is not the issue.

B. Their user account is not logged in properly →Incorrect

If the login was incorrect, they would belogged out or receive an error message.

The issue here isa lack of permissions, not a login failure.

C. Their user account was not approved by their manager →Incorrect

Manager approval is not required for standard ITSM roles and access.

Why Other Options Are Incorrect?

User Roles in ServiceNow

Assigning Roles and Group Memberships

Official ServiceNow Documentation Reference:

In ServiceNow,tagsare used to categorize and organize records for quick access. When managing tags, users can control theirvisibilityby settingwho can see them.

B. Everyone

The tag ispublicand visible to all users in the instance.

Example: AService Desk teamcreates a " High Priority " tag that everyone can use.

C. Groups and Users

Tags can be restricted to specificgroupsorindividual users.

Example: ASecurity Teamcreates a tag only visible toIT Security staff.

E. Me

Tags can beprivate, meaning only the creator (you) can see them.

Example: A user creates a " Follow-up " tag for theirownpersonal tracking.

A. Admins

Incorrect—Admins can manage tags, but " Admins " isnota visibility setting.

Instead, visibility is set toEveryone, Groups, or Me.

D. Roles and Permissions

Incorrect terminology—ServiceNowdoes notprovide a tag visibility setting based on " Roles and Permissions. "

Tags are assigned based onspecific users or groups, not roles.

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)

=================

The ServiceNow platform providespre-built workflowsthat help organizationsautomate processesacross different domains. These workflows are designed to streamline operations, improve efficiency, and enhance user experience. Thethree primary types of workflowsincluded in the platform are:

Employee Workflows– Designed to improve employee experiences, covering HR services, onboarding, workplace services, and more.

Customer Workflows– Focused on customer service management (CSM), case management, field service management, and proactive customer engagement.

IT Workflows– These workflows enable IT Service Management (ITSM), IT Operations Management (ITOM), and IT Business Management (ITBM) for efficient IT operations.

B. Infrastructure Workflows–No specific " Infrastructure Workflows " exist as a built-in category in ServiceNow. Infrastructure processes are generally managed underIT Workflows (ITOM/ITSM).

C. Federal Workflows–Not an official workflow category. Federal agencies useServiceNow’s Government, Risk, and Compliance (GRC) solutions, but this is not classified as a workflow.

D. Manufacturing Workflows–ServiceNow does not have a dedicated " Manufacturing Workflows " category. However, manufacturers often useCustomer and IT Workflowsfor managing operations.

EveryServiceNow instancecomes with a set ofdefault tablesthat supportcore platform functionality.

User (sys_user)Stores user records for authentication and authorization.

Contains user details such asusername, email, roles, department.

Incident (incident)Stores incident records for ITSM (IT Service Management).

Part of thedefault ITSM applicationused for managingissues and requests.

Task (task)Base table for all task-related records in ServiceNow.

Many other tables (e.g., Incident, Change, Problem)extend from Task.

Storescommon task fields like Assignment Group, State, and Short Description.

The Three Default Tables in ServiceNow:

C. ItemIncorrect– No default table named " Item " exists in ServiceNow.

Possible confusion withsc_cat_item (Service Catalog Items), but this is part of theService Catalogmodule, not a core default table.

D. IssueIncorrect– No " Issue " table exists by default in ServiceNow.

Possible confusion withProblem Management(problemtable), which is separate from Incident Management.

E. ProjectIncorrect–Project Management(pm_project) is part of theProject Portfolio Management (PPM)plugin, which isnot enabled by default.

Incorrect Answer Choices Analysis:

ServiceNow Docs – Default Tables Overview???? ServiceNow Table Structure

ServiceNow Docs – Task Table and Extensions???? Understanding Task-Based Tables

Official ServiceNow Documentation References:

In ServiceNow,UI Actionsare customizable elements that enhance user interaction withforms,lists, and other UI components. When applied to forms, UI Actions allow users to trigger workflows, scripts, or system operations efficiently.

A. Form Context Menu

TheForm Context Menu(accessible by right-clicking on a form header or field) contains UI Actions such as:

Save,Insert,Insert and Stay,Configure Form Layout, etc.

Admins can customize this menu to include additional actions.

C. Form Buttons

Buttonsappear at the top or bottom of a form, allowing users to take specific actions.

Examples include:

Submit,Update,Resolve,Approve,Reject

These actions can be customized using UI Action scripting.

D. Form Links

Form Linksappear as clickable links at the bottom of a form.

Example:

“Show Related Incidents”link on an incident form.

These links allow users to navigate quickly between related records.

B. Form View

Form Viewis a layout configuration that determines how fields appear but isnota UI Action.

UI Actionstriggeractions, while Form Viewsdefine appearance.

E. Form Columns

Form Columnsrefer to the arrangement of fields within a form.

Columns help withform designbut do not serve as UI Actions.