Reporting, SLA and Imports practice questions

17:00

Why wrong: 17:00 is the assignment time. The breach time is not based on assignment unless assignment triggers a different SLA start, which is not indicated. Without resolution duration, this cannot be the breach time.

16:30

Why wrong: 16:30 is the creation/start time. The breach time is start time + resolution duration, which is always after the start time, so this is incorrect.

18:00

Why wrong: 18:00 is an arbitrary time. No basis for this value is provided in the question. It cannot be determined.

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

Why wrong: The stem states the incidents are active, so they cannot be closed. The 'Active = true' condition would be met for active incidents, so the issue must be elsewhere.

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

Why wrong: This is unnecessary because the 'Active = true' condition already ensures only active incidents are considered.

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

Why wrong: Group assignment does not affect SLA triggering; SLA definitions apply to all incidents that meet the condition, regardless of assignment.

Re-create the import set definition

Why wrong: Re-creating the import set definition is not necessary and would not fix a script referencing a non-existent table. The error is in the transform map script, not the import set definition.

Change the data source type

Why wrong: Changing the data source type would not resolve a script error referencing a missing table. The data source type determines how data is parsed, not table references.

Run the import set in a different scope

Why wrong: Running the import set in a different scope would only change which tables are visible; if the table does not exist in any scope, this will not help. The error says the table does not exist, so scope is irrelevant.

Import set row errors

Why wrong: Import set row errors capture row-level failures like missing mandatory fields or data type mismatches, but not JavaScript script execution errors. The error here is a script execution error, so row errors are not the primary source.

Data source configuration

Why wrong: Data source configuration defines how to connect to the import source; it does not store runtime script errors from field map scripts.

Transform map's field map log

Why wrong: The transform map's field map log shows the field mapping configuration, but not runtime script execution details or error messages.

The SLA has breached its response time

Why wrong: A breach occurs when the SLA timer expires, but a processing error indicates a configuration issue, not a breach. Thus, this option is incorrect.

The SLA definition's condition is not satisfied

Why wrong: The SLA definition's condition determines when an SLA starts, but a processing error during SLA processing typically indicates a schedule issue, not a condition failure. Thus, this option is incorrect.

The SLA response time has exceeded the target

Why wrong: The error log entry is about processing the SLA, not about the response time exceeding the target; that would be a breach event, not a processing error. Thus, this option is incorrect.

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

Why wrong: Business rules run after insert, not during mapping.

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

Why wrong: The API inserts raw data; mapping is done via transform map.

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

Why wrong: Manual editing is not scalable and error-prone.

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

Why wrong: Time scale is not a standard report setting; it's the filter that controls date range.

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

Why wrong: Report type does not affect data inclusion.

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

Why wrong: Group by field determines aggregation, not data filtering.

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

Why wrong: SLA is based on the incident record, not the assignment group.

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.

Why wrong: Business hours would extend real time, not cause a breach within 3 hours.

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

Why wrong: The condition is evaluated at trigger time; changes after do not affect SLA.

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

Why wrong: The import set row table contains the raw data; the error is during transform to the target table.

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

Why wrong: The error says the field is not found in the target table, not the source.

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

Why wrong: Data type mismatch would cause a different error (e.g., invalid data).

Bar chart report with a condition for resolved incidents.

Why wrong: Bar chart is a presentation type, not the underlying data aggregation.

Pivot table report with a 'Average' aggregation.

Why wrong: Pivot tables are for multi-dimensional analysis, not simple average.

Scorecard report with a metric for average resolution time.

Why wrong: Scorecards are for performance indicators, not dynamic data aggregation.

5:45 PM Friday.

Why wrong: This ignores the business schedule and assumes 24/7 counting.

4:45 PM Saturday.

Why wrong: The schedule does not include weekends.

4:45 PM Monday.

Why wrong: This would be if the full hour was counted from Monday start, but only 45 minutes remain.

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

Why wrong: Pie chart does not show trends over time.

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

Why wrong: List report does not produce a line chart.

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

Why wrong: Bar chart is not a line chart.

Schedule the import to run automatically.

Why wrong: Scheduling is optional; imports can be run manually.

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

Why wrong: The API is not required; transform maps can be created via the UI.

Create a data lookup table to standardize values.

Why wrong: Data lookup is optional, not required.

Create a business rule on the Incident table that checks the SLA percentage.

Why wrong: Business rules run on database operations, not on SLA timing events.

Create a scheduled job that runs every minute to check SLA percentages.

Why wrong: Scheduled jobs are not efficient and not part of SLA automation.

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

Why wrong: All tables have a sys_id field.

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

Why wrong: The import set table is the source, not the target.

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

Why wrong: SLAs can be triggered at any time; restricting to business hours would miss off-hours incidents.

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

Why wrong: This changes business requirements; the question states without changing requirements.

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

Why wrong: Less frequent updates may cause delayed breach detection and could worsen breach percentage.

In Progress (still running)

Why wrong: The SLA breached at 1 PM, so it is not still running.

In Progress (not breached)

Why wrong: The SLA has already breached because 5 business hours have elapsed.

Breached (at 2 PM)

Why wrong: The breach occurred at 1 PM, not 2 PM.

The import fails because the 'manufacturer' field is not mapped

Why wrong: Unmapped fields are not imported but do not cause failure.

The 'name' field contains 'Laptop123, 12345' because the script for 'serial_number' overrides the co-paste for 'name'

Why wrong: Scripts run per target field; co-paste for 'name' uses source values, not the script output for 'serial_number'.

The 'serial_number' field remains '12345' because the co-paste mapping for 'name' consumed the source field

Why wrong: Source fields are not consumed; they are available for multiple mappings.

List report, sort by Opened

Why wrong: List report does not aggregate counts.

Pie chart, group by Month on the Opened field

Why wrong: Pie chart is for proportions, not trend over time.

Line chart, group by Day on the Opened field

Why wrong: Grouping by day would show daily counts, not monthly, and line chart is less typical for this purpose.

When a task is not updated for 24 hours

Why wrong: SLA triggers require a condition on the record, not a timeout.

When a scheduled job runs at a specific time each day

Why wrong: SLA triggers are based on record events, not time-based jobs.

Automatically for every record in the incident table

Why wrong: SLA definitions apply based on conditions, not to all records.