Text preview & study summary

ServiceNow CIS-HR - HR Service Delivery Implementation - Employee Center Onboarding Lifecycle Events

A free sample of 5 questions from this quiz, shown in full with answer choices and explanations. No interactivity — everything is visible on this page for study and review.

Want to test your knowledge? Launch the Interactive Exam Simulator

Question 1

During an HR Service Delivery implementation, the client wants to track HR metrics including: case volume by HR Service, average case resolution time per COE, and employee self-service utilization rate. Which reporting approach is BEST?

Answer choices

  • A. Export case data to Excel monthly and calculate metrics manually

  • B. Configure ServiceNow Dashboards with HR-specific reports, and use Performance Analytics indicators to track trends over time with targets for each metric (Correct)

  • C. Use system logs to extract performance data

  • D. Schedule weekly email reports of case list exports

Explanation

ServiceNow HR Service Delivery includes pre-built HR reports and dashboard templates. The recommended approach: (1) HR Case Volume by Service — Report showing case count grouped by HR Service over selected time periods; (2) Resolution Time by COE — Average duration report grouped by assignment group/COE; (3) Self-Service Utilization — Knowledge Base view-to-case ratio (deflection rate), Portal vs. phone/email case creation source tracking; (4) Performance Analytics — trend indicators with targets (e.g., target: 80% of cases resolved within 5 business days). PA shows historical trends and burndown vs. targets. Manual Excel exports (option A) are not scalable and lose real-time visibility needed for managing SLA compliance.

Question 2

An HR implementation team is configuring the Employee Center portal. They want the portal to show different content and quick links based on whether the employee is a full-time employee, contractor, or manager. Which feature controls this personalization?

Answer choices

  • A. Create three separate Employee Center portals

  • B. Configure Audience segments in Employee Center and use content targeting to show different tiles, announcements, and quick links based on user attributes (employee type, is_manager) (Correct)

  • C. Use business rules to redirect users to different portal pages at login

  • D. Create custom roles for each employee type and configure three homepage layouts

Explanation

Employee Center (Next Experience) supports content personalization through Audience configuration: (1) Audiences are defined based on user attributes (employee type = contractor, manager = true, location = APAC); (2) Content blocks, tiles, announcements, and quick links in Employee Center can be targeted to specific audiences; (3) A contractor sees contractor-specific links (extend contract, submit timesheet) while a manager sees manager-specific tiles (approve time off, submit promotion request); (4) No login redirects or multiple portals required. Custom roles for homepage layouts (option D) is a legacy approach that doesn't provide the granular content targeting available in the modern Employee Center. Multiple portals (option A) create maintenance complexity.

Question 3

A company wants HR employees to be able to submit requests to update their personal information (address change, emergency contact, direct deposit) through Employee Center, with the changes routed to the appropriate HR team for verification and processing in their payroll system. What is the CORRECT catalog design?

Answer choices

  • A. Create one general "Update My Information" catalog item that goes to a generic HR inbox

  • B. Create specific HR catalog items for each change type (Address Change, Emergency Contact Update, Direct Deposit Change) with appropriate fields, routing to the correct HR COE, with integration actions to update the system of record upon approval (Correct)

  • C. Allow employees to directly edit their own user records in ServiceNow

  • D. Require employees to email HR with their changes attached to a PDF form

Explanation

Best practice for HR self-service data changes: (1) Specific catalog items for each change type — this allows different routing (Address → HR Records team, Direct Deposit → Payroll COE), different required fields, and different approval chains (Direct Deposit may require manager approval for fraud prevention); (2) Variable fields capture the new information; (3) Approval workflow routes to the correct COE; (4) IntegrationHub or spoke actions update the authoritative system of record (Workday, ADP, SAP HR) upon approval; (5) Confirmation notification to employee upon completion. Direct employee editing of user records (option C) bypasses HR oversight and can create compliance issues. Generic email (option D) is untracked and inefficient.

Question 4

A company wants employees to acknowledge receipt of the annual Employee Handbook and updated Code of Conduct. The system must track which employees have acknowledged and send reminders to those who haven't. Which ServiceNow HR feature handles this?

Answer choices

  • A. Mass email campaign to all employees with an email confirmation request

  • B. Document Acknowledgment — configure acknowledgment tasks pushed to all employees via Employee Center, with dashboard tracking of completion rates and automated reminders for non-responders (Correct)

  • C. Create an HR Case for each employee requesting acknowledgment

  • D. Post the documents to SharePoint and use web analytics for view tracking

Explanation

ServiceNow HR Document Acknowledgment is purpose-built for enterprise-wide compliance acknowledgments: (1) Documents are uploaded and configured as acknowledgment items; (2) Acknowledgment tasks are distributed to targeted employee populations (all employees, specific departments, new hires); (3) Employees access and acknowledge documents through Employee Center with a digital signature/confirmation; (4) Real-time dashboard shows completion percentage by department/location; (5) Automated reminder emails are sent on a schedule to employees who haven't completed acknowledgment; (6) Audit report for compliance purposes shows each employee's acknowledgment date and IP. Creating individual HR cases (option C) would generate thousands of records and is not scalable. Email campaigns (option A) have no binding acknowledgment tracking.

Question 5

An HR specialist needs to create a new type of HR case — "Relocation Assistance" — that doesn't currently exist in ServiceNow HRSD. This new case type needs specific fields (origin city, destination city, relocation budget) and should route to the HR Benefits team. What is the CORRECT implementation process?

Answer choices

  • A. Modify the generic hr_case table to add fields for all possible HR services

  • B. Create a new HR Service Configuration record for "Relocation Assistance," add specific custom fields to the hr_case table (with field names indicating the service), create a catalog item for employee submission, and configure routing to the Benefits group (Correct)

  • C. Create a completely new table unrelated to hr_case to track relocations

  • D. Use the existing Change Request table to track relocations

Explanation

Adding a new HR Service in ServiceNow HRSD involves: (1) Create a new HR Service record in HR Service Configuration with name, COE assignment (Benefits), and template; (2) Service-specific fields — add custom fields to hr_case (e.g., u_origin_city, u_destination_city, u_relocation_budget) using Field Descriptors or extending the hr_case table; (3) Create a Catalog Item in Employee Center with variables for the specific fields, mapped to hr_case fields on submission; (4) Configure fulfillment flow/workflow for the Relocation Assistance HR Service; (5) Routing rules assign to Benefits group. Adding all service-specific fields to a shared table (option A) creates a schema bloat problem. A separate table (option C) breaks the HRSD framework and reporting consistency.