Free certification test prep

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:

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:

In ServiceNow, metrics are essential tools used to track and measure key performance indicators (KPIs) related to IT Service Management (ITSM) processes. They help organizations assess how effectively they are meeting their objectives by collecting data over time.
Understanding ServiceNow Metrics:
Definition of a Metric:
A metric in ServiceNow refers to a method of measuring and evaluating the performance and effectiveness of IT service management processes over time.
It allows organizations to track changes in records and measure how long specific conditions exist within a workflow.
Key Characteristics of a Metric:
It is used to assess process performance and evaluate efficiency within IT services.
It provides quantifiable data to analyze trends and improvements in Service Management.
Common use cases include tracking incident resolution times, change request approvals, and SLA compliance.
Why Answer “C” is Correct:
✔️ “A metric is used to measure and evaluate the effectiveness of IT service management processes.” This definition aligns precisely with how ServiceNow defines metrics-they track, measure, and analyze the efficiency of various ITSM processes over time.
Metrics help organizations understand service performance trends and make data-driven decisions.
Why the Other Answers Are Incorrect:
❌ A. “A metric is a report gauge used on homepages to display real-time data.” Incorrect because gauges are UI elements that visualize data from reports or metrics but are not themselves metrics. Metrics collect and measure data, whereas gauges display the information.
❌ B. “A metric is a time measurement used to report the effectiveness of workflows and SLAs.” Incorrect because while time-based metrics exist (e.g., tracking how long an incident stays in a particular state), metrics in ServiceNow are broader and not limited to time measurement alone.
❌ D. “A metric is a comparative measurement used to report the effectiveness of workflows and SLAs.” Incorrect because metrics are not necessarily comparative; they are absolute measures of process effectiveness. Metrics provide raw performance data, which can later be compared or analyzed over time.
Reference from the Certified System Administrator (CSA) Documentation:
ServiceNow CSA Study Guide – Reporting & Performance Analytics
ServiceNow Docs: Metrics Definition & Configuration (ServiceNow Docs – Metrics) ServiceNow Performance Analytics & Reporting Overview

The customer .* ACL rule would grant access to all rows and all fields to both the customer_table_admin and customer_table_user roles because it uses a wildcard (*) to match any operation on the customer table. The other options are either too restrictive or too broad.
References1: Access control list rules – Product Documentation: Utah – ServiceNow4: Access Controls – ServiceNow Elite

To display reminder messages or alerts to users as they interact with forms in ServiceNow, Client Scripts are used. Specifically, an onSubmit Client Script can be configured to display a message or perform validation just before the form is submitted by the user. This script runs on the client (browser) and can prevent submission or prompt the user with informational messages.
Business Rules execute on the server and cannot directly interact with the user interface in real-time. Policies and Data Policies enforce data consistency but do not provide user messages or reminders during form submission.
Therefore, the Client Script is the correct mechanism to display a reminder message dynamically as the incident is submitted.
References:
ServiceNow System Administrator Study Guide, Client Scripts section
ServiceNow Docs: Client Scripts – onSubmit
ServiceNow Docs: Data Policy Overview

A UI Policy is the preferred no-code approach in ServiceNow to dynamically control the mandatory, read-only, or visibility state of form fields based on specified conditions. Unlike Client Scripts, which require JavaScript coding, UI Policies provide an easy-to-configure, rule-based solution.
Why Use UI Policies?
They allow administrators to control form behavior without scripting.
They are faster and more efficient than Client Scripts.
They run on the client-side, meaning changes occur dynamically as users interact with the form.
How UI Policies Work:
Define conditions (e.g., “Priority is High”).
Set actions (e.g., make “Due Date” mandatory, read-only, or hidden).
Apply the UI Policy to the form automatically when the condition is met.
Why Other Options Are Incorrect:
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 a low-code rather than a no-code solution.
C . UI Script → UI Scripts are reusable JavaScript libraries, not designed for controlling form fields.
D . UI Rule → No such feature exists in ServiceNow.
Reference:
ServiceNow Docs: UI Policies
ServiceNow Docs: Field Administration – Data Policies
ServiceNow CSA Official Study Materials

By default, ServiceNow encrypts data in transit using industry-standard Transport Layer Security (TLS) protocols. This ensures that any data transmitted between the client and the ServiceNow platform, or between ServiceNow and integrated systems, is encrypted and protected from interception or tampering.
While ServiceNow also offers options for data at rest encryption and customer-managed encryption keys, these features often require additional configuration or subscription services. Encryption of data in use (while data is being processed in memory) is a more advanced concept and not provided by default.
Thus, encryption of data in transit is the baseline encryption feature included automatically in all ServiceNow instances.
Reference:
ServiceNow Security Operations Documentation, Encryption section
ServiceNow Trust and Compliance Documentation
ServiceNow System Administrator Study Guide, Security Chapter

Performance Analytics (PA) is the best solution for the manager’s requirements because it provides:
Snapshot of Sales Performance Data- PA allows the creation of historical and real-time dashboards to track sales performance against targets.
Trend Analysis Over Time- With PA, historical data is captured and can be visualized in trend reports, showing patterns over time.
Forecasting Capabilities- PA includes predictive intelligence that can project future trends based on past performance, helping managers make data-driven decisions.
A: Scheduled Reports, a custom snapshot table, and a Trend report- While reports and snapshots provide historical data, they do not offer forecasting capabilities.
B: Scheduled Reports and Excel- Excel is static and does not provide built-in forecasting or trend analysis.
C: Scheduled Reports, a custom snapshot table, and a Projection report- This approach is manual and lacks the dynamic analytics that PA provides.
E: Key Performance Indicators (KPIs)- KPIs track metrics but do not inherently provide trend analysis or forecasting.
Reference:ServiceNow Performance Analytics – Forecasting Data

Reference: https://docs.servicenow.com/bundle/rome-platform-user-interface/page/administer/navigation-and- ui/task/ui16-navigator-tasks.html

An Update Set in ServiceNow is a mechanism that tracks and packages customizations and configuration changes so they can be transferred between instances (e.g., from Development to Test or Production).
It is primarily used in instance migration and change management, ensuring that changes made in one environment can be applied consistently in another.
Key Features of Update Sets:
Tracks Customizations – Records changes to system configurations, such as Business Rules, Client Scripts, UI Policies, and Workflows.
Facilitates Deployment – Enables controlled migration of changes from one ServiceNow instance to another.
Reduces Manual Effort – Instead of manually reconfiguring settings in different environments, administrators can package updates into a single unit.
Why the Correct Answer is A:
✅ A. An Update Set allows administrators to group a series of changes into a named set and then move this set as a unit to other systems (Correct) This accurately describes the primary function of an Update Set.
Administrators group multiple changes into an Update Set, export it, and apply it to another instance.
Example Workflow:
Admin makes configuration changes (e.g., modifies a Business Rule, updates a Workflow).
Update Set captures those changes in a structured format.
The Update Set is exported from the Development instance.
The Update Set is imported into the Testing/Production instance and applied.
Why the Other Options Are Incorrect:
❌ B. By default, an Update Set includes customizations, Business Rules, and homepages (Incorrect) Update Sets do include customizations and Business Rules, but they do not include homepages by default.
Dashboards and homepages require a separate process using sys_portal_page and sys_ui_page tables.
❌ C. An Update Set is a group of customizations that is moved from Production to Development (Incorrect) Update Sets are typically moved from Development to Test/Production, not the other way around.
Best practice is to make changes in Development, test them in Test/UAT, and then deploy them to Production.
❌ D. By default, the changes included in an Update Set are visible only in the instance to which they are applied (Incorrect) This is misleading because an Update Set can be exported and applied to multiple instances.
Once an Update Set is imported and committed, its changes become active in that instance.
Best Practices for Using Update Sets:
✔ Always preview an Update Set before committing it to ensure it contains the correct changes.
✔ Use Named Update Sets, not the default “Default Update Set,” to track changes effectively.
✔ Ensure all related changes are included (e.g., dependencies such as script includes and tables).
✔ Test Update Sets in a sub-production instance before applying them in Production.
Reference:
ServiceNow Documentation: Update Sets Overview
ServiceNow Learning Path: Update Set Fundamentals
ServiceNow Docs: Moving Customizations Between Instances