Select Two (Multi-Select) Questions

Delete or edit inappropriate user-submitted posts

Deleting or editing inappropriate posts directly enforces forum content standards, satisfying the requirement to maintain order and quality. Moderators hold this editorial privilege within community platforms, letting them remove spam, abuse or off-topic material before it disrupts peer-to-peer support. This is a core moderation capability, distinct from administrative configuration tasks.

Lock discussion threads to prevent further replies

Locking threads halts further replies, immediately containing off-topic drift, flame wars or resolved discussions without deleting content. This directly satisfies the moderator's need to maintain order and quality in peer-to-peer forums, since it stops escalation while preserving the existing record for reference.

Adding a comment on the portal

Customers can add comments to their cases through the portal, which posts to the case activity stream and notifies the assigned agent. This is a supported customer interaction, satisfying the requirement for portal-based case communication.

Replying to an email notification

Inbound email replies are parsed by the email client and appended to the existing case activity stream, letting customers add information without portal login. This satisfies the requirement for a valid interaction channel alongside the customer portal and phone.

The Case state value being used in practice does not match the backend choice value specified in the pause condition.

Mismatched display labels vs. backend choice values (e.g., 'Awaiting Info' vs 'awaiting_info') will prevent condition evaluation.

The Pause condition field on the SLA Definition is empty or incorrectly formulated.

If the pause condition is blank or references invalid fields, the engine will never trigger a pause.

Another matching SLA definition with a higher order (lower number) lacks a pause condition, overriding the behavior.

Precedence rules can cause a different matching SLA definition to dictate the runtime behavior.

Allowing multiple customer cases to be tied to a single root-cause problem record

Problem records consolidate many related cases under one root cause, so a single investigation and fix resolves numerous customer incidents. This many-to-one linkage is the core benefit, reducing duplicate troubleshooting and preventing engineers from treating each case as an isolated defect.

Providing linked customers visibility into the underlying problem investigation status (if configured)

Linking cases to a problem lets affected customers track the underlying investigation's status when the portal is configured to expose it, satisfying the visibility requirement. This keeps customers informed of root-cause progress without agents manually updating every individual case.

Enabling cascade updates or resolutions from the problem down to linked cases

Linking cases to a problem creates a parent-child relationship where resolving or updating the problem cascades down to all linked cases, closing them consistently. This satisfies the stem's requirement for a distinct behaviour enabled by the case-to-problem link.

Defining point values for specific community actions (e.g., creating a post, receiving an upvote)

Gamification requires awarding points for tracked community actions, so defining point values per action (posting, receiving upvotes) establishes the scoring currency. Without this mapping, reputation totals cannot accrue, making it a required configuration step for the reputation engine.

Configuring reputation rules to determine user tier levels or expert statuses

Reputation rules translate accumulated points into tier levels or expert statuses, governing how users are ranked and recognised. Configuring these thresholds is essential because gamification's progression logic depends on rules that map point totals to defined reputation tiers.

Creating custom badges and assigning threshold requirements

Badges provide visible recognition beyond points, and each badge needs a threshold requirement to trigger awarding. Creating custom badges with threshold values is therefore a required configuration step, since badges only unlock when a user's accumulated score meets the defined criterion.

Remove child cases

Removing child cases is available because the Major Case context aggregates related cases under a parent, and the child relationship must be severable without deleting records. This satisfies the stem's requirement for actions specific to that context, distinct from standard case actions such as reassignment or closure.

Add child cases

Adding child cases is available in the Major Case context, letting you link related incidents under one parent for coordinated resolution. This satisfies the stem's requirement for actions specific to that context, since child-case creation is a standard capability there, enabling agents to group interconnected issues and track them together.

Send broadcast communication

Broadcast communication is a Major Case action, letting agents push a single update to all affected users simultaneously rather than updating each case individually. This satisfies the stem's requirement for actions available specifically within the Major Case context, where coordinated mass notification across related incidents is the defining capability.

Selecting a predefined schedule directly in the Schedule field on the SLA Definition record.

The Schedule field on the SLA Definition record accepts a predefined business schedule, letting the SLA inherit that schedule's time zone and working hours. This satisfies the stem by applying a custom schedule without writing code or creating a schedule source.

Referencing a schedule dynamically through a schedule source field on the Task or SLA definition.

A schedule source field on the Task or SLA definition resolves the schedule dynamically at runtime, so the SLA uses whichever business schedule the referenced record supplies. This satisfies the stem's requirement by applying a custom schedule per task rather than a single fixed predefined one.

Average response time and resolution rate for unanswered questions

Average response time and resolution rate for unanswered questions measure how quickly community members engage and resolve queries, indicating deflection effectiveness. This satisfies the stem's requirement for a community performance metric reviewed by the director.

Number of cases deflected via community search

The count of cases deflected via community search quantifies how many incoming cases the peer-to-peer community prevented, directly evidencing deflection effectiveness. This satisfies the stem's requirement for a community performance metric reviewed by the director.

Active community users and engagement trends over time

Active community users and engagement trends reveal whether peer-to-peer discussions are actually drawing participants over time, directly measuring the engagement half of the director's deflection-and-engagement goal. Tracking this trend shows whether community activity correlates with reduced case volume, satisfying the evaluation requirement.

Associate the Search Context with the Workspace Search Config or Table Configuration

Associating the Search Context with the Workspace Search Config or Table Configuration wires the context into the agent workspace, so suggested articles surface against the record being viewed. Without this binding, the context never activates for agents.

Configure the Search Context to include the appropriate Knowledge Base search sources

Configuring the Search Context to include the appropriate Knowledge Base search sources determines which articles are eligible for suggestion. Omitting this leaves the context with no knowledge sources, so no relevant articles can be recommended to agents.

Task SLA [task_sla] table for tracking runtime durations, breach counts, and compliance percentages.

The task_sla table stores per-task SLA records, so it exposes actual elapsed runtime against defined targets, breach occurrences, and the resulting compliance percentage. That directly satisfies the stem's demand for metrics covering durations, breach counts, and compliance, which no configuration or definition table provides.

Contract SLA [contract_sla] table to report on definition configurations and target thresholds.

The Contract SLA table stores the definition configurations and target thresholds against which performance is measured, satisfying the need for a reporting baseline. Without these definitions, breach calculations and resolution targets cannot be evaluated accurately.

Performance Analytics indicators targeting SLA breach counts and resolution rates.

Performance Analytics indicators supply the quantitative SLA evidence the reporting strategy requires, surfacing breach counts and resolution rates over time. These satisfy the scenario's need for measurable, trend-based reporting on whether contractual targets are being met.

Grouping under Service Contracts.

Entitlements link to service contracts, letting you group them so coverage is inherited from the contract rather than defined per entitlement. This satisfies the stem's requirement for a genuine Entitlements feature, since contract-level grouping governs which customers or assets qualify for specific support terms.

Tracking remaining support units measured by number of cases or hours.

Entitlements in ServiceNow CSM quantify a customer's purchased support allowance and decrement it as cases are consumed, whether measured in case count or hours. This tracking satisfies the scenario's requirement for a feature tied to entitlement consumption.

Restricting support coverage to specific products or installed assets.

Entitlements scope support coverage by binding service contracts to defined products or installed assets, so only covered items receive entitled support. This directly satisfies the stem's constraint of restricting coverage, since the entitlement record evaluates the customer's purchased products or assets before granting support eligibility.

Table

The Table field is mandatory because an SLA Definition must bind to a specific task table, such as the Case table, to know which records it evaluates. Without this target, the SLA engine cannot attach conditions or schedules, so ServiceNow blocks saving the definition until a table is selected.

Duration

Duration defines the response and resolution targets that the SLA engine measures against, so ServiceNow rejects an SLA Definition without it. It satisfies the stem's mandatory-component constraint because the schedule, workflow and conditions all reference this timing value, making it structurally required rather than optional configuration.

Task SLA [task_sla] table where runtime instance adjustments are recorded.

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.

System Audit [sys_audit] table which tracks field-level changes on Contract SLA and Task SLA records.

The System Audit [sys_audit] table records field-level before-and-after values on audited tables, so enabling auditing on Contract SLA and Task SLA captures exactly which fields changed, by whom, and when, meeting the strict SLA modification auditing requirement.

Contract SLA [contract_sla] table where definition updates are stored.

The Contract SLA [contract_sla] table holds the SLA definition records themselves — conditions, schedules, and duration settings — so edits to those definitions are stored there, satisfying the requirement to audit changes made to SLA definitions rather than runtime instances.

Modern SLA Notifications are easier to maintain for simple email alerts at specific percentages without building full workflow graphs.

Modern SLA notifications are configured declaratively against percentage thresholds, so simple percentage-based email alerts need no workflow graph. This satisfies the stem's maintenance constraint: where only straightforward alerts are required, the notification feature avoids the overhead of building and maintaining full workflow logic.

SLA Workflows allow complex programmatic branching, such as creating sub-tasks or escalating to external web services upon breach.

SLA Workflows execute scripted workflow activities, enabling branching logic that creates sub-tasks or calls external web services when a breach occurs. This satisfies the stem's complexity constraint: programmatic escalation and orchestration beyond simple percentage emails require the workflow engine rather than notification records.

State change

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.

Comment added

Adding a comment to a case fires a notification event, alerting relevant recipients such as the assigned agent or customer. Comment insertion is a supported notification trigger, satisfying the stem's requirement for comment-driven case notifications.

The complexity and frequency of start, stop, pause, and reset condition evaluations across active task records.

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.

The size of the Task SLA [task_sla] table and lack of proper indexing on custom condition fields.

A bloated task_sla table forces full scans during breach and pause recalculation, while missing indexes on custom condition fields make each SLA evaluation read far more rows than necessary. In a high-volume CSM environment, that combination directly degrades SLA engine calculation throughput, satisfying the performance constraint in the stem.

The frequency and complexity of custom calendar schedules evaluated during elapsed time calculations.

Custom calendar schedules force the SLA engine to resolve working-hours, holidays and time-zone boundaries for every elapsed-time calculation, so frequent, intricate definitions multiply per-record processing cost. This directly drives calculation load in a high-volume CSM environment, where elapsed time must be recomputed continuously across large ticket volumes.

Review

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.

Published

Published is a terminal state in the baseline knowledge workflow, marking articles approved and visible to end users. It satisfies the stem's requirement for an out-of-the-box lifecycle state, sitting alongside Draft and Review. Articles reach Published only after passing through the workflow's approval stages, enabling self-service access.

Draft

Draft is a baseline state in the standard knowledge workflow, representing an article still being authored and not yet visible to end users. It satisfies the stem's requirement for out-of-the-box lifecycle states, alongside Review and Published, forming the default progression before an article is approved for consumption.

Account

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.

Product / Asset

Entitlements in ServiceNow CSM can be explicitly tied to Product or Asset records, satisfying the requirement that entitlements map to the specific offerings a customer owns. This linkage lets support agents verify entitlement coverage against purchased products or assets before delivering services.

Contact

An Entitlement can be explicitly tied to a Contact, satisfying the requirement that entitlements be scoped to individual people rather than only accounts. This lets a specific customer contact receive defined support levels independently of their parent account, which is essential when contacts at the same account hold differing service agreements.

Assets / Installed Base items

Installed Base items (assets) carry an Account reference, tying each customer's deployed products to their account record. This direct association supports entitlement checks and case resolution, satisfying the stem's requirement for record types linked to an Account.

Entitlements

Entitlements define the support coverage a customer receives and are linked directly to an Account record, governing SLA and case options. This direct relationship satisfies the stem's requirement for record types associable with an Account in CSM.

Contacts

Contacts are stored as separate records linked to an Account via the Account field, letting CSM agents track customer personnel independently of the account itself. This direct relationship satisfies the stem's requirement for record types associable with an Account.

Service Portal

The Service Portal provides a self-service interface where end users submit cases directly, satisfying the requirement for a valid case-creation method in CSM. Submissions generate case records through the portal's configured record producer, distinct from agent-side or backend creation paths. This makes it one of the two valid mechanisms the question demands.

Manual creation in the CSM module

Manual creation through the CSM module's case form remains a supported method, satisfying the stem's requirement for valid case-creation paths. Agents populate mandatory fields directly, and the record is written to the case table without relying on automated intake channels such as email or Microsoft Entra ID-driven workflows.