ServiceNow Certified Implementation Specialist - Human Resources (CIS-HR, HR Service Delivery) (CIS-HR) (CIS-HR) — Questions 1–75

'Wait for completion' halts the engine's progression at that activity, so subsequent activities in the flow do not start until the current one finishes. This satisfies the requirement that dependent work is not triggered prematurely, keeping execution order aligned with actual completion.

Assignment logic such as default assignment group belongs on the HR Service record itself, since the service definition drives case creation behaviour. Defining the target HR group there ensures every case raised against that service is routed automatically, satisfying the stem's requirement without extra workflow configuration.

The sn_hr_core_profile table stores the HR Profile record itself, so mapping external payroll data here writes directly to the fields the HR Profile displays. This satisfies the stem's requirement that payroll data populate the HR Profile, rather than an intermediary staging or case table.

The HR Service record holds the Case Template field, which defines the default template applied when that service generates a case. Configuring the link there satisfies the requirement, since templates themselves carry no reference back to services.

A single Lifecycle Event can be associated with multiple Activity Sets, each containing the activities required for a particular transition such as onboarding or offboarding. This one-to-many relationship lets one event drive several parallel or sequential activity sets across different teams.

Scoped applications encapsulate their artefacts, so changes stay contained rather than touching global tables and scripts. This containment means patches and upgrades can be applied without overwriting customisations, satisfying the stem's benefit of easier updates across the HR application lifecycle.

Employee Center is the standard self-service portal in HR Service Delivery that provides a unified experience across departments, including HR, IT, and Workplace. It allows employees to search knowledge, open HR cases, and access services from multiple departments in one place. This matches the requirement for a single interface for HR requests and knowledge.

Topic Category groups HR services into logical classifications, driving catalogue navigation and filtering for employees while feeding reporting dimensions. It satisfies the stem's requirement by organising services rather than defining fulfilment, approval, or assignment logic — those belong to separate configuration records such as workflows and assignment rules within HR Service Delivery.

The sn_hr_core_profile table holds the HR profile record and references sys_user via its user field, so it is the correct store for core HR data linked to a user account. Other HR tables handle cases, tasks or documents rather than the profile itself.

An HR Profile Business Rule executes automatically when a user record is created, generating the linked HR Profile without manual intervention. Configuring this logic on the HR Profile table satisfies the requirement that profiles be created automatically upon user creation.

HR criteria define conditions on HR profile, case, or related fields; when matched, they drive template selection and routing. In this scenario, the team needs dynamic routing based on employee and case attributes, so HR criteria is the correct component. It evaluates conditions at case creation and applies the associated HR template, which can specify assignment group and other defaults.

HR Criteria can evaluate case attributes such as the topic or selected catalog item and determine the assignment group dynamically. This allows a single HR service to route payroll cases to Payroll and benefits cases to Benefits based on the criteria matched. It satisfies the requirement of conditional routing within one HR service definition.

A Record Producer allows you to define a catalog form that captures user input and maps variables to fields on the HR Case record. By associating it with the HR Service, the form appears when an employee selects that service on the Employee Center, ensuring destination city and move date are collected before case creation.

Updating case status is permitted because HR Agents hold the case-writer role, which grants write access to the state field on HR cases within Agent Workspace. This satisfies the stem's requirement for actions an HR Agent can perform, as status transitions remain within their delegated case-management permissions rather than requiring elevated admin rights.

The Lifecycle Event Engine drives the overall lifecycle process, sequencing activities and triggering HR Tasks and cases as the employee moves through stages. This orchestration role is precisely what the stem asks for, distinguishing it from individual tasks or cases.

Topic Category groups HR Services into logical classifications, driving catalogue navigation and enabling reporting breakdowns by service area. It does not control access or approval routing, so it satisfies the stem's classification purpose for reporting and navigation.

HR criteria are conditions that determine which HR services are available to a user. By creating criteria that check the employee's legal entity (e.g., using the HR profile or user record), and applying those criteria to the relevant HR services, the administrator can ensure that employees only see services for their entity. This is the standard mechanism for controlling service visibility.

HR Case Management provides the central workspace where an HR administrator views, filters and manages every HR case across the organisation, regardless of assignment group. It satisfies the stem's requirement to see and manage all cases system-wide from one module.

The 'Source' field identifies which system or record supplies the incoming value during field mapping, satisfying the stem's requirement to denote origin. It specifies the authoritative system — for example, Workday or Microsoft Entra ID — from which each attribute is drawn, so transformations and target assignments reference the correct upstream data.

HR Templates predefine the case structure, tasks and fields generated for a given HR request, ensuring consistent handling. It is a valid HR Service Delivery component, sitting alongside HR Services and HR Tasks in the ServiceNow HR application architecture.

Integration Hub provides reusable spokes and actions for outbound REST or SOAP calls to third-party providers. Using it satisfies the background check integration requirement, keeping external calls governed and separate from core case processing logic.

Read ACLs on the HR case table are a standard way to control which roles can view HR case records. By requiring specific roles, you ensure that only authorized users can read the records. This is a fundamental security measure in ServiceNow and directly meets the requirement to restrict access based on roles.

HR Criteria are conditions evaluated against the employee's profile and location attributes to determine which HR services, catalog items, and knowledge articles are visible. By defining criteria such as Country equals a specific value and applying them to services and articles, the administrator ensures each employee sees only relevant content from the single Employee Center portal.

Approval is a valid Activity Type within Lifecycle Events, satisfying the stem's requirement for genuine activity categories. It defines an authorisation step where designated approvers must sanction a lifecycle transition before it proceeds, distinct from notification or task activities. This makes it a legitimate selectable activity when configuring event workflows in Microsoft Entra ID.

The Lifecycle Events > Lifecycle Events module lists and creates the parent lifecycle event records themselves, distinct from event activities or activity definitions. Navigating here lets an administrator define the parent object's name, description and associated configuration before building its child activities.

HR case records are stored in the `sn_hr_core_case` table, which extends the base Task table and holds HR-specific fields such as case type, HR service, and employee subject. This satisfies the stem's requirement for the dedicated HR Case data table, distinguishing it from generic case or task tables.

Flow Designer supports multi-step approval logic, conditional branching and record actions, meeting the stem's complex approval workflow requirement. It supersedes legacy Workflow Editor for HR Service automation, letting you trigger approvals and actions on HR case records without custom scripting.

Lifecycle Events provide a single, governed trigger mechanism that fires automated provisioning actions across HR, IT and security systems from one authoritative joiner-mover-leaver state change. This removes per-department manual handoffs, satisfying the stem's requirement for a main advantage: consistent, repeatable cross-departmental workflow execution rather than isolated team-specific processes.

HR Criteria control which users can view a catalog item on the Employee Center by evaluating conditions such as department, location or role. If the criteria exclude the user, the item stays hidden even when the catalog and service are correctly published.

Date-based trigger conditions evaluate against the system time zone, not the user's or case's local zone. This means the trigger fires according to server-configured time, so the constraint of consistent, predictable scheduling across all users is satisfied.

Taxonomy underpins the Employee Center by organising content into a structured hierarchy of topics and categories, which drives the mega-menu navigation and targeted content delivery. This satisfies the architecture's requirement for a governed classification framework, letting employees browse curated knowledge by department, location or service rather than relying on unstructured search.

HR Criteria replaces hard-coded ACL scripts with declarative, condition-based rules that business users configure through the ServiceNow interface. This satisfies the stem's constraint by removing developer dependency, letting HR staff maintain complex security logic themselves without scripting knowledge or code deployment cycles.

Assignment rules route new HR cases to the correct group based on field values, so a rule matching category 'Payroll' directs those cases to the Payroll group. This satisfies the routing constraint; assignment rules run on case creation, unlike business rules or UI policies.

The HR case table is a fundamental table in HR Service Delivery, storing all HR cases created from the HR catalog or by agents. It holds case details, assignment, state, and related HR profile information. It is the central transactional table for HR service delivery and is used for reporting, routing, and agent workspaces. This makes it part of the standard data model.

Attachments are stored in the sys_attachment table, and access to them is controlled by ACLs on that table. By creating an ACL that evaluates the associated HR case's assigned agent and opened_for fields, you can restrict download access to only those users. This is the correct approach because it directly secures the attachment records and integrates with the platform's security model.

If the HR task has a condition that evaluates to false at the time of activation, it will be skipped or not run. Even though the approval is complete and 'Wait for completion' is satisfied, the condition could be blocking the task. Checking the condition is the first step to diagnose why the task is not starting, as it directly controls whether the activity executes.

A Data Retention Policy defines destruction rules on the HR case table, automatically deleting records once they reach the seven-year threshold. This satisfies the compliance requirement without manual intervention, unlike archiving or scheduled jobs that merely move or flag data.

Notifications can be configured on the Activity table (or its child tables) to fire on state change. By filtering on state='Complete' and the activity name, the manager receives the notification precisely after the contract is signed, which matches the requirement without affecting the activity set's sequencing.

Task Templates define the standard task structure generated for an HR case, specifying which tasks are created and their sequencing. They satisfy the requirement by providing the reusable blueprint that shapes each case's task hierarchy.

Enabling 'Show to Subject Person' publishes the activity to the subject person's Employee Center portal view, letting them see and act on it. Disabling it keeps the activity internal to agents, so this setting controls subject-facing visibility.

HR Security Profiles are the primary HR-specific restriction mechanism, scoping case visibility by criteria such as department, location or HR service. They satisfy the requirement to limit which HR cases a user can access, alongside ACLs.

HR Criteria evaluates HR-specific fields such as department, job title and location, which User Criteria cannot reference. This directly satisfies the stem's requirement for the primary benefit: targeting approvals and tasks by organisational data held in the HR system, rather than by generic user attributes.

An HR Case Template supplies default values for fields such as category, assignment group and short description when a case is created. This satisfies the requirement by pre-populating fields, reducing manual entry and enforcing consistency.

HR Tasks records are stored in the 'sn_hr_core' scope, satisfying the requirement for items belonging to the core HR application. This scope holds foundational HR data such as cases, tasks and profiles, distinguishing it from scoped applications like HR Service Delivery Advanced, which use separate scopes.

The source field identifies which incoming record attribute supplies the value being transformed, so the mapping knows what data to read from the raw activity. It satisfies the stem by being one of the three standard mapping components, alongside the target field and transformation logic.

HR Criteria build condition-based filters that evaluate user attributes such as location, employment type or department. HR services and templates consume these criteria to determine applicability, making reusable filtering their primary function rather than case routing or approval.

Employment Start Date is a standard HR Profile field because it records when the employee's tenure with the organisation begins. This satisfies the stem's requirement for standard HR Profile information, as opposed to IT-specific attributes such as device assignments or software licences, which belong to other record types.

Access Control lists (ACLs) are the platform's native mechanism for row-level and field-level authorization. A read ACL on the HR Case table with a condition such as opened_by equals the session user restricts any query to only the records the user owns, applies consistently across list views, reports, portal widgets, and APIs, and is reusable without per-case-type scripting.

Employee Center provides the standard self-service interface where employees raise requests, track cases, and access HR knowledge articles. It satisfies the stem's requirement for a single, unified portal for HR interactions, unlike the backend ServiceNow platform interface or agent-facing workspaces used by HR staff.

Column-level encryption protects sensitive HR fields such as salary or national insurance numbers at rest, so even database-level access reveals only ciphertext. This directly satisfies the stem's requirement to secure HR data within the instance, complementing access controls with cryptographic protection.

User Criteria define which users or groups may read, write or cannot access a Knowledge Base, evaluated against user attributes and roles. This satisfies the requirement to control visibility, restricting each knowledge base to its intended audience rather than exposing it to all portal users.

The Record Producer's own HR Service field is empty, so the value never populates onto the created case. Record Producers map their field values directly onto the target record; when that mapping source is blank, the case inherits nothing. This satisfies the scenario's constraint that only one specific producer is affected.

HR criteria allow the system to evaluate employee attributes such as country and automatically select the appropriate HR service and assignment group. By matching on the employee's country, the case will be routed to the UK payroll team and use the UK payroll service, meeting the requirement precisely.

Social Security Number is a government-issued identifier that uniquely identifies an individual, so it falls within Sensitive HR Data categories. The stem asks for three such categories, and SSN qualifies because exposure enables identity theft and requires restricted handling.

The Help text field on the Record Producer variable definition stores the custom guidance shown to the user beside that variable. Populating it satisfies the stem's requirement, as this field is the native mechanism for per-variable help text.

Activity Field Mappings bind activity fields to HR Case fields, so the welcome email's recipient name is pulled dynamically from the case record. This satisfies the requirement to populate activity content automatically without hard-coding values or writing custom scripts.

Field-level ACLs evaluate specifically against the field being read, so a read ACL on the compensation fields that requires a privileged HR role will block employees from seeing salary and bonus while leaving other fields on the same HR Profile record readable. This is the most direct, declarative way to protect individual sensitive fields without hiding the entire record.

The Delegated Developer role grants scoped application development rights without requiring global admin, letting developers build and manage their own scoped apps. It satisfies the stem's requirement by enabling scoped application management without elevated global privileges.

Immediate triggers run the activity set automatically the moment the record is created, whereas Manual requires a user or agent to launch it explicitly. This distinction satisfies the scenario's need to differentiate automatic execution from on-demand initiation.

ACLs are the platform's core authorization mechanism and evaluate on the server for every read and write. In HR Service Delivery they can restrict which HR cases, HR profiles, and specific fields a user can access, applying consistently across the UI, portals, and APIs. This makes ACLs a native and direct component of an HR data protection strategy.

The 'Order' field on each Activity Set defines its execution sequence within a lifecycle event, so the system triggers activity sets in ascending numeric order. This directly satisfies the stem's requirement for deterministic sequencing across multiple activity sets, rather than relying on creation date or alphabetical naming.

The My Cases widget on the Employee Center portal lists cases the signed-in user has submitted, giving direct visibility of their own open and closed requests. This satisfies the stem's requirement to locate submitted cases without navigating to the full case list, which shows records beyond the user's own.

The HR Profile record is the central HRSD data model record that stores employee-specific HR information such as hire date, termination date, HR department, and other HR attributes. It is linked to the user record but is separate, so HR data is kept distinct from platform user data. This record is used throughout HRSD for case creation, HR criteria evaluation, and reporting.

The HR Profile extends the user record with HR-specific data such as employee number, hire date and job details, keeping sensitive HR information separate from the standard user profile. This matches the stem's stated purpose.

HR ACLs are user-defined access control lists that restrict record-level access, so only the assigned HR agent holds write permission on that case. They enforce the assignment constraint directly at the record level, unlike role-based or table-level controls.

HR criteria records are stored in the `sn_hr_core_criteria` table, which holds the conditions defining which employees belong to a given HR profile or case. This satisfies the stem's requirement for the criteria storage table, distinguishing it from profile and case tables such as `sn_hr_core_profile`.

The Send Email activity type is specifically designed to send an email to a specified recipient. It supports using field values from the HR profile or other related records, so it can dynamically populate the personal email address. This activity can be placed at the beginning of the activity set to ensure it executes first, making it the correct choice for sending a welcome email immediately.

sn_hr_core.case_writer is an HR-scoped role granting write access to HR cases, letting HR agents create and update case records. It satisfies the stem's requirement for genuine HR Scoped Roles, as its sn_hr_core prefix confines it to the HR application scope.

HR Task is a lifecycle-generated to-do assigned to a human, such as collecting a signed policy or completing onboarding paperwork. It satisfies the stem because lifecycle events spawn actionable work items distinct from automated provisioning, approvals or signature requests.

Mapping the variable to the Department field on the Record Producer's Map to field tab writes the employee_department value directly into the HR Case Department column on submission. Mapping to a variable set or description would not populate that specific field.

An HR Task creates an actionable item assigned to the employee, with a due date and completion tracking, which suits policy review and signature. Activity sets and lifecycle events orchestrate; they do not capture individual acknowledgement.

Scripts define HR Criteria audiences through the ServiceNow HR Criteria engine, which evaluates server-side JavaScript against user and HR profile attributes. This satisfies the stem's requirement for a supported audience-definition method, unlike static groups or manual lists, because the script returns a true/false condition that dynamically determines membership.

HR Security Profiles assigned to a user are viewed through the HR Profile record itself, not the user record. Opening HR Profile → [User Name] → Security Profiles lists every profile granted to that individual, satisfying the stem's requirement to see assignments for a specific user.

HR Criteria define the audience conditions that determine which employees see a catalog item, satisfying the targeting requirement for HR Catalog Items. Without criteria, the item cannot be scoped to specific employee groups, so it is a mandatory component alongside the catalog item itself.

HR policy articles are stored in kb_knowledge, the base knowledge table, distinguished by knowledge base and category rather than a separate HR-specific table. This satisfies the stem because HR knowledge reuses the standard knowledge architecture.