Which are required to retrieve and commit an update set?
Choose 2 answers
Answer : C, D
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-separated instances, 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.
What is the best practice regarding User Criteria and Shared Knowledge Bases?
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.
What does the system property glide.sys.domain.delegated_administration do?
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.
What is the first step an admin must perform before using domain-separation for Service Catalog items?
Answer : D
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.
Name the methods available to provide data access to a user outside of their domain hierarchy.
Choose 2 answers
Answer : C, D
In ServiceNow, providing data access to a user outside of their domain hierarchy can be achieved through the following methods:
1. Access Control Lists (ACLs): ACLs are used to define permissions for accessing data within ServiceNow. By configuring ACLs, you can grant specific users or groups access to data outside their domain hierarchy. This is done by setting up rules that allow or deny access based on various conditions, such as roles, user attributes, or specific field values1.
2. sys_visibility.domain system property: This system property can be configured to control the visibility of records across different domains. By setting this property, you can define which domains' data should be visible to users outside their own domain hierarchy. This allows for more granular control over data access and visibility2.
These methods ensure that users can access the necessary data while maintaining the integrity and security of the domain separation model.
1: ServiceNow ACL Documentation
2: ServiceNow Domain Separation Documentation
How should you assign user record to a specific domain other than the one based on their company?
Answer : A
To assign a user record to a specific domain other than the one based on their company, you should use the ''Managed Domain'' option and set their domain field to the desired domain. This method allows administrators to manually assign a user to a different domain, ensuring that the user has the appropriate access and permissions within that domain.
* ServiceNow Documentation on Domain Separation explains how to set the domain for a user.
* ServiceNow Developer Documentation provides detailed information on domain separation and managing domains.
With the System Property csm_auto_account_domain_generation set to True:
Answer : C
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.