Free ServiceNow CIS-SP Practice Exam with Questions & Answers | Set: 2

In ServiceNow, domain separation allows for hierarchical data visibility. Users in a parent domain can see data in their child domains, which is referred to as downstream visibility. This ensures that higher-level domains have access to the data of their subdomains, facilitating centralized management and oversight. However, users in child domains cannot see data in their parent domains (upstream) or sibling domains unless explicitly granted access.

References:

•ServiceNow Domain Separation Documentation1

•ServiceNow Knowledge Base on Domain Separation2

When selecting a field to populate UserID in ServiceNow, it’s crucial to choose an identifier that is globally unique to ensure that each user can be distinctly identified. The best practices for such identifiers include:

•Employee Number: Typically, an employee number is unique to an individual within an organization and does not change, making it a reliable identifier1.

•Email: An email address is inherently unique as it is tied to an individual and is used for communication, which also makes it a suitable candidate for UserID2.

•SSN (Social Security Number): While SSN is unique to each individual, it’s important to note that using SSN as an identifier should be approached with caution due to privacy and security concerns. However, it is unique and could technically be used to populate UserID3.

The Last Name is not a good candidate for UserID because it is not globally unique; many individuals can share the same last name and it can change over time due to personal reasons.

For further details on creating unique identifiers and best practices, ServiceNow provides documentation and guidelines which can be referred to for implementing these practices within the ServiceNow environment.

In ServiceNow, when applying an Update Set, administrators must select the Global domain. This is because Update Sets are designed to be applied from the Global domain to ensure that the changes are captured and can be moved across the instance without being restricted by domain separation1. The Global domain is the default domain where all the configuration records are created and where administrators typically work unless they switch to another domain for specific tasks1.

The Update Set system in ServiceNow is a mechanism for grouping and moving customizations from one instance to another or within the same instance. It captures the configuration changes made by administrators and bundles them into a set that can be transferred and applied elsewhere. Since the Global domain is the highest level in the domain hierarchy and is not restricted by domain-specific rules, it is the appropriate choice for applying Update Sets to ensure that the changes are universally available across all domains within the instance