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

HR Task Templates define the set of tasks generated when a case for a specific HR service is created. By attaching a template to the tuition reimbursement service, the system automatically creates the manager approval and payment processing tasks, ensuring consistent execution and reducing manual effort.

The Date trigger fires an activity set when a specified date field on the HR Case reaches its configured offset, satisfying the requirement to act on the form's date value rather than on record creation or field change events.

An Approval Definition must be referenced, since the activity needs to know which approval records to generate and route. Specifying it satisfies the required setting, linking the activity to the configured approval logic rather than leaving it unresolved.

This is true. The encryption context is a configuration that specifies the fields to encrypt and the roles that are allowed to decrypt. It can be scoped to specific fields, allowing granular control over which data is encrypted and who can access it. This is essential for compliance with data protection regulations.

A read ACL on the 'Notes' field can include a condition that checks the case's confidentiality status. If the case is marked 'Confidential', the ACL denies read access to the field for HR agents. This directly prevents agents from viewing the notes in confidential cases while allowing access in non-confidential ones. Field-level ACLs are ideal for this granular control.

The HR service record includes a case creation setting that determines whether a case is generated automatically upon submission, and an assignment group field that routes the case to the correct team. Configuring both ensures the offboarding request creates a case and assigns it to HR operations without manual intervention.

Assignment group controls which group owns and can view a case, so restricting visibility to the HR Benefits group is achieved by setting that field to HR Benefits. It directly enforces the record-level access constraint stated in the scenario.

The Journey Designer provides a graphical view of the Lifecycle Event and its activities. For an in-progress event, you can open a specific activity instance and update its 'Assigned to' field, which reassigns that task without affecting the template. This is the correct way to handle ad-hoc reassignments for a single case.

The sn_hr_core.reader role grants read access to HR case records and related data, which an HR Agent needs to view employee cases and profiles. Combined with a write role, it satisfies the two-role requirement for performing day-to-day HR Agent duties.

The sequence in which activities are listed in an Activity Set dictates their execution order. Activities are processed sequentially, and this order determines when each activity starts relative to others. This is a fundamental factor in timing, especially when combined with 'Wait for completion' settings. It directly influences when an activity is triggered within the set.

Data Classification applies classification tags to fields, letting administrators mark sensitive HR data such as salary or personal details for protection. It satisfies the scenario's requirement for a feature that identifies sensitive HR data fields.

ACLs are the standard ServiceNow mechanism for enforcing record-level security. By creating an ACL on the HR case table that checks if the case's opened_for or employee field matches the logged-in user, you can ensure employees only see their own cases. This is the correct and secure way to enforce this requirement in the HR Service Portal.

The Localization/Internationalization framework stores translated labels and content against language records, so HR Services display in each user's locale. It satisfies the global-audience constraint by resolving text at runtime per user language preference, rather than duplicating services per region.

HR Assignment Rules hold the routing logic that determines case ownership, so location-based assignment is configured there. They evaluate case fields such as the employee's location and direct the case to the appropriate assignment group automatically.

The HR Service record specifies the default HR Template, so case creation inherits field values from the template linked to that service. This satisfies the inheritance requirement by tying template selection to the service the employee selects.

HR Criteria are condition sets evaluated against a user's HR profile to determine which knowledge articles that user can access. Assigning criteria to knowledge articles restricts visibility by department, location or employment type, satisfying the requirement that HR Criteria control knowledge article availability.

An Activity Set groups the individual HR tasks that make up a lifecycle event, acting as their container. Each task sits within the set, which governs ordering and assignment, so the Activity Set is the parent object that holds and organises the discrete tasks.

HR Criteria evaluate fields on the HR Profile, such as work location, to determine eligibility for HR services and routing rules. In this scenario, criteria based on the employee's work location can automatically direct cases to the appropriate regional team, ensuring inquiries reach the correct agents without manual triage.

Adding HR_Auditors to the existing ACL's roles list grants that group the same Read access without creating a duplicate ACL. This satisfies the access requirement while preserving a single, maintainable rule for the HR table.

Lifecycle Events is a genuine HR Service Delivery component, orchestrating onboarding, offboarding and transitions by triggering tasks, cases and notifications across departments. It meets the stem's criterion of being a valid component of the application.

This is correct. HR criteria support advanced conditions where you can use OR to combine multiple conditions. By creating a single HR criterion with an advanced condition that checks if the user's department is 'HR' OR if the user has the 'hr_admin' role, you can accurately include all required users. This is the most efficient and maintainable approach.