
[2024年12月25日] CIS-SPのPDFで最近更新された問題です集試験点数を伸ばそう
CIS-SP完全版問題集には無料PDF問題で合格させる
質問 # 15
Even though the Inbound Actions table has a domain field, records in this table should all be placed in this single location within the domain hierarchy.
- A. Default
- B. Top
- C. Service Provider
- D. Global
正解:D
解説:
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
質問 # 16
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. Global
- B. Default
- C. Top
- D. Customer domain
- E. Service Provider domain
正解:D
解説:
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.
質問 # 17
Process Separation is also known as:
- A. process administration
- B. admin administration
- C. domain administration
- D. proxy administration
- E. delegated administration
正解:C
解説:
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
質問 # 18
What are common concerns that might lead to a multi-instance strategy:
Choose 3 answers
- A. Sensitive internal service provider data
- B. Data residency
- C. Domain separation licensing cost
- D. Centralized reporting
- E. Highly regulated industries
正解:A、B、E
解説:
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.
質問 # 19
To grant domain visibility to a user you can
Choose 2 answers
- A. Associate a visibility domain to one of the user's groups
- B. Set the visibility domain's parent to the user's domain
- C. Associate a visibility domain to the user's domain
- D. Associate a visibility domain to the user record
- E. Associate a visibility domain to one of the user's roles
正解:A、E
解説:
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.
質問 # 20
If a business rule exists in the parent domain and is overridden in the child domain, which rule will run for the parent domain?
- A. The parent rule will run
- B. Neither rule will run
- C. The child rule will run
- D. Both rules will run
正解:A
解説:
In ServiceNow, the concept of domain separation allows for data and administrative segregation between different domains within an instance. When a business rule is defined in a parent domain, it applies to that domain and all child domains unless specifically overridden in a child domain1.
If a business rule is overridden in a child domain, the original rule in the parent domain continues to apply only to the parent domain and any other child domains that have not overridden the rule. The overridden rule in the child domain applies only to that specific child domain1.
Therefore, for the parent domain, the business rule that was created in the parent domain will run. The child domain's override does not affect the operation of the parent domain's business rules. This ensures that each domain can have customized behavior while still inheriting the broader rules set at the parent level.
It's important to manage these rules carefully to maintain the intended data integrity and operational workflows across different domains within the ServiceNow environment4.
質問 # 21
The Default domain should be specifically used for which purposes?
Choose 2 answers
- A. contain the default process for an instance
- B. to be configured as the Primary domain for an instance
- C. Capture records with no domain on tables that should not have global data
- D. Help identify integrations that are incorrectly creating global data
- E. contain sharable domain data across domains in an instance
正解:C、D
解説:
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
質問 # 22
On a new standalone table, what domain will a new record be created in by default?
- A. The records domain
- B. The user's current session domain
- C. The domain of the referenced company
- D. The users home domain
正解: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.
質問 # 23
If a user has the ITIL role and resides in the MSP domain, which is true?
- A. They can administer other domains by granting the Domain Admin role.
- B. They can be restricted to self-service in other domains by granting the Self-Service role.
- C. They have that role in all domains they have access to.
- D. They may be granted the Admin role in other domains.
正解:C
解説:
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.
質問 # 24
What tables that are considered process related tables are excluded from domain separation?
Choose 3 answers
- A. System Property
- B. Workflow
- C. Access Controls
- D. Ul Policies
- E. Business Rules
- F. Script Include
- G. Client Scripts
正解:A、C、E
解説:
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 as per domain requirements2.
質問 # 25
What does an admin click to view only global domain process while in the global domain?
- A. Global Domain Scope
- B. Configure Domain Scope
- C. Revert Domain Scope
- D. Collapse Domain Scope
正解:A
解説:
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
質問 # 26
Which are required to retrieve and commit an update set?
Choose 2 answers
- A. You must have the admin role.
- B. A change request must be approved.
- C. You must be working in a non-production instance.
- D. The domain picker must be set to global.
正解:A、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.
質問 # 27
When an administrator working in a domain modifies a policy that exists in a higher domain or in global, the system automatically:
- A. Creates a new record for that administrators current domain and overrides the original
- B. Modifies original policy but not current domain
- C. Creates a new Pol'cy and application in the current domain
- D. Modifies the module record and overrides the original
正解:A
解説:
When an administrator working in a domain modifies a policy that exists in a higher domain or in the global domain, ServiceNow automatically creates a new record for that administrator's current domain and overrides the original policy. This ensures that the changes are specific to the current domain and do not affect the policies in the higher or global domains. This behavior is part of the domain separation feature, which allows different domains to have their own customized policies and configurations without impacting each other.
For more detailed information, you can refer to the following resources:
* ServiceNow Support Article on Domain Separation
* Developing Domain-Separated Applications
質問 # 28
When configuring a shared process, to avoid updating a global process a developer should:
- A. Change to a process domain such as TOP
- B. No need to worry about the domain when you are a developer
- C. Change to customer domain
正解:A
解説:
D Change to global domain
Explanation:
When configuring a shared process in ServiceNow, it's important to ensure that the global process is not inadvertently updated. To avoid this, a developer should change to a process domain such as TOP. This is because the TOP domain is the highest level in the domain hierarchy and allows for the creation of shared processes that can be used by all subdomains without affecting the global domain. This approach aligns with best practices for maintaining clear separation between global processes and those that are domain-specific, ensuring that any modifications are contained within the intended scope.
The ServiceNow documentation on domain separation and best practices for developers emphasizes the importance of understanding the domain hierarchy and selecting the appropriate domain when making changes to shared processes. By working within a process domain like TOP, developers can leverage the benefits of domain separation to manage data, processes, and administrative tasks in a multi-tenant environment effectively.
For further details and guidelines on domain separation and process configuration, ServiceNow provides extensive documentation and resources for developers, which can be found on their official support and learning portals
質問 # 29
Process Domains are used to consolidate process updates for easy maintenance. What is the recommendation for handling such domains?
- A. Update the Global processes rather than creating overrides in the process domain
- B. Create overrides in the process domain or update Global processes
- C. Create overrides in the process domain rather than updating Global processes
- D. Creating overrides in the process domain and update Global processes
正解:C
解説:
When handling process domains in ServiceNow, the recommended approach is to create overrides in the process domain rather than updating the global processes. This strategy ensures that any customizations or specific requirements for a particular domain do not interfere with the global processes, which are intended to be standard and consistent across the entire organization.
Creating overrides in the process domain allows for more granular control and flexibility, enabling specific adjustments without impacting the overall system's integrity. This approach aligns with best practices for maintaining system stability and ensuring that updates or changes are isolated to the relevant domain.
For more detailed information, you can refer to the following resources:
* ServiceNow Learning Portal
* ServiceNow Knowledge Base
* ServiceNow Developer Portal
質問 # 30
Which are the available Domain Types on a baseline instance?
Choose 3 answers
- A. MSP
- B. Primary
- C. Vendor
- D. TOP
- E. Customer
正解:B、D、E
解説:
In a baseline ServiceNow instance, the available domain types include Primary, TOP, and Customer. These domain types are part of the domain hierarchy that ServiceNow uses to organize data, processes, and administrative tasks within the platform.
* Primary: This is the main domain where the instance is initially set up. It's the starting point for the domain hierarchy and typically contains the core configurations and settings for the instance.
* TOP: The TOP domain is the highest level in the domain hierarchy, above all other domains. It is used for defining global processes and settings that can be inherited by lower-level domains.
* Customer: Customer domains are created to represent individual customers or tenants in a multi-tenancy environment. Each customer domain can have its own unique configurations, processes, and data that are separate from other domains.
The concept of MSP (Managed Service Provider) and Vendor domains are not standard domain types in a baseline instance but can be configured as part of a domain separation strategy to cater to specific business needs. The ServiceNow documentation provides detailed information on domain separation, including the types of domains and how they are used within the platform. Domain separation allows organizations to maintain data privacy and process customization across different business entities within a single instance of ServiceNow.
質問 # 31
Why would you set Choice Action to Ignore on a transform field map?
- A. To reject new rows that doen't have choice values present.
- B. To avoid inserting dummy referenced records into global.
- C. To transform a field value using a script.
- D. To insert missing rows in a referenced table.
正解:B
解説:
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
質問 # 32
How should you assign user record to a specific domain other than the one based on their company?
- A. Select Managed Domain, and set their domain field to the desired domain.
- B. Set Default to true on their domain record.
- C. Use a Source Script on your LDAP transform.
- D. Change their Company reference to a company with the desired domain.
正解: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.
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.
質問 # 33
To data separate a new table, add a field named:
- A. sys_domain with a reference to the Domain table.
- B. sys_domain with a field type of Domain ID.
- C. sys_domain with a field type of String.
- D. Domain referencing the Company table.
正解:A
解説:
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.
Reference:
* ServiceNow Domain Separation Documentation
* ServiceNow Knowledge Base Article
質問 # 34
......
ServiceNow CIS-SP 認定試験の出題範囲:
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
100%更新されたのはServiceNow CIS-SP限定版PDF問題集:https://jp.fast2test.com/CIS-SP-premium-file.html