[2025年01月10日] CIS-SP PDFで最近更新された問題です集試験点数を伸ばそう
CIS-SP完全版問題集には無料PDF問題で合格させる
ServiceNow CIS-SP 認定試験の出題範囲：
| トピック | 出題範囲 |
|---|---|
| トピック 1 |
|
| トピック 2 |
|
| トピック 3 |
|
| トピック 4 |
|
質問 # 11
If a business rule exists in the parent domain and a separate non-overriding business rule exists in the child domain, which rule will run for the child domain?
- A. Neither rule will run
- B. Both rules will run
- C. The child rule will run
- D. The parent rule will run
正解：B
解説：
In ServiceNow, domain separation allows for the partitioning of data, processes, and administrative tasks into distinct domains within the same instance. When it comes to business rules, if a business rule exists in the parent domain and another non-overriding business rule exists in the child domain, both rules will be executed for the child domain1.
This behavior is part of the domain hierarchy logic, where the child domain inherits the properties and rules of its parent unless explicitly overridden. Since the business rule in the child domain is non-overriding, it does not cancel or replace the parent domain's rule. Instead, it adds to the logic that will be processed when the conditions for the business rule are met.
Therefore, when an action occurs that triggers the business rules, the system will first run the business rule from the parent domain followed by the business rule from the child domain. This ensures that the foundational logic set by the parent domain is always applied, while still allowing for additional, domain-specific customizations in the child domains2.
It's important to note that this behavior can be controlled and configured according to the needs of the organization, and understanding the implications of domain inheritance is crucial for proper domain separation management in ServiceNow3.
質問 # 12
What happens when the glide.knowman.allow_edit_global_articles system property is enabled ?
- A. Users in global can check out and edit global articles
- B. Users from any domain with a knowledge admin role and can check out and edit global articles
- C. Users with admin rights from global domain can check out and edit global articles
- D. Any user from a domain other than the global domain can check out and edit global articles
正解：A
解説：
The glide.knowman.allow_edit_global_articles system property in ServiceNow, when enabled, allows users in the global domain to check out and edit global knowledge articles. This property is particularly useful in scenarios where an organization wants to centralize the editing of knowledge articles to users who are part of the global domain, typically administrators or designated knowledge managers.
This setting ensures that while users from other domains can view and utilize the global knowledge articles, the editing rights are reserved for global domain users to maintain consistency and control over the content. It's important to note that this property does not extend editing privileges to users from non-global domains or to all users with a knowledge admin role; it specifically targets users within the global domain.
The configuration of this property is a part of the knowledge management best practices in ServiceNow, as it helps in maintaining the quality and integrity of knowledge articles by restricting edit access to a controlled group of users. This approach aligns with the overall strategy of domain separation, where the goal is to separate and protect the data and operations of different business units or domains within the same ServiceNow instance1.
質問 # 13
A System Administrator wants to setup their domain hierarchy in a new instance, which practice should they follow when creating the structure?
- A. Having a totally flat domain heirarchy with no TOP domain
- B. Adding several domain layers below TOP before getting to the customer domain
- C. A domain heirarchy 3-5 layers deep that allows for use of contains if needed and does not contain a defualt domain
- D. A domain heirarchy 3-5 layers deep that allows for use of contains if needed and contains a defualt domain
- E. Using Service Offerings in the domain hierarchy
正解：D
解説：
Best practices for setting up a domain hierarchy in ServiceNow recommend creating a structure that is not too shallow or too deep. A hierarchy that is 3-5 layers deep is considered optimal as it allows for the use of 'contains' relationships where necessary12. This structure should include a default domain, which typically serves as the catch-all layer for any data that does not belong to a more specific domain3. The default domain is often the TOP domain or a domain just below it. This setup facilitates better organization and management of data and processes across different domains within the instance45.
質問 # 14
Which role restricts access and allows for managing items in a domain-separated catalog?
- A. catalog_manager
- B. catalog admin
- C. catalog_manage_admin
- D. domain_catalog_admin
正解：D
解説：
The role domain_catalog_admin is specifically designed to manage items within a domain-separated catalog in ServiceNow. This role restricts access and allows for the management of catalog items, ensuring that only users with the appropriate permissions can make changes within their designated domain. This is crucial for maintaining data privacy and integrity across different domains, especially in environments where multiple customers or departments are served by a single ServiceNow instance.
Reference:
* ServiceNow Domain Separation and Service Catalog1
* ServiceNow Product Documentation on Domain Separation2
質問 # 15
What is the best practice regarding User Criteria and Shared Knowledge Bases?
- A. Knowledge bases and User criteria should be defined in the parent domain so that they can be visible in a child domain
- B. Knowledge bases and User criteria should be defined in the company domain
- C. Knowledge bases and User criteria should be defined in the service provider domain
- D. Knowledge bases and User criteria should be defined in Global
正解：A
解説：
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.
質問 # 16
Which are the available Domain Types on a baseline instance?
Choose 3 answers
- A. Primary
- B. TOP
- C. MSP
- D. Vendor
- E. Customer
正解：A、B、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.
質問 # 17
Visibility can be granted to users by which of the following means:
Choose 2 answers
- A. Default Domain
- B. Role
- C. User visibility domains
- D. Group Membership
正解：B、D
解説：
Visibility in ServiceNow can be granted to users through Group Membership and Role.
* Group Membership: Users can be assigned to specific groups, and these groups can be granted visibility to certain records or functionalities within ServiceNow. This method allows for efficient management of user permissions based on their group affiliations.
* Role: Roles define a set of permissions that can be assigned to users. By assigning roles to users, administrators can control what users can see and do within the platform. Roles are a fundamental part of access control in ServiceNow.
Reference:
* ServiceNow User Criteria and Access Control
* ServiceNow Group Management
質問 # 18
On a new standalone table, what domain will a new record be created in by default?
- A. The records domain
- B. The users home domain
- C. The domain of the referenced company
- D. The user's current session domain
正解：D
解説：
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.
質問 # 19
What does the system property glide.sys.domain.delegated_administration do?
- A. Enable Process Separation
- B. Allow users without a system admin role to develop applications.
- C. A Allow customer admins to safely configure their own domains without impacting others.
- D. Allow another user to handle approvals and task assignments, for a specified time frame.
正解：C
解説：
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.
質問 # 20
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 Pol'cy and application in the current domain
- B. Modifies the module record and overrides the original
- C. Creates a new record for that administrators current domain and overrides the original
- D. Modifies original policy but not current domain
正解：C
解説：
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
質問 # 21
The system automatically sets which field when an administrator attempts to modify a policy, application, or module that belongs to another domain higher in the hierarchy?
- A. sys_admin_domain
- B. sys_overrides
- C. sys_primary_domain
- D. sys_domain_owner
正解：D
解説：
When an administrator attempts to modify a policy, application, or module that belongs to another domain higher in the hierarchy, the system automatically sets the sys_domain_owner field. This field ensures that the ownership of the record is correctly attributed to the domain that originally created or owns the record, maintaining the integrity and separation of data across different domains.
Reference:
* ServiceNow Domain Separation - Advanced Concepts and Configurations
* Understanding Domain Separation - Basics
質問 # 22
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. Neither rule will run
- B. The parent rule will run
- C. The child rule will run
- D. Both rules will run
正解：B
解説：
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.
質問 # 23
In a new domain separated instance, which data will a user in customer Domain X definitely have visibility to?
Choose 2 answers
- A. Primary Domain
- B. Domain X
- C. Parent domains of Domain X
- D. Default Domain
- E. Child domains of Domain X
正解：B、E
解説：
In ServiceNow, domain separation is used to segregate data, processes, and administrative tasks into logical groupings called domains. This allows for control over data visibility and operations within an instance. When it comes to data visibility:
* Domain X: A user in Domain X will definitely have visibility to their own domain, as this is the primary context in which they operate1.
* Child domains of Domain X: Users can view data in their home domain (Domain X) and any child domains of that home domain. This is because child domains inherit permissions and visibility from their parent domains, allowing users in a parent domain to see data in the child domains1.
However, users do not have access to data present in their parent domains or other unrelated domains by default. The primary domain and default domain are typically reserved for global or top-level administrative purposes and are not automatically visible to users in customer domains unless specific permissions are granted12.
It's important to configure domain separation carefully to ensure that users have the appropriate level of access to data necessary for their roles while maintaining the security and integrity of the data across the instance31.
質問 # 24
What tables that are considered process related tables are excluded from domain separation?
Choose 3 answers
- A. Access Controls
- B. System Property
- C. Ul Policies
- D. Client Scripts
- E. Script Include
- F. Workflow
- G. Business Rules
正解：A、B、G
解説：
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
Why would you set Choice Action to Ignore on a transform field map?
- A. To avoid inserting dummy referenced records into global.
- B. To transform a field value using a script.
- C. To reject new rows that doen't have choice values present.
- D. To insert missing rows in a referenced table.
正解：A
解説：
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
質問 # 26
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. Collapse Domain Scope
- D. Revert 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
質問 # 27
To data separate a new table, add a field named:
- A. Domain referencing the Company table.
- B. sys_domain with a field type of Domain ID.
- C. sys_domain with a reference to the Domain table.
- D. sys_domain with a field type of String.
正解：C
解説：
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
質問 # 28
Which represents the direction in the domain hierarchy in which can you see data?
- A. You can see data in child domains of your current domain (downstream)
- B. You can see data from parents and children of your current domain.
- C. You can see data in parent domains of your current domain (upstream).
- D. You can only see data in your current domain.
正解：A
解説：
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.
Reference:
* ServiceNow Domain Separation Documentation1
* ServiceNow Knowledge Base on Domain Separation2
質問 # 29
......
100%更新されたのはServiceNow CIS-SP限定版PDF問題集：https://jp.fast2test.com/CIS-SP-premium-file.html