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

Question 1

At the current time (09:45), what is the total pause duration for this SLA instance?

Accepted Answer

15 minutes. The SLA instance was paused at 09:30 and resumed at 09:45, resulting in a total pause duration of 15 minutes. In ServiceNow, SLA pause duration is calculated as the cumulative time between pause and resume actions, excluding the paused time from the SLA clock.

Answer

0 minutes

Answer

45 minutes

Answer

30 minutes

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

Which role is required to create a report in the Reporting module?

Accepted Answer

report_admin. The report_admin role is required to create reports in the Reporting module because it grants full administrative permissions over reports, including creation, editing, and deletion. The report_user role only allows viewing and running existing reports, not creating new ones.

Answer

admin

Answer

report_user

Answer

report_creator

Question 4

An SLA is breached, but the breach time appears incorrect. The SLA definition uses a business schedule that excludes weekends. The incident was created on Friday at 5 PM and breached on Monday at 8 AM. Why did the breach time not exclude the weekend?

Accepted Answer

The business schedule is not attached to the SLA definition. For an SLA to use a business schedule to calculate breach time, the schedule must be attached to the SLA definition. If the schedule is not attached, the SLA clock runs based on calendar time without excluding weekends. In this scenario, the incident was created at 5 PM on Friday and breached at 8 AM on Monday, which is exactly 63 hours later—consistent with calendar time (24 hours Friday to Saturday, 24 hours Saturday to Sunday, 15 hours Sunday 8 AM to Monday 8 PM? Wait recalc: Friday 5 PM to Monday 8 AM is 63 hours? Actually, Friday 5 PM to Monday 8 AM is 63 hours? No: Friday 5 PM to Saturday 5 PM = 24h, to Sunday 5 PM = 48h, to Monday 5 AM = 60h, to Monday 8 AM = 63h. That is calendar time. If the schedule were attached excluding weekends, the clock would have stopped at Friday 5 PM and resumed Monday 8 AM (if schedule starts at 8 AM), so breach would be at Monday 5 PM? Actually, if SLA duration is e.g., 24 hours, and schedule excludes weekends, the breach time would be Monday 5 PM (24 hours of schedule time). But here breach is at Monday 8 AM, which is exactly calendar time, indicating the schedule was not applied. Therefore, the business schedule is not attached to the SLA definition.

Answer

The schedule's 'Use schedule for progress' is unchecked

Answer

The SLA condition is not met

Answer

The schedule's time zone is incorrect

Question 5

The JSON above shows part of a transform map configuration. What will happen when an import set row containing a value in the 'short_desc' field is processed?

Accepted Answer

An existing incident record is updated with the short_description. The transform map configuration shown in the JSON includes a field mapping where 'short_desc' from the import set row is mapped to 'short_description' on the Incident table. When an import set row contains a value in 'short_desc', the transform engine will use the coalesce setting (if enabled) to match an existing incident record based on a unique identifier (e.g., number or sys_id). If a match is found, the existing incident is updated with the new short_description value; otherwise, a new incident would be created. Since the question implies the coalesce is set to true (common in such configurations), the correct behavior is an update to an existing incident record.

Answer

A task record is created instead

Answer

The import fails because the target field name is incorrect

Answer

A new incident record is created with the short_description populated

Question 6

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 7

Which TWO data sources are commonly used to import data into ServiceNow via Import Sets? (Choose two.)

Accepted Answer

CSV. CSV (C) is correct because Import Sets natively support loading data from delimited flat files such as CSV via the Load Data task, which parses the file into a staging table before transformation. JDBC (D) is correct because ServiceNow provides a JDBC data source type that connects to external relational databases and pulls rows into an Import Set staging table. Email (A) is not a standard Import Set data source; inbound email actions create records directly rather than staging them through Import Sets. REST (B) is used for integrations and Scripted REST APIs, not as a built-in Import Set data source type. LDAP (E) is used for user authentication and directory synchronization via LDAP servers, not for general Import Set data loading.

Answer

Email

Answer

REST

Answer

LDAP

Question 8

Which THREE elements are required when creating a new report in the Reporting module? (Choose three.)

Accepted Answer

Report name. When creating a new report in the Reporting module, the report name (C) is required because it uniquely identifies and saves the report definition. A table (D) is required because it specifies the data source the report will query and display. A chart type (E) is required because the Reporting module renders the report output as a chart, so the visualization format must be selected. By contrast, a condition (A) is optional filtering criteria that can be added to narrow results but is not mandatory, and a group by field (B) is an optional aggregation setting used only when summarizing data, so neither is required to create the report.

Answer

Condition

Answer

Group by field

Question 9

A ServiceNow administrator wants to share a report with the Sales team. The Sales team members do not have direct read access to the underlying table, but they need to see the report results. Which action should the administrator take?

Accepted Answer

Add the report to a dashboard and share the dashboard with the Sales team, ensuring the dashboard's 'Use dashboard owner's security context' option is enabled.. Enabling the 'Use dashboard owner's security context' option on a shared dashboard allows users without direct read access to the underlying table to view the report results. This works by executing the report queries under the security context of the dashboard owner, bypassing the viewers' lack of table permissions while still respecting the owner's access rights.

Answer

Schedule the report to be sent via email to the Sales team daily.

Answer

Export the report to PDF and email it manually.

Answer

Set the report's 'Share with' field to the Sales team group.

Question 10

During an import, the source data contains duplicate records that should be ignored (not imported). The target table has a unique key field u_employee_id. Which configuration in the transform map will prevent these duplicates from creating new records?

Accepted Answer

Set the 'Coalesce' field to true on the field mapping for u_employee_id.. Setting the 'Coalesce' field to true on the field mapping for u_employee_id tells the transform map to use that field as the key for deduplication. When coalesce is enabled, the import engine checks if a record with the same value in that field already exists in the target table; if it does, the incoming record is skipped (not imported). This directly prevents duplicate records from being created without requiring custom scripting or additional configuration.

Answer

Use a script in the 'On Before' transform to check for existing records.

Answer

Set the 'Reject duplicates' checkbox on the transform map.

Answer

Configure a business rule on the target table to reject duplicates.

Question 11

An SLA is defined with a condition that triggers only when a field 'priority' is 1 or 2. However, some tickets with priority 1 are not getting SLA attached. What should the administrator check first?

Accepted Answer

Check the SLA definition condition.. The SLA definition condition determines when the SLA starts. Since the condition should trigger for priority 1 or 2, but some priority 1 tickets are not attaching, the first step is to verify the condition is correctly configured and not missing any additional conditions that might prevent attachment.

Question 12

After importing data, some records show as 'Ignored' in the import log. What is the most likely cause?

Accepted Answer

Coalesce matched an existing record and the transform map action is 'Insert only'.. When a transform map uses the 'Insert only' action and the Coalesce function finds a match on the source and target fields, the import engine ignores the record to prevent duplicates. This is a standard behavior in ServiceNow where coalesce is used to identify existing records, and if the action is set to 'Insert only', no update occurs, resulting in an 'Ignored' status in the import log.

Answer

The source field was empty and the target field is optional.

Answer

A field mapping script returned null for a mandatory target field.

Answer

The transform map condition evaluated to false.

Question 13

An SLA is defined to pause when state is 'Awaiting Customer'. The SLA timer continues to run even when the state changes to that value. What should the administrator check first?

Accepted Answer

Verify the SLA pause condition script or condition.. The SLA timer continues to run despite the state being 'Awaiting Customer', which indicates that the pause condition is not being evaluated correctly. The administrator must first verify the SLA pause condition script or condition to ensure it properly triggers a pause when the state changes to 'Awaiting Customer'. If the condition is misconfigured or not returning true, the timer will not pause as expected.

Answer

Ensure the business rule that triggers SLA recalculation is active.

Answer

Check the SLA schedule for the 'Pause' field.

Answer

Check the SLA metric timeline.

Question 14

When importing data, the import set table rows are not appearing after running the import. What is the most likely cause?

Accepted Answer

The transform map has the 'Cleanup after transform' checkbox selected.. When the 'Cleanup after transform' checkbox is selected on the transform map, ServiceNow automatically deletes all rows from the import set table after the transform completes. This is designed to keep the import set table clean, but it means the rows are removed immediately after processing, so they will not appear when you query the import set table post-import.

Answer

The import source file was empty.

Answer

The transform map condition rejected all rows.

Answer

The transform map action is set to 'Create' and coalesce matches no records.

Question 15

What is the effect of this script on the import transform?

Accepted Answer

It will skip records that have no employee ID and set department for existing records only.. The script uses `source.u_employee_id.nil()` to check if the employee ID field is empty. If it is nil, the script returns `false`, which causes the import transform to skip that record entirely (no insert or update). For records with an employee ID, the script then checks `action == 'update'` and only sets the department to the current user's department for existing records being updated. New records (action 'insert') are not affected, so the department field remains unchanged for them.

Answer

It will set the department to the current user's department for all imported records.

Answer

It will cause an error because the target might be null.

Answer

It will skip records without employee ID and prevent updating department for new records.