Service Level Agreements practice questions

SLA Definition [contract_sla]

Why wrong: Contract SLA stores the definition templates, not the individual runtime instances needed for duration reporting.

Metric Instance [metric_instance]

Why wrong: Metric instance tracks database field durations, not native SLA runtime metrics.

Case [sn_customerservice_case]

Why wrong: While cases contain SLA flags, detailed SLA duration and breach metrics reside on the Task SLA table.

In the SLA Engine Properties module

Why wrong: Engine properties configure background worker behavior, not visual stages.

In Service Portal widget configurations

Why wrong: Service Portal widgets only render what the server provides; they do not define data engine stages.

In the Workflow Editor stage mapping settings

Why wrong: Workflows can interact with stages, but SLA stages are native to the Task SLA lifecycle engine.

Case [sn_customerservice_case]

Why wrong: While Case extends Task, SLA Definitions are created on the Task SLA [sow_sla] or SLA Definition [contract_sla] table, which uses Task as the base table to evaluate extended tables.

SLA Definition [contract_sla]

Why wrong: Contract SLA is the table where the definition record itself is stored, not the base table targeted by the SLA condition.

Customer Account [customer_account]

Why wrong: The Customer Account table is not a task-based table and cannot support task SLAs natively without custom relationships.

In a Business Rule running on the Task SLA table

Why wrong: Custom business rules on Task SLA are discouraged for native pause logic, as the SLA engine handles this out of the box.

In the SLA Workflow using a Timer activity

Why wrong: Timers in workflows are for delays, not for managing the internal Pause state of the Task SLA engine.

In the SLA Definition record using the Pause condition field

Why wrong: Wait, the pause condition is configured directly on the SLA Definition record. Let's check option D.

Customer SLA

Why wrong: Customer SLA is not a standard native SLA type classification in ServiceNow.

Resolution SLA

Why wrong: Resolution SLAs measure the time from creation to resolution/closure.

Operational SLA

Why wrong: Operational SLAs define agreements between internal departments, not primary case metrics.

SLA Properties set in Service Level Management properties

Why wrong: Global SLA properties define general engine behavior, not specific 75% warnings for individual definitions.

SLA Workflow with a Workflow Timer set to 75%

Why wrong: SLA workflows can be attached, but percentage-based triggers are typically handled using SLA Percentage or Breach stages.

Data Policy enforcing notification fields at 75%

Why wrong: Data policies enforce mandatory and read-only states, not workflow notifications.

In the Dictionary entry for the Case priority field

Why wrong: Dictionary entries define field attributes and choices, not operational schedules.

In the System Properties under com.glide.sla.business_hours

Why wrong: System properties do not control specific custom business hours schedules for individual SLAs.

In the Workflow properties of the attached SLA workflow

Why wrong: SLA workflows handle actions upon breach or warning, but do not dictate the base calendar schedule.

The system automatically cancels the Response SLA breach when the Resolution SLA is met.

Why wrong: Meeting one SLA does not retroactively cancel the breach state of a different completed SLA.

The Case indicator remains normal because the Resolution SLA was met.

Why wrong: A breach on any attached SLA typically causes the task's SLA indicator to show breached.

The SLA engine deletes the Response SLA record to keep reporting clean.

Why wrong: SLA records are preserved for auditing and reporting purposes and are never automatically deleted upon resolution.

They are deleted from the database immediately.

Why wrong: SLA records are never deleted upon task cancellation; their state is updated to Cancelled for auditing.

They remain paused indefinitely.

Why wrong: Cancellation terminates the lifecycle rather than leaving them in a perpetual paused state.

They continue running until they reach their breach time.

Why wrong: Running SLAs on a cancelled task are terminated to prevent false breaches.

sn_customerservice_manager

Why wrong: Managers oversee cases and reports but do not inherently have SLA configuration rights without specific admin roles.

sn_customerservice_agent

Why wrong: Agents handle cases, not SLA definition setups.

itil

Why wrong: The ITIL role is for ITSM processes and does not grant CSM SLA definition management.

Reset condition

Why wrong: Reset conditions restart the SLA lifecycle entirely.

Pause condition

Why wrong: Pause conditions temporarily halt the timer without completing the SLA.

Start condition

Why wrong: Start conditions determine when the SLA begins tracking.

Modify the base system SLA Workflow script to query account tiers dynamically.

Why wrong: SLA durations are set at the definition level; scripting workflows for this purpose violates best practices.

Configure a client script to prompt the agent for the duration when the case is opened.

Why wrong: SLAs are calculated automatically by the backend engine, not prompted via client scripts.

Write a custom business rule to overwrite the duration field on the task_sla table.

Why wrong: Custom business rules are unnecessary because SLA definitions support filtering by account attributes.

It determines which user group receives breach notifications.

Why wrong: Notification recipients are managed via workflow notifications or email notifications, not the Target field.

It restricts the SLA to a specific customer tier.

Why wrong: Customer tiers are filtered using start and stop conditions or account criteria.

It defines the specific workflow that executes when the SLA breaches.

Why wrong: Workflows are defined in a separate field on the SLA definition record.

In the SLA Definitions module under System Policy

Why wrong: SLA Definitions are configuration records, not runtime user views.

In the System Log module

Why wrong: System logs are for debugging and technical errors, not user-facing case tracking.

In the Metric Definitions table list view

Why wrong: Metric definitions are underlying reporting metrics, not the agent case interface.

Notification activity with incident payload mapping

Why wrong: Notification activities send emails; they do not generate database records.

SLA Breach Action business rule

Why wrong: There is no native business rule named 'SLA Breach Action'.

Run Script activity using current.insert() on the Incident table

Why wrong: While possible, using raw script in workflows is less maintainable than native workflow activities like Create Task.

Delete the SLA Definition before making updates

Why wrong: Deleting definitions breaks historical reporting and active SLA linkages.

Disable the SLA background worker thread

Why wrong: Disabling background workers stops all SLA processing globally.

Lock the Task SLA table using Access Control Lists (ACLs)

Why wrong: ACLs control security read/write, not engine calculation behavior.

The system will throw a severe security exception due to table-level ACL restrictions.

Why wrong: Admins and specific roles have insert access, so security exceptions are not the primary programmatic risk.

Dictionary overrides on the task_sla table will fail to load.

Why wrong: Dictionary overrides are evaluated at the schema level, independent of manual insertion.

The scheduled job processor will immediately delete the manually inserted record.

Why wrong: Scheduled jobs do not delete valid task SLA records.

To retroactively change the duration of the SLA

Why wrong: Durations are configured on the definition, not altered via reset conditions.

To pause the SLA timer until further notice

Why wrong: Pausing is handled by the pause condition.

To mark the SLA as successfully completed

Why wrong: Completion is handled exclusively by the stop condition.

Cancelled

Why wrong: Cancelled indicates the task or SLA was aborted.

Breached

Why wrong: Breached indicates failure to meet the target time.

Achieved

Why wrong: Achieved is not the standard ServiceNow SLA stage name (Completed is used). Let's check option C.

All matching SLAs attach simultaneously, creating multiple competing timers.

Why wrong: While multiple SLAs can attach, precedence or specific conditions prevent overlapping conflicts based on definition configuration.

The system prompts the user to select the correct SLA during case creation.

Why wrong: SLA attachment is entirely automated by the backend engine.

ServiceNow processes SLAs alphabetically by name.

Why wrong: Alphabetical processing is not used for SLA precedence.