# Free SISCS practice questions

> 10 free SISCS practice questions with the correct answer and an explanation.

Page: https://devopscodelab.com/exams/servicenow-cis-csm/free-practice-questions/
Practice exams: https://devopscodelab.com/exams/servicenow-cis-csm/

### Question 1 of 10

A support contract covers 20 cases per year for a customer's printer fleet. The client wants the remaining case count to decrease each time a case is opened for that fleet. Which data model configuration supports this?

- A. An entitlement linked to the contract with a per-case unit characteristic that is consumed by cases
- B. A service contract line with a quantity of 20 that blocks the customer's portal access when it reaches zero
- C. A count field on the account that a business rule decrements each time a case is inserted
- D. An SLA definition with a 20-case limit set in the retroactive start condition of the definition

**Answer:** A

**Explanation:** Entitlements can carry characteristics such as a number of units per case, and cases consume those units, so the remaining allowance is tracked against the contract. A custom count field on the account duplicates the entitlement model and is not product-specific. SLA definitions measure elapsed time and have no case-count limit. Contract line quantities describe what is covered, and nothing in the base system uses them to block the portal.

### Question 2 of 10

A manufacturer sells industrial pumps to other companies, and each buying company has several employees who raise support requests. Which CSM data model fits this business?

- A. Business-to-consumer, with each buying company stored as a household and its employees as household members
- B. Business-to-business, with each buying company stored as an account and its employees as contacts on that account
- C. Business-to-business-to-consumer, with each employee stored as a consumer linked to a partner account
- D. Business-to-consumer, with each employee stored as a consumer record and the buying company's name held in a custom field

**Answer:** B

**Explanation:** When the customers are companies whose employees request service, CSM uses the B2B model: the company is an account and its employees are contacts. Households and consumers belong to the B2C model for individual people, so storing companies as households or employees as consumers breaks account-level visibility and entitlements. B2B2C is for businesses that serve consumers through a partner or intermediary, which is not the case here.

### Question 3 of 10

A software vendor wants each customer's deployed products tracked so agents can see exactly which product instances an account owns, including items that are not configuration items in the CMDB. Which CSM feature should be used?

- A. Install Base items related to the account, each referencing a product model
- B. Contract line items on the service contract listing every licensed product
- C. Service offerings from CSDM subscribed to by each account's user group
- D. Asset records in alm_asset with the Assigned to field set to the primary contact

**Answer:** A

**Explanation:** Install Base items represent the products a customer owns, link to the account or consumer and a product model, and can exist with or without a CMDB CI. Assets assigned to a contact describe internal asset ownership and do not model customer installed products well. Service offerings describe services, not owned product instances. Contract line items record what is covered commercially, not what is actually installed.

### Question 4 of 10

Cases arriving through chat and the portal must be pushed to available agents based on capacity and skills rather than picked from a shared list. Which feature should be configured?

- A. Data lookup rules that set the assignment group from category and priority
- B. Advanced Work Assignment with service channels, queues and assignment rules
- C. Assignment rules on the case table using conditions on product and account
- D. An On-Call Scheduling rota attached to each customer service assignment group

**Answer:** B

**Explanation:** Advanced Work Assignment routes work items into queues and offers them to agents according to availability, capacity and optional skills, which is push-based assignment. Classic assignment rules and data lookups only set a group or user on the record without checking capacity. On-call scheduling decides who is on duty for escalations rather than distributing incoming work.

### Question 5 of 10

An administrator wants the case resolution SLA to run only for customers whose contract includes premium support. What is the recommended approach?

- A. Create a business rule that deletes the task SLA whenever the case's account has no premium support contract
- B. Copy the SLA definition for each premium account and filter it by account name
- C. Add a condition on the SLA definition that checks the account's Customer checkbox
- D. Associate the SLA definition with the premium contracts through the contract SLA relationship

**Answer:** D

**Explanation:** Linking SLA definitions to contracts lets the SLA attach only to cases covered by those contracts, which is the supported pattern in CSM. A copy per account is unmaintainable as customers change. Deleting task SLAs by script fights the SLA engine and loses history. The Customer checkbox only identifies an account as a customer and says nothing about its support level.

### Question 6 of 10

In Advanced Work Assignment, cases for a premium product line must go to a dedicated team before any other team. What determines which queue a case enters?

- A. The assignment rule's round-robin or most-capacity setting
- B. The service channel's utilization condition script
- C. The queue's routing condition, evaluated in queue order
- D. The agent's presence status in the workspace inbox

**Answer:** C

**Explanation:** Queues have conditions and an order; AWA places a work item in the first matching queue, so a premium-product condition on a high-order queue sends those cases to the dedicated team. Assignment rule strategies choose an agent within a queue. Presence decides whether an agent receives offers. The utilization condition decides when a record becomes a work item for the channel, not which queue it joins.

### Question 7 of 10

A widespread service outage generates hundreds of customer cases. The client wants one case to represent the issue so that updates and resolution are copied to all related cases. Which capability provides this?

- A. Grouping the cases under one parent with a database view and report
- B. Merging all the duplicate cases into a single case with the merge action
- C. Major issue management, which promotes a case to a major case with child cases
- D. Creating a problem record and linking every affected customer case to it with the Problem field

**Answer:** C

**Explanation:** Major issue management lets an agent propose a case as a major case candidate; once accepted, related cases become child cases and updates and resolution flow from the major case to them. Linking cases to a problem tracks root cause but does not propagate customer communication. Merging would discard the separate customers' cases. A database view only reports on cases and cannot update them.

### Question 8 of 10

An agent needs the customer to send log files before work can continue, and the SLA should not breach while waiting. What should the agent do?

- A. Reassign the case to the customer's primary contact
- B. Cancel the case and ask the customer to raise a new one
- C. Set the case state to Awaiting Info so the SLA pauses
- D. Add the customer to the watch list and keep the case Open

**Answer:** C

**Explanation:** Awaiting Info indicates the case is waiting on the customer, and SLA definitions are commonly configured to pause in that state; a customer reply moves it back to Open. Customers cannot be assignees on a case. A watch list sends updates but leaves the SLA running. Cancelling and recreating loses history and frustrates the customer.

### Question 9 of 10

A catalog item for ordering replacement parts must appear on the Customer Service Portal only for contacts of accounts with a hardware contract. How should visibility be controlled?

- A. A separate portal for hardware customers that lists the item on its home page
- B. A UI policy on the catalog item that hides its order button
- C. Available for user criteria on the catalog item based on the contract
- D. A read ACL on the sc_cat_item table for each eligible account

**Answer:** C

**Explanation:** Catalog item availability is controlled by Available for and Not available for user criteria, which can check scripted conditions such as account contract coverage. UI policies run after the item is displayed. Per-account ACLs on catalog items are hard to maintain. A separate portal duplicates the experience for one item.

### Question 10 of 10

A client wants many changes to the CSM case form and processes. Which approach best follows ServiceNow implementation guidance?

- A. Modify the base CSM business rules and script includes directly to fit each request
- B. Copy sn_customerservice_case into a new custom table and change that copy freely
- C. Configure with base features first and add custom work only for proven gaps
- D. Disable CSM business rules and rebuild case behaviour with client scripts

**Answer:** C

**Explanation:** Staying close to the base system and configuring before customising keeps upgrades simple and uses capabilities ServiceNow maintains. Editing base scripts creates skipped records on every upgrade. A copied case table loses integration with CSM features. Replacing server logic with client scripts moves rules to the browser, where they are easy to bypass and hard to maintain.

Ready for a timed run? Take the free 15-question SISCS mini exam: https://devopscodelab.com/app/exams/servicenow-cis-csm/mini/

DevOpsCode Lab is not affiliated with ServiceNow. SISCS and related names are trademarks of their owners. We write every question ourselves; these are not real exam questions.
