CCNA Reporting Sla Imports Questions

Why this answer

How to eliminate wrong answers

Option A is wrong because the SLA does not pause and resume; it stops when the condition is no longer met, and a new instance starts when the condition is met again. Option C is wrong because the SLA does not resume with the same elapsed time; it stops completely and a new SLA instance begins with a fresh timer. Option D is wrong because the SLA does not continue running; it is condition-based, and once the priority changes away from 1, the condition fails and the SLA stops.

Why this answer

How to eliminate wrong answers

Option A is wrong because a Bar chart report is a visualization type, not a report type that supports automatic updating of aggregated data; it requires a data source that must be manually refreshed or scheduled. Option B is wrong because a Pivot table report is designed for cross-tabulation and grouping, not for automatically updating a single average metric over time; it would need manual re-run to reflect new incidents. Option C is wrong because a Scorecard report is used for performance indicators with targets and thresholds, not for simple average calculations; it relies on pre-defined metrics that do not automatically update with new incident resolutions.

Why this answer

How to eliminate wrong answers

Option A is wrong because duplicate rows in the CSV would cause duplicates only if the transform map does not use coalesce to deduplicate; the question states 'several records are duplicated' implying the issue is systematic, not just repeated rows. Option B is wrong because an index on the number field would help enforce uniqueness and prevent duplicates, not cause them—indexes improve lookup performance but do not control import deduplication logic. Option D is wrong because exceeding the import set row limit would cause the import to fail or truncate, not create duplicate records; the limit caps the number of rows processed per import set run.

Why this answer

How to eliminate wrong answers

Option B is wrong because scheduling the SLA job only during business hours would delay SLA processing for incidents created outside those hours, potentially causing breaches due to late evaluation and violating business requirements. Option C is wrong because disabling SLA evaluation for low-priority incidents changes the business requirements by removing SLA coverage for those incidents, which is not allowed per the question. Option D is wrong because increasing the SLA job interval from 1 minute to 5 minutes reduces execution frequency but does not address the root cause of excessive processing per execution; it would simply delay breach detection and could worsen the backlog of queued jobs.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because removing the incident from the SLA definition condition would modify the definition itself, potentially affecting future incidents that match the condition, and it does not stop tracking for the specific incident already attached. Option C is wrong because setting the SLA definition to inactive would stop all SLA tracking for any incident using that definition, not just the specific incident. Option D is wrong because deleting the SLA record from the SLA table would remove the historical data and could cause errors or data integrity issues; the correct approach is to cancel the SLA on the indicator, not delete the record.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the SLA schedule (24x7) would not prevent the SLA from starting; it only defines when time counts toward the SLA, not whether the SLA starts. Option B is wrong because a pause condition would stop an already-running SLA, not prevent it from starting; the issue is that the SLA never starts. Option D is wrong because the SLA definition is explicitly configured on the 'incident' table (as stated in the question), so being on the 'task' table would not apply here and would not cause this behavior.

Why this answer

How to eliminate wrong answers

Option A is wrong because import set row errors capture row-level import failures (e.g., missing required fields, invalid reference qualifiers), but they do not contain JavaScript execution errors from script actions. Option B is wrong because the data source configuration defines how to connect to the source and parse records, but it does not log runtime script errors. Option C is wrong because the transform map's field map log shows field mapping details and transformation results, but it does not capture script execution errors; those are logged in the system log.

Why this answer

How to eliminate wrong answers

Option A is wrong because sharing a report link via email does not grant dashboard access; it only shares a static snapshot or link that may fail due to ACL restrictions, and it requires individual recipients to have appropriate permissions. Option B is wrong because ServiceNow dashboards do not have a 'Public' setting; visibility is controlled via roles, not a public toggle, and making a dashboard public would violate security best practices. Option C is wrong because publishing a dashboard to a homepage only makes it visible on that specific homepage, not to the entire team, and homepage visibility is still governed by role-based access controls.

Why this answer

How to eliminate wrong answers

Option A is wrong because it assumes the entire 2-hour SLA duration was consumed, but the SLA was paused for 30 minutes while on hold, so the actual elapsed time is less. Option B is wrong because it incorrectly calculates from the first state change at 10:30 to resolve at 12:00, which is 1 hour 30 minutes, but this ignores the initial 30 minutes in 'New' state that also counts toward the SLA. Option D is wrong because it only counts the time after the hold period (11:30 to 12:00), omitting the 30 minutes in 'New' and the 30 minutes in 'In Progress' before the hold.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the business rule that triggers SLA recalculation is responsible for updating the SLA after changes, but it does not directly control the pause behavior; a misconfigured pause condition would still cause the timer to run even if the recalculation rule is active. Option B is wrong because checking the SLA metric timeline shows historical data on timer states but does not identify why the pause condition failed to trigger; it is a diagnostic tool, not the first step in troubleshooting a configuration issue. Option D is wrong because the SLA schedule's 'Pause' field is used to define non-working hours or holidays that pause the timer, not to pause the timer based on a specific incident state like 'Awaiting Customer'; that state-based pause is controlled by the pause condition on the SLA definition itself.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because there is no coalesce conflict; the coalesce field 'number' matches exactly one existing record, so the transform proceeds with an update. Option B is wrong because a new record is created only when no matching record is found via the coalesce field; here a match exists. Option C is wrong because the coalesce field 'number' is valid and correctly configured to identify duplicates; it is not invalid.

Why this answer

How to eliminate wrong answers

Option B is wrong because creating a scheduled job to delete old import set rows is an unnecessary workaround; the platform provides a built-in mechanism for automatic cleanup after transform, making a scheduled job redundant and less efficient. Option C is wrong because setting a retention policy on the import set table is not a native feature of ServiceNow for import set tables; retention policies are typically used for syslog or other log tables, not for import set staging tables. Option D is wrong because using a business rule to delete the import set row after transform is overly complex and error-prone; the 'Cleanup after transform' checkbox achieves the same result declaratively without custom scripting.

Why this answer

How to eliminate wrong answers

Option B is wrong because the import set row table (sys_import_set_row) stores the raw data from the source; the error specifically states the field is not found in the target table, not the import set row table. Option C is wrong because a misspelled column in the source CSV would cause a different error (e.g., 'Field not found in source') or a mapping failure, but the error explicitly says the field is not found in the target table, not the source. Option D is wrong because a data type mismatch would produce a different error (e.g., 'Cannot convert data type'), not a 'field not found' error; the error is about the existence of the column, not its type.

Why this answer

How to eliminate wrong answers

Option A is wrong because a homepage with an iframe embeds external content and does not provide native auto-refresh capability for ServiceNow reports; it would require custom scripting or external page refresh. Option C is wrong because Performance Analytics indicators are designed for tracking KPIs and trends over time, not for refreshing multiple reports on a dashboard at a fixed interval. Option D is wrong because report scheduling sends reports via email or stores them as snapshots, but does not automatically refresh a live dashboard view for users.

Why this answer

How to eliminate wrong answers

Option B is wrong because if the field mapping's 'Field name' were incorrect, the import would either fail with a field-not-found error or populate a different field, not leave the target field empty after the script runs. Option C is wrong because the script for a transform field mapping is written directly in the 'Script' field of the mapping, not in a separate Script Include; checking a Script Include is irrelevant. Option D is wrong because the staging table field is only used to store the source value before transformation; the target field being empty is a post-transform issue, not a staging table schema issue.

Why this answer

How to eliminate wrong answers

Option A is wrong because the error is about a missing source field, not about the target field being read-only; a read-only target field would cause a different error during field assignment. Option C is wrong because the 'caller_id' field is a standard reference field on the Incident table, and the error message does not indicate a missing target field. Option D is wrong because the co-paste function can combine multiple fields (up to 10 by default), and the error is not about exceeding a field limit but about a missing source column.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because a line chart of daily resolved incidents shows a trend over time but does not break down by assignment group or SLA compliance, missing the key grouping requirement. Option C is wrong because a bar chart showing total incidents per group lacks the SLA status dimension, so it cannot distinguish within-SLA from breached incidents. Option D is wrong because a pie chart showing overall SLA compliance percentage aggregates all groups together, failing to provide per-assignment-group breakdown.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because splitting the report into two separate reports changes the output — the original OR condition produces a combined result set, and two separate reports would require manual merging, altering the report's output. Option C is wrong because increasing the timeout does not improve performance; it only allows the report to fail later, leaving the underlying slow query unchanged. Option D is wrong because adding indexes on filter fields may help with simple lookups but does not address the performance cost of joining multiple tables and aggregating large datasets; indexes are less effective for complex joins and aggregate queries compared to pre-computed summary fields.

Why this answer

How to eliminate wrong answers

Option A is wrong because the time_of_day setting is used to specify when the report runs; an incorrect value would cause it to run at the wrong time, not fail to execute entirely. Option B is wrong because the frequency being set to 'daily' is valid and does not require additional scheduling; the schedule is defined by the frequency and time_of_day fields. Option C is wrong because roles are not required for a report to execute; roles control access to the report, not its scheduling or execution.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the report source definition determines what data the report queries, not how the results are delivered; if the report generates successfully, the source definition is working. Option B is wrong because checking the report filter for data existence is irrelevant if the report already generated; the issue is with notification delivery, not data population. Option C is wrong because the output format (PDF, CSV, etc.) affects the file attached to the email, but if the email is not being sent at all, the format is not the root cause.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the condition script does not prevent the SLA from starting for all states; it only prevents starting for the explicitly listed standard states (1,2,3,6,7), meaning the SLA will start for any other state. Option C is wrong because 'In Progress' corresponds to state value 2, which is explicitly excluded by the condition (currentState != 2), so the SLA does not start when the incident is in 'In Progress'. Option D is wrong because 'New' corresponds to state value 1, which is also excluded by the condition (currentState != 1), so the SLA does not start when the incident is in 'New'.

Why these pairings

Why this answer

How to eliminate wrong answers

Option A is wrong because the timeline is already set to 24x7, as noted in the scenario, so changing it again will not fix the stop condition issue. Option B is wrong because creating a business rule to stop the SLA is unnecessary and not the standard approach; SLA stop conditions are handled natively within the SLA definition itself. Option D is wrong because there is no 'Stop on Resolution' field in SLA definitions; the stop behavior is controlled entirely by the stop condition script.

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the 'Time scale' setting in a report controls how time is displayed on the x-axis (e.g., grouping by day, week, month), not which records are filtered out; it does not limit the data to the current week. Option B is wrong because the type of report (bar chart, pie chart, etc.) affects visualization, not the underlying data set; all report types show the same aggregated data from the same filtered records. Option D is wrong because the 'Group by' field determines how data is categorized (e.g., by assignment group vs. assigned to), not the time range of records; changing it would not resolve the issue of missing resolved incidents.

Why this answer

How to eliminate wrong answers

Option A is wrong because a missing staging table would cause a different error, such as 'Staging table not found' or a failure during the import set creation, not an 'Invalid table name' error. Option B is wrong because a corrupt source file would typically result in parse errors or malformed data, not a table name validation error. Option C is wrong because a transform map referencing a missing table would cause an error during transform map execution, but the 'Invalid table name' error occurs at the import set row level, before the transform map runs.

Why this answer

How to eliminate wrong answers

Option A is wrong because unmapped fields in an import set row do not cause the import to fail; they are simply not populated in the target table. Option C is wrong because the script for 'serial_number' does not override the co-paste for 'name'; both mappings operate independently on their respective target fields. Option D is wrong because the co-paste mapping for 'name' does not consume the source 'serial_number' field; it reads it as a source value but does not remove it from the row, so the 'serial_number' mapping still receives the original source value.

Why this answer

How to eliminate wrong answers

Option A is wrong because a before business rule runs after the record is inserted, meaning the reference field would already have failed validation or stored an incorrect value; it's too late to convert the department name to a sys_id. Option C is wrong because the Import Set Row API is used for programmatic row-level operations, not for defining reusable field-level mappings or lookups; it bypasses the transform map's declarative capabilities. Option D is wrong because manually editing the CSV to include sys_id values is error-prone, not scalable, and violates the principle of automated, repeatable imports; ServiceNow provides transform maps precisely to avoid this.

Why this answer

How to eliminate wrong answers

Option A is wrong because a pie chart cannot display trends over time as a line chart; it shows proportions at a single point in time, not daily counts over 30 days. Option B is wrong because a list report with 'Count' aggregation grouped by 'Opened' and 'Category' produces a tabular list, not a line chart, and cannot visualize the data as a line chart with multiple lines. Option D is wrong because a bar chart with 'Group by' set to 'Category' and 'Stacked' set to 'Yes' creates stacked bars, not separate lines; stacking would combine categories into a single bar per day, obscuring individual category trends.

Why this answer

Why this answer

How to eliminate wrong answers

Option B is wrong because the SLA was paused at 09:30, so the pause duration cannot be 0 minutes; a pause event occurred. Option C is wrong because 45 minutes would imply the pause started at 09:00 and ended at 09:45, but the pause began at 09:30, not 09:00. Option D is wrong because 30 minutes would require the pause to last from 09:15 to 09:45 or 09:30 to 10:00, but the resume time is 09:45, making 15 minutes the correct duration.

Why this answer

How to eliminate wrong answers

Option A is wrong because the admin role is a global administrator role that provides full system access, but it is not specifically required for creating reports; the report_admin role is the designated role for report creation. Option B is wrong because the report_user role only permits viewing and executing existing reports, not creating new ones. Option D is wrong because report_creator is not a valid role in ServiceNow; the correct role for creating reports is report_admin.

Why this answer

How to eliminate wrong answers

Option A is wrong because a breached response time would generate a breach notification or state change, not an error log entry during processing. Option C is wrong because an unsatisfied condition would prevent the SLA from starting or applying, but it would not produce a processing error; the SLA would simply not be created. Option D is wrong because exceeding the target is the definition of a breach, which is a state, not a processing error; the error log entry points to a configuration issue, not a timing violation.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because 'Run as GlideRecord' processes each row individually but does not fix the null reference error; the script would still fail on rows with missing department codes. Option B is wrong because creating a separate import set for each record would be impractical and does not solve the underlying script logic issue; it would also break the batch import process and increase administrative overhead. Option D is wrong because skipping rows with null values in the department field would discard valid records that simply lack a department code, whereas the requirement is to import all rows reliably, possibly with a default value for missing data.

Why this answer

How to eliminate wrong answers

Option A is wrong because scheduling a report to run daily does not affect whether data appears; scheduling only controls when the report is generated, not the visibility of data. Option B is wrong because a bar chart can display numeric data; the chart type is a visualization choice and does not cause an empty report. Option D is wrong because a modulo condition on sys_id would filter results but would not cause a report to show no data unless the condition is impossible; even then, it would be a logical filter issue, not a permissions or context issue.

Why this answer

How to eliminate wrong answers

Option A is wrong because the SLA is not 'in progress (still running)' — the 4-hour duration has already elapsed by 2 PM Monday, so the SLA is breached, not still running. Option B is wrong because 'in progress (not breached)' implies the SLA is still within its allowed time, but the 4-hour window ended at 1 PM, so it is breached. Option D is wrong because the breach occurs at 1 PM, not 2 PM — the 4-hour duration from the schedule start (9 AM) ends at 1 PM, making 2 PM a post-breach state.

Why this answer

How to eliminate wrong answers

Option B is wrong because the caller_id condition is met (caller_id=user1 matches the definition), so it does not prevent the SLA from starting. Option C is wrong because the category condition is met (category='network' matches the definition), so it does not prevent the SLA from starting. Option D is wrong because SLA conditions must be fully met; partial satisfaction does not trigger the SLA start.

Why this answer

How to eliminate wrong answers

Option B is wrong because if the import source file was empty, no rows would be created in the import set table during the import, but the question states rows are not appearing after running the import, implying the import ran successfully but rows are missing. Option C is wrong because if the transform map condition rejected all rows, the rows would still exist in the import set table (they would just not be transformed into target records), so they would appear in the import set table. Option D is wrong because if the transform map action is set to 'Create' and coalesce matches no records, the transform would create new target records, but the import set rows would still remain in the import set table unless explicitly deleted.

Why this answer

How to eliminate wrong answers

Option B is wrong because a List report displays raw data in a table format, not a visual bar chart, and sorting by Opened does not group or aggregate counts by month. Option C is wrong because a Pie chart shows proportions of a whole, not trends over time, and grouping by Month on the Opened field would create a pie slice per month, which is inappropriate for a 12-month time series. Option D is wrong because a Line chart could show trends but grouping by Day on the Opened field would produce daily data points, not monthly aggregates, and the requirement specifies months on the x-axis.

Why this answer

How to eliminate wrong answers

Option A is wrong because a Data Source configuration defines how to parse the CSV file (e.g., delimiter, encoding) but does not include row-level validation logic to filter out invalid emails. Option B is wrong because an Import Set Row is a staging record that holds the raw imported data; it does not provide a mechanism to conditionally prevent rows from being transformed or inserted. Option D is wrong because the Import Set Table API is used to programmatically load data into an import set table, but it does not enforce validation rules on individual field values like email format.

Why this answer

How to eliminate wrong answers

Option A is wrong because SLA recalculation business rules are used to recalculate SLA metrics after changes, not to control pause behavior; the issue is that the timer is not pausing, not that it needs recalculation. Option B is wrong because the SLA schedule's 'Pause' field defines when the SLA should pause based on time (e.g., weekends or holidays), not based on state changes like 'Awaiting Customer'. Option D is wrong because checking the SLA metric timeline would show the timer's history but does not identify the root cause of why the pause condition failed to trigger.

Why this answer

How to eliminate wrong answers

Option A is wrong because the script does not set the department for all imported records; it only sets it for records that have an employee ID and are being updated. Option B is wrong because the script does not cause an error due to a null target; the `target` object is always available in transform scripts, and the script safely uses `source.u_employee_id.nil()` to avoid null issues. Option C is wrong because while it correctly notes that records without employee ID are skipped, it incorrectly states that the script prevents updating department for new records; the script actually only updates department for existing records (update action) and does nothing for new records, so it does not 'prevent' an update that wasn't going to happen.

Why this answer

How to eliminate wrong answers

Option A is wrong because 11am Monday would be only 2 hours into Monday's schedule, totaling 4 hours (2 on Friday + 2 on Monday), not the full 8 hours required. Option B is wrong because 7pm Friday is outside the SLA schedule (9am-5pm), and the SLA clock stops at 5pm, so the breach cannot occur outside the defined schedule. Option C is wrong because 9am Monday is the start of the next scheduled window, but the remaining 6 hours have not yet elapsed, so the breach time must be later.

Why this order

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A (Default value) is wrong because it only sets a default value for a field when the source data is empty, and does not perform any deduplication logic. Option B (Ignore) is wrong because it simply skips the field during import, meaning the field is not mapped or processed, which does not prevent duplicate records. Option D (Run script) is wrong because it allows custom scripting for field transformation but does not inherently provide deduplication; while a script could be written to check for duplicates, the Coalesce operation is the dedicated, built-in mechanism for this purpose.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because the report explicitly uses an 'Aggregate' on Resolved time with a bar chart, which defaults to average (mean) unless median is selected; the issue is missing data, not the aggregation method. Option B is wrong because the report filter is set directly on the Incident table, not based on a saved search; a saved search would appear in the report source, and the filter 'Active = false' and 'Resolved time is not empty' already includes resolved and closed incidents. Option C is wrong because the filter 'Active = false' includes incidents with state 'Resolved' (since 'Active' is a boolean field that is false for both 'Resolved' and 'Closed' states); excluding 'Resolved' would require a specific state condition, not the 'Active' field.

Why this answer

How to eliminate wrong answers

Option A is wrong because scheduling a report via email sends a static snapshot of the data at that moment, but the email itself does not grant read access to the underlying table; the recipients still cannot view the live report or interact with it in the platform. Option C is wrong because exporting to PDF and emailing it manually is a manual, non-scalable workaround that does not leverage ServiceNow's sharing capabilities and still does not provide direct access to the report or its underlying data within the platform. Option D is wrong because setting the report's 'Share with' field to the Sales team group only shares the report object, but if the group members lack read access to the underlying table, they will receive an error or see no data when trying to view the report.

Why this answer

Why this order

Why this answer

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because removing the pause condition would not fix the issue; the SLA never starts because the start condition is not met, and pausing is irrelevant when the timer hasn't begun. Option C is wrong because the condition already includes 'Assigned to group is Hardware Support' and priority=2 is part of the SLA definition; updating the condition to include both again does not address the start condition problem. Option D is wrong because the SLA schedule defines business hours and excluding weekends is correct for the 4-hour resolution time; modifying it to include weekends would change the SLA's intended behavior and not fix the start condition issue.

Why this answer

How to eliminate wrong answers

Option B is wrong because changing the assignment group does not affect the SLA timer or breach calculation unless the SLA definition is scoped to a specific group and the group change triggers a re-evaluation, but the scenario does not indicate that. Option C is wrong because if the SLA duration is defined in business hours, the 4-hour window would be longer in real time, not shorter, so resolving in 3 real hours would not cause a breach. Option D is wrong because the SLA condition 'Category is Network' is evaluated when the SLA is triggered; updating the category field after the trigger does not retroactively invalidate the SLA, as the condition is checked at the time of trigger.

Why this answer

How to eliminate wrong answers

Option A is wrong because a bar chart grouped by day is a visual representation, but the question asks for a report type, not a chart type; ServiceNow list reports can display grouped data without requiring a chart. Option C is wrong because a pie chart shows proportions of a whole at a single point in time, not a trend over time. Option D is wrong because a line chart with date series on x-axis and count on y-axis is a chart type, not a report type; ServiceNow reports can include charts, but the most appropriate report type for viewing a trend is a list report with grouping.

Why this answer

How to eliminate wrong answers

Option B is wrong because it ignores the business schedule and assumes the SLA counts all calendar hours, which would incorrectly place the breach at 5:45 PM Friday. Option C is wrong because it incorrectly assumes the SLA runs through Saturday, but the business schedule excludes weekends entirely. Option D is wrong because it assumes the SLA pauses entirely over the weekend and resumes at 9:00 AM Monday, but fails to account for the 15 minutes of business time already consumed on Friday, leading to a breach at 4:45 PM Monday instead of the correct 9:45 AM Monday.

Why this answer

How to eliminate wrong answers

Option A is wrong because using the 'Tasks' table would include all task types (e.g., incidents, problems, changes) and requires an additional filter for 'Incident', which is unnecessary and can lead to performance issues or inclusion of unintended records. Option B is wrong because 'Created on is relative today - 30 days' is not a valid condition syntax in ServiceNow; the correct relative condition is 'On or after (relative) today - 30 days'. Option C is wrong because the 'Assignment groups' module is a configuration table for groups, not a data table containing incidents; it cannot be used to report on incident records directly.

Why this answer

Why this answer

How to eliminate wrong answers

Option A is wrong because an incorrect coalesce field would cause duplicate records or update failures, not a complete absence of records in the target table; the import log would typically show warnings or errors about coalesce mismatches. Option B is wrong because scheduling an import set during off-hours does not affect whether records appear in the target table; it only affects when the import runs. Option C is wrong because if the data source had been aborted, the import set would not run successfully and the import log would show an aborted status or error, not a successful completion.

Why this answer

How to eliminate wrong answers

Option A is wrong because an inactive schedule would show as 'Inactive' in the schedule record, and the question states the schedule is 'set to run daily'—implying it was configured but not executing, not that it was manually deactivated. Option B is wrong because sharing a report affects visibility and access, not the execution of a scheduled job; schedules run regardless of sharing settings. Option C is wrong because ServiceNow does not limit scheduled report execution based on row count; large reports may take longer or hit system limits, but they will still attempt to run and fail with an error, not silently not execute.

Why this answer