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

Updated On: 24-Aug-2026

An HR Admin without the System Admin role can do what? (Choose three.)

  1. Grant roles to users or groups
  2. Modify the HR Administration > Properties
  3. Reset user passwords
  4. Create HR Criteria
  5. Configure business rules
  6. Add users to groups

Answer(s): B,D,F

Explanation:

The correct answer is BDF because it aligns with the capabilities granted to an HR Admin role within the ServiceNow platform, excluding elevated system administrative privileges.
B: Modify the HR Administration > Properties: HR Admins are typically responsible for configuring HR-specific settings. These settings, often found under the "HR Administration > Properties" module, control how HR processes and features operate. Modifying these properties allows the HR Admin to tailor the system to the specific needs of the HR department. This is a core function of the HR Admin role, differentiating it from more general administration.
D: Create HR Criteria: HR Criteria are used to define rules and conditions for automatically assigning tasks, determining visibility of content, and personalizing the employee experience within the HR Service Delivery portal. Creating and managing these criteria is a critical task for HR Admins, enabling them to automate and target HR services effectively. This doesn't require system-level access but is confined to the HR application's logic.
F: Add users to groups: The HR Admin can add users to HR-related groups. This is necessary for managing access to sensitive HR information and ensuring the right individuals have the appropriate permissions within the HR Service Delivery application. Adding users to groups like "HR Case Readers" or "HR Managers" is essential for controlling access within the HR application. However, adding users to all groups in the instance would generally require elevated privileges.
Why other options are incorrect:

A: Grant roles to users or groups: Granting roles is typically reserved for users with elevated system administrator privileges. The HR Admin role generally does not have the authority to assign roles as it would circumvent security and access control protocols. This is because it could grant unintended access to sensitive areas of the instance beyond HR. C. Reset user passwords: Password resets are typically handled by the system or the user themselves through self-service. An HR Admin role would typically not have the ability to reset all user passwords. E. Configure business rules: Configuring business rules requires advanced technical skills and could potentially impact the entire instance, not just the HR module. It is thus limited to administrators with elevated system roles.
Supporting Documentation:
ServiceNow Docs - Roles in HR Service Delivery: https://docs.servicenow.com/bundle/utah-hr-service-delivery/page/product/human-resources/concept/c_RolesInHRServiceDelivery.html



After the HR Admin [sn_hr_core.admin] role has been removed from the Admin role, how may a user with only the Admin role add members to HR groups?

  1. The Admin must elevate their role to security_admin to add members to HR groups.
  2. The Admin follows the same process as with any group membership change.
  3. The Admin can no longer add members to HR groups.
  4. The Admin must impersonate an HR Admin to add members to HR groups.

Answer(s): C

Explanation:

The correct answer is C: The Admin can no longer add members to HR groups. Here's a detailed justification:
ServiceNow employs a role-based access control (RBAC) system.
When the sn_hr_core.admin role is removed from the standard admin role, the admin role loses the specific privileges associated with managing HR-
related data and configurations, including HR group memberships. The sn_hr_core.admin role explicitly grants the permission to manage HR-related groups. Without this role, the admin role only has the permissions associated with its default configuration which are typically system-wide admin tasks, but not HR-specific configurations.
Option A is incorrect because security_admin elevates privileges for security configurations, not user management in restricted modules. Option B is incorrect as the 'same process' relies on the sn_hr_core.admin role which is now removed. Option D requires impersonation which means there is an understanding that Admin Role alone does not possess this capability.
Essentially, access to modify HR groups is now gated behind the sn_hr_core.admin role. Removing this role from the admin role creates a separation of duties. This practice enhances security and ensures that only designated HR administrators can manage sensitive HR data. Even with the system-wide administrator role, the admin would be restricted from performing HR-specific admin functionalities if they do not have the explicit HR admin role.
Further research can be conducted on ServiceNow's role-based access control system, specifically focusing on delegated administration and role separation.
Authoritative Links:
ServiceNow Roles: https://docs.servicenow.com/bundle/utah-platform-administration/page/administer/roles/concept/c_Roles.html ServiceNow HR Roles: (Requires ServiceNow instance access and entitlement to HR documentation). Search for "HR Service Delivery Roles" within the ServiceNow documentation portal.



In the Create Bulk Cases module, which Filter by options are available in the dropdown? (Choose four.)

  1. Document Template
  2. Upload File
  3. HR Service Template
  4. User Criteria
  5. HR Template
  6. HR Profiles
  7. HR Criteria

Answer(s): B,D,F,G

Explanation:

The correct answer identifies the available filter options within the ServiceNow Create Bulk Cases module: Upload File, HR Profiles, HR Criteria, and HR Service Template. This module is designed to expedite the process of creating multiple HR cases simultaneously, and the filtering options are crucial for accurately targeting the correct population or applying the correct case configurations.
B: Upload File: This option allows users to upload a file containing a list of users (e.g., employee IDs, user names) or data relevant to the bulk case creation, such as compensation data for mass salary adjustments. This upload facilitates the creation of HR cases for the specific individuals listed in the file. F. HR Profiles: Selecting "HR Profiles" allows filtering the users based on different parameters/attributes stored in their HR Profile such as department, location, or job title. This ensures that the bulk cases are created for the appropriate group of employees based on the specific HR profile attributes. G. HR Criteria: HR Criteria is a powerful feature in ServiceNow HRSD used to define conditions that determine which users are eligible for certain HR services or policies. Filtering by HR Criteria in the Bulk Case module allows you to target cases based on predefined eligibility rules. For example, cases related to benefits enrollment could be targeted based on employee tenure or location, as defined by the HR Criteria. D. HR Service Template: When "HR Service Template" is selected, users can apply a specific pre-configured HR service template to the bulk cases. This ensures standardization and consistency in case creation, applying the same workflow, assignment rules, and SLAs to all the generated cases.
Options A, C and E are incorrect.
Document Template is not a filter option in Create Bulk Cases module User Criteria is not a valid filter option in the Create Bulk Cases module. HR Template is not a filter option in Create Bulk Cases module
Therefore, the answer BDFG is correct because it identifies the available options for filtering users when creating bulk HR cases in ServiceNow. These filtering methods ensure the creation of accurate and targeted cases, streamlining HR processes and ensuring consistent application of policies and services across the organization.
Relevant links for further research:
ServiceNow HR Service Delivery Documentation: (Requires ServiceNow login to access specific details about the Create Bulk Cases module, but provides general information about HRSD functionalities). ServiceNow Community Forums: (Search for "Create Bulk Cases" and "HR Criteria" to find user discussions and examples).



If you have both Admin and HR Admin roles and wanted to configure an Access Control for the Employee Relations Cases table, what must first be done?

  1. Add the Delegated Developer role to your User record
  2. From the User dropdown in the banner, elevate your role to security_admin
  3. Manually add the security_admin role to your User record
  4. Nothing would need to be done

Answer(s): B

Explanation:

The correct answer is B. From the User dropdown in the banner, elevate your role to security_admin.
Access Controls (ACLs) in ServiceNow govern data access and security.
While having the 'admin' role grants broad administrative privileges, modifying or creating ACLs, especially for sensitive tables like 'Employee Relations Cases,' requires the 'security_admin' role. This elevation is a deliberate security measure to prevent accidental or unauthorized changes to security rules that could expose sensitive data.
The 'security_admin' role isn't automatically granted even with the 'admin' role. ServiceNow utilizes a privilege elevation mechanism specifically for security-related tasks. By elevating to 'security_admin,' you temporarily gain the privileges necessary to modify ACLs. This elevation is initiated through the user dropdown menu within the platform itself, ensuring a conscious decision to perform security-sensitive operations.
Option A is incorrect because the 'Delegated Developer' role is for developing applications, not for modifying system security configurations like ACLs. Option C is incorrect because directly adding the 'security_admin' role to your user record is generally discouraged; privilege elevation is the preferred method to avoid persistent and potentially misused security privileges. Option D is incorrect as you must elevate to security_admin. Without elevating you will not be able to make access control changes to the Employee Relations Cases table.
Therefore, before configuring an Access Control for the Employee Relations Cases table when having both 'Admin' and 'HR Admin' roles, you must first elevate your role to 'security_admin' from the User dropdown in the banner to gain the necessary permissions.
Authoritative links for further research:
ServiceNow Docs - Access Control Rules: https://docs.servicenow.com/bundle/utah-platform-security/page/administer/contextual_security/concept/access_control_rules.html ServiceNow Docs - Elevate to a privileged role: https://docs.servicenow.com/bundle/utah-platform-security/page/administer/roles/task/t_ElevateRole.html



What type of information does the HR Profile contain?

  1. Personal employee data
  2. Group membership and role information
  3. User login and department information
  4. A user’s password

Answer(s): A

Explanation:

The correct answer is A. Personal employee data.
The HR Profile in ServiceNow, specifically within the Human Resources Service Delivery (HRSD) module, serves as a comprehensive record of an employee's personal information. This includes details like name, address, contact information, date of birth, marital status, emergency contacts, and other relevant personal identifiers. The HR Profile is the central repository for managing employee data throughout their lifecycle within the organization. This data is critical for various HR processes, such as onboarding, offboarding, benefits administration, and payroll.
While group membership and role information (B) are related to an employee and might influence HR processes, they are typically managed separately within ServiceNow's User Administration or related modules. Similarly, user login information (C) is primarily handled within user account settings and authentication protocols, not the HR Profile itself. A user's password (D) is never stored directly in the HR Profile for security reasons. Password management is handled through secure hashing and authentication mechanisms, not as part of the personal data record. The HR Profile strictly focuses on employee-specific personal information.
Therefore, the HR Profile is fundamentally about capturing and maintaining the personal employee data necessary for core HR functions.
Relevant Links:
ServiceNow HR Service Delivery: https://www.servicenow.com/products/hr-service-delivery.html ServiceNow Documentation: https://docs.servicenow.com/ (Search for HR Profile or Employee Profile within the HR Service Delivery documentation)



How many User Criteria Records may be applied to a single KB or KB Article?

  1. Only two
  2. Only three
  3. Unlimited
  4. Only one

Answer(s): C

Explanation:

The correct answer is C: Unlimited.
User Criteria in ServiceNow provides a powerful mechanism for controlling access to knowledge bases (KBs) and individual knowledge articles. Think of it as a sophisticated access control list (ACL) tailored for knowledge management. It allows administrators to define specific conditions based on various user attributes (like roles, groups, departments, locations, or even specific user IDs) that determine whether a user can read, write, or contribute to a knowledge base or article.
Unlike some systems where access control is limited to a small number of rules or groupings, ServiceNow's User Criteria design is highly flexible. This is key to its utility in large, complex organizations with diverse user populations. The ability to apply an unlimited number of User Criteria records to a KB or article means you can create highly granular access policies. For example, you might have one User Criteria record granting access to all employees in the HR department, another granting access to all managers, and yet another specifically granting access to a particular team working on a sensitive project. These can all be applied concurrently to the same KB.
The ServiceNow platform evaluates all applied User Criteria records to determine a user's effective access. If any of the "Can Read" criteria are met, the user can read the article (unless explicitly blocked by other criteria). This provides a comprehensive and adaptable approach to knowledge management access control, allowing organizations to tailor their knowledge sharing policies to precisely match their organizational structure and information sensitivity requirements. This scalability is crucial for enterprises operating in cloud environments, where managing access across a dispersed workforce is paramount.
Further reading:
ServiceNow Documentation: User Criteria ServiceNow Community: User Criteria Best Practices



In the base ServiceNow instance, how are User Criteria used?

  1. To control which users can access the HR Case application
  2. To control what a user sees in the information and suggested reading widgets
  3. To control read and write access to Knowledge bases and articles
  4. To control which users can access the HR Service Portal

Answer(s): C

Explanation:

The correct answer is C. To control read and write access to Knowledge bases and articles.
User Criteria in ServiceNow is a powerful mechanism primarily used to define conditions that determine who can access specific Knowledge bases and articles. User Criteria records specify conditions based on user attributes (like roles, groups, departments, locations) to grant or deny access to Knowledge content. This ensures that only authorized users can view and interact with specific knowledge articles.
While User Criteria can be leveraged indirectly for other functionalities within ServiceNow, its core purpose is to manage Knowledge access control. Options A and D are not the primary function of User Criteria. HR Cases' access is managed through roles and other access controls within the HR application. Similarly, while the HR Service Portal can present information based on roles, User Criteria doesn't directly control portal access in the base instance. Option B, although related to information visibility, is more accurately tied to other configuration options, such as audiences and content targeting within widgets, rather than direct User Criteria application.Therefore, only option C aligns directly with the documented functionality of User Criteria in the base ServiceNow instance.
For further research and validation, refer to the official ServiceNow documentation on User Criteria:
ServiceNow Docs - User Criteria: https://docs.servicenow.com/en-US/bundle/utopic-knowledge-management/page/product/knowledge-management/concept/c_KnowledgeUserCriteria.html



Which of the following are true for an HR application as it relates to the User [sys_user] Table and the HR Profile [sn_hr_core.profile] Table?

  1. Both are required.
  2. Only HR Profile table is required in HR.
  3. Neither are required.
  4. Only the User table is required in HR.

Answer(s): A

Explanation:

The correct answer is A: Both the User [sys_user] and HR Profile [sn_hr_core.profile] tables are required for a functional HR application in ServiceNow. The User table is a fundamental component of the ServiceNow platform, responsible for storing core user information, including login credentials, name, email, department, and location. Without a User record, an individual cannot access the ServiceNow instance or be associated with any records within it, including HR profiles.
The HR Profile table, on the other hand, specifically stores HR-related information about an individual, such as employee number, job title, manager, start date, and other attributes relevant to their employment. The HR Profile table extends the User table. It provides the necessary structure to manage employee-specific data within the HR module. A one-to-one relationship generally exists between a user record and an HR profile record.
While the User table provides the foundational identity and authentication, the HR Profile table enriches that identity with specific HR-related data. Together, they provide a comprehensive view of an individual within the organization, enabling efficient HR processes such as onboarding, offboarding, performance management, and benefits administration. Therefore, both are required.
For further research, you can consult the official ServiceNow documentation on the HR Service Delivery application:
ServiceNow HR Service Delivery Documentation: https://docs.servicenow.com/bundle/utopia-employee-service-management/page/product/human-resources/concept/hr-service-delivery.html



Viewing page 2 of 30
Viewing questions 9 - 16 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!