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

HR skills are stored on the user record's Skills related list, so assignment happens through the agent's User Profile rather than the HR Profile or group membership. This directly satisfies the stem's question of how skills reach an agent.

Job details sit in the HR Profile because it stores employment-specific data such as position, department and employment type. This satisfies the stem by identifying one of the three profile information categories, distinct from personal and work contact details.

Task Templates populate fields on child tasks automatically, satisfying the requirement to standardise data entry across related HR cases. When a parent task spawns child tasks, inherited values flow into mapped fields, eliminating manual re-entry and reducing inconsistency. This mechanism differs from workflow routing or approval logic, which govern task progression rather than field-level data propagation.

HR ACLs apply record-level rules that restrict read access to cases matching the Benefits HR Service, limiting visibility to the HR Benefits group. This satisfies the stem's constraint that only that group can read those sensitive cases.

Access Control Lists on the sn_hr_core_case table governing the work_notes field restrict read access to internal roles, hiding work notes from the employee portal. This satisfies the stem's requirement by enforcing field-level security on the correct table and field.

This is correct because ACLs are the platform's standard mechanism for controlling record-level access. By creating a read ACL on the HR Case table that requires the 'sn_hr_core.case_reader' role, only users with that role (i.e., members of the HR Case Viewers group) will be able to read HR case records. This directly enforces the requirement without affecting other tables.

ACLs on the medical records table or fields enforce role-based access at the database layer, restricting reads to the HR Benefits role. The broader case_reader role cannot bypass ACL checks, giving precise field-level protection beyond UI policies or views.

Scoped Application ACLs restrict record access at the application boundary, so the HR Scoped App's tables stay invisible to users lacking HR roles. This satisfies the stem's requirement to hide tables from non-HR users, since ACLs evaluate the caller's roles before granting read access to any scoped table.

Record Producers render variables, not table columns, so adding a variable places the new input field on the producer's form. The variable then maps to the HR case field during submission, satisfying the requirement to extend the producer's data capture.

Platform Encryption allows field-level encryption at rest using keys managed in the Key Management Framework. Access to decrypt is controlled by roles that have permission to use the key. This meets the requirement for encrypted fields and role-based decryption without custom code.

The HR Service definition links to HR Criteria, which determines visibility control by matching user attributes. This linkage enforces data security, ensuring only users meeting the criteria can view records tied to that HR service.

The HR case form can be customized to include fields from related records, such as the employee's HR profile. By adding the job title, department, and manager fields to the form layout, the HR agent can view this information directly on the case. This is the standard way to display related data on a form without navigating away.

Using relative due dates based on the employee's last day ensures that any change to that date automatically recalculates the due dates of all activities. This is the intended design for dynamic scheduling in Lifecycle Events. It provides flexibility and reduces manual updates. The offsets define how many days before or after the last day the activity is due.

Enabling 'Enforce HR Security' on a table triggers HR Security Profile evaluation, applying profile-based read, write and query rules to that table's records. This satisfies the stem's requirement by activating profile evaluation rather than merely assigning roles.

A delete ACL on the HR case table (sn_hr_core_case) that requires the HR administrator role will restrict delete operations to users with that role. This is the standard way to control record deletion in ServiceNow. By specifying the role in the ACL condition, only HR administrators can delete HR cases, meeting the requirement precisely.

HR Services define the categories of HR requests, such as payroll or benefits, and carry configuration like templates and criteria. They connect employees to the appropriate case handling and routing. As a standard architectural component, the HR Service is central to how requests are structured and processed, making it a required element in the data model design.

The Assignment Group field determines which department's queue receives the HR case, driving routing and ownership. Populating it satisfies the requirement that cases reach the correct department, since assignment rules and group membership then notify the appropriate agents.

ACLs evaluate group membership against the record, restricting read access to Payroll members only. This satisfies the stem's requirement to limit sensitive HR case visibility by group, which a simple role or assignment rule cannot enforce at field level.

Conditions in Lifecycle Event activities can indeed reference fields from the HR profile of the employee for whom the event is triggered. This allows for dynamic behavior based on employee data, such as location, department, or job level. For example, you can create a condition that checks if the employee's location is 'New York' to trigger a specific activity. This is a fundamental capability of the condition builder.

The sn_hr_core.case_writer role grants write access to the HR case table, letting the holder open new cases and modify existing ones. It satisfies the stem's requirement to both create and update, without granting the broader configuration rights reserved for case_admin or HR admin roles.

Assignment rules evaluate the skills held by HR agents and match them against the skills required on an HR case, routing work to appropriately qualified staff. This satisfies the scenario's routing constraint directly: skills act as a routing criterion within assignment rules, ensuring cases reach agents whose skill profiles fit the case requirements.

The sn_hr_core.admin role grants full configuration rights over HR Services and HR Criteria. It satisfies the stem's management requirement, unlike scoped admin or case-only roles that lack authority to create or modify these HR configuration records.

Contextual security evaluates record attributes against the user's context at query time, so a department filter on HR case records dynamically restricts visibility to only those cases matching the user's own department. This satisfies the stem's requirement for dynamic, attribute-based restriction rather than static role-based access.

Lifecycle Events automate joiner, mover and leaver tasks across connected systems, removing repetitive manual provisioning and deprovisioning. This directly reduces administrative effort and error rates, delivering the operational efficiency the question identifies as a common benefit.

Topic detail refines the topic by defining the specific category an HR service belongs to, and it is a mandatory field on the HR service record. Configuration fails validation unless a topic detail is selected alongside the parent topic.

Activity Field Mappings define how HR Case values populate generated task fields, satisfying the requirement to carry a custom field across to the task record. Configured on the HR service, these mappings specify the source case field and target task field, so the custom value transfers automatically when the task is created.

Audience segments lifecycle event recipients by attributes such as role, department, or location, so each group receives content relevant to them. This satisfies the stem's personalisation benefit, delivering tailored experiences rather than identical messages to all users.

The HR Service is the record defining the case type, its fields and associated workflows; it drives which routing logic applies when a case is created, anchoring the lifecycle routing process alongside assignment rules and groups.

HR Profile is a primary component of the HR Service Delivery architecture, storing employee data that drives case routing, approvals and service catalogue personalisation. It satisfies the stem's requirement by acting as the foundational record linking HR services to individual employees, enabling scoped access and automated workflows across the HR Service Delivery application.

Mapping cases to services by Category is configured through HR Administration > HR Services, where each service record defines the Category value it responds to. This path satisfies the requirement to route Employee Center cases to the correct HR service automatically.

A Trigger Condition on the Activity Set record, built with the Condition builder, evaluates the new hire's Location and Department fields and fires the Activity Set only when both equal New York and Engineering. This enforces the stem's compound requirement.

Encrypted field values are stored as ciphertext, so the database cannot match plaintext query strings against them. Platform search therefore returns no results for those fields, satisfying the stem's constraint that searching encrypted data is unsupported.

The HR Profile table in HR Service Delivery is sn_hr_core_profile, which stores the core employee HR record linked to a user. It satisfies the stem's requirement by being the dedicated table holding HR Profile data, distinguishing it from case, task, or lifecycle event tables that reference it.

HR Criteria are condition sets evaluated against the user's profile and HR profile, and they gate catalogue item visibility. This satisfies the stem's requirement by controlling which users see a specific HR catalog item, rather than user criteria or catalogue permissions alone.

ACLs enforce role-based restrictions at the record and field level, so only holders of sn_hr_core.admin can write to HR Services definitions. This satisfies the stem's requirement that the role restriction be enforced during service definition, which UI policies or business rules alone cannot guarantee.

The HR profile table stores employee-specific HR data and is the correct place to add custom fields like hire date or compensation grade. It is referenced by HR criteria, so extending it makes those attributes available for routing decisions. Each employee has one HR profile record linked to their user record, making it the central data source for HR attributes.

The Activity Set field associates an Activity Definition with a specific activity set, grouping related activities so they can be assigned and tracked together. This linkage determines which set the activity belongs to during lifecycle processing.

The 'Quick Links' widget queries the sn_ex_sp_quick_link table, which stores the link records configured for the Employee Center portal. This satisfies the stem's requirement that the widget sources its data from a dedicated ServiceNow table rather than from a static UI page or hard-coded markup.

Data encryption renders HR records unreadable without the correct decryption key, satisfying the requirement to prevent leakage even if files are copied, intercepted or stolen. It protects data at rest and in transit, so exposure of the underlying storage or network does not disclose salaries, health details or personal identifiers.

HR Criteria evaluate user attributes to determine which catalog items a user is eligible to see or request. Applied to HR Catalog items, they define audience eligibility, matching the stem's stated function rather than controlling pricing, fulfilment or approval routing.

ACLs define which users or groups may read, write or delete specific records and fields, so they are the first place to inspect when HR data appears in IT-visible reports. Checking ACLs reveals whether overly permissive read rules on HR tables are exposing records beyond the intended HR audience.

The HR Case table records employee enquiries and their resolution, storing each request's details, status and assigned agent. It satisfies the stem's requirement to define the table's function by acting as the central repository for HR service interactions, distinct from tables holding employee records or knowledge articles.

Roles are a supported HR criteria type, letting service visibility be restricted to users holding specified roles. Selecting Roles satisfies the stem's requirement, as HR criteria combine role-based and condition-based rules to determine who sees a service.

The sn_hr_core.admin role grants full write access to HR criteria records, satisfying the requirement to manage them. Unlike sn_hr_core.manager or sn_hr_core.case_writer, which permit only case and profile actions, this role carries the elevated configuration privileges needed for criteria table administration. Microsoft Entra ID plays no part here; authorisation is enforced natively within ServiceNow.

Automatic case creation for new hires is typically achieved through a Business Rule or Flow that triggers on the creation of a user or HR Profile. The flow would use the HR Service to create the case. This is the most reliable method to ensure cases are generated for each new hire.

Assignment rules evaluate conditions on the HR case and route it to the appropriate assignment group or agent. They directly determine which group receives the case, satisfying the routing factor requirement alongside topic detail and HR service definition.

Location is one of the user-profile attributes evaluated when HR Criteria run, so a service or task can be restricted to employees at particular sites. This satisfies the visibility requirement by matching the user's location field.

Task Subject appears in the 'My Tasks' widget for an active Journey, giving the employee a concise label identifying each assigned action. It satisfies the stem's requirement by naming one of the three displayed fields, alongside due date and Journey context.

The 'My Cases' widget filters on the case's Opened for or Subject person field matching the logged-in user. If that field references someone else, the case will not appear, making this the first thing to verify.

To enforce the tenure requirement, the HR Criteria must include a condition on the employee's start date, such as 'Employment start date before [one year ago]'. This ensures only employees with more than one year of service qualify.

HR Services are published catalogue items in Employee Center that surface HR information and requests to employees, such as policies, forms and case creation. They satisfy the requirement by delivering HR content directly through the portal's topic and service structure.

Before Query Business Rules execute before the query runs and can add or remove encoded query conditions, silently widening result sets beyond ACL restrictions. With ACLs verified intact, such a rule is the likely cause of unauthorised users reading HR Profile records, satisfying the stem's exposure scenario.

A Record Producer is the catalog item that allows employees to submit an HR case. It defines the form fields and the target table (HR Case). Linking a Record Producer to the HR Service enables employees to create cases for that service from the Employee Center. Without it, there is no submission mechanism.

The Execution Order field sequences activities within a set, determining which runs first when a set contains multiple activities. This satisfies the stem's requirement by defining precedence among activities inside a single set, not across workflows or stages. It governs intra-set ordering only, so activities execute in the specified numeric sequence.

Activity status indicators appear on the Lifecycle Event case form, showing progress of each activity within the event. They are one of the three required items, distinct from unrelated fields such as case priority or assignment group.

ACLs enforce record-level read, write and delete permissions directly on HR tables, so access is restricted to the specific employees, groups or roles named. This satisfies the stem's requirement to secure sensitive HR data at the data layer, independent of any UI or form-level restriction.

Lifecycle Events cannot cascade: a single event, such as a joiner or leaver transition, cannot itself trigger a further Lifecycle Event. This satisfies the stem's constraint that only one event fires per identity state change, so chained or nested event execution is unsupported in Microsoft Entra ID.

Lifecycle Events orchestrate complex, multi-step HR processes such as onboarding or offboarding, coordinating provisioning tasks across Microsoft Entra ID and connected systems. This satisfies the stem's requirement for handling intricate workflows that simple joiner-mover-leaver rules cannot manage, enabling event-driven automation triggered by authoritative HR source changes.

Flow Designer builds the approval directly into the HR Service workflow, letting HR admins add approval actions without scripting. This satisfies the stem's efficiency constraint by defining the approval in one place, rather than splitting logic across separate workflow or business rule records.

Performance Analytics collects indicator data over time, giving trend dashboards and breakdowns of HR processes such as case volumes and resolution times. It satisfies the monitoring requirement by providing historical, aggregated insight rather than real-time transaction-level diagnostics.

Selecting 'Wait for completion' makes the activity set halt at that activity and resume only once the activity reaches a finished state. This enforces sequential execution, satisfying the requirement that the set pauses until the preceding activity completes before proceeding.

To link an HR case to multiple employees, a many-to-many relationship is needed because a case can involve multiple employees and an employee can be involved in multiple cases. A custom table that stores case-to-profile associations allows this flexibility and can include additional attributes about the relationship, such as the role of each employee on the case.

Taxonomy governs how Employee Center content is categorised and organised, letting administrators structure topics and subtopics that surface HR information. It is one of the two administration areas, controlling the navigational hierarchy users browse rather than the portal's visual layout or widgets.

Domain separation in the HR Service Delivery data model creates distinct domains for Germany and the United States, and HR agents assigned to a domain can only access records within that domain. This satisfies the requirement to use identical HR services and forms while enforcing country-specific visibility of HR cases and HR profiles. It is the standard architecture for multi-country HRSD implementations.

Lifecycle Events include a trigger condition that determines when the event should be initiated. By configuring a trigger condition that checks the termination date field on the HR profile, the system automatically creates the Lifecycle Event case when that condition is met. This is the declarative, native method for initiating Lifecycle Events based on record changes, ensuring proper orchestration and case creation.

e-Signature is a discrete HR task type that routes a document to a subject person for signing within an HR case or lifecycle event, satisfying the stem's requirement for a task category alongside Approval and Upload Document.

HR Criteria Diagnostics evaluates the criteria attached to an HR service and reports why a given user does or does not match, exposing the failing condition. That directly answers why the service is not appearing for that specific user.

HR Case ACLs control record-level read, write and create access, so restricting them to the HR Tier 1 group limits visibility to those members only. This satisfies the constraint that sensitive cases be viewable solely by that group.

A Record Producer can be attached to an HR Service so that the producer's catalogue item generates the correct case type with mapped variables. This link satisfies the requirement by connecting the request intake form to the service definition.

Activity Definition configurations reside under Lifecycle Event Administration > Activities, where each activity's trigger, target population, and associated lifecycle event are defined. This module satisfies the stem by housing the configuration objects that drive lifecycle processing.

Widgets are configurable components placed on HR Service Portal pages, so they form part of the portal configuration. They render content and functionality within the portal layout, satisfying the stem's request for a portal configuration feature.

Activity Sets bundle multiple activities, such as tasks and approvals, into a reusable collection executed together when a defined trigger fires. This satisfies the stem's requirement for grouping several activities under a single triggering condition.

HR Criteria act as a user-based filter controlling whether a service is visible in the Employee Center. If the criteria conditions are unmet, the service is hidden from that user, explaining the absence during testing. This directly satisfies the stem's visibility constraint, unlike publishing or catalogue issues.

The `sn_hr_core_case` table is the base class from which every HR case type inherits, including HR service cases, lifecycle events and employee relations cases. This inheritance hierarchy satisfies the stem's requirement for a single parent entity, since child tables extend it rather than defining separate roots.

The Condition Builder on the HR case list allows the agent to construct a filter using fields such as Assignment group, Active, and Due date to return exactly the open, overdue cases for their group. This is the standard, efficient way to filter records in the HR case list and produce a focused work queue.