What does the system property glide.sys.domain.delegated_administration do?
Correct Answer: D
The system property glide.sys.domain.delegated_administration is designed to empower customer administrators by allowing them to configure their own domains. This is crucial in a multi-tenant environment where multiple customers or departments are operating within the same ServiceNow instance but need to maintain separate configurations and data. By enabling this property, customer admins can make changes specific to their domain without the risk of affecting the configurations of other domains. This property essentially enables domain separation, which is a method of separating data into logically defined domains.
Question 12
If a user has the ITIL role and resides in the MSP domain, which is true?
Correct Answer: A
In ServiceNow, domain separation allows organizations to segregate data, processes, and administrative tasks into logical groupings called domains1. This is particularly useful for Managed Service Providers (MSPs), where multiple organizations or customers use the same ServiceNow instance but require isolation from each other2. When a user has the ITIL role within the MSP domain, they inherently have that role across all domains they have access to. This is because roles in ServiceNow are global by default, meaning they apply across all domains unless specifically restricted31. The ITIL role is a set of permissions that typically includes the ability to manage incident, problem, and change records, which are fundamental to IT service management. The other options, such as being granted the Admin role in other domains (B), administering other domains by granting the Domain Admin role , or being restricted to self-service in other domains by granting the Self-Service role (D), are actions that require explicit configuration by an administrator with the appropriate level of access and are not automatic outcomes of having the ITIL role in the MSP domain4. It's important to note that while the ITIL role may be global, access to specific records and the ability to perform certain actions can still be controlled within each domain through ACLs (Access Control Lists) and other domain-specific configurations1.
Question 13
What are common concerns that might lead to a multi-instance strategy: Choose 3 answers
Correct Answer: B,C,D
A multi-instance strategy is often adopted due to concerns about data security, regulatory compliance, and data sovereignty. * Sensitive internal service provider data (B): Multi-instance architectures provide a separate database for each user interaction, which significantly reduces the risk of attacks and ensures data isolation1. This is crucial for service providers who handle sensitive data and require strict data control and privacy. * Highly regulated industries : Industries such as finance, healthcare, and government are subject to stringent regulations. Multi-instance infrastructures offer on-premise-level security and allow for greater flexibility and control, which is necessary to comply with industry-specific regulations1. * Data residency (D): Data residency refers to the physical or geographical location of an organization's data. Due to various national laws and regulations, organizations may need to ensure that their data is stored and processed within specific jurisdictions. Multi-instance infrastructures support this requirement by providing dedicated databases that can be located as per the data residency needs1. Centralized reporting (A) and domain separation licensing cost (E) are not typically concerns that lead to a multi-instance strategy. Centralized reporting can be achieved within both multi-instance and multi-tenant environments, and domain separation licensing cost is a factor related to the ServiceNow platform's domain separation feature, which is different from the infrastructure considerations of multi-instance versus multi-tenant setups234.
Question 14
On a new standalone table, what domain will a new record be created in by default?
Correct Answer: B
In ServiceNow, when a new record is created on a standalone table, the domain of the new record is set to the user's current session domain by default. This means that the domain context in which the user is operating at the time of record creation determines the domain assignment for that record. This behavior ensures that the data is correctly categorized within the domain structure, adhering to the visibility and access controls that have been established. The concept of domain separation in ServiceNow is integral to its multi-tenancy model, allowing for data, processes, and administrative tasks to be segregated across different domains within a single instance. This is particularly useful for managed service providers (MSPs) who need to maintain distinct operational environments for multiple customers or departments within the same ServiceNow instance. For a new standalone table, unless explicitly defined otherwise, the system defaults to using the user's current session domain for new records. This is supported by ServiceNow's documentation on domain separation best practices and the management of data within domains12. It's important to note that while the default behavior is as described, administrators have the ability to configure domain rules and behaviors to suit specific organizational needs.
Question 15
What is the best practice regarding User Criteria and Shared Knowledge Bases?
Correct Answer: C
In ServiceNow, the best practice for setting up User Criteria and Shared Knowledge Bases is to define them in the parent domain. This approach ensures that the knowledge bases are accessible to all relevant child domains, promoting efficient information sharing and management. When knowledge bases and user criteria are defined at the parent domain level, they inherit down to the child domains, allowing for centralized control while still supporting visibility across the domain hierarchy. This practice aligns with the principles of domain separation, which is a key feature in ServiceNow for managing data and user access in a multi-tenant environment. By defining these elements in the parent domain, organizations can maintain a clear and organized structure that supports both separation and sharing of knowledge as needed. For more detailed guidance on this topic, ServiceNow's official documentation provides insights on designing user criteria for knowledge bases, which can be found in their support portal. It is recommended to review these resources for a comprehensive understanding of the best practices in configuring user criteria and knowledge bases within ServiceNow.
