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 Knowledge Management, thepublishing and retiring process for knowledge articlesis managed throughWorkflows. These workflows define the steps an article must go through before it is published, updated, or retired.

Submission:

A user creates a knowledge article and submits it for approval.

Approval Process:

Based on the workflow, an article may require manager or SME (Subject Matter Expert) approval.

Publishing:

Once approved, the article ispublishedand made available in the Knowledge Base.

Updating & Versioning:

If edits are needed, the article enters adraft or reviewstate.

Retirement:

When an article is no longer needed, it follows the workflow toretire or archiveit.

Knowledge Approval Publish(requires approval before publishing)

Knowledge Instant Publish(automatically publishes the article)

Knowledge Retire(handles retiring or archiving articles)

A. Approval Policies(Incorrect)

ServiceNow does not use a separate " Approval Policy " for knowledge articles; approvals are managed within the workflow.

B. Approval Definitions(Incorrect)

There is no such specific feature in ServiceNow. Approvals are configured within workflows, not separate definitions.

C. Workflow Designer(Incorrect)

TheWorkflow Designeris a tool used tocreate workflows, but it does not control the publishing process directly. The workflows themselves do.

E. State Lifecycle(Incorrect)

While knowledge articleshave a lifecycle (Draft → Review → Published → Retired), this is controlledby workflows, not by an independent " State Lifecycle " feature.

Knowledge Workflows Overview:https://docs.servicenow.com/bundle/rome-servicenow-platform/page/product/knowledge-management/reference/r_KnowledgeWorkflows.html

ServiceNow Knowledge Management Process:https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/knowledge-management/concept/knowledge-management-overview.html

How Workflows Control Knowledge Article Publishing & Retiring:Common Knowledge Workflows in ServiceNow:Explanation of 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:

When usingHigh Security Settingsin ServiceNow, administrators often gaintemporary elevated privileges. To revert to normal security levels, they mustlog out and back into refresh their session.

High Security Settingsprovide elevated security configurations and mayoverride standard role-based access controls.

Logging outclears any temporary security settingsand restores normal administrator privileges.

This is therecommended practiceafter making security changes.

Why is Option B Correct?

Why Are the Other Options Incorrect?A. Select Normal role

Incorrectbecausethere is no " Normal " rolein ServiceNow.

C. Use System Administration > Normal Security module

Incorrectbecausethere is no " Normal Security " modulein ServiceNow.

D. Select Global Update Set

Incorrectbecause Update Sets controlcustomizations and configurations,not security settings.

E. End Impersonation

Incorrectbecause ending impersonation onlyswitches back to the admin accountif you were impersonating a user.

Itdoes not resetsecurity settings from High Security Mode.

ServiceNow CSA Guide - High Security Settings

ServiceNow Best Practices - Managing Security Configurations

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow,Visual Task Boards (VTBs)provide aKanban-style interfaceto manage and track work. There arethree main typesof Visual Task Boards, but " Feature " is notone of them.

Freeform Board (Valid Type)

Manually created boards wherecards can be moved freelywithout predefined conditions.

Users canadd and organize tasks as needed.

Example: Personal task management.

Guided Board (Valid Type)

Createdfrom a list viewandlinked to a ServiceNow table(e.g., Incident, Change, Task).

Cards on the boardautomatically updatebased on conditions.

Example: Managing Incidents or Change Requests.

Flexible Board (Valid Type)

Similar toGuided Boards, but allows users tomanually reordertasks within lanes.

Offers moreflexibilitywhile still being linked to a data source.

Example: Sprint Planning or ITSM Workflows.

" Feature " is NOT a Visual Task Board type in ServiceNow.

ServiceNow does use the term " Feature " in Agile Development (for tracking high-level product functionalities), but it is not related to VTBs.

Types of Visual Task Boards in ServiceNow:Why is " Feature " Incorrect?

Why Other Options Are Correct?Guided, Flexible, and Freeformare thethree valid typesof Visual Task Boards in ServiceNow.

Visual Task Boards Overview

ServiceNow Visual Task Boards

Types of Visual Task Boards

Creating and Using VTBs

References from ServiceNow 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:

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.

In ServiceNow,Priorityis achoice field, meaning it has predefined values (e.g., 1 - Critical, 2 - High, etc.). If a customer wants to change the values to displayP1, P2, P3, P4consistently across all tasks, you must modify thechoice list valuesfor the Priority field.

Right-click on the Priority fieldin the Incident form.

Select“Show Choices”from the context menu.

In theChoice List Entriestable, modify theLabelvalues to match the internal terminology (P1, P2, P3, P4).

Ensure that the changes applyto all Task-related tables(such as Incident, Change, and Problem).

The“Show Choices”option displays the choice list for that specific field, allowing modifications to the values displayed in the dropdown.

This ensures consistency across all records using thePriorityfield.

A. Configure Lists:Configures list views,not choice field values.

B. Show Options:Not a valid option in ServiceNow for modifying choice fields.

C. Configure Task:Configures the task table settings,not choice list values.

E. Show Choice List:Not a valid ServiceNow menu option.

F. Configure Options:Not a valid option in ServiceNow for modifying choice fields.

Modifying Choice Lists in ServiceNow:ServiceNow Docs

How to Customize Dropdown Fields in ServiceNow

Steps to Modify the Priority Field Choices:Why is the Correct Answer " Show Choices " ?Why Not the Other Options?References from the Certified System Administrator (CSA) Official Documentation:Using“Show Choices”, administrators can updatechoice valueswhile preserving the existingbackend values, ensuring consistency in workflows and reports.

In ServiceNow,Data Policiesare rules thatenforce data consistencyby ensuring that specific fields meet certain conditionsbefore being saved to the database. They apply toall data operations, including form submissions, web services, and data imports.

Work at the server-side level, ensuring data integrity before it is stored.

Canmake fields mandatoryorread-onlyacross different interfaces (e.g., forms, API calls, imports).

UnlikeUI Policies, which apply only toforms, Data Policies apply to alldata transactions, including integrations and imports.

Help maintaindata quality and consistencyacross the system.

Making a Field Mandatory:

Ensure that the " Short Description " field is always filled before saving anIncident.

Enforcing a Read-Only Field:

Prevent users from modifying the " Created Date " field.

Standardizing Data on Import:

When importing employee data, ensure that the " Department " field is always set and not left blank.

Data Policies ensuredata accuracy and integritybefore it is stored.

They apply toforms, web services, import sets, and background processes.

They help organizationsmaintain standardized and structured data.

A. Data Policies enforce security – Incorrect

Security is enforced usingAccess Control Lists (ACLs), not Data Policies.

B. Data Policies standardize data in Update Sets – Incorrect

Update Sets trackconfiguration changes, not data validation.

D. Data Policies apply to lists to standard data – Incorrect

Data Policies do not specifically target lists; they enforce rules at thedatabase level.

ServiceNow Docs: Data Policies Overview

ServiceNow CSA Study Guide – Data Policies vs. UI Policies

ServiceNow Product Documentation: Enforcing Data Consistency with Data Policies

Key Features of Data Policies:Example Use Cases of Data Policies:Why " C. Data Policies enforce data consistency " is the Correct Answer?Explanation of Incorrect Options:References from Certified System Administrator (CSA) Documentation:

ServiceNow provides multiplesecurity-related modulesthat aSystem Administratorfrequently uses to manage access, authentication, and overall system security.

Why These Options Are Correct?A. System Properties > Security

This module allowsadministrators to configure general security settings, including password policies, session timeout, and encryption settings.

It helps manage security parameters at a system-wide level.

E. System Security > Access Control (ACL)

Access Control Lists (ACLs)define what data users can access, modify, and delete within the instance.

ACLs operate at thetable, field, and record levels, ensuring proper role-based access control (RBAC).

This is one of themost commonly usedsecurity modules by admins.

G. System Security > High Security Settings

High Security Settings (previously known as Security Hardening)enforce strict security controls, such as requiring multi-factor authentication (MFA) and enforcing strict password policies.

It is often used for compliance withsecurity regulationslike HIPAA, GDPR, and ISO 27001.

Why the Other Options Are Incorrect?B. Utilities > Migrate Security

This optiondoes not existin ServiceNow. There is no " Migrate Security " under Utilities.

C. System Security > Security

There is no " System Security > Security " module in ServiceNow. The correct structure isSystem Security > Access ControlorSystem Properties > Security.

D. Self-Service > My Access

This is aself-service modulefor end users to request and review their access.

It isnota tool thatSystem Administratorsuse to manage security settings.

F. Password Management > Security Questions

This is used to configuresecurity questions for password recoverybut isnot a core security modulethat admins frequently use.

General Security Settings in ServiceNow

ServiceNow Access Control (ACL) Best Practices

ServiceNow System Security and Role Management

References to Official Certified System Administrator (CSA) Documentation:

InServiceNow, anEventis a system-generatednotificationthatindicates an occurrence within the platform. Events are triggered automatically or manually whenspecific conditionsare met and can be used to initiatenotifications, business rules, workflows, or integrations.

Events Indicate That Something Has Happened

Example: When anIncident is assigned, an event like " incident.assigned " can be triggered.

These eventsdo not execute actions themselves, but theynotify other processesto take action.

Events Are Stored in the [sys_event] Table

TheEvent Log(System Policy > Events > Event Log) records all generated events.

Administrators can monitorwhat events were triggered, their sources, and timestamps.

Events Can Be Used for Notifications & Workflows

Example: An event " incident.closed " can be configured to send a " Thank You " emailto the requester.

Example: A custom event " task.overdue " can be used to trigger a workflow escalation.

Eventssignal that something has happened, allowing other processes (like email notifications or workflows) to react.

Theydo not execute actions themselvesbut notifyscripts, business rules, or workflows.

Key Characteristics of Events in ServiceNow:Why is " B. An Event is an indication to the ServiceNow processes that something has occurred " the Correct Answer?

A. " An Event is a trigger that has a direct response in the platform " →Incorrect

Events themselvesdo not trigger direct responses; they onlynotify the systemabout occurrences.

The system must beconfigured to respond to an event(e.g., via aBusiness Rule, Notification, or Script Action).

C. " An Event is an indicator that a Priority 1 (P1) Incident has been logged " →Incorrect

While ServiceNowcan generate an event when a P1 Incident is logged, events arenot limited to incidents.

Events apply toall ServiceNow processes(incidents, changes, tasks, etc.).

D. " An Event is a recognized, scheduled occurrence of a process " →Incorrect

Eventsare not scheduled; they aretriggered by system activities(e.g., record updates, conditions met).

Scheduled Jobs or Scheduled Scripts handletime-based automation, not events.

Why the Other Options Are Incorrect?

Navigate to:System Policy > Events > Event Log

Review the event records, including event names, sources, and timestamps.

Navigate to:System Policy > Events > Registryto see predefined event names.

UseEvent Registryto create new events that triggernotifications or workflows.

How to View and Use Events in ServiceNow?

ServiceNow Docs: Events in ServiceNowhttps://docs.servicenow.com/en-US/bundle/utah-platform-administration/page/administer/events/reference/r_Events.html

ServiceNow CSA Official Training Guide (Event Management & Notifications)

References from Certified System Administrator (CSA) Documentation:This confirms that " An Event is an indication to the ServiceNow processes that something has occurred " is the correct answer.

In ServiceNow, theglobal search baris located in theBanner Frame, which is thetopmost sectionof the user interface. Theglobal search featureallows users to search across multiple tables and records within the platform.

Searches across multiple record types(Incidents, Knowledge Articles, Change Requests, etc.).

Auto-suggests resultsas you type.

Filters resultsbased on user roles and permissions.

Uses indexingto improve search speed and efficiency.

Key Features of the Global Search in the Banner Frame:

Why " B. Banner frame " is Correct:TheBanner Framecontains theglobal search bar, which enables users to search across all available records in ServiceNow.

A. Application Navigator→The Application Navigator is used forbrowsing modules and applications, not for performing a global search.

C. List pane→The List Pane only displaysrecords from a specific table, and its search is limited to that list view.

D. Content frame→The Content Frame displaysforms, lists, and dashboards, but does not provide a global search function.

Why Other Options Are Incorrect:

ServiceNow Documentation:Global Search in ServiceNow

CSA Exam Guide:CoversBanner Frame and its functions, including Global Search.

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

B. Banner frame

Abusiness rulein ServiceNow is a server-side script written inJavaScriptthat executes when a record is inserted, updated, deleted, or queried. Business rules allow for automation and enforcement of business logic without requiring manual intervention.

Business rules arenot tied to formsbut instead runon the server-sidewhen a database operation occurs. They can be configured to execute:

Beforea record is saved (Before Business Rule)

Aftera record is saved (After Business Rule)

Asynchronously(Async Business Rule)

Before a query is run on the database(Query Business Rule)

Explanation of the Correct Answer:B. A business rule can be a piece of JavaScript(Correct)

Business rules are written inJavaScript, allowing administrators to define custom logic that executes on the server.

These scripts can modify data, enforce rules, validate fields, or trigger other workflows.

Example JavaScript snippet for a business rule:

if(current.state== ' 3 ' & & current.priority!= ' 1 ' ) {

current.priority= ' 1 ' ;

gs.addInfoMessage( " Priority set to High because state is Resolved. " );

}

This rule ensures that if an incident ' s state is changed toResolved, its priority is automatically set to High.

Why the Other Options Are Incorrect:A. A business rule must run before a database action occurs (Incorrect)

Business rulescan run before a database action occurs, but they can also executeafterorasynchronously.

Business rules have four execution types:

Before– Runs before the record is inserted/updated in the database.

After– Runs after the record is committed to the database.

Async– Runs in the background after the transaction completes.

Query– Runs before data is returned to a user (modifies query results).

C. A business rule must not run before a database action occurs (Incorrect)

This is false because some business rulesdo run beforea database action (e.g., aBefore Business Rulecan validate data before saving).

D. A business rule monitors fields on a form (Incorrect)

Business rulesdo not monitor form fields directly. Instead, they execute based on database operations.

If real-time monitoring of form fields is needed,Client Scripts(not Business Rules) are used for this purpose.

Automaticallyassigning prioritybased on ticket severity.

Preventing updates to certain records if a condition is not met.

Sending email notifications when a record changes.

Modifying data before it is saved to enforce business policies.

Example Use Cases for Business Rules:

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: