ServiceNow Certified Implementation Specialist - Customer Service Management (CIS-CSM) (CIS-CSM) (CIS-CSM) — Questions 226–255

The Task SLA [task_sla] table stores each running SLA instance against a task, so any runtime adjustment — pause, restart, or recalculated breach time — is written there, satisfying the requirement to audit changes to runtime instances rather than definitions.

The Pause condition on the SLA Definition determines when the SLA timer halts. Adding a condition matching State is Awaiting Problem pauses the running SLA, so it no longer accrues duration while the case sits in that state.

When a case is created through the CSM portal, the system automatically populates the Contact field with the contact record linked to the authenticated user. This ensures the case is related to the correct contact without manual entry. The administrator should verify that the portal's case creation logic correctly maps the logged-in user to their contact record, which is the standard behavior in CSM.

The Domain Path [sys_domain] field on the Account record enforces isolation by assigning each account to a domain within the domain hierarchy. Regional service agents inherit visibility only from their own domain, so accounts outside their geographic branch remain hidden, satisfying the requirement that agents view solely their region's accounts.

SLA Definitions are separate records, each with its own start conditions and duration. Referencing the Account Tier field in each definition's start condition lets the correct SLA attach based on tier, satisfying the requirement for tier-dependent durations without scripting.

Case State Flows define permitted transitions between states and support role-based transition conditions, so the Awaiting Info to Cancelled path can be restricted to sn_csm.manager. This enforces the lifecycle restriction declaratively rather than through UI policies.

Entitlements can be explicitly tied to an Account, defining what products or services that customer organisation is entitled to consume. This satisfies the stem's requirement, alongside Contact and Consumer as the other supported entity types.

Assignment Rules with Skill Matching evaluates case attributes against agent skills and capacity, automatically routing each new case to a qualified, available agent. This satisfies the requirement for skill-based and workload-balanced distribution without manual intervention.

The Start condition should trigger when the case is assigned to the specific group, as that is when the SLA timer should begin. The Stop condition should trigger when the case state becomes Closed, as that is when the SLA timer should end. This aligns with the business requirement and uses the appropriate condition types.

Review is a baseline knowledge workflow state in CSM, sitting between Draft and Published so articles receive approval before publication. It satisfies the stem's requirement for one of the three out-of-the-box lifecycle states, alongside Draft and Published.

The Case priority field is surfaced directly on the case form, so agents opening a case see the calculated priority without running reports or queries. This satisfies the requirement that agents view priority in their normal working interface.

The Pin option on the thread management menu fixes the announcement at the top of the category listing, ahead of chronologically ordered threads. This satisfies the visibility constraint, since pinning overrides normal sort order so every visitor encounters the announcement first.

Deduplication rules detect matching records by email and other fields, and merging consolidates the duplicates into one master contact, preserving related activities and history. This removes the ambiguity caused by slightly different email spellings without losing data.

Linking the Entitlement to Asset establishes the consumption relationship, so resolving a case against a covered asset decrements the account's remaining units. Without this field relationship, entitlement usage cannot be tracked against specific assets, and automatic decrementing on case resolution will not occur.

Completed marks the stage where the SLA's stop condition has been satisfied ahead of the breach time, halting the SLA timer. Unlike breached, which triggers when the breach time passes without resolution, completed confirms the task met its stop condition within the allotted window, directly satisfying the stem's requirement.

Virtual Agent and Live Chat are native CSM channels: both create cases through the Conversational Interfaces and chat channel configuration shipped out-of-the-box, requiring no custom integration. This satisfies the requirement for natively supported case creation channels.

Even when published and readable, an article may be absent from search if the search source or profile index has not indexed it. Verifying AI Search or Contextual Search Source configuration and index status addresses this indexing constraint.

Account Tier records service level such as Tier 1 or Tier 2, driving entitlement, escalation and support priority. It satisfies the stem's categorisation requirement by ranking accounts on value or service commitment, a different axis from type or geography.

The 'Schedule' field on the SLA definition determines which schedule is used to calculate elapsed time. By setting it to 'Business Hours', the SLA engine will only count time within the defined schedule periods. The 'Schedule source' field indicates where the schedule comes from; setting it to 'SLA definition' means the schedule specified on the SLA definition is used, which is correct for this scenario. This ensures the SLA pauses outside business hours as required.

Notification triggers are configured against case field events; a state change fires the notification when the case transitions, such as to Resolved or Closed. This satisfies the stem's requirement that state transitions can initiate a case notification.

Reset conditions recalculate an SLA's timeline when a specified field changes, so switching priority from Medium to Critical restarts the attached SLA against the shorter critical duration. This satisfies the stem's requirement that the existing SLA reflect the new critical target rather than continuing on the original timeline.

The Customer Relationship [customer_relationship] table stores peer and partner links between accounts, satisfying the requirement to establish non-hierarchical relationships. Unlike the account hierarchy, which handles parent-child structures, this table defines lateral connections such as partner or peer associations, directly meeting the stem's need for relationship methods between accounts.

Checking out a published article creates a separate draft version; the published version stays live and readable. Readers continue seeing the last published content until the draft is published, satisfying the requirement that the published version remains visible during editing.

Every active task record is repeatedly evaluated against start, stop, pause and reset conditions, so condition complexity and evaluation frequency drive engine load directly. More conditions and more frequent checks multiply the calculation work in high-volume environments.

Out-of-the-box notification records handle email dispatches when events occur on community content tables.

Entitlement consumption can be metered by time or effort rather than per-incident, so elapsed hours or logged effort decrement the entitled units. This satisfies the stem's requirement for how units are consumed when cases are created, reflecting effort-based rather than flat-rate deduction.

AI Search External Content Sources lets ServiceNow index and query content held outside its own tables, including community discussions on other instances or repositories. This directly satisfies the federated search requirement, since the connector framework retrieves external results at query time rather than relying on local knowledge bases or Microsoft Entra ID-authenticated directories.

Entitlement configuration defines which product models a contact may select. When an unsupported model is chosen, CSM either blocks submission outright or flags the case as out-of-entitlement, depending on the configured enforcement setting, satisfying the negotiated model-specific entitlement constraint.

Enclosing a phrase in double quotes in ServiceNow search (including Contextual Search) forces an exact phrase match. This excludes articles that contain the individual words separately. The agent will get only articles that have the exact sequence 'password reset failed', significantly narrowing results. This is the standard syntax for exact phrase search in ServiceNow.

Trust levels and reputation thresholds directly govern whether a post enters the moderation queue or publishes automatically. A high-trust author can bypass keyword or spam filters entirely, so a flagged post may reflect a misconfigured threshold rather than a rule fault. Investigating this area satisfies the stem's requirement to trace why moderation rules flag community posts.