Sign in
Home/ServiceNow/Human Resources (CIS-HR)/Free questions

ServiceNow Certified Implementation Specialist - Human Resources (CIS-HR) — Free Practice Questions

10 free sample questions from a bank of 277, with the correct answers and explanations. No signup required — start practising right now.

1An HR Admin without the System Admin role can do what? (Choose three.)
  • Grant roles to users or groups
  • Modify the HR Administration > Properties
  • Reset user passwords
  • Create HR Criteria
  • Configure business rules
  • Add users to groups
Answer: B, D, F

The short version

BDF — HR Admin without System Admin keeps scoped HR duties. Properties, HR Criteria, and group membership stay allowed, while platform-wide powers stay blocked.

Key concepts in this question

  • HR Admin role: scoped administrator for HRSD configuration, criteria, and service setup without full platform control.
  • System Admin separation: platform role governing business rules, password resets, and role grants across all scopes.
  • HR Criteria: conditions controlling who can view HR services and cases based on employment attributes.
  • Least-privilege HRSD: model letting HR configure its own module while protecting core platform integrity.

Why BDF is correct

B is correct because HR Administration properties are module settings delegated to HR Admins for HRSD tuning. D is correct because creating HR Criteria is core HR access logic owned by HR administration. F is correct because adding users to groups supports HR team staffing without granting platform role management. Together they reflect scoped duties safe without System Admin rights.

Why the others are wrong

  • A. Granting roles to users or groups is platform security requiring System Admin authority.
  • C. Resetting user passwords is identity administration reserved for System Admin control.
  • E. Configuring business rules affects platform logic and stays under System Admin governance.

CIS-HR exam tip

Split scoped from platform: HR properties, criteria, and group adds belong to HR Admin, while roles, passwords, and rules need System Admin.

2What role is required, at a minimum, to view confidential HR Profile data?
  • HR Admin [sn_hr_core.admin]
  • HR Basic [sn_hr_core.basic]
  • LE Admin [sn_hr_le.admin]
  • HR Manager [sn_hr_core.manager]
Answer: B

The short version

B — HR Basic is the minimum for confidential HR Profile data. It grants employee-level HR access without full administrative power.

Key concepts in this question

  • HR Profile table: store of sensitive employment data including department, beneficiaries, and compensation details.
  • HR Basic role: baseline HR access permitting profile and case visibility for authorized HR consumers.
  • HR Admin versus Manager: higher roles for configuration and team oversight, exceeding minimum viewing needs.
  • Confidentiality boundary: HRSD restriction preventing System Admin and non-HR users from seeing private HR fields.

Why B is correct

B is correct because ServiceNow grants HR Profile read access starting at HR Basic, which is positioned as the entry HR role for confidential data. Higher roles also see the data but violate the at-a-minimum test by adding unnecessary privilege. The settled key therefore reflects least-privilege viewing of sensitive HR fields.

Why the others are wrong

  • A. HR Admin can view the data but exceeds the minimum by adding configuration authority.
  • C. LE Admin governs Lifecycle Events setup, not baseline HR Profile confidentiality access.
  • D. HR Manager adds managerial oversight and exceeds the minimum viewing requirement.

CIS-HR exam tip

Choose the lowest HR role for viewing: confidential profile reads start at HR Basic, not Admin or Manager.

3If both the Knowledge Base and the KB article have no "Can Read" User Criteria, what role is required to read the article?
  • HR Basic [sn_hr_core.basic]
  • HR Manager [sn_hr_core.manager]
  • No role is needed
  • HR Admin [sn_hr_core.admin]
Answer: C

The short version

C — with no Can Read criteria, no role is needed. Open Knowledge Base plus open article means public readability.

Key concepts in this question

  • User Criteria: records defining who can read or contribute to knowledge, catalog, and HR content.
  • Can Read control: read gate evaluated on both the Knowledge Base and the individual article.
  • Inheritance logic: restrictive criteria on either level block access, while empty on both leaves content open.
  • Knowledge access default: absence of criteria means no entitlement check is enforced for reading.

Why C is correct

C is correct because ServiceNow evaluates Can Read on the Knowledge Base and then on the article, denying when either imposes a restriction. When both levels carry no Can Read User Criteria, no entitlement filter applies and the article is readable without any special role. This open-by-default behavior for unrestricted content is the documented knowledge access rule.

Why the others are wrong

  • A. HR Basic is unnecessary when no Can Read restriction exists on base or article.
  • B. HR Manager is unnecessary for open content and governs oversight, not public reads.
  • D. HR Admin is unnecessary for reading when no criteria gate is configured.

CIS-HR exam tip

Empty means open: if both base and article lack Can Read criteria, answer no role needed.

4Using the base HRSD configuration with no integrations, when the subject person electronically signs an HR document or PDF document, the signature is saved as what?
  • a digital signature
  • a picture of the signature that is added to the document
  • a digital key
  • a digital certificate
Answer: B

The short version

B — base e-signature saves as a picture added to the document. It is an image acknowledgement, not cryptographic signing.

Key concepts in this question

  • Electronic signature: typed, drawn, or clicked acknowledgement image placed on an HR document or PDF.
  • Digital signature distinction: cryptographic mechanism using keys and certificates for tamper evidence and identity proof.
  • HR document workflow: base HRSD capture of subject-person approval stored with the case record.
  • No-integration baseline: out-of-box behavior without third-party signing providers or PKI services.

Why B is correct

B is correct because base HRSD implements e-signing as capture of a signature image that is overlaid onto the document for acknowledgement. HR Fundamentals explicitly states e-signatures are pictures representing approval, distinct from digital signatures. Without integrations there is no key, certificate, or cryptographic sealing, only the stored image.

Why the others are wrong

  • A. A digital signature implies cryptographic identity and integrity, which base e-sign lacks.
  • C. A digital key implies PKI key material, which is not created in base signing.
  • D. A digital certificate implies CA-issued identity binding, absent from the image workflow.

CIS-HR exam tip

Contrast image versus crypto: base HR signature equals picture on document, digital equals keys and certificates.

5What role needs to be removed from the Admin role at go live to prevent the System Admin from being able to see HR Profile information?
  • HR Manager [sn_hr_core.manager]
  • HR Agent [sn_hr_core.agent]
  • Core Admin [sn_core.admin]
  • HR Admin [sn_hr_core.admin]
Answer: D

The short version

D — remove HR Admin from Admin to hide confidential profile fields. System Admin then sees only User-table attributes, not private HR data.

Key concepts in this question

  • HR Admin containment: role granting access to confidential HR Profile fields such as beneficiaries and sensitive employment details.
  • Admin inheritance: System Admin initially includes HR Admin during implementation for setup convenience.
  • User versus HR Profile sync: shared fields like department mirror between tables, while confidential fields stay HR-only.
  • Go-live hardening: removing HR Admin from Admin enforces HR confidentiality for platform administrators.

Why D is correct

D is correct because HR Admin is the role that exposes confidential HR Profile information beyond the common User record. After configuration, stripping HR Admin from the Admin role leaves System Admin able to open the profile only through the User reference with shared fields visible. Private HR fields remain visible solely to HR professionals, achieving the go-live privacy goal.

Why the others are wrong

  • A. HR Manager governs case oversight, not the core confidential-profile access granted by HR Admin.
  • B. HR Agent handles case fulfillment and does not control Admin visibility into profile confidentiality.
  • C. Core Admin is platform scaffolding, not the HR confidentiality grant to remove at go-live.

CIS-HR exam tip

Harden at go-live by removing HR Admin from Admin: shared User fields stay visible, confidential HR fields go dark.

6If you select Data Type Numeric Scale on the Assessment Metric (Survey Question) form there is a Scale definition field made visible. What does it mean to select High for the Scale definition?
  • It means a high score is bad
  • It means a high score is good
  • There is no option for Scale definition
  • There is no option for High
Answer: B

The short version

B — High scale definition means a high score is good. The setting orients respondents and reporting toward positive-high interpretation.

Key concepts in this question

  • Assessment Metric form: survey question definition controlling data type, scale, and reporting behavior.
  • Numeric Scale type: quantitative question revealing Scale definition options once selected.
  • Scale definition: orientation flag declaring whether higher numbers represent better or worse outcomes.
  • Reporting impact: dashboards and averages interpret High as favorable when this definition is chosen.

Why B is correct

B is correct because ServiceNow documentation defines High as declaring that larger numeric responses indicate positive sentiment or good performance. Selecting it labels the upper end of the scale as desirable for engagement, satisfaction, or effectiveness surveys. This semantic setting guides analysts to read high averages as favorable rather than adverse.

Why the others are wrong

  • A. High score is bad corresponds to the opposite Low definition, not High.
  • C. Scale definition does appear once Numeric Scale is chosen, so no-option is incorrect.
  • D. High is an available definition value, so claiming absence is incorrect.

CIS-HR exam tip

Read High as good: Numeric Scale plus High tells reporting that up means favorable.

7In which Application Scope is the Lifecycle Events table contained?
  • Human Resources: Core
  • Human Resources: Lifecycle Events
  • Human Resources: Integrations
  • Human Resources: Service Portal
Answer: B

The short version

B — Lifecycle Events lives in Human Resources: Lifecycle Events scope. The dedicated scoped app owns onboarding and transition tables.

Key concepts in this question

  • Application Scope: namespace isolating tables, scripts, and configuration for a ServiceNow module.
  • Human Resources Core: base HRSD scope for profiles, cases, and core services.
  • Lifecycle Events scope: extension app for enterprise onboarding, transitions, and activity sets.
  • Scoped table ownership: Lifecycle Events table governed by its own scope for upgrades and permissions.

Why B is correct

B is correct because ServiceNow packages Lifecycle Events tables and logic in the Human Resources: Lifecycle Events scoped application for onboarding and transitions. Vancouver documentation on activating enterprise onboarding identifies this scope as the enabler for lifecycle processing. Core, Integrations, and Service Portal scopes own different artifacts, not this table.

Why the others are wrong

  • A. Human Resources Core owns profiles and cases, not the Lifecycle Events table.
  • C. Human Resources Integrations owns connector logic, not lifecycle event records.
  • D. Human Resources Service Portal owns portal widgets, not the lifecycle data model.

CIS-HR exam tip

Match lifecycle to its scope: Lifecycle Events table always sits in Human Resources: Lifecycle Events.

8What settings define and track cross-scope access to applications?
  • Access Controls
  • Restricted Caller Access
  • Access Restrictions
  • Business Rules
Answer: B

The short version

B — Restricted Caller Access defines and tracks cross-scope access. It governs which scoped apps may call each other and logs requests.

Key concepts in this question

  • Application scoping: isolation boundary preventing one scope from reading another without explicit permission.
  • Restricted Caller Access: table and settings granting scoped APIs and tables to approved calling scopes.
  • Access Controls versus Restrictions: generic terms, while the formal cross-scope mechanism has a specific name.
  • Business Rules: server logic automating record behavior, not the cross-scope permission framework.

Why B is correct

B is correct because ServiceNow uses Restricted Caller Access records to allow or block a requesting scope from invoking another scope resources. Administrators define allowed callers, and the platform tracks runtime requests against those allowances. This is the documented control for safe inter-scope communication.

Why the others are wrong

  • A. Access Controls is a generic label, not the named cross-scope tracking setting.
  • C. Access Restrictions is not the ServiceNow term for scoped caller governance.
  • D. Business Rules automate behavior and do not define cross-scope caller permissions.

CIS-HR exam tip

Name the gatekeeper: cross-scope calls always point to Restricted Caller Access.

9What determines which Knowledge bases, Knowledge articles, and Service Catalog Items an employee can view?
  • Filters
  • User Groups
  • HR Criteria
  • User Criteria
Answer: D

The short version

D — User Criteria determines Knowledge and Catalog visibility. It filters bases, articles, and items per employee eligibility.

Key concepts in this question

  • User Criteria: reusable eligibility records based on roles, groups, departments, or scripted conditions.
  • Knowledge visibility: Can Read gates on bases and articles evaluated against employee criteria.
  • Service Catalog visibility: Available For and Can View logic using the same criteria engine.
  • HR Criteria distinction: HR-specific filters for HR services, separate from platform-wide User Criteria.

Why D is correct

D is correct because ServiceNow evaluates User Criteria to decide which Knowledge bases, articles, and Catalog Items an employee may see. Documentation for knowledge user access and catalog entitlement centers on User Criteria matching. This single mechanism unifies content targeting across knowledge and service storefronts.

Why the others are wrong

  • A. Filters narrow lists but do not define entitlement to bases, articles, and items.
  • B. User Groups can feed criteria but alone do not determine visibility without criteria evaluation.
  • C. HR Criteria targets HR services and cases, not the broader knowledge plus catalog visibility rule.

CIS-HR exam tip

Think User Criteria for viewership: Knowledge plus Catalog visibility always resolves through User Criteria.

10The Template field referenced on the HR Service record is used to do what?
  • Populate fields on the HR Case record
  • Filter who can access the HR Service
  • Create pre-configured responses HR professionals can use
  • Make the HR Service accessible on the Employee Service Center
Answer: A

The short version

A — HR Service Template populates fields on the HR Case. It pre-fills case values to standardize fulfillment.

Key concepts in this question

  • HR Service: catalog entry defining an HR offering, routing, and fulfillment expectations.
  • Template field: reference to a case template carrying preset field values for new HR cases.
  • HR Case record: fulfillment ticket created when an employee requests the service.
  • Field population: automatic copying of priority, assignment, short description, and custom fields from template.

Why A is correct

A is correct because ServiceNow HR Service configuration uses the Template to stamp consistent values onto each generated HR Case. Documentation for configuring HR services describes templates as field-population aids for case creation. This reduces manual entry and enforces standard handling across similar requests.

Why the others are wrong

  • B. Access filtering is handled by HR Criteria and User Criteria, not by the Template field.
  • C. Pre-configured responses are knowledge or response templates, not the HR Service Template purpose.
  • D. Portal accessibility is controlled by service visibility and criteria, not by template population.

CIS-HR exam tip

Link Template to pre-fill: on HR Service it means populate HR Case fields automatically.

Want the full bank of 277 questions for ServiceNow Certified Implementation Specialist - Human Resources (CIS-HR)? See all practice exams.