CSA Exam Questions & Answers

In ServiceNow, the best practice for managing users, groups, and roles is based on role-based access control (RBAC).

Best Practices for Users, Groups, and Roles:

Assign Roles to Groups (Correct )

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

This ensures better role management, easier administration, and scalability.

Example:

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

All users in this group automatically get the itil role.

Add Users to Groups (Correct )

Users should be assigned to groups rather than roles directly.

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

Example:

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

Why Other Options Are Incorrect?

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

Incorrect: Assigning roles to groups is the recommended best practice.

Managing roles at the group level makes access control more efficient and scalable.

B . You should assign roles to users (Incorrect)

Incorrect: Assigning roles directly to users is not a best practice because it becomes difficult to manage as the organization grows.

Instead, users should be added to groups that have the necessary roles.

Reference from ServiceNow CSA Documentation:

Managing Users, Groups, and Roles

ServiceNow Best Practices for Roles & Groups

Role-Based Access Control (RBAC)

User Administration

When importing data into ServiceNow via an Import Set, the system determines whether to update existing records or create new ones based on the Coalesce field setting.

Behavior When No Coalesce Field is Specified:

If no Coalesce Field is defined, ServiceNow treats every imported row as a new record.

The import process does not check for existing records, meaning no records in the target table are updated.

This can result in duplicate entries if the imported data includes records that already exist in the target table.

How Coalescing Works:

A Coalesce Field is used to match incoming data to existing records.

If a matching record is found, it is updated instead of inserting a new one.

If no matching record is found, a new record is created.

Incorrect Answers

A . All rows are rejected from the import, as coalesce field is required

This is incorrect because the import does not require a coalesce field to proceed. The system will still import all rows. C . Duplicate rows are rejected from the import

Without a coalesce field, duplicates are not rejected. Instead, every row is inserted as a new record, even if it already exists in the target table. D . All rows are treated as new records, but errors will be flagged in the import log

Errors are only flagged in cases of data mismatches, validation failures, or incorrect mappings, not just because coalescing is missing.

Reference from Certified System Administrator (CSA) Documentation:

ServiceNow Documentation 'Importing Data - Coalescing Best Practices'

ServiceNow Import Set Documentation 'Understanding Import Set Behavior Without Coalescing'

In ServiceNow, when viewing a list view, you can easily filter out specific values by right-clicking on the field value and selecting 'Filter Out'. This action dynamically updates the filter to exclude records with that value.

Steps to Exclude Incidents with the State 'Resolved':

Navigate to the Incident List.

Locate a record with State = Resolved.

Right-click on the 'Resolved' value in the State column.

Select 'Filter Out' from the context menu.

The list automatically refreshes, showing only incidents excluding 'Resolved'.

Why Other Answers Are Incorrect:

A . On the list of records, locate the right-click on the Resolved value, select Exclude.

'Exclude' is not an option in the ServiceNow list filter menu. The correct option is 'Filter Out'.

B . Click Funnel icon, click AND, Select Resolved, is Not State click Run.

The funnel icon opens the filter panel, but this answer is unnecessarily complex. Right-clicking and filtering out is faster.

C . On state column title, right-click, select Filter Out > Resolved.

You cannot right-click the column title to filter out a specific value; you must right-click on a specific field value.

D . On Search, select State, type not Resolved, press enter.

The correct syntax in the filter bar is 'State != Resolved', but right-clicking is a more user-friendly method.

Reference from Certified System Administrator (CSA) Official Documentation:

ServiceNow Filtering and List Views

ServiceNow CSA Training Module: 'Working with Lists and Filters'

To access reports in ServiceNow, users navigate to:

Reports > View / Run

Key Features of 'View / Run' Module:

Displays all reports available to the user.

Allows running, modifying, and creating new reports (if permissions allow).

Users can filter reports by category (e.g., incidents, requests, changes).

Why Other Options Are Incorrect?

B . Reports > Homepage Incorrect

No such module named 'Reports > Homepage.'

C . Self-Service > My Reports Incorrect

The Self-Service module is primarily for end users, not for accessing platform-wide reports.

D . Report > Overview Incorrect

'Overview' provides reporting summaries but does not list all available reports.

Official ServiceNow Documentation Reference:

Running and Managing Reports