SNOW-CSA Reporting, SLA and Imports Practice Test 5 — 15 Questions

Question 1

An administrator loads a CSV file into an import set for the Incident table. The transform map uses Coalesce on the Number field. After running the transform, the administrator notices that existing incidents were updated, but new incidents were not created. What is the most likely cause?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

The Coalesce option is set to true, which prevents inserts when a matching record is not found. Coalesce on a field mapping makes the transform behave as an update-only operation for rows that match the coalesce value, and rows without a match are not inserted. Disabling Coalesce for the Number mapping allows the transform to insert new incidents while still updating existing ones if a separate coalesce or duplicate detection is configured. Missing scripts, staging indexes, and business rules do not produce the described pattern of updates without inserts.

Answer

The target Incident table has a business rule that blocks inserts when the caller is empty

Answer

The import set table has a unique index on the Number column that blocks new rows

Answer

The transform map is missing a source script that calls insert() on the target table

Question 2

A ServiceNow administrator is configuring an SLA definition for the Incident table. The SLA should start when an incident is created, pause when the incident is in Awaiting Vendor state, and stop when the incident is resolved. The administrator also wants to ensure that the SLA only applies to incidents with a priority of 1 or 2. Which two configurations are required to meet these requirements? (Choose two.)

Accepted Answer

Set the SLA start condition to 'Incident is created' and the stop condition to 'Incident is resolved'.. The correct configurations are setting the start condition to incident creation and stop condition to resolution, and adding a filter for priority 1 or 2. These are standard fields in the SLA definition. The pause condition for Awaiting Vendor is also needed, but it is not among the correct choices because the pause schedule is irrelevant. The other options either misconfigure start/stop or use custom scripting instead of native SLA features.

Answer

Configure the SLA pause condition to 'State is Awaiting Vendor' and set the pause schedule to use a 24x7 schedule.

Answer

Create a business rule that manually starts and stops the SLA based on incident state changes.

Answer

Set the SLA start condition to 'Priority is 1 or 2' and the stop condition to 'State is Awaiting Vendor'.

Question 3

A ServiceNow administrator is creating a transform map to import user data from a CSV file into the User [sys_user] table. The CSV has a column 'dept' that should populate the Department field, which is a reference to the Department [cmn_department] table. The administrator wants to ensure that if the department does not exist, it is created automatically. Which transform map feature should be used?

Accepted Answer

Enable 'Create missing reference' on the field mapping. The 'Create missing reference' option on a reference field mapping automatically creates the referenced record if it does not exist. This is the standard, no-code method for importing reference data and creating missing entries. Other options either do not apply to reference fields or require custom scripting.

Answer

Set the 'Coalesce' option on the Department field mapping

Answer

Use a 'Choice' field mapping with the 'Create missing' option

Answer

Add a script to the transform map's onBefore script to insert the department

Question 4

An administrator is building a report on the Incident table that must show only incidents assigned to the caller's assignment groups and must be visible to all users in those groups. Which two configuration steps are required? (Choose two.)

Accepted Answer

Add a filter condition using the dynamic filter 'Assigned to is (dynamic) My groups'. To show each user only the incidents for their assignment groups, the report needs a dynamic filter such as 'My groups' on the Assigned to field. To make the report visible to all members of those groups, the report must be shared with those groups rather than made public. Personal assignment filters, public sharing, and scheduled emails do not achieve both the data scoping and the group-level visibility required.

Answer

Add a filter condition using the dynamic filter 'Assigned to is (dynamic) My assignments'

Answer

Create a scheduled report to email the results to the assignment groups daily

Answer

Enable the 'Public' check box on the report to allow all users to view it

Question 5

A ServiceNow administrator is creating a report that shows the average duration of all closed incidents per assignment group. The administrator selects the 'Incident' table and chooses the 'Bar' chart type. Which additional configuration is required to display the average duration?

Accepted Answer

Add a grouping by 'Assignment group' and set the 'Aggregate' to 'Average' on the 'Duration' field.. To display average duration per assignment group, you must group by Assignment group and apply an Average aggregation on the Duration field. Filtering for closed incidents ensures only resolved incidents are considered. The other options use incorrect aggregations (Count, Sum, Max) that do not yield an average. The Average aggregation is available in the report designer when you select a numeric field and choose the aggregate function.

Answer

Add a filter for 'State is Closed' and group by 'Assignment group', then add a 'Sum' aggregation on the 'Duration' field.

Answer

Add a filter for 'State is Closed' and group by 'Assignment group', then add a 'Count' aggregation on the 'Number' field.

Answer

Add a filter for 'State is Closed' and group by 'Assignment group', then add a 'Max' aggregation on the 'Duration' field.

Question 6

A ServiceNow administrator is troubleshooting an import set that is not updating existing records as expected. The import set is configured to coalesce on the 'email' field of the User [sys_user] table. After running the transform, the administrator notices that new records are created instead of updating existing ones, even though the email addresses already exist in the User table. What is the most likely cause?

Accepted Answer

The email addresses in the import file have different casing (e.g., 'John.Doe@example.com' vs 'john.doe@example.com') than those in the User table.. The most likely cause is a case mismatch between the email addresses in the import file and those in the User table. Coalesce matching is case-sensitive, so 'John.Doe@example.com' will not match 'john.doe@example.com'. This leads to the creation of new records. The other options are either impossible (coalesce on staging table), would cause different errors (missing mapping), or do not explain new record creation (Update unchecked). Ensuring consistent casing resolves the issue.

Answer

The 'Coalesce' option is enabled on the transform map but the 'Update' check box is not selected.

Answer

The transform map is missing a field mapping for the 'email' field.

Answer

The coalesce field is set on the staging table instead of the target table.

Question 7

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 8

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 9

An admin has set up an SLA on the Incident table with a condition 'Priority = 1' and a duration of 1 hour. The SLA is triggered when the incident state becomes 'In Progress'. The SLA definition includes a business schedule that only counts business hours (9 AM to 5 PM, Monday-Friday). An incident with Priority 1 is created at 4:30 PM on Friday and state is changed to 'In Progress' at 4:45 PM. At what time will the SLA breach if it is not resolved?

Accepted Answer

9:45 AM Monday.. The SLA has a duration of 1 hour but uses a business schedule that only counts hours between 9 AM and 5 PM, Monday through Friday. The incident entered 'In Progress' at 4:45 PM on Friday, so only 15 minutes of business time remain that day (4:45 PM to 5:00 PM). The remaining 45 minutes of SLA duration must be fulfilled starting Monday at 9:00 AM, pushing the breach time to 9:45 AM Monday.

Answer

5:45 PM Friday.

Answer

4:45 PM Saturday.

Answer

4:45 PM Monday.

Question 10

A manager wants a report that shows the number of incidents opened each day for the past 30 days, broken down by category. They want to see the data as a line chart with multiple lines (one per category). What report type and options should the admin select?

Accepted Answer

Line chart with 'Group by' set to 'Category' and 'Stacked' set to 'No'.. A line chart with 'Group by' set to 'Category' and 'Stacked' set to 'No' produces a multi-line chart where each line represents a distinct category, showing the number of incidents opened each day over the past 30 days. This directly meets the manager's requirement for a line chart with multiple lines, one per category, without stacking the values.

Answer

Pie chart with a filter for the last 30 days and a breakdown by category.

Answer

List report with a 'Count' aggregation grouped by 'Opened' and 'Category'.

Answer

Bar chart with 'Group by' set to 'Category' and 'Stacked' set to 'Yes'.

Question 11

An administrator is setting up an import set to load data from a CSV file into the Incident table. Which TWO of the following are required steps in the import process?

Accepted Answer

Create an import set table to store the imported data.. An import set table must be created to temporarily store the raw data from the CSV file before any transformation occurs. This table acts as a staging area, allowing the system to hold the imported records and then apply a transform map to map and move the data into the target Incident table. Without an import set table, there is no structure to receive the incoming CSV data.

Answer

Schedule the import to run automatically.

Answer

Use the Import Set Row API to create a transform map.

Answer

Create a data lookup table to standardize values.

Question 12

An administrator is troubleshooting an import that is failing silently. The import set rows show 'Processed' with no errors, but no records are created or updated in the target table. Which THREE areas should the admin investigate?

Accepted Answer

Check if the coalescing field is set correctly in the transform map.. The coalescing field in the transform map determines how ServiceNow matches incoming records to existing records in the target table. If the coalescing field is misconfigured or missing, the import may appear to process successfully (rows show 'Processed') but no records are created or updated because the system cannot identify which records to insert or update, leading to a silent failure.

Answer

Check if the target table has a 'sys_id' field.

Answer

Check if the import set table is set as the target table.

Question 13

A large enterprise uses ServiceNow for IT Service Management. They have a complex SLA structure with multiple SLA definitions on the Incident table. Each SLA definition has conditions based on category, priority, and assignment group. The company recently merged with another organization, and the new combined company has doubled the number of incidents. The SLA performance has degraded significantly: SLA breaches have increased by 40%, and the SLA engine is taking longer to process. The system administrator has checked the instance health and found that the SLA job is running but taking an average of 5 minutes per execution, and there are often multiple instances of the SLA job queued. The administrator needs to improve SLA performance without changing the business requirements. Which course of action is most effective?

Accepted Answer

Consolidate similar SLA definitions by using conditions with OR operators and simplify the SLA structure to reduce the number of active SLA definitions.. Consolidating SLA definitions reduces the number of active SLA records that the SLA job must evaluate per incident. The SLA job iterates through all active SLA definitions for each incident; fewer definitions mean fewer evaluations per incident, directly reducing processing time and the likelihood of queued job instances. This approach preserves all business requirements by using OR conditions to combine similar rules rather than removing them.

Answer

Schedule the SLA job to run only during business hours to reduce off-hours processing.

Answer

Disable SLA evaluation for incidents with low priority (4 and 5) to reduce volume.

Answer

Increase the SLA job interval from 1 minute to 5 minutes to reduce the frequency of execution.

Question 14

A ServiceNow administrator needs to create a report that shows the number of incidents opened each month for the last 12 months. The report should display a bar chart with months on the x-axis and count on the y-axis. Which report type and grouping should the administrator use?

Accepted Answer

Bar chart, group by Month on the Opened field. A bar chart is ideal for comparing discrete categories (months) over time, and grouping by Month on the Opened field aggregates incident counts per month. This meets the requirement of showing the number of incidents opened each month for the last 12 months with months on the x-axis and count on the y-axis.

Answer

List report, sort by Opened

Answer

Pie chart, group by Month on the Opened field

Answer

Line chart, group by Day on the Opened field

Question 15

A large enterprise uses ServiceNow for IT Service Management. They have recently configured SLA definitions for incident management with a 4-hour resolution time during business hours (Monday-Friday, 8 AM to 6 PM, excluding holidays). The SLA is triggered when an incident is created with priority=2 and assigned to the 'Hardware Support' group. After one week, the IT manager notices that some priority=2 incidents assigned to 'Hardware Support' are not showing any SLA timer. Upon investigation, you find that the incidents were created on weekends and the SLA condition includes 'Assigned to group is Hardware Support'. The SLA definition has 'Start condition' set to 'State changes to In Progress' and 'Pause condition' set to 'State changes to On Hold'. The incidents were created with state 'New' and then assigned to the group, but they remain in 'New' state. How should you fix the issue so that the SLA starts correctly?

Accepted Answer

Change the start condition to trigger on incident creation or when assigned to group. The SLA start condition is currently set to 'State changes to In Progress', but the incidents remain in 'New' state after being assigned to the group. Since the SLA is not starting, you need to change the start condition to trigger on incident creation or when assigned to the group, ensuring the SLA timer begins even if the state does not change to In Progress.

Answer

Remove the pause condition so the SLA continues even when on hold

Answer

Update the condition to include 'Assigned to group is Hardware Support AND Priority is 2'

Answer

Modify the SLA schedule to include weekends