Scenario practice questions

Which TWO scenarios represent valid use cases for the Customer Relationship [customer_relationship] table rather than the standard Account Parent field? (Choose two.)

Trap 1: Assigning individual contacts to accounts.

Contact-account links use the contact table's account field.

Trap 2: Creating a simple corporate headquarters to regional subsidiary…

Parent-child hierarchy fields handle strict tree structures.

Trap 3: Linking consumers to business accounts.

Consumers do not participate in business customer relationships.

A
Assigning individual contacts to accounts.
Why wrong: Contact-account links use the contact table's account field.
B
Creating a simple corporate headquarters to regional subsidiary tree structure.
Why wrong: Parent-child hierarchy fields handle strict tree structures.
C
Establishing peer relationships or joint ventures where neither account is a strict subsidiary of the other.
Peer connections use relationship definitions rather than strict parent-child trees.
D
Defining a partner organization that provides support across multiple independent customer accounts.
Partner-to-customer support networks are modeled via customer relationships.
E
Linking consumers to business accounts.
Why wrong: Consumers do not participate in business customer relationships.

Question 2hardmultiple choice

An administrator is troubleshooting a scenario where community discussions are not appearing in Contextual Search results during case creation. Which table must be indexed or included in the Contextual Search table configurations to resolve this issue?

Trap 1: kb_knowledge

Incorrect. kb_knowledge is strictly for knowledge base articles.

Trap 2: sn_customerservice_case

Incorrect. This is the case table, not the community content table.

Trap 3: sys_user

Incorrect. This table stores user records.

A
kb_knowledge
Why wrong: Incorrect. kb_knowledge is strictly for knowledge base articles.
B
sn_communities_content
Correct. sn_communities_content is the primary table storing community content that needs to be configured in search sources for Contextual Search.
C
sn_customerservice_case
Why wrong: Incorrect. This is the case table, not the community content table.
D
sys_user
Why wrong: Incorrect. This table stores user records.

Question 3hardmultiple choice

An administrator is troubleshooting a scenario where community users with the sn_communities_reader role cannot view content inside a newly created private forum. Which component should the administrator inspect first to resolve this access issue?

Trap 1: The Forum Access Control List (ACL) definitions for the…

While ACLs apply, private forums specifically rely on User Criteria associations managed out-of-the-box.

Trap 2: The CSM Community Property table for the property…

This property does not exist in standard ServiceNow community configurations.

Trap 3: The Portal Page widget security settings in Service Portal…

Portal widget security controls page-level access, whereas forum content security is record-level and criteria-driven.

A
The Forum Access Control List (ACL) definitions for the sn_communities_forum table
Why wrong: While ACLs apply, private forums specifically rely on User Criteria associations managed out-of-the-box.
B
The User Criteria definitions mapped to the specific private forum record
Private forums use User Criteria to determine visibility; if criteria are not met, readers cannot view content.
C
The CSM Community Property table for the property glide.community.private.disable
Why wrong: This property does not exist in standard ServiceNow community configurations.
D
The Portal Page widget security settings in Service Portal Configuration
Why wrong: Portal widget security controls page-level access, whereas forum content security is record-level and criteria-driven.

Question 4mediummultiple choice

An agent is trying to add a new contact to an account, but the contact already exists as a user in the system linked to a different account. What is the correct procedure to handle this scenario in CSM?

Trap 1: Delete the existing user record and create a new one

Deleting user records corrupts historical audit trails and case history.

Trap 2: Change the Account field on the existing contact record directly

This would orphan the contact from their original account instead of sharing them.

Trap 3: Convert the contact into a consumer

Consumers cannot be linked to business accounts in this manner.

A
Delete the existing user record and create a new one
Why wrong: Deleting user records corrupts historical audit trails and case history.
B
Change the Account field on the existing contact record directly
Why wrong: This would orphan the contact from their original account instead of sharing them.
C
Convert the contact into a consumer
Why wrong: Consumers cannot be linked to business accounts in this manner.
D
Associate the existing contact to the new account using the Account Contact relationship
CSM supports multi-account contact relationships allowing a contact to belong to multiple accounts.

Question 5hardmultiple choice

An implementation specialist is configuring entitlement management for a key customer account. The customer has a support contract that covers phone support up to 50 cases per year, but only for products installed at a specific physical location. How should the specialist configure the entitlement to handle this scenario?

Trap 1: Create a child entitlement for every asset and roll them up using…

Entitlements do not roll up child entitlements in this manner; they are evaluated based on matching criteria.

Trap 2: Configure a Business Rule on the Case table to validate the caller…

Standard entitlement determination rules handle matching without needing custom Business Rules.

Trap 3: Set the entitlement type to 'Location-based' and select the…

There is no 'Location-based' entitlement type native to CSM; entitlements are tied to Accounts, Contacts, Products, or Assets.

A
Create a child entitlement for every asset and roll them up using an Account rollup definition.
Why wrong: Entitlements do not roll up child entitlements in this manner; they are evaluated based on matching criteria.
B
Configure a Business Rule on the Case table to validate the caller location against the Account location before applying the entitlement.
Why wrong: Standard entitlement determination rules handle matching without needing custom Business Rules.
C
Set the entitlement type to 'Location-based' and select the account's primary site in the Location field.
Why wrong: There is no 'Location-based' entitlement type native to CSM; entitlements are tied to Accounts, Contacts, Products, or Assets.
D
Create an entitlement with 'Remaining units' tracking, linked to the Account, and add the specific location assets to the Entitled Assets related list.
Linking specific assets to the Entitled Assets related list ensures that cases only consume entitlement units when opened for those specific assets.

Question 6mediummulti select

Which TWO statements are true regarding how the SLA engine handles Case re-opening scenarios? (Choose two.)

Trap 1: Re-opening a case automatically deletes all previous task_sla…

Historical SLA records are never deleted automatically upon case re-opening.

Trap 2: Active SLAs are automatically resumed from their exact previous…

Unless specifically configured via cancel/pause rules, standard lifecycle conclusion closes the SLA instance.

Trap 3: The system prevents cases from being re-opened if an SLA has…

SLA breaches do not lock cases from being re-opened.

A
If start conditions are met upon re-opening a Case, a new Task SLA instance can be automatically generated.
Re-opening a case changes its state, which can re-satisfy start conditions and trigger a new SLA instance.
B
Re-opening a case automatically deletes all previous task_sla records to maintain a clean slate.
Why wrong: Historical SLA records are never deleted automatically upon case re-opening.
C
Previously completed SLAs are preserved for historical audit and reporting purposes.
Completed SLA records remain intact on the task_sla table and are never overwritten by new instances.
D
Active SLAs are automatically resumed from their exact previous pause point without generating new instances.
Why wrong: Unless specifically configured via cancel/pause rules, standard lifecycle conclusion closes the SLA instance.
E
The system prevents cases from being re-opened if an SLA has breached.
Why wrong: SLA breaches do not lock cases from being re-opened.