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

Question 1

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 2

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.

Question 3

Which TWO are best practices for creating dashboards in ServiceNow?

Accepted Answer

Use filters to allow interactive data exploration.. Filters enable interactive data exploration by allowing users to dynamically refine dashboard data without modifying the underlying reports or widgets. This aligns with ServiceNow's best practice of empowering end-users to self-serve insights while maintaining a clean, focused dashboard layout.

Answer

Share the dashboard with all users by default.

Answer

Use widgets instead of reports.

Answer

Use multiple data sources for a single dashboard.

Question 4

Which TWO elements are mandatory when defining an SLA definition in ServiceNow?

Accepted Answer

Condition. An SLA definition in ServiceNow requires a Condition to determine which records are covered by the SLA. Without a condition, the SLA would apply to all records or none, making it impossible to scope the SLA to specific criteria like priority or category. The condition is a mandatory field that defines the filter for when the SLA should start tracking.

Answer

Breach timers

Answer

Metrics

Answer

Escalation

Question 5

Which THREE factors can cause a transform to skip a row (resulting in 'Skipped' status in the import log)?

Accepted Answer

A field mapping script returns false.. A field mapping script that returns false explicitly tells the transform engine to skip the current row. When the script evaluates to false, the import engine does not process the row further, resulting in a 'Skipped' status in the import log. This is a deliberate mechanism to filter out rows based on custom logic.

Answer

The source field is empty for an optional target field.

Answer

The target field is read-only.

Question 6

A large organization uses a weekly scheduled report to analyze incident trends. The report queries a database view that joins several tables. The report has filters: ((category=Network OR category=Database) AND priority<=2) OR (assigned_to in (specific group)). The report takes over 30 minutes to run and often times out. The administrator wants to improve performance without altering the report's output. Which action should be taken?

Accepted Answer

Create summary fields on the incident table to pre-calculate counts and sums for the relevant filters.. Creating summary fields on the incident table pre-calculates aggregate values for the filters (category, priority, assigned_to), allowing the report to read precomputed data instead of scanning and joining large tables each time. This directly addresses the performance bottleneck without altering the report's output, as summary fields are updated incrementally and maintain the same logical results.

Answer

Remove the OR condition and split the report into two separate reports.

Answer

Increase the report's timeout value to 60 minutes.

Answer

Add indexes to the fields used in the filters.

Question 7

An SLA is defined for incident resolution with a 4-hour breach timer. The SLA should not count time when the incident is in 'Awaiting Customer' status. The administrator has configured a pause condition on the SLA definition. However, when the state changes to 'Awaiting Customer', the SLA timer continues to run. The administrator wants to troubleshoot the issue. What should the administrator check first?

Accepted Answer

Verify the SLA pause condition script or condition.. The pause condition on the SLA definition is the primary mechanism that stops the breach timer when the incident enters a specific state, such as 'Awaiting Customer'. If the timer continues to run despite the state change, the most likely cause is that the pause condition script or condition is incorrectly configured, not evaluating to true, or missing entirely. The administrator should first verify this condition before investigating other potential issues.

Answer

Ensure the business rule that triggers SLA recalculation is active.

Answer

Check the SLA metric timeline.

Answer

Check the SLA schedule for the 'Pause' field.

Question 8

A company imports employee data from an HR system weekly. The import set table always retains the data from previous imports, causing storage issues. The administrator wants to automatically delete the import set rows after a successful transform to free up space. Which configuration should be made?

Accepted Answer

Select the 'Cleanup after transform' checkbox on the transform map.. Selecting the 'Cleanup after transform' checkbox on the transform map instructs the platform to automatically delete the import set rows from the staging table once the transform has completed successfully. This directly addresses the storage issue caused by retaining all historical import data, without requiring manual or scheduled cleanup.

Answer

Create a scheduled job to delete old import set rows.

Answer

Set a retention policy on the import set table.

Answer

Use a business rule to delete the import set row after transform.

Question 9

An organization is importing help desk tickets from a legacy system using ServiceNow Import Sets. The import runs successfully, but no records are created in the Incident table. Which two steps should the administrator verify to resolve this issue?

Accepted Answer

Confirm the Data Source is associated with the Import Set Row.. The Data Source must be associated with the Import Set Row to define how the incoming data is parsed and mapped. Without this association, the Import Set cannot process the data correctly, even if the import runs without errors. This is a fundamental requirement in ServiceNow's import architecture.

Answer

Ensure the import source is an email integration.

Answer

Review the Import Set Row condition field to ensure it is not set to 'Skip'.

Answer

Check that the Import Set table has a 'Staging Table' defined.

Question 10

A company uses Service Operations Workspace to manage incidents. They have configured an SLA definition for 'Resolution' with a stop condition when the incident state is 'Resolved'. However, the SLA is not stopping when the incident is resolved. The administrator checks the SLA log and sees that the SLA is still running. The SLA definition is active and attached to a specific SLA definition record. The administrator notices that the incident state is indeed set to 'Resolved', and the SLA timeline is set to 24x7. What should the administrator do to fix the issue?

Accepted Answer

Review and correct the stop condition in the SLA definition to properly reference the incident state field.. The SLA stop condition is a condition script that must evaluate to true for the SLA to stop. If the stop condition does not correctly reference the incident state field (e.g., using 'state' instead of 'incident_state' or a wrong value), the SLA will continue running even when the incident is resolved. The administrator must review and correct the stop condition script to ensure it properly checks for the 'Resolved' state.

Answer

Ensure the SLA definition's timeline is set to '24x7'.

Answer

Create a business rule to stop the SLA when the incident resolves.

Answer

Set the SLA definition's 'Stop on Resolution' field to true.

Question 11

A large import set of 10,000 user records from an HR system is failing intermittently during transformation to the sys_user table. Some rows are inserted successfully, but others show errors in the import log: 'Transform script error: null reference at line 15 of the transform map script.' The administrator reviews the transform map and finds a script that sets the department field by looking up a department table. The script assumes the department code always exists in the department table, but some records have codes that are not present. The administrator needs to ensure all rows are imported reliably, even if some data is missing. What is the best course of action?

Accepted Answer

Fix the transform script to check for the existence of the department code before using it, and set a default value or skip the field if not found. Then use an Import Set Row condition to only process rows that are valid.. It directly addresses the root cause: the transform script fails when a department code is missing from the reference table. By adding a null check before using the lookup result and providing a default or skipping the field, the script becomes resilient to missing data. Using an Import Set Row condition then ensures that only rows with valid department codes are processed, preventing the intermittent null reference errors while still importing all other rows successfully.

Answer

Use a 'Run as GlideRecord' operation in the transform map to ensure each row is processed individually.

Answer

Create a separate import set for each user record to isolate failures.

Answer

Add a condition to skip rows that have null values in the department field.

Question 12

A manager requests a report showing the average time to resolve incidents, grouped by assignment group, for the last month. The administrator creates a report on the Incident table using a bar chart with a 'Group By' on Assignment group and a 'Aggregate' on Resolved time (duration). The report displays an average that seems too low. Upon investigation, the administrator notices that incidents with very long resolution times (e.g., over 30 days) are not included in the report. The report filter is set to 'Active = false' and 'Resolved time is not empty'. The administrator suspects the time filter is incorrect. What is the most likely cause of the missing long-duration incidents?

Accepted Answer

The report uses a relative time filter that filters on the 'Created' date instead of the 'Resolved' date, excluding older incidents that were resolved in the last month.. The report uses a relative time filter that defaults to filtering on the 'Created' date rather than the 'Resolved' date. This means only incidents created within the last month are considered, even if they were resolved later. Incidents with very long resolution times (e.g., over 30 days) that were created before the filter window but resolved in the last month are excluded, causing the average to appear too low.

Answer

The average calculation is using median instead of mean.

Answer

The report is based on a saved search that excludes incidents with 'Closed' state.

Answer

The report filter excludes incidents with state 'Resolved'.

Question 13

A ServiceNow administrator needs to create a report that shows all incidents with a priority of '1 - Critical' that have been assigned to the 'Hardware' assignment group. The report should only include incidents that were created in the last 30 days. Which approach should the administrator take to create this report?

Accepted Answer

Create a report using the 'Incidents' module, add a condition for 'Priority equals 1 - Critical' AND 'Assignment group equals Hardware', then use the 'Created on' condition with 'On or after (relative) today - 30 days'.. It uses the 'Incidents' module (which automatically restricts the report to the Incident table) and applies the correct condition syntax for a relative date range: 'On or after (relative) today - 30 days'. This ensures only incidents created within the last 30 days are included, while the other conditions filter for priority '1 - Critical' and assignment group 'Hardware'.

Answer

Create a report using the 'Tasks' table, filter by 'Incident' and then apply the conditions for priority, assignment group, and created on.

Answer

Create a report using the 'Incidents' module, add a condition for 'Priority equals 1 - Critical' AND 'Assignment group equals Hardware' AND 'Created on is relative today - 30 days'.

Answer

Create a report using the 'Assignment groups' module, then filter incidents with priority critical.

Question 14

Refer to the exhibit. A ServiceNow administrator has created an SLA definition for critical incidents. Which TWO statements accurately describe the behavior of this SLA?

Accepted Answer

The SLA will start when an incident with priority 1 is created.. The SLA definition is configured to start when an incident is created with priority 1, as indicated by the 'Start condition' set to 'Priority is 1' and 'Start type' set to 'Created'. Option E is correct because the 'Stop condition' is set to 'State is 6 (Resolved)', which means the SLA timer will stop once the incident reaches the Resolved state.

Answer

The SLA will reset if the incident priority changes to a higher value.

Answer

The SLA will pause when the incident is placed on hold (state=3).

Answer

The SLA applies to incidents with priority 1 and priority 2.

Question 15

A ServiceNow administrator is responsible for importing data from an external HR system into the Employee table. The import set uses a transform map that creates new records and updates existing ones based on the employee number. Recently, the administrator noticed that some existing records are being incorrectly duplicated. The transform map is configured with a coalesce on the 'Employee Number' field. After reviewing the import log, the administrator finds that the import set rows are being processed, but the coalesce is not matching correctly. The HR system sends data with employee numbers that have leading zeros, but the ServiceNow employee number field is stored without leading zeros. For example, employee number '0123' in the source is '123' in ServiceNow. The administrator needs to fix this issue without modifying the HR system data. Which course of action should the administrator take?

Accepted Answer

Add a script in the transform map to remove leading zeros from the employee number before the coalesce runs.. The coalesce operation in a transform map runs before field mapping scripts, so a script placed in the transform map's 'Script' field (or a 'Before' script) can normalize the source value by removing leading zeros before the coalesce attempts to match. This ensures the incoming '0123' is converted to '123' and correctly matches the existing record in the Employee table.

Answer

Modify the import set table to store employee numbers as strings with leading zeros.

Answer

Change the coalesce field to a different unique field such as email address.

Answer

Use a before business rule on the Employee table to trim leading zeros on the employee number field.