[2024] Pass ServiceNow CIS-SP Test Practice Test Questions Exam Dumps
Verified CIS-SP dumps Q&As - CIS-SP dumps with Correct Answers
ServiceNow CIS-SP Exam Syllabus Topics:
| Topic | Details |
|---|---|
| Topic 1 |
|
| Topic 2 |
|
| Topic 3 |
|
| Topic 4 |
|
NEW QUESTION # 28
The Default domain should be specifically used for which purposes?
Choose 2 answers
- A. Capture records with no domain on tables that should not have global data
- B. contain sharable domain data across domains in an instance
- C. to be configured as the Primary domain for an instance
- D. Help identify integrations that are incorrectly creating global data
- E. contain the default process for an instance
Answer: A,D
Explanation:
The Default domain in ServiceNow is specifically used for the following purposes:
1. Help identify integrations that are incorrectly creating global data: The Default domain can be used to track and identify any integrations that are mistakenly creating data in the global domain instead of the intended specific domain. This helps in maintaining data integrity and ensuring that data is correctly segregated.
2. Capture records with no domain on tables that should not have global data: The Default domain is also used to capture records that do not have a domain specified on tables where global data should not be present. This ensures that such records are not incorrectly placed in the global domain, maintaining the separation and security of data.
For more detailed information, you can refer to the following resources:
* ServiceNow Support Article on Domain Separation
* Developing Domain-Separated Applications
NEW QUESTION # 29
Process Separation is also known as:
- A. admin administration
- B. delegated administration
- C. process administration
- D. proxy administration
- E. domain administration
Answer: E
Explanation:
Process Separation in ServiceNow is also known as domain administration. This concept is part of the broader domain separation feature, which allows you to separate data, processes, and administrative tasks into logical groupings called domains. This is particularly useful for Managed Service Providers (MSPs) or large enterprises that need to manage multiple clients or departments within a single ServiceNow instance. Domain separation ensures that each domain can have its own set of data, processes, and administrative controls, providing a high level of customization and security.
For more detailed information, you can refer to the following resources:
* ServiceNow Support Article on Domain Separation
* Understanding Domain Separation in ServiceNow
NEW QUESTION # 30
Which are required to retrieve and commit an update set?
Choose 2 answers
- A. The domain picker must be set to global.
- B. A change request must be approved.
- C. You must have the admin role.
- D. You must be working in a non-production instance.
Answer: A,C
Explanation:
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.
NEW QUESTION # 31
A Service Provider Incident Manager wants to create a 'Plan Definition' for Task Communication Management for a specific customer domain when a major incident is accepted on-behalf of that specific domain. In what domain should they create the definition?
- A. Customer domain
- B. Global
- C. Service Provider domain
- D. Default
- E. Top
Answer: A
Explanation:
In ServiceNow, when a Service Provider Incident Manager is tasked with creating a 'Plan Definition' for Task Communication Management specifically for a major incident in a customer domain, the plan should be created within that customer domain. This ensures that the communication plan is tailored to the customer's environment and is triggered only when conditions within that domain are met.
The ServiceNow documentation provides guidance on setting up communication plans. It states that a communication plan should be defined for a task record to specify communication tasks and contact definitions. When the conditions for the plan definition are met, the communication plan and its associated records are automatically attached to the task record, which in this case would be the major incident accepted on behalf of the customer domain1.
Creating the plan definition within the customer domain ensures that the communication tasks and contacts are relevant and specific to the customer's needs, which is essential for effective communication management during major incidents. This approach aligns with ServiceNow's best practices for domain separation, where customer-specific configurations are maintained within their respective domains to avoid interference with global settings and other customer domains.
NEW QUESTION # 32
What does an admin click to view only global domain process while in the global domain?
- A. Global Domain Scope
- B. Collapse Domain Scope
- C. Configure Domain Scope
- D. Revert Domain Scope
Answer: A
Explanation:
When an admin wants to view only the global domain process while in the global domain, they need to click on the Global Domain Scope. This option allows the admin to filter and view processes that are specific to the global domain, ensuring that they are not seeing processes from other domains. This is particularly useful in a domain-separated environment where maintaining clarity and separation of processes is crucial.
Reference:
* ServiceNow Domain Separation - Basics
* ServiceNow Domain Separation - Advanced Concepts
NEW QUESTION # 33
Which of the following is a good practice to allow Service Providers to view all customer data?
- A. Put customer data in Global
- B. No action required
- C. Setup a domain contains relationship
- D. Setup a visibility group
Answer: C
Explanation:
Setting up a domain contains relationship is a good practice to allow Service Providers to view all customer data. This approach leverages ServiceNow's domain separation capabilities, which enable data segregation and access control across different domains. By configuring a domain contains relationship, you can ensure that Service Providers have the necessary visibility into customer data while maintaining proper data governance and security.
Reference:
* ServiceNow Domain Separation Documentation
* ServiceNow Knowledge Base Article
NEW QUESTION # 34
To grant domain visibility to a user you can
Choose 2 answers
- A. Set the visibility domain's parent to the user's domain
- B. Associate a visibility domain to the user's domain
- C. Associate a visibility domain to one of the user's roles
- D. Associate a visibility domain to the user record
- E. Associate a visibility domain to one of the user's groups
Answer: C,E
Explanation:
In ServiceNow, domain visibility determines whether users from one domain can access records from another domain. To grant domain visibility to a user, you can:
AAssociate a visibility domain to one of the user's roles: This allows any user with that role to see records in the associated visibility domain1.
EAssociate a visibility domain to one of the user's groups: Groups grant their members the visibility domains of the group, which means when a user is part of a group, they inherit the visibility domains associated with that group1.
It's important to note that when a user leaves a group, they lose the group's visibility domains, and the use of visibility domains should be done thoughtfully as excessive use can slow performance2. Moreover, the domain hierarchy should be optimal to prevent performance issues2.
The options B, C, and D are not standard practices for granting domain visibility according to the ServiceNow documentation and best practices. Specifically, associating a visibility domain directly to a user record or setting the visibility domain's parent to the user's domain are not mentioned as recommended methods3421.
NEW QUESTION # 35
Name the methods available to provide data access to a user outside of their domain hierarchy.
Choose 2 answers
- A. Visibility
- B. Contains
- C. sys_visibility.domain system property
- D. Access Control Lists
- E. Domain scope
Answer: C,D
Explanation:
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
NEW QUESTION # 36
What type of detailed results or actions are included in the domain audit?
Choose 3 answers
- A. recommended actions to remedy errors and warnings
- B. ability to re-run the audit
- C. incorrect user domain logins
- D. records or configurations affected
- E. escalate the errors as incidents
Answer: A,B,D
Explanation:
A domain audit in ServiceNow is a comprehensive review process that includes various actions and results to ensure the integrity and proper functioning of domain-separated environments1. The detailed results or actions included in a domain audit typically encompass:
* Records or configurations affected : The audit identifies which records or configurations have been impacted by any issues. This includes changes to the operating system, applications, or devices, and is crucial for tracking system operations and use2.
* Recommended actions to remedy errors and warnings (D): The audit provides recommendations for corrective actions to address any identified errors and warnings. This is part of the audit management process, where continuous monitoring using indicators and CMDB evidence helps in building or editing pre-built workflows for audit engagements, control or risk assessments, and remediation3.
* Ability to re-run the audit (E): After addressing the issues, the audit can be re-run to verify that the errors have been resolved and that the domain is functioning correctly. This ensures ongoing compliance and security within the ServiceNow environment2.
Incorrect user domain logins (A) and escalating errors as incidents (B) are not typically included in the domain audit results or actions. Instead, these aspects are more related to the operational monitoring and incident management processes within ServiceNow2.
NEW QUESTION # 37
What are common concerns that might lead to a multi-instance strategy:
Choose 3 answers
- A. Data residency
- B. Sensitive internal service provider data
- C. Centralized reporting
- D. Domain separation licensing cost
- E. Highly regulated industries
Answer: A,B,E
Explanation:
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.
NEW QUESTION # 38
What business logic can be created in a domain?
Choose 3 answers
- A. Ul Policy
- B. Ul Script
- C. Business Rule
- D. Script Include
- E. Email Notification
Answer: C,D,E
Explanation:
In ServiceNow, domain separation allows for the segregation of data, processes, and administrative tasks into logical groupings called domains. Within these domains, you can create specific business logic that is unique to each domain. The business logic that can be created in a domain includes:
* Business Rules: These are server-side scripts that execute when a record is displayed, inserted, updated, or deleted, or when a table is queried. Business rules can be used to apply business logic across all applications within a domain1.
* Email Notifications: These can be configured to respond to various events within a domain and can be set up to target users within specific domains. This allows for domain-specific communication strategies2.
* Script Includes: These are reusable server-side scripts that can be included in other scripts. Script includes can be used to store common functions or classes that are applicable to the domain-specific business logic3.
UI Policies and UI Scripts, while they can be part of the user interface customization in a domain-separated environment, are not considered business logic in the context of this question. UI Policies dynamically change information on a form and UI Scripts can add JavaScript to forms. However, they do not define the underlying business logic like Business Rules, Email Notifications, and Script Includes do.
For further details and best practices regarding domain separation and the creation of business logic within domains, you can refer to the ServiceNow documentation and resources provided23.
NEW QUESTION # 39
How should you assign user record to a specific domain other than the one based on their company?
- A. Use a Source Script on your LDAP transform.
- B. Change their Company reference to a company with the desired domain.
- C. Select Managed Domain, and set their domain field to the desired domain.
- D. Set Default to true on their domain record.
Answer: C
Explanation:
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.
Reference:
* 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.
NEW QUESTION # 40
What is the first step an admin must perform before using domain-separation for Service Catalog items?
- A. add the sysoverrides field to the catalog table
- B. assign catalog admin role to catalog administrators
- C. publish the catalog items to each domain
- D. activate the Service Catalog Domain Separation plugin
Answer: D
Explanation:
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.
NEW QUESTION # 41
Why would you set Choice Action to Ignore on a transform field map?
- A. To insert missing rows in a referenced table.
- B. To avoid inserting dummy referenced records into global.
- C. To transform a field value using a script.
- D. To reject new rows that doen't have choice values present.
Answer: B
Explanation:
Setting the Choice Action to "Ignore" on a transform field map in ServiceNow is used to avoid inserting dummy referenced records into the global domain. When importing data, if the system encounters a reference field value that does not match any existing records, setting the Choice Action to "Ignore" will prevent the creation of a new, potentially incorrect record. Instead, the system will skip the field and leave it blank, ensuring data integrity and avoiding the clutter of unnecessary records.
For more detailed information, you can refer to the following resources:
* ServiceNow Support Article on Transform Maps
* Choice Action Field in ServiceNow
NEW QUESTION # 42
Given a parent and child domain, explain data accessibility between domains.
- A. The child users can access all parent data
- B. Both parent and child users can access each others data
- C. The parent users can access all child data, but cannot access domains contained in the child domain
- D. The parent users can access all child data
Answer: C,D
Explanation:
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
NEW QUESTION # 43
Given TOP as a parent domain for MSP, ACME, and Initech, and MSP contains TOP What additional domain configuration is required for UserA in MSP to read records in ACME?
- A. Add contains between MSP and ACME
- B. Add both visibility to ACME for UserA, and contains between MSP and ACME
- C. No additional configurations
- D. Add visibility to ACME for UserA
Answer: D
Explanation:
In ServiceNow, domain separation is used to manage data visibility and access control in a multi-tenant environment1. The 'contains' relationship in domain separation defines a hierarchy where a parent domain contains child domains, and by default, users in a parent domain can see the records in child domains1.
Given that TOP is the parent domain for MSP, ACME, and Initech, and MSP contains TOP, UserA in MSP would already have visibility into TOP. However, for UserA to read records in ACME, additional configuration is required because ACME is not a child domain of MSP by default.
The correct action is to add visibility to ACME for UserA . This is typically done by configuring the user's domain membership or by adjusting the domain visibility settings to include ACME for UserA. This ensures that UserA can access records in ACME while still being primarily associated with the MSP domain1.
The 'contains' relationship between MSP and ACME (A) is not necessary because it would imply a hierarchical relationship that does not reflect the given structure. Adding both visibility to ACME for UserA and contains between MSP and ACME (B) is also not required and could potentially create an incorrect domain hierarchy. No additional configurations (D) would not suffice as it would not grant UserA the access needed to read records in ACME.
NEW QUESTION # 44
On a new standalone table, what domain will a new record be created in by default?
- A. The user's current session domain
- B. The records domain
- C. The users home domain
- D. The domain of the referenced company
Answer: A
Explanation:
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.
NEW QUESTION # 45
......
CIS-SP certification guide Q&A from Training Expert ExamCost: https://www.examcost.com/CIS-SP-practice-exam.html
The Best CIS-Service Provider Study Guide for the CIS-SP Exam: https://drive.google.com/open?id=1FyG5stleBllsfx-eJLj4IAn9Hr0IQXcr
