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

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.
Reference:
ServiceNow CMDB Best Practices (CSA Official Documentation)
ServiceNow Docs: CMDB Use Case Modeler
CSDM and CMDB Overview

In ServiceNow,groupsare stored in thesys_user_grouptable. This table definesgroups of userswho share common responsibilities, such asIT support teams, HR teams, or security teams.
Groups are used toassign roles and permissionsto multiple users at once.
Common groups includeService Desk, IT Support, Change Advisory Board (CAB), and HR teams.
Thesys_user_grouptable is linked tosys_user(Users) andsys_user_role(Roles).
B: Group [sn_sys_user_group]- No such table prefix (sn_) exists for user groups in ServiceNow.
C: User Group [user_groups]- Incorrect table name; ServiceNow follows thesys_naming convention.
D: User Groups [sn_user_groups]- Not a valid ServiceNow table.
E: Groups [sys_user_groups]- Incorrect pluralization; ServiceNow tables typically usesingular names(e.g., sys_user_group).
ServiceNow sys_user_group Table Documentation
ServiceNow CSA Training Module:"User and Group Administration"
Key Details about sys_user_group:Why Other Answers Are Incorrect:References from Certified System Administrator (CSA) Official Documentation:

InServiceNow Service Catalog, approvals forcatalog item requestsare handled through workflows. Since the approval policy is based on thetotal cost of a request, it is managed within theService Catalog Request workflow.
C: Service Catalog Request
This workflowhandles approvals for catalog item requests, includingpurchase approvals.
Since the policy change involvesadjusting an approval threshold, this workflow needs to be updated.
The approval logic is likely configured in aconditional activity (if total cost > $3,100, require approval), which must be modified to$3,150.
A: Services Approval Processing
Not a standard ServiceNow workflowfor managing purchase approvals.
Service approvals are typically handled within theService Catalog Requestworkflow.
B: 6 Services Catalog Item Request
Likely acustom workflow, but not adefault ServiceNow workflowfor purchase approvals.
D: Purchasing Process Flow
There isno default "Purchasing Process Flow"in ServiceNow.
Theapproval workflow for purchasesis managed withinService Catalog Request workflows.
References:ServiceNow Documentation:Service Catalog Workflows
ServiceNow Developer Guide:Modifying Approval Conditions in Workflows

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.