ServiceNow CIS-HR Exam Prep
Certified Implementation Specialist - Human Resources (Page 3 )

Updated On: 24-Aug-2026

In the base instance, what determines the conditions a Case must meet before it can be assigned to an agent?

  1. Matching Rules
  2. Client Rules
  3. ACLs
  4. Escalation Rules

Answer(s): A

Explanation:

The correct answer is A, Matching Rules. In ServiceNow HR Service Delivery, Matching Rules are the primary mechanism for automatically assigning HR Cases to agents based on specific criteria. These rules define conditions, such as the subject person's location, HR service, or topic detail, which, when met by an HR Case, trigger assignment to an agent or group possessing the necessary skills or belonging to the appropriate department. Matching Rules use condition builders and scripts to determine suitability and target the appropriate assignee. This ensures efficient and accurate routing of HR inquiries.
Client Rules, ACLs (Access Control Lists), and Escalation Rules serve different purposes. Client Rules primarily govern client-side behavior and UI interactions. ACLs control data access and security permissions, determining who can read, write, or create records. Escalation Rules manage the prioritization and escalation of tasks or cases based on time elapsed or severity.
While ACLs influence visibility and access, and Escalation Rules manage timelines, they don't directly dictate the initial assignment of HR Cases based on case attributes. Matching Rules provide a robust framework tailored explicitly for intelligent case assignment, optimizing the HR service delivery workflow. Leveraging matching rules reduces manual intervention, improves agent efficiency, and ensures HR cases reach the most qualified agent for resolution quickly, leading to improved employee satisfaction. The rules also provide consistency in how cases are assigned.
Further Reading:
ServiceNow Product Documentation on Matching Rules: https://docs.servicenow.com/ (Search for "Matching Rules" in the ServiceNow documentation portal) ServiceNow Community Forums: https://community.servicenow.com/ (Search for "Matching Rules HR Service Delivery" for relevant discussions and examples)



What role is required, at a minimum, to view confidential HR Profile data?

  1. HR Admin [sn_hr_core.admin]
  2. HR Basic [sn_hr_core.basic]
  3. LE Admin [sn_hr_le.admin]
  4. HR Manager [sn_hr_core.manager]

Answer(s): B

Explanation:

The correct answer is B. HR Basic [sn_hr_core.basic]. Here's why:
While roles like HR Admin and HR Manager inherently possess elevated privileges, the minimum role necessary to view confidential HR Profile data is the HR Basic role. The HR Basic role grants fundamental access to HR case and profile information. Without this base role, users would lack the necessary permissions to even see HR profiles, let alone access their confidential data. Roles like HR Admin [sn_hr_core.admin] and HR Manager [sn_hr_core.manager] provide broader access to configure, manage, and process HR information. LE Admin [sn_hr_le.admin] pertains to Legal Entity Administration, not core HR Profile data.
The HR Basic role serves as the foundation for HR access, acting as a prerequisite for more granular roles.
While specialized roles might be needed to modify or create HR records, the ability to view is governed by the HR Basic role. This reflects the ServiceNow HR architecture's layered approach to security and access management. The principle of least privilege dictates that only the necessary access should be granted to perform a task, and viewing a confidential HR Profile needs at minimum the HR Basic role. HR administrators configure these roles to adhere to data privacy and compliance requirements.
Further research can be conducted via the official ServiceNow documentation for HR Service Delivery roles:
ServiceNow Docs: HR roles



What types of HR Document templates may be created in ServiceNow? (Choose two.)

  1. Document Templates
  2. Word document templates
  3. PDF document templates
  4. Text document templates

Answer(s): A,C

Explanation:

The correct answer is AC: Document Templates and PDF document templates. Let's break down why.
ServiceNow's HR Service Delivery module provides capabilities for managing various HR processes, including document generation.
While ServiceNow can integrate with external tools that handle diverse document formats, the core functionality within ServiceNow HRSD specifically supports two main template types for HR documents.
Firstly, "Document Templates" refers to templates created directly within the ServiceNow platform using the platform's capabilities. These are essentially structured data records that can be populated with employee information to generate documents. These could include things like offer letters, promotion letters, and so on. They rely on data already present within the ServiceNow instance, like employee records and HR case data.
Secondly, "PDF document templates" are also supported within the ServiceNow HRSD framework. This involves uploading pre-designed PDF forms, such as I-9 forms or W-4 forms, into the ServiceNow platform. ServiceNow can then automatically populate these forms with relevant employee data.
Word document templates are not directly created and managed within ServiceNow's core document generation capabilities.
While you could potentially integrate with external document generation tools that work with Word documents, it isn't a natively supported option. Similarly, basic text document templates lack the formatting and robust capabilities needed for complex HR documents.
In summary, ServiceNow HRSD primarily uses its own internal "Document Templates" alongside "PDF document templates" to streamline document generation and ensure data consistency. The templates leverage information stored within the ServiceNow platform to automate the creation of HR-related documents.
Here are a few resources that highlight ServiceNow's HRSD capabilities:
ServiceNow HR Service Delivery Documentation: (Search ServiceNow's official documentation for HR Service Delivery; exact URL varies based on ServiceNow version) - This is the most authoritative source for information on document management within ServiceNow HRSD. ServiceNow Community Forums: (community.servicenow.com) - Explore discussions on HRSD implementations and common use cases.



What are the advantages of removing the HR Admin role from the system Admin role after the HR Implementation tasks have been completed? (Choose two.)

  1. This ensures that HR has control over further HR configurations.
  2. The HR Admin role should remain a part of the system Admin role.
  3. This ensures that confidential HR data is only accessible to users with an HR role.
  4. It is not necessary because the system Admin always has access to all HR data.

Answer(s): A,C

Explanation:

The selected answer (A and C) highlights critical security and governance considerations when managing sensitive HR data within a ServiceNow instance after initial implementation.

A: This ensures that HR has control over further HR configurations. Removing HR Admin from the system admin role allows HR to manage its configurations independently, fostering a more agile and responsive HR function. It prevents accidental or unauthorized changes to HR processes by non-HR personnel. This separation of duties aligns with the principle of least privilege, a core cloud security concept emphasizing granting only the minimum necessary access rights to users. This enables the HR department to own and evolve its processes without constantly relying on IT or system administrators.
C: This ensures that confidential HR data is only accessible to users with an HR role. One of the most important aspects of HR data is its confidentiality. By restricting system admin access after the implementation, organizations strengthen their compliance with data privacy regulations like GDPR and CCPA. The principle of data minimization suggests collecting and retaining only necessary information and limiting access to that data. By restricting access based on the HR role, only authorized users can access employee records, salary information, and other sensitive data.
Option B is incorrect because it contradicts the principle of least privilege and separation of duties. Option D is incorrect because, in a well-managed system, system admin access should not automatically extend to all HR data after implementation. Segregation of duties is essential to prevent a single user from having excessive control. This segregation prevents the potential for abuse of power and helps to ensure that changes are subject to review and approval.
Further Research:
ServiceNow Role Management Documentation: https://docs.servicenow.com/ (Search for role management and HR security) NIST Cybersecurity Framework: https://www.nist.gov/cyberframework (Relevant to data security and access control) Cloud Security Alliance (CSA): https://cloudsecurityalliance.org/ (Provides resources on cloud security best practices)



What does ServiceNow now call the HR application?

  1. HRDS - HR Deliver Service
  2. HRSM - HR Service Management
  3. HRMS - HR Management System
  4. HRSD - HR Service Delivery

Answer(s): D

Explanation:

The correct answer is D, HRSD - HR Service Delivery, because ServiceNow has rebranded its HR application to reflect its broader capabilities and focus. HRSD encompasses not just traditional HR functions like record-keeping (which is implied in HRMS - HR Management System), but also emphasizes the delivery of services to employees throughout their lifecycle. This aligns with the modern cloud computing paradigm of service-oriented architecture (SOA), where applications are designed as a collection of loosely coupled services that can be accessed and consumed over a network, in this case, the ServiceNow platform. ServiceNow positions HRSD as a platform for transforming the employee experience by providing a unified and seamless way to access HR services, knowledge, and support. The "delivery" aspect stresses providing efficient and effective employee-centric services leveraging cloud computing's scalability and accessibility. HRSD is specifically designed to improve employee engagement, automate HR processes, and provide data-driven insights. Options A and C are simply incorrect acronyms within the ServiceNow ecosystem. Option B, HRSM (HR Service Management), is partially correct in that it acknowledges the service-oriented nature, but ServiceNow specifically uses HRSD as the name of its HR application, highlighting the actual delivery of those services. Therefore, HRSD best captures ServiceNow's approach to modern HR management.
For further research, refer to the official ServiceNow documentation:
ServiceNow HR Service Delivery: https://www.servicenow.com/products/hr-service-delivery.html ServiceNow Knowledge Base: Search ServiceNow documentation for HRSD related articles within your instance or on the ServiceNow website.
These resources from ServiceNow directly confirm the usage and meaning of the HRSD acronym within their platform.



What defines an employee's access to the HR Service Portal / Employee Service Center?

  1. Group membership
  2. User Criteria
  3. HR Criteria
  4. Client Roles

Answer(s): D

Explanation:

The correct answer is D, Client Roles. Here's why:
Client Roles in ServiceNow specifically control access to UI elements and functionalities within service portals, including the HR Service Portal/Employee Service Center. They define what an employee can see and do within the portal.
While User Criteria (Option B) plays a significant role in controlling knowledge base access, catalog item availability, and record producer visibility, its primary focus isn't the overall access to the portal itself. User Criteria can further refine content access within the portal after a user has already gained entry.
Group membership (Option A) is primarily used for task assignment, security incident management, and granting roles that provide broader system-level access, but it doesn't directly control portal access. Group membership might indirectly influence access if a role associated with the group grants access to the portal.
HR Criteria (Option C) in ServiceNow defines the audience for HR cases and knowledge articles. It is used to determine which cases or articles an employee can access based on attributes such as department or location. However, HR Criteria doesn't directly grant or deny initial access to the HR Service Portal.
Client Roles are the mechanism designed to grant access to specific parts of the ServiceNow platform, like the HR Service Portal. By assigning a specific Client Role to a user, that user can access the designated components within the HR Service Portal or Employee Service Center. This allows for segmented content management and access, meaning that certain groups of employees can have different interfaces for different categories.
In short, while group membership, user criteria, and HR criteria can impact what someone sees within the portal, Client Roles define the initial access to the portal itself. Without the appropriate Client Role, an employee won't even be able to access the HR Service Portal, regardless of their group membership, user criteria matches, or HR criteria alignment. https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/roles/concept/c_Roles.htmlhttps://docs.servicenow.com/bundle/utah-employee-service-management/page/product/human-resources/concept/hr-service-portal.html



What kind of records do HR Requests create?

  1. HR Incidents
  2. HR Files
  3. HR Problems
  4. HR Cases

Answer(s): D

Explanation:

The correct answer is D, HR Cases. HR Requests in ServiceNow directly generate HR Cases. This is the core functionality and purpose of HR Requests within the ServiceNow Human Resources Service Delivery (HRSD) module. HR Cases are the primary records used to track, manage, and resolve employee inquiries and requests.
When an employee submits an HR Request through the service portal or other channels, ServiceNow automatically creates a corresponding HR Case. This case then becomes the central point for all activities related to that specific request, including tasks, approvals, documentation, and communication.
HR Incidents are typically related to IT service disruptions or failures, and HR Problems are used to investigate and resolve underlying causes of recurring issues. HR Files are generally used for storing and managing documents.
While HR Cases may reference files, they don't create them. The main function of an HR Request is to initiate a structured process managed through an HR Case to address an employee need. The creation of HR Cases ensures a consistent and trackable way of handling employee interactions within the ServiceNow HRSD framework. It ensures that the HR department can efficiently manage its workload, track service level agreements (SLAs), and provide a positive employee experience.
Refer to ServiceNow's official documentation on HRSD and HR Case Management for comprehensive details:
ServiceNow HR Service Delivery: https://www.servicenow.com/products/hr-service-delivery.html ServiceNow Documentation (HR Case Management): Search "ServiceNow HR Case Management" in the ServiceNow documentation portal for in-depth information within your specific ServiceNow version.



In the HR Guided Setup Module, why are some tasks locked in the Task view?

  1. They require an elevated role to access.
  2. They are deprecated tasks that should not be completed.
  3. They require other tasks to be completed first.
  4. They require a plugin to be activated first.

Answer(s): D

Explanation:

The correct answer is D. They require a plugin to be activated first.
Here's a detailed justification:
The ServiceNow Guided Setup provides a structured way to configure applications and features. The tasks within the setup are often dependent on specific functionalities within the platform. These functionalities are frequently packaged within plugins.
Plugins in ServiceNow are essentially bundled sets of features, tables, scripts, and other components that extend the platform's base functionality. Before a feature managed by a particular plugin can be accessed or configured, that plugin must be activated.
When a plugin is not activated, related Guided Setup tasks are often locked or unavailable. This is because the system lacks the underlying code and data structures provided by the plugin that are essential for the task to function correctly. Attempting to complete these tasks without the plugin enabled would result in errors or incomplete configurations. This mechanism ensures that configurations are performed in the right order and prevents errors that can arise from missing dependencies. It also provides a way of keeping the platform lean, and only activate the required features.
Options A, B and C are not correct because:

A: They require an elevated role to access: While some tasks within ServiceNow do require specific roles to access, this is not the primary reason tasks are locked in the Guided Setup. Role-based access control applies independently of whether a plugin is activated or not. Tasks that are locked due to missing plugins will usually provide messaging specifying this condition. B. They are deprecated tasks that should not be completed: Deprecated tasks are usually clearly marked as such and often hidden or removed. They are generally not simply locked. C. They require other tasks to be completed first: Task dependencies exist within Guided Setup. However, when a task is locked due to a dependency, the system usually indicates which prerequisite tasks must be completed first, with different visual cues. Locking solely due to a task dependency is distinct from plugin dependency.
In summary, a locked Guided Setup task typically indicates that a required plugin hasn't been activated, thus preventing the configuration or feature from functioning correctly. You need to navigate to the Plugins module and activate the appropriate plugin to unlock the task.
Supporting resources:
ServiceNow Docs: Plugins ServiceNow Docs: Activate a plugin



Viewing page 3 of 30
Viewing questions 17 - 24 out of 229 questions


Post your Comments and Discuss ServiceNow CIS-HR exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!