SNOW-CSA Reporting, SLA and Imports — Timed 10 Questions

Question 1

A high-priority incident is created on Monday at 16:30 (within schedule). The incident is assigned to an agent at 17:00. The state changes to 'In Progress' at 17:30. What is the SLA breach time?

Accepted Answer

17:30. The SLA breach time is calculated as the start time plus the resolution duration, minus any paused time. The start time is 16:30 (creation within schedule). No pauses are specified. However, the resolution duration is not provided in the question. Without this duration, a specific breach time cannot be determined from the given information. Therefore, none of the options (17:00, 16:30, 17:30, 18:00) can be confirmed as the correct breach time.

Answer

17:00

Answer

16:30

Answer

18:00

Question 2

An SLA is defined with a condition 'Active = true' but some incidents that are active are not triggering the SLA. What is the most likely cause?

Accepted Answer

The SLA definition is not set to active. The most likely cause is that the SLA definition itself is not set to active. In ServiceNow, an SLA definition must be active for it to be evaluated and triggered. Even if the condition 'Active = true' is met, if the SLA definition is inactive, it will not start for any incident. Option A is incorrect because the stem explicitly states that the incidents are active, so their state cannot be closed. Option C is incorrect because the condition already checks for active state. Option D is irrelevant because group assignment does not affect whether the SLA starts if the definition is inactive.

Answer

The incidents have a state of 'Closed' and are no longer active

Answer

The SLA condition needs to also check that the incident state is not 'Closed'

Answer

The incidents are assigned to a group that does not have the SLA

Question 3

An import set fails with error 'Import set row processing error'. The transform map uses a script that references a table that does not exist. What is the first step to resolve this?

Accepted Answer

Update the transform script to reference a valid table. The import set row processing error specifically states that the referenced table does not exist. The appropriate first step is to update the transform script to reference a valid table that exists in the instance. Changing the scope (Option C) would not resolve the issue if the table truly does not exist—it only changes which tables are accessible, but if the table is missing entirely, no scope change will make it appear. Therefore, the correct action is to fix the script.

Answer

Re-create the import set definition

Answer

Change the data source type

Answer

Run the import set in a different scope

Question 4

An import set transform map includes field maps with script actions. The import fails with 'Script execution error'. Where should the administrator look first?

Accepted Answer

System log. When a script action in a transform map field map throws an error, the system log (syslog) is the primary source for detailed JavaScript error messages, stack traces, and line numbers. Import set row errors only capture row-level failures like missing mandatory fields, not script execution details. The data source configuration and field map log do not store runtime script errors.

Answer

Import set row errors

Answer

Data source configuration

Answer

Transform map's field map log

Question 5

The error log entry above appears when processing an SLA for an incident. What does this indicate?

Accepted Answer

The SLA schedule is incorrectly configured. The error log entry indicates that the SLA schedule is incorrectly configured. In ServiceNow, SLAs rely on a defined schedule (e.g., 8x5 or 24x7) to calculate response and resolution times. If the schedule is missing, misconfigured, or has overlapping entries, the SLA engine cannot compute timers, resulting in an error during processing.

Answer

The SLA has breached its response time

Answer

The SLA definition's condition is not satisfied

Answer

The SLA response time has exceeded the target

Question 6

A company needs to import user records from a CSV file into the User [sys_user] table. The file contains a 'department' column that should map to the 'department' field in ServiceNow. However, the department values in the CSV are full names (e.g., 'Human Resources'), but the department field in ServiceNow uses a reference to the Department [cmn_department] table. What is the best practice for handling this import?

Accepted Answer

Create a transform map that maps the source field to the target field, and use a field mapping script to convert the department name to the correct sys_id.. Import Set Rows are processed through transform maps, which allow field mapping scripts to convert source values (like 'Human Resources') into the corresponding sys_id in the Department [cmn_department] table. This is the standard, supported approach for handling reference field lookups during imports, ensuring data integrity without manual intervention or post-insert processing.

Answer

Use a before business rule on the User table to convert the department name after the record is inserted.

Answer

Use the Import Set Row API to programmatically map the values during import.

Answer

Manually edit the CSV file to replace department names with the corresponding sys_id values.

Question 7

An administrator has configured a report on the Incident table showing the count of incidents by assignment group. The report shows data for the current week, but the numbers seem too low. The administrator suspects that incidents resolved before the current week are not being included. What should the administrator check first?

Accepted Answer

Check the condition (prompt) filter of the report to see if there is a time-based filter that limits to the current week.. The report's condition filter (often called a 'prompt' or 'filter condition') directly controls which records are included. If a time-based condition like 'Opened > Current week' or 'Resolved > Current week' is applied, it would exclude incidents resolved before the current week, causing the low count. The administrator should first inspect the filter conditions to see if such a restriction exists.

Answer

Check the 'Time scale' setting and ensure it is set to 'All' instead of 'Current week'.

Answer

Check the type of the report (e.g., bar chart vs pie chart) as some types only show aggregated data.

Answer

Check the 'Group by' field to ensure it is set to 'Assigned to' instead of 'Assignment group'.

Question 8

An organization has a Service Level Agreement (SLA) defined on the Incident table with a condition of 'Category is Network' and a duration of 4 hours. The SLA is triggered when the incident state changes from 'New' to 'In Progress'. A network incident is created and assigned to the Network Support group. The incident state is changed to 'In Progress' immediately. After 3 hours, the incident is resolved. However, the SLA shows a breach despite the resolution being within 4 hours. What is the most likely cause?

Accepted Answer

The SLA stop condition is set to 'State is Resolved', but the SLA was paused due to a schedule (e.g., after-hours pause) and the pause time was not counted, causing the actual working time to exceed 4 hours.. The most likely cause is that the SLA stop condition is set to 'State is Resolved', but the SLA timer was paused due to a schedule (e.g., after-hours) at the time the incident was resolved. Because the timer was paused, the stop condition was not evaluated immediately. When the schedule resumed, the working timer continued to run, and by the time the stop condition was evaluated, the accumulated working time had already exceeded the 4-hour duration, resulting in a breach. In ServiceNow, SLA timers that are paused do not trigger stop conditions until they resume, which can cause breaches even when the incident is resolved within the expected real-time window.

Answer

The SLA is assigned to the Network Support group, but the assignment group was changed during the incident.

Answer

The SLA duration is defined in business hours, and the incident was created after business hours, so the elapsed time counted only business hours, making the 4-hour window longer in real time.

Answer

The SLA condition 'Category is Network' was not evaluated correctly because the category field was updated after the SLA was triggered.

Question 9

A company frequently imports data from an external HR system into the Employee [hr_employee] table using an import set. The import set runs nightly and maps fields correctly. Recently, the import started failing with the error 'Field 'manager' not found in table 'hr_employee''. The manager field exists in the import set rows but not in the target table. What is the most likely cause?

Accepted Answer

The transform map has a field mapping that references 'manager' as a target field, but the hr_employee table does not have a 'manager' column.. The error 'Field 'manager' not found in table 'hr_employee'' indicates that the transform map is attempting to map a source field to a target column that does not exist in the hr_employee table. Since the import set rows contain the 'manager' field, the mapping in the transform map must be referencing 'manager' as a target field, but the target table lacks that column. This is the most likely cause because the transform map defines the field-to-field mapping between the import set row and the target table, and if the target field name is incorrect or missing from the table, the import will fail.

Answer

The import set row table (sys_import_set_row) does not have a 'manager' column.

Answer

The source CSV file contains a column named 'manager' that is misspelled.

Answer

The manager field in the target table is of a different data type (e.g., string vs reference).

Question 10

An administrator is creating a new report to show the average time to resolve incidents for the last quarter. They want the report to automatically update as new incidents are resolved. Which report type should they use?

Accepted Answer

List report with a 'Average' aggregation on the 'Resolved' field.. A List report with an 'Average' aggregation on the 'Resolved' field is the correct choice because it automatically recalculates the average as new records are added or updated, ensuring the report reflects the most current data without manual intervention. List reports in ServiceNow support real-time aggregation on specific fields, making them ideal for dynamic metrics like average resolution time.

Answer

Bar chart report with a condition for resolved incidents.

Answer

Pivot table report with a 'Average' aggregation.

Answer

Scorecard report with a metric for average resolution time.