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

The HR Profile record is stored in sn_hr_core_profile, so custom fields that must sync with external payroll belong on that table. Extending it preserves the profile's link to the employee record and keeps the integration mapping consistent.

Log redaction strips or masks PII fields before records are written or shared, limiting exposure across HR Service Delivery systems. It satisfies the data protection strategy's requirement to minimise sensitive data propagation, complementing access controls and retention policies rather than replacing them.

sn_hr_core_profile stores the HR profile record linking a user to their employment data, forming a core table in the HR Service Delivery data model. This satisfies the stem's requirement for a standard HR Service Delivery table.

Trigger Condition defines the event-driven logic that initiates an HR Lifecycle Event, such as a new hire or termination, satisfying the requirement for a configurable activation setting. It specifies the criteria the system evaluates to determine when the lifecycle event fires, making it one of the three settings found within the event configuration.

The `cmn_location` table stores physical location records, including address and geographic hierarchy, which HR Service Delivery references for HR locations. It satisfies the requirement to hold organisational location data, unlike `core_company` (legal entities) or `sys_user` (people). HR profiles and cases link to these location records for reporting and routing.

Activity Field Mappings are defined directly on the Activity Definition record, binding source fields to the activity's input or output fields. This is the configuration point the stem asks for, so creating mappings anywhere else, such as the Activity Set, would not associate them with the specific activity.

The Activity table (sn_hr_le_activity) stores all activities generated from Activity Sets for Lifecycle Events. Each activity record includes the assigned user, state, and link to the parent Lifecycle Event case. Querying this table with a filter on the Lifecycle Event case will show all activities and their statuses.

Employee Center provides a unified portal where employees see personalized HR cases, tasks, and announcements. Content can be targeted by audience using criteria such as department or location, so each employee sees relevant items without custom page development. This directly meets the need for a single personalized entry point that aggregates HR activity and communications.

Domain Separation partitions HR case data by domain, so users in one domain cannot view records belonging to another. This isolates sensitive HR case information between business units or regions, satisfying the stem's requirement for a recommended data-protection method.

An HR Task is a child record under an HR case that represents a discrete unit of work assigned to a fulfiller, such as gathering documentation. It exists to perform work as part of an HR case, not to define the case itself.

Defining data mapping and normalisation rules first establishes how legacy fields translate into the target schema, resolving format and value conflicts before loading. This satisfies the data integrity constraint by preventing duplicates and inconsistent records during migration.

Audience targeting allows HR administrators to define conditions based on user attributes, such as department, to control which content is displayed. By applying audience targeting to the Quick Links widget, different sets of links can be shown to employees in different departments without creating multiple portals. This is a scalable and maintainable solution that leverages the personalization capabilities of Employee Center.

HR Criteria allow you to define conditions based on user attributes, such as country, to determine which HR services, catalog items, or knowledge articles are visible to specific employees. By creating criteria that match the employee's country, the system can automatically filter and display only the relevant services, ensuring a personalized experience without manual intervention.

Transform Maps provide field-level coalescing and mapping between the import staging table and the HR Profile target, satisfying the requirement to load legacy HR data without duplicate profile creation. They let you define source-to-target field relationships and transform scripts, which is the documented mechanism for importing HR data into HR Profiles.

HR case types in HR Service Delivery can be based on dedicated tables that extend the base HR case table. This allows unique fields like expected due date and leave duration to be stored directly on the case record, keeping the data model clean and enabling type-specific reporting and form design for the parental leave process.

Restricted Caller Access records govern cross-scope access between applications in ServiceNow, satisfying the stem's requirement to define that function. They explicitly permit or deny one application's scripts from reaching another scope's resources, overriding default cross-scope privilege behaviour. This makes them the mechanism for managing inter-application access boundaries.

Associating the HR Template with the HR Service ensures the template is offered whenever that service is selected, so agents apply the correct structure. Linking templates elsewhere, such as to cases or users, breaks this automatic application.

The HR Profile record aggregates the employee's employment data, including position, department, job history and HR case relationships. Opening the profile gives an HR agent the consolidated employment history needed, rather than scattered case records.

The HR Service name is stored in the HR Service field on the case record, which directly satisfies the stem's requirement for locating where that value resides. This reference field links the case to its associated HR service definition, making it the authoritative location queried when reporting or routing on service name.

Access accumulates across every assigned HR Security Profile, so the union of permissions applies rather than a single winning profile. This satisfies the stem's multiple-assignment constraint: the system evaluates all profiles additively, granting the combined access level. No precedence or override logic reduces the result, so the highest privilege from any profile is included.

An ACL defines granular read and write permissions on individual records, so it directly grants the HR group 'Read' access to all HR case records. This satisfies the stem's requirement for record-level access, unlike role-based controls that govern broader module or table privileges rather than per-record permissions.

HR Profile consolidates employee data into a single view, surfacing benefits and payroll details directly to the HR agent without navigating separate modules. This satisfies the stem's "at a glance" constraint by aggregating the relevant records on one screen, rather than requiring the agent to query each source individually.

With Trigger set to Immediate, the activity set launches as soon as it is invoked. Containing no activities means there is nothing to execute, so the set transitions straight to completed without waiting or erroring.

A Manual trigger means the Activity Set does not fire automatically from lifecycle event conditions. Instead, an HR Agent starts it from the user interface, giving them control over when the contained tasks are generated and assigned.

HR Assignment Rules evaluate case attributes, such as the HR service or category selected, and route the case to the matching assignment group automatically. This satisfies the stem's requirement that Payroll cases be assigned without manual intervention, since the rule triggers on case creation rather than relying on agent triage.

The sn_hr_core.admin role grants the elevated privileges needed to create or modify HR Services, including their configuration and associated records. Standard HR agent roles lack this administrative access, so the stem's create-or-modify requirement is satisfied only by this role.

Activity field mapping can pull values from the HR case record, populating activity fields with case data such as employee, department or short description. This is one of the three true statements, since the mapping source may be the parent case rather than only the activity or event.

HR skills reside in the `cmn_skill` table, which holds the skill definitions referenced across ServiceNow, including HR Skill records used by HR Service Delivery. This satisfies the stem's requirement for the table storing HR Skills, distinguishing it from HR-specific profile or case tables.

HR criteria are defined once and referenced by multiple HR services, so the same rule set governs hiring, promotion and termination without duplication. This reusability across HR services is the defining property, letting administrators maintain consistent logic centrally rather than redefining criteria for each service.

Activity Type drives how the activity is generated when the flow executes, selecting the generation logic that produces the activity records. It does not control scheduling, assignment or conditions; those sit elsewhere in the activity definition. Choosing the correct type therefore determines the generation behaviour the scenario requires.

The hr_admin role carries the elevated privileges needed to create, edit and delete HR Criteria records. Standard employee or manager roles lack this administrative scope, so hr_admin is the role that grants the required access.

Date of Birth is a core HR Profile field because it stores employee-specific personal data on the HR profile record, distinct from IT-facing identity attributes. It satisfies the stem's requirement by belonging to the HR-managed data set, not the Microsoft Entra ID user object, so it qualifies among the three correct selections.

The user account identifies which person receives the Delegated Developer role, granting them elevated development rights within the HR scope. It is one of the two required factors, paired with the application scope that bounds where those rights apply.

Upload Document is the HR task type that presents a file-upload control to the fulfiller, letting them attach the required file to the task. It satisfies the stem's upload requirement directly, unlike standard form or approval tasks that cannot accept file attachments.

Field-level ACLs control access to a specific field independently of table-level ACLs. By creating a read ACL on the confidential notes field that requires the HR case manager role, only users with that role can read the field. Other HR agents who have table-level read access to HR cases will see the case but the field will be hidden. This is the standard approach for restricting sensitive fields.

The HR Profile record extends the User table with HR-specific fields such as employee number, hire date and job details, keeping that data separate from core platform user records. This satisfies the requirement to hold employee-specific data distinct from the User table.

The 'sn_hr_core_topic_category' table groups HR services into categories, enabling employees to browse the HR Service Portal by topic rather than searching individually. This satisfies the stem's requirement to organise HR Services, structuring catalogue content hierarchically so related services surface together under a single category node.

My HR Cases is a module filtered on the assigned-to field set to the logged-in user, so it lists only HR cases currently owned by that agent. This directly satisfies the stem's constraint of viewing cases assigned to you.

The Employee Center delivers a single, unified portal experience where staff access HR services, content and tasks from one destination, rather than navigating separate siloed applications. This satisfies the stem's requirement for a consolidated entry point for employee services across the organisation.

Column Level Encryption encrypts designated table columns at rest, so HR case data is unreadable in the database without the encryption key. This platform capability directly satisfies the at-rest encryption requirement, unlike transport-layer or application-level controls.

The 'Map to field' attribute on the variable binds it directly to the target case field, so Short Description populates automatically on submission. Configuring this in the Record Producer's Variables related list satisfies the mapping requirement without scripting.

HR Assignment Rules evaluate case attributes and route the case to the appropriate group or agent, satisfying the requirement to direct HR cases automatically. They determine assignment targets, unlike SLA definitions or notification rules, which govern timing and messaging rather than ownership.

The hr_case_writer role grants the ability to create and update HR cases. It provides write access to case records without the broader administrative privileges of other HR roles, fitting agents who handle case work directly.

With Wait for completion enabled, the next activity set cannot start until the current one finishes, so it remains pending. This satisfies the sequential ordering constraint by blocking downstream sets rather than running them in parallel.

ACLs are the standard ServiceNow mechanism to restrict record-level access based on conditions such as assignment group. By creating an ACL on the HR case table (sn_hr_core_case) with a condition that the assignment group matches the user's assignment group, you can ensure agents only see cases assigned to their group. This directly enforces the required restriction.

Taxonomy organises catalog items and knowledge articles into hierarchical categories and topics, grouping related content so users browse a structured Employee Center. This satisfies the stem's requirement to group related items and articles, whereas portals, topics alone or search configurations do not provide that hierarchical grouping.

A Restricted Caller Access record grants a scoped application permission to call into a table outside its own scope, such as global cmdb_ci. This satisfies cross-scope access without altering the HR role's scope or granting broad global privileges.

HR Service field mapping automatically propagates the updated Department value from the HR system of record to the user's identity profile when the Lifecycle Event fires, satisfying the requirement that the change be handled without manual intervention. This keeps the identity attribute synchronised with authoritative HR data throughout the promotion workflow.

Automatically routing cases to appropriate groups or agents is precisely the HR Case Assignment engine's core purpose, satisfying the stem's demand for its primary function. It evaluates case attributes against defined assignment rules, then dispatches each record to the correct resolver group or individual, eliminating manual triage and ensuring cases reach the right queue without human intervention.

Categories provide the taxonomy that classifies knowledge base articles, enabling HR agents to browse and filter content by topic. Without at least one category, articles cannot be organised or surfaced through the knowledge base interface, so this component satisfies the structural prerequisite the question demands.

An HR service defines the end-to-end process for a specific HR request. When an employee submits a catalog item linked to an HR service, the service configuration determines the case type, template, and other attributes, and the system creates an HR case. The HR service is the central component that maps the request to a case.

Activity Field Mappings pull values from the HR Case record, which stores the data the user entered on the Lifecycle Event case form. Mapping from HR Case therefore supplies the correct source object for those user-entered fields.

The HR Profile table is stored under the physical name sn_hr_core_profile, holding employee HR profile records used across HR Service Delivery. This satisfies the stem's requirement to identify the correct table name rather than a label or related table.

The Display field controls the human-readable label shown for the HR Criteria record in lists and references. It does not affect evaluation logic or the conditions themselves; it simply gives administrators a meaningful name when selecting criteria elsewhere.

An HR Task is the discrete unit of work generated within a Lifecycle Event, assigned to an individual to complete. It satisfies the stem's requirement for executing individual work items, since the Lifecycle Event itself orchestrates the sequence rather than performing each action.

HR Services define the case types offered, while Assignment Rules route each case to the correct regional HR group based on criteria such as location or country. Together they partition case management by region without duplicating the underlying data model.

The Subject Person tab holds the employee record linked to the HR case, displaying their profile, employment details and job information. This directly satisfies the stem's requirement for the affected employee's information, since the case's subject person field references the worker the case concerns.

Mapping the 'Assigned to' field to the employee's user record ensures the activity is assigned to that employee. In the HR portal, activities assigned to the logged-in user appear in their to-do list. This is the standard way to surface employee tasks. Without this mapping, the activity would not be routed to the employee.

The sn_hr_core_case table is the base table from which all HR Case types extend, making it the parent entity in the table hierarchy. Child case types inherit its fields and behaviour, satisfying the stem's requirement for a single parent for all HR Case types.

This is correct. ACLs are the platform's record-level security mechanism. By creating a read ACL on the HR Case table with a script condition that checks if the current user is the opener, the assigned to, or has the 'sn_hr_core.admin' role, you can enforce the requirement precisely. This ensures that only authorized users can view the case.

Field-level ACLs override table-level ACLs. By creating a read ACL on the employee_salary field that requires a more privileged role, the hr_agent will not have read access to that field even though they have table-level read access. This is the minimum configuration needed to hide the field. No other changes are required.

Activity Type on the Activity Definition specifies whether the generated activity behaves as an HR Task, an Approval, or a Signature, determining the resulting record type and its processing behaviour. This directly answers which field controls that classification.

Lifecycle Events extend the HR case record, so the base table must be sn_hr_le_case. Creating the record on this table makes it visible to the Lifecycle Event engine, satisfying the stem's requirement for engine availability.

HR Criteria drives record-level read ACLs, so a case outside the user's criteria is filtered from query results entirely. The portal therefore cannot distinguish 'no access' from 'no such record', returning 'Record not found' rather than an authorisation error.

Knowledge bases store the articles that answer HR questions, and Employee Center surfaces them through search and topic browsing. This satisfies the stem's requirement for a feature helping users find relevant HR information, since articles are indexed and returned by the portal's search.

The 'Active' boolean field directly controls whether an HR Security Profile is enabled or disabled, satisfying the stem's requirement for the setting that defines profile activity status. Toggling this field to true activates the profile; setting it false deactivates it, making it the precise configuration element governing the profile's operational state.

HR Criteria combine roles and conditions with AND logic, so a record qualifies only when the user holds the specified role *and* meets every configured condition. This satisfies the stem's requirement to use both together, narrowing matching precisely rather than broadening it as OR would.

Selecting an HR Service Type is mandatory because it determines the fulfilment path the platform applies when the service is requested. The type governs which workflow, approval routing and task generation logic activate, so the service cannot be saved without it. This directly satisfies the stem's requirement for creating a new HR Service.

User Criteria define which users or groups match conditions granting access to the HR Service Portal, controlling visibility at the portal level. This satisfies the scenario's requirement for the primary mechanism defining HR user access.

HR Service configuration is the correct location because the subflow trigger is bound to the service record itself, not to the catalogue item or workflow. The stem's constraint—triggering on creation of the HR Service—requires the subflow to be attached within the HR Service definition, where the creation event and its associated subflow are declared.

The sn_hr_core.admin role grants full configuration rights over HR Services, HR Templates and related HR structures. Case reader or case writer roles only permit working with cases, not managing the underlying service and template definitions.

Assignment routes the HR Case to the target group's queue, where it remains pending until an active agent becomes available to work it. This satisfies the stem's constraint: no active agents in the assigned group, so the case simply waits rather than being reassigned or closed.

Conditions form one of the three factors driving HR Case assignment logic: the criteria evaluated against the case and employee to select the appropriate assignment. They determine which assignment rule fires, alongside assignment group and skills.

Notification is a valid Lifecycle Event activity type, sending an email or alert to specified recipients as part of the event flow. It satisfies the stem's requirement for a genuine activity type, alongside HR Task and Approval, enabling automated communication at defined lifecycle stages.

The 'Wait for completion' option on an activity, including an HR task, ensures that the next activity in the Activity Set does not start until that task is completed. This directly addresses the scenario by blocking progression until the manager closes the task. It is the correct mechanism for sequencing within an Activity Set when a specific activity must finish first.