Question Q-8546 A company wants employees to acknowledge receipt of the annual…
2 comments · last active Jun 5, 2026
ServiceNow CIS-HR - HR Service Delivery Implementation - Employee Center Onboarding Lifecycle Events
By Marcus Chen · Updated Jul 10, 2026
| Questions | 25 |
| Passing Score | 75% |
| Format | 100% Multiple Choice |
| Sessions Logged | 694 |
| Your progress | Log in / Register to track times taken, best score, questions mastered, and coverage on this quiz. |
| Rating |
Topics covered
Uncategorized25 questions
Discussion
Log in to post a comment, reply, or expand a question.
Employee Center SSO = SAML to Okta for browser. HR bot API = OAuth 2.0 Application Registry client credentials — two auth patterns.
Don't reuse employee SAML token for machine-to-machine bot — separate OAuth app.
Integration security questions are easy points if you separate human SSO vs API OAuth.
PIP active on employee → before BR on hr_case flags case + notifies HR Director when subject employee has open PIP.
Reactive manager email after case created is too late — automation on insert is the answer.
Employee Relations confidential cases: Confidential HR Service + restricted COE + HR confidentiality settings — not public catalog queue.
Managers shouldn't see ER cases even if they can see Benefits — service-level ACL separation.
Relocation stipend: sequential approvals HR → Manager → Finance in hr_case flow — all must approve before advance.
Parallel UI Action buttons lack audit trail vs workflow/flow approval records.
Investigation cases: field-level restrictions, disable export/print for Investigation HR Service, strict COE ACLs — confidentiality beyond normal HR case.
UI hide alone fails audit — need platform-level field access control.
Workday changes → IntegrationHub Workday Spoke or REST/SOAP scheduled flow polling deltas → triggers HR Lifecycle Events.
Nightly CSV import can work but spoke/API is the real-time HRSD pattern in implementations.
Employee Center + HR Knowledge + Virtual Agent HR topics = self-service before hr_case. Classic Service Portal isn't Employee Center.
VA deflects password/policy questions; KB handles static policy content.
HR Leave case type + manager approval + balance integration — not generic incident with PTO in description.
Approval triggers notification and balance update on hr_case fulfillment flow.
Onboarding = HR Lifecycle Events with Activity Sets per department (IT, Facilities, Payroll) and sequencing — not one giant catalog item.
+2 votesActivity Sets group tasks by owning team with dependencies — critical for multi-department new hire.
Offboarding Lifecycle Event triggered from separation date in HR system of record — Activity Sets for IT access revoke, badge, equipment return.
Manual checklist email day-of is how outages happen — lifecycle event enforces dependencies.
Employee Center Audience targeting: managers see manager tiles, contractors see limited catalog — content targeting by user attributes.
+2 votesDuplicate portals per employee type is unmaintainable — audiences scale.
Question catalog for this preview
Catalog listing of the 5 preview questions for this quiz.
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?
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?
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?
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?
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?
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.
Policy acknowledgment: Document Acknowledgment tasks via Employee Center + completion dashboard + auto reminders.
Email blast with read receipt doesn't prove completion in platform audit.