SISHSD
Free SISHSD practice questions
10 questions from our SISHSD practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.
Question 1 of 10, HR System Architecture
A global customer wants HR cases for each country routed to agents who speak the employee's language and are certified for that country's labour rules, while balancing workload across eligible agents. Which design is MOST appropriate?
- AUse a business rule that queries agent records and sets Assigned to based on the subject person's country
- BConfigure HR skills on services and agents and use matching rules to pick an agent by skills and workload Correct answer
- CLet employees choose their preferred agent from a list on the Employee Center record producer form shown to them
- DCreate one assignment group per country and language pair and hard-code that group in every HR template
Answer and explanation: HR Service Delivery supports skills on services and agents plus matching rules that select agents based on criteria such as skills, location and current workload, so routing scales without custom code. Hard-coding groups per country and language in templates multiplies configuration and does not balance load inside a group. A custom business rule recreates base matching logic and is harder to maintain. Letting employees pick an agent ignores certification and workload requirements.
Question 2 of 10, HR System Architecture
A customer wants every new Benefits enrollment question from the portal to arrive with a preset short description, priority and assignment group. Where should the implementer configure these default values so they apply whenever that HR service is used?
- AIn a client script on the HR Agent Workspace form for benefits cases
- BIn the record producer script attached to the benefits catalog category
- CIn the HR template referenced by the HR service for benefits enrollment Correct answer
- DIn a business rule on sn_hr_core_case that checks the topic detail on insert
Answer and explanation: HR templates hold the field values that pre-populate a case when an HR service is used, so linking the template to the HR service applies them on every channel. A custom business rule would duplicate base functionality and increase upgrade risk. A record producer script only affects portal submissions, not cases created by agents. A workspace client script only runs when an agent opens the form, so the values would be missing on portal-created cases.
Question 3 of 10, HR System Architecture
An employee in Employee Center asks a question without knowing whether HR, IT or Facilities owns it. The customer wants an agent to triage the request and transfer it to the right department while keeping one record the employee can track. Which capability addresses this?
- AUniversal Request, which routes a primary ticket to department-specific cases Correct answer
- BLifecycle Events, which creates activity sets for each department involved
- CHR Agent Workspace playbooks, which guide agents through cross-team steps
- DInbound email actions, which classify replies into the right COE table automatically
Answer and explanation: Universal Request lets employees raise a request without picking a department; agents triage and transfer it while the employee keeps tracking a single primary ticket. Lifecycle Events coordinate planned transitions such as onboarding, not ad hoc triage. Inbound email actions process emails but do not provide cross-department transfer with a single tracking record. Playbooks guide agent steps inside one case rather than routing between departments.
Question 4 of 10, Core HR Applications and Employee Center
A company wants new hires to see a personalised onboarding plan with tasks spread over their first 90 days, with managers notified when their new hire's tasks are overdue. Which configuration BEST meets this?
- AA single HR case per hire with a long checklist the agent ticks off manually
- BA lifecycle event with date-based activity sets and reminders for overdue tasks Correct answer
- CA recurring scheduled report emailed to managers listing every open onboarding case
- DA knowledge article listing the 90-day plan that managers share with new hires
Answer and explanation: Lifecycle events support activity sets triggered relative to dates like the start date, create to-dos for the new hire and manager, and can send reminders when tasks are overdue. A manual checklist does not give the employee personalised to-dos. A static article cannot track completion. Scheduled reports provide visibility but no personalised plan or task-level reminders.
Question 5 of 10, Core HR Applications and Employee Center
After go-live, employees complain that searching 'payslip' in Employee Center returns IT articles first. Which change BEST improves relevance without restructuring content?
- ATune the search configuration and synonyms for the portal's search profile Correct answer
- BRemove IT articles from Employee Center so only HR content is searched
- CMove all HR articles into a single knowledge base named Payslips
- DRename every payroll article title so that it begins with the word payslip
Answer and explanation: Tuning the portal search configuration, such as synonyms, result improvement rules and search sources, improves relevance without moving content. Collapsing all HR articles into one base breaks existing organisation and access. Removing IT content defeats the multi-department portal. Renaming titles is a workaround that does not scale and harms readability.
Question 6 of 10, Core HR Applications and Employee Center
An Employee Center content manager wants the 'Parental leave' topic to show the leave policy article, the leave request record producer and a link to an external benefits provider. Which approach is correct?
- AAdd the items to a catalog category and set that category as the topic's parent
- BCreate a knowledge category named Parental leave and move all items into it
- CConnect each content item to the Parental leave topic in the employee taxonomy Correct answer
- DAdd each item as a widget on a custom page and link that page in the header menu
Answer and explanation: Employee Center organises content by connecting items such as articles, record producers and quick links to taxonomy topics, so the topic page shows them together. Building a custom page bypasses the taxonomy and adds maintenance. Knowledge categories only organise articles and cannot hold record producers or external links. Catalog categories organise catalog items, and taxonomy topics are not children of catalog categories.
Question 7 of 10, Core HR Applications and Employee Center
An HR knowledge manager wants agents to be able to turn a well-resolved case into a draft knowledge article for review. Which practice supports this in HR Case and Knowledge Management?
- AAgents publish the case to Employee Center so others can read its notes
- BAgents create a knowledge article from the case so it enters the review workflow Correct answer
- CAgents copy case details into an email and send them to the knowledge team
- DAgents attach the resolution to the HR template so that future cases reuse it
Answer and explanation: Creating knowledge from a case drafts an article that follows the knowledge base's review and publishing workflow, which supports knowledge-centred practices. Emailing details is manual and untracked. Adding resolution text to a template only pre-fills new cases and does not create searchable knowledge. Cases are never published to the portal for others to read because they contain personal data.
Question 8 of 10, Platform, Role, and Contextual Security
A field ACL protects the national ID field on the HR profile. A user passes the table-level read ACL but fails the field ACL. What does the user experience?
- AThe user receives an error and is logged out of the session
- BThe field is shown but the value is masked with asterisks
- CThe record is visible but the protected field is not displayed Correct answer
- DThe whole HR profile record is hidden from the user's list view
Answer and explanation: Field ACLs are evaluated separately from table ACLs, so a user who can read the record but fails the field ACL sees the record without that field. Failing a field ACL does not hide the whole record; only the table ACL does that. ACL failures never log the user out. Masking is a feature of specific encryption or masking configurations, not of a failed read ACL, which simply hides the field.
Question 9 of 10, Platform, Role, and Contextual Security
An IT technician is assigned an HR task during onboarding to prepare equipment. The technician has no HR roles. What is the expected behaviour of HR security?
- AThe technician sees the full parent HR case including the employee's HR profile
- BThe task is reassigned to HR automatically because the technician lacks any HR role
- CThe technician can work the assigned task without seeing any other HR case Correct answer
- DThe technician cannot open the task until an admin grants sn_hr_core.case_writer
Answer and explanation: Contextual security lets users assigned to an HR task access that task based on their relationship to it without broad HR roles, so sensitive cases and profiles stay protected. Granting case_writer would expose all HR cases unnecessarily. Being assigned a task does not reveal the full parent case and profile. There is no base behaviour that reassigns tasks because of missing roles.
Question 10 of 10, Platform, Role, and Contextual Security
Production is cloned to a development instance every quarter. The security team insists that real employee HR data must never land in non-production. Which approach BEST meets this?
- AClone everything and then instruct developers never to open HR records in the dev instance
- BUse clone exclusions or data preservers for HR tables plus synthetic test data Correct answer
- CRun a post-clone script that changes HR case short descriptions to placeholders
- DRestrict the dev instance with IP allowlisting so only HR staff can access it
Answer and explanation: Excluding HR tables from clones, or scrubbing them with data privacy techniques, keeps employee data out of non-production while synthetic data supports testing. Relying on developer discipline does not meet the requirement. IP allowlisting limits who logs in but still copies the data. Changing only short descriptions leaves profiles, attachments and other sensitive fields intact.