Free Practice Questions for ServiceNow CIS-SP Exam

When the system property csm_auto_account_domain_generation is set to True, it specifies that a new domain is created automatically and placed under the TOP domain whenever a new account in the Customer Service application is created. If the ‘parent’ field on the account form is populated and a new record is inserted, it creates that account as a subdomain of the parent. This property is particularly relevant in domain-separated environments, ensuring that new account records are properly organized within the domain hierarchy2.

In ServiceNow, domain separation is used to segregate data, processes, and administrative tasks into logical groupings called domains. This allows for control over data visibility and operations within an instance. When it comes to data visibility:

•Domain X: A user in Domain X will definitely have visibility to their own domain, as this is the primary context in which they operate1.

•Child domains of Domain X: Users can view data in their home domain (Domain X) and any child domains of that home domain. This is because child domains inherit permissions and visibility from their parent domains, allowing users in a parent domain to see data in the child domains1.

However, users do not have access to data present in their parent domains or other unrelated domains by default. The primary domain and default domain are typically reserved for global or top-level administrative purposes and are not automatically visible to users in customer domains unless specific permissions are granted12.

It’s important to configure domain separation carefully to ensure that users have the appropriate level of access to data necessary for their roles while maintaining the security and integrity of the data across the instance31.

Before using domain separation for Service Catalog items, the first step an administrator must perform is to activate the Service Catalog - Domain Separation plugin (com.glideapp.servicecatalog.domain_separation). This plugin enables domain separation within the Service Catalog, allowing for the separation of data, processes, and administrative tasks into logical groupings called domains1. By activating this plugin, the admin ensures that the Service Catalog is prepared to handle the complexities of a domain-separated environment, which is essential for maintaining data integrity and proper access controls across different domains21.

In ServiceNow’s domain separation model, data accessibility is designed to maintain the integrity and segregation of data across different domains. Here’s how data accessibility works between parent and child domains:

•The parent users can access all child data: Users in a parent domain have visibility into the data of their child domains. This is because the parent domain is considered to have a higher level of data access privilege, allowing it to oversee and manage the data within its child domains1.

•The parent users can access all child data, but cannot access domains contained in the child domain: While parent domain users can access data in their immediate child domains, they cannot access data in “grandchild” domains or any domains that are further nested within a child domain. This maintains a level of data isolation and ensures that users only have access to the data they are permitted to view and manage1.

The options stating that both parent and child users can access each other’s data (A) and that child users can access all parent data © are incorrect. The domain separation model is hierarchical, not reciprocal, meaning that child domains do not have inherent access to parent domain data, and access between domains is not automatically bidirectional1.

For detailed information on domain separation and data accessibility, ServiceNow provides extensive documentation and best practices, which can be referenced for a deeper understanding of these concepts12

To data separate a new table in ServiceNow, you should add a field named sys_domain with a reference to the Domain table. This approach leverages ServiceNow’s domain separation capabilities, which allow for the segregation of data across different domains. By referencing the Domain table, you ensure that the new table can properly segregate data based on domain, maintaining data integrity and security.

References:

•ServiceNow Domain Separation Documentation

•ServiceNow Knowledge Base Article

Visibility in ServiceNow can be granted to users through Group Membership and Role.

•Group Membership: Users can be assigned to specific groups, and these groups can be granted visibility to certain records or functionalities within ServiceNow. This method allows for efficient management of user permissions based on their group affiliations.

•Role: Roles define a set of permissions that can be assigned to users. By assigning roles to users, administrators can control what users can see and do within the platform. Roles are a fundamental part of access control in ServiceNow.

References:

•ServiceNow User Criteria and Access Control

•ServiceNow Group Management

In ServiceNow, domain separation is used to separate data, processes, and administrative tasks into logical groupings called domains. This allows for control over various aspects of this separation1. However, certain process-related tables are excluded from domain separation to maintain the integrity and functionality of the system across different domains.

•Business Rules (B): Business rules are global by nature and are designed to apply system-wide logic before or after database operations, regardless of the domain. This is why they are excluded from domain separation.

•Access Controls ©: Access controls (ACLs) define what data users can access and how they can interact with it. Similar to business rules, ACLs are also global and not domain-specific to ensure consistent security practices across the platform.

•System Property (D): System properties are configuration settings that affect the entire ServiceNow instance. Since these settings can have far-reaching implications on the system’s behavior, they are not separated by domain to avoid conflicts and ensure uniformity in configuration.

These exclusions are necessary to ensure that fundamental system behaviors remain consistent and predictable, regardless of the domain context. It’s important to note that while these tables are excluded from domain separation, the data within other tables can be separated and controlled asper domain requirements2.

In ServiceNow, even though the Inbound Actions table has a domain field, records in this table should all be placed in the Global domain. This is because inbound actions, such as inbound email actions, are designed to be accessible across the entire platform, regardless of the specific domain. By placing these records in the Global domain, ServiceNow ensures that the actions can be executed and managed universally, without domain-specific restrictions.

For example, if an inbound email action creates an incident, the system creates the incident in the same domain as the user in the Caller field. If that user is not in the User [sys_user] table, the incident is placed in the Global domain1.

This approach maintains the integrity and accessibility of inbound actions across the platform.

1: ServiceNow Inbound Email Actions Documentation

To retrieve and commit an update set in ServiceNow, certain prerequisites must be met to ensure proper management and deployment of changes across instances:

•You must have the admin role ©: Having the admin role is crucial because it provides the necessary permissions to manage update sets, which includes retrieving and committing them. This role ensures that only authorized users can make significant changes to the system12.

•The domain picker must be set to global (D): When working with domain-separatedinstances, the domain picker must be set to global to ensure that the update set is applied across all domains. This is important for maintaining consistency and avoiding conflicts between different domains within the instance2.