Question 1

Why would you set Choice Action to Ignore on a transform field map?

Accepted Answer

A

Explanation: The Choice Action setting on a transform field map determines how the system handles an incoming value for a choice or reference field when that value does not match an existing choice or referenced record. Setting this action to Ignore instructs the import process to skip the transformation for that specific field, leaving it blank on the target record, but continuing to process the rest of the row. This is the correct strategy when you want to prevent the automatic creation of new, potentially invalid, choices or referenced records (i.e., "dummy records") in the target tables, thereby maintaining data integrity.

Question 2

The system automatically sets which field when an administrator attempts to modify a policy, application, or module that belongs to another domain higher in the hierarchy?

Accepted Answer

A

Explanation: When an administrator in a child domain attempts to modify a record (such as a policy or business rule) that belongs to a parent or global domain, the system prevents direct modification. Instead, it creates a copy of the record in the administrator's current domain. This new record is called an override. To maintain the relationship between the original record and the new override, the system automatically populates the sysoverrides field on the new record with the sysid of the original record. This allows the system to use the domain-specific version for users in that domain.

Question 3

Visibility can be granted to users by which of the following means: Choose 2 answers

Accepted Answer

A, B

Explanation: In a ServiceNow instance with Domain Separation, a user's visibility into different domains is determined by an inheritance model. Visibility can be explicitly granted to an individual user by adding domains to the 'Visibility domains' related list on their user record. Alternatively, and more commonly for scalability, visibility is granted to a group. Any user who is a member of that group automatically inherits the domain visibility assigned to it. These two methods allow users to see records and data from domains other than their session domain.

Question 4

What happens when the glide.knowman.allow_edit_global_articles system property is enabled ?

Accepted Answer

D

Explanation: The glide.knowman.alloweditglobalarticles system property is specifically designed to override the default security behavior in a domain-separated environment for Knowledge Management. By default, knowledge articles in the 'global' domain can only be edited by users who are also in the global domain. When this property is set to true, it explicitly grants users in other, specific domains the ability to check out and edit these global articles. The user must still possess the necessary underlying permissions (e.g., contributor access to the specific knowledge base) to perform the edit. The edited article remains in the global domain.

Question 5

Process Separation is also known as:

Accepted Answer

D

Explanation: Process Separation is a core component of ServiceNow's Domain Separation architecture. It allows different domains (e.g., representing different customers or business units) to have unique business processes, user interfaces, and business logic (like business rules, client scripts, and UI policies) on a single instance. This capability enables a domain-specific administrator, often with the domainadmin role, to manage their domain's configuration and processes independently. This practice of managing a specific domain's processes and configuration is known as domain administration. Therefore, Process Separation is the technical mechanism that enables the function of domain administration.

Question 6

Which are the available Domain Types on a baseline instance? Choose 3 answers

Accepted Answer

A, D, E

Explanation: On a baseline ServiceNow instance where the Domain Support - MSP Extension plugin is activated, several default domain types are created to support common Managed Service Provider (MSP) business structures. These predefined types are 'MSP', 'Customer', and 'Vendor'. They serve as classifications within the [domain] table to logically organize the domain hierarchy. The 'MSP' type is for the provider's own domain, 'Customer' for client domains, and 'Vendor' for third-party supplier domains, enabling tailored data and process segregation.

Question 7

Select the recommended approach to Domain Separation

Accepted Answer

D

Explanation: The recommended approach for a successful and maintainable Domain Separation implementation, as advised by ServiceNow, is to heavily rely on standard data separation. This model suggests that at least 80% of separation requirements should be met using the out-of-the-box sysdomain field on data records. Approximately 15% can be handled through data-driven rules, where domain assignment is automated based on record attributes (e.g., company). Critically, configuration-level separation (creating domain-specific business rules, UI policies, etc.) should be minimized to less than 5%. This strategy reduces complexity, lowers maintenance overhead, and simplifies future platform upgrades.

Question 8

If a business rule exists in the parent domain and a separate non-overriding business rule exists in the child domain, which rule will run for the child domain?

Accepted Answer

B

Explanation: In a domain-separated ServiceNow instance, child domains inherit configurations and processes, including business rules, from their parent domains. When a business rule exists in a parent domain and a separate, non-overriding business rule is created in a child domain for the same table, the system's behavior is additive. Both business rules will be triggered and executed for records within the child domain, provided their respective conditions are met. The parent domain's rule typically runs first, followed by the child domain's rule, allowing for layered business logic across the domain hierarchy.

Question 9

Given a parent and child domain, explain data accessibility between domains.

Accepted Answer

B

Explanation: ServiceNow's domain separation model operates on a hierarchical, top-down principle of data visibility. Users assigned to a parent domain have the ability to view and access data within their own domain as well as all data contained within any of its child domains. This allows a service provider (in the parent domain) to manage and report on all its customers (in child domains). Conversely, users in a child domain are restricted from accessing data in the parent domain or any sibling domains, ensuring data segregation and security for each tenant.

Question 10

What type of detailed results or actions are included in the domain audit? Choose 3 answers

Accepted Answer

C, D, E

Explanation: The ServiceNow Domain Separation audit is a tool designed to identify and help resolve potential configuration issues. The audit results page provides a comprehensive report that includes a list of all records or configurations affected by identified errors or warnings (C). For each issue, the system provides recommended actions to remedy errors and warnings, guiding the administrator on how to correct the misconfiguration (D). The interface for the audit results also includes functionality such as the ability to re-run the audit, allowing administrators to verify that their fixes have resolved the reported issues (E).

Free ServiceNow CIS-SP Actual Exam Questions