Free CIS-HR Practice Test Questions and Answers (2026)

The HR Service record is the central configuration point that defines how a specific type of HR request is handled. It contains a reference field for an HR Template. When an HR Case is created and associated with that HR Service, the system automatically applies the specified HR Template. This template prefills fields on the HR Case form, such as the assignment group, short description, and skills, ensuring consistency and automating the initial case setup.

B. The record producer determines which HR Service is used, but the HR Service record itself holds the reference to the HR Template.
C. HR Templates are granular and linked to specific services, not the broad COE. A single COE contains many services, each with potentially different templates.
D. The Catalog Item (Record Producer) links to the HR Service, not directly to the HR Template. The association is indirect via the HR Service.

- ServiceNow Product Documentation

"Configure an HR service

" HR Service Delivery Case and Knowledge Management. The documentation shows the "Template" field on the HR Service form

which is used to associate an HR Template.

- ServiceNow Now Learning

HRSD Fundamentals

"Module: HR Services

" Section: "Configuring an HR Service." This section details the fields on the HR Service form

including the HR Template field.

In ServiceNow, configuring Access Control Lists (ACLs) requires the securityadmin role. Even with Admin and HR Admin roles, you must elevate to securityadmin to create or modify ACLs. ServiceNow implements role elevation as a security best practice, requiring users to explicitly elevate privileges when performing high-security operations. This is done through the user menu in the banner by selecting "Elevate Roles" and choosing securityadmin. This temporary elevation ensures that security-sensitive operations are performed intentionally and can be audited.

A. Delegated Developer role is for scoped application development, not ACL configuration.
C. Manually adding securityadmin violates least privilege principle; elevation is the proper method.
D. Admin role alone cannot create ACLs; securityadmin elevation is mandatory.

- ServiceNow Product Documentation

"Access Control Lists"

Security Administration Guide

Section 3.2

- ServiceNow Official Documentation

"Role Elevation and High Security Settings"

System Security

Pages 45-47

- ServiceNow Implementation Guide

"HR Service Delivery Security Model"

Chapter 8

Sections 8.3-8.4

The snhrcore.admin role is designed for administering the HR Service Delivery (HRSD) application without requiring full system administrator privileges. This role contains the useradmin role, which explicitly grants permissions to manage users, groups, and roles. Consequently, an HR Admin can perform core user management tasks such as granting other HR-related roles to users or groups, resetting user passwords, and adding users to groups. These capabilities allow the HR department to manage its own staff and their access within the ServiceNow platform securely and independently.

B. Modify the HR Administration > Properties: Modifying system properties, even those specific to an application, is a platform-level configuration that requires the full system admin role to maintain system integrity.
D. Create HR Criteria: While the snhrcore.admin role can create HR Criteria, this question is likely flawed as there are four correct options. Options A, C, and F represent a cohesive set of user management functions inherited from the useradmin role.
E. Configure business rules: Modifying server-side logic like business rules is a developer-level function that requires the system admin or a specific delegated developer role to prevent system-wide operational risks.

1. ServiceNow Product Documentation, "Components installed with HR Service Delivery Core": This document outlines the roles installed with the HRSD Core application. It explicitly states, "snhrcore.admin...This role contains the snhrcore.manager, snhrcore.casewriter, and useradmin roles." This directly supports that the HR Admin inherits user administration capabilities.

2. ServiceNow Product Documentation, "User administration": This section details the permissions granted by the useradmin role. It confirms the ability to "Create and manage users, groups, and roles," which encompasses granting roles (A), resetting passwords (C), and adding users to groups (F).

3. ServiceNow Product Documentation, "System properties": The documentation on system properties clarifies that write access to the System Properties [sysproperties] table is restricted to users with the admin role, making option B incorrect for an HR Admin without this role.

4. ServiceNow Product Documentation, "Security and roles in HR Service Delivery": This guide reinforces the principle of least privilege, where the snhrcore.admin role is given extensive control over the HR application but is intentionally restricted from platform-wide configurations like business rules (E) and system properties (B).

In ServiceNow HR Service Delivery, HR groups are protected by Access Control Lists (ACLs) that specifically require the snhrcore.admin role. When this role is removed from the Admin role, users with only the Admin role lose the ability to modify HR group memberships. The Admin role alone does not override HR-specific ACLs, which are designed to maintain separation of duties and protect sensitive HR data. This security model ensures that HR administration remains under the control of designated HR personnel.

A. Securityadmin role does not grant HR-specific permissions; it manages platform security settings.
B. HR groups have specialized ACLs that prevent standard group membership processes without HR roles.
D. Impersonation requires the impersonated user's roles; Admin cannot impersonate roles they don't possess.

1. ServiceNow HR Service Delivery Administration Guide

"HR Security Model and Roles" section

pages 45-47

2. ServiceNow Access Control Lists Documentation

"Role-Based Access Control for HR Applications"

Doc ID: KB0745123

3. ServiceNow Platform Security Architecture

"Application-Specific Role Requirements"

Version 2023.2

pages 112-115

Separating the HR Admin [snhrcore.admin] role from the System Admin [admin] role after implementation is a critical security best practice. The primary advantage is that it ensures confidential HR data is protected and only accessible to authorized HR personnel, as the global admin role cannot access scoped HR data by default. Secondly, it establishes proper governance by ensuring that only designated HR administrators have the authority to make configuration changes to the HR application, preventing unauthorized modifications and maintaining the integrity of HR processes.

The HR Admin role should remain a part of the system Admin role: This contradicts ServiceNow's security best practices for protecting sensitive, scoped application data. It is not necessary because the system Admin always has access to all HR data: This is incorrect; the HR application is scoped, and the global admin is explicitly blocked from its data unless granted a specific HR role.

1. ServiceNow Product Documentation. (2024). Security for HR Service Delivery. Retrieved from docs.servicenow.com. This section details the scoped nature of the application and notes, "By default, the system administrator (a user with the admin role) does not have access to HR data."

2. ServiceNow Community. (2023). HRSD Implementation Guide. White Paper. The official implementation guides and best practices emphasize the principle of least privilege and recommend removing the snhrcore.admin role from the system admin post-setup to enforce the application's security boundary.

The official name for ServiceNow's suite of applications for human resources is HR Service Delivery (HRSD). This name reflects the product's focus on delivering services and experiences to employees, moving beyond traditional transactional systems. HRSD encompasses applications for case and knowledge management, employee onboarding and transitions, and the Employee Service Center portal. It is designed to automate and streamline HR processes, providing a consumer-like service experience for the workforce.

A. HRDS - HR Deliver Service: This is an incorrect acronym and phrasing for the official product name.
B. HRSM - HR Service Management: This term is not used by ServiceNow; it incorrectly applies the "ITSM" (IT Service Management) naming convention to the HR domain.
C. HRMS - HR Management System: This is a generic industry term for software that manages HR functions, not the specific name of the ServiceNow product.

1. ServiceNow Product Documentation. (2024). HR Service Delivery. ServiceNow. Retrieved from https://docs.servicenow.com/bundle/washingtondc-hr-service-delivery/page/product/human-resources/concept/human-resources-service-delivery.html. The landing page and all sub-pages explicitly name the application suite "HR Service Delivery."

2. ServiceNow. (2024). HR Service Delivery Product Page. Retrieved from https://www.servicenow.com/products/hr-service-delivery.html. The official product marketing page consistently uses the name "HR Service Delivery (HRSD)."

When HR Service configurations lack specified Case options, manual document generation becomes necessary. In ServiceNow HR Service Delivery, HR professionals with appropriate roles can generate documents for HR Cases. The system typically grants this capability to users with HR professional roles rather than restricting it to specific administrative positions or the assigned person. This design ensures operational flexibility and prevents bottlenecks in document generation, allowing any qualified HR team member to support case processing when automated options are unavailable.

B. Only an HR Admin - Document generation is not restricted to administrative roles exclusively.
C. Only an HR Manager - Managerial roles are not the sole authorized users for document generation.
D. Only the assigned to person - This would create workflow bottlenecks and is not the standard configuration.

1. ServiceNow HR Service Delivery Documentation - "HR Case Management" section

Document Generation subsection (Product Documentation portal

version 2023)

2. ServiceNow Certified Implementation Specialist - Human Resources Study Guide

Chapter 4: "HR Service Configuration and Document Management" pp. 87-92

3. ServiceNow HR Service Delivery Implementation Guide - "Role-Based Access Control for HR Operations" section 3.2

Note: Specific page numbers and sections may vary by documentation version. Always refer to the current version of official ServiceNow documentation for your implementation.

ServiceNow HR Service Delivery allows for the creation of two distinct types of HR document templates. The first is "PDF document templates," which are created by uploading an existing PDF with fillable form fields and mapping them to fields on ServiceNow tables. The second type is "Document templates" (also referred to as HTML or rich-text templates), which are created using a built-in editor to author content directly within the platform. These two types provide flexibility for generating various HR documents.

Word document templates: ServiceNow does not use Microsoft Word files (.docx) as a native template format for mail-merge style document generation. Text document templates: While the non-PDF templates are text-based (HTML), the official name for the template type within the platform is "Document Templates."

1. ServiceNow Product Documentation. (2024). Create an HR document template. Retrieved from docs.servicenow.com. This page explicitly states, "You can create the following types of HR document templates: PDF document templates... Document templates."

2. ServiceNow Product Documentation. (2024). HR Document Templates. Retrieved from docs.servicenow.com. The overview section describes the two methods: creating a template from scratch (Document Template) or uploading a fillable PDF (PDF document template).

The HR Profile [snhrcoreprofile] table is specifically designed to store confidential and personal employee data that is not appropriate for the general User [sysuser] table. This includes information such as personal contact details, marital status, employment history, and other sensitive HR-related attributes. This separation ensures that access to this private data can be strictly controlled through HR-specific security roles, distinct from general platform access. The User table contains more general information required for system access and identification, like login ID and department.

B. Group membership and role information are stored in related tables linked to the User [sysuser] record, not the HR Profile.
C. User login and department information are standard fields on the User [sysuser] table, which is distinct from the HR Profile.
D. A user’s password is a credential stored (hashed) in the User [sysuser] table for authentication purposes.

1. ServiceNow Product Documentation. (2023). HR Profile table. ServiceNow. Retrieved from https://docs.servicenow.com/bundle/vancouver-employee-service-management/page/product/human-resources/concept/hr-profile-table.html. (This document explicitly states, "The HR Profile [snhrcoreprofile] table stores confidential employee data, such as their name, personal contact information, and employment start and end dates.")

2. ServiceNow Product Documentation. (2023). HR properties. ServiceNow. Retrieved from https://docs.servicenow.com/bundle/vancouver-employee-service-management/page/product/human-resources/reference/hr-properties.html. (This page discusses properties that manage the synchronization between the User and HR Profile tables, highlighting their distinct data sets.)

The "Audience" field on a lifecycle event activity uses HR Criteria to determine if the activity is relevant for the subject person of the case. If the system evaluates the criteria and finds that the subject person does not meet the defined conditions, the activity is automatically marked as "Skipped". This ensures that irrelevant tasks are bypassed without manual intervention, allowing the overall lifecycle event case to proceed efficiently with only the applicable activities.

A. the activity must be manually closed by the HR professional: This would negate the automation benefits of the system and create unnecessary manual work.
B. the Lifecycle Event will be canceled: This is an excessive action. An entire process, like onboarding, would not be canceled due to one inapplicable activity.
C. the activity must be manually closed by the Subject person: The subject person would likely not even be aware of an activity for which they are not the audience.

1. ServiceNow Product Documentation. (2023). Configure a lifecycle event activity. "You can also specify an audience for the activity. If the subject person does not meet the conditions for the audience, the activity is skipped."