CCNA HR System Architecture Questions

Assignment logic such as default assignment group belongs on the HR Service record itself, since the service definition drives case creation behaviour. Defining the target HR group there ensures every case raised against that service is routed automatically, satisfying the stem's requirement without extra workflow configuration.

The sn_hr_core_profile table stores the HR Profile record itself, so mapping external payroll data here writes directly to the fields the HR Profile displays. This satisfies the stem's requirement that payroll data populate the HR Profile, rather than an intermediary staging or case table.

Employee Center is the standard self-service portal in HR Service Delivery that provides a unified experience across departments, including HR, IT, and Workplace. It allows employees to search knowledge, open HR cases, and access services from multiple departments in one place. This matches the requirement for a single interface for HR requests and knowledge.

An HR Profile Business Rule executes automatically when a user record is created, generating the linked HR Profile without manual intervention. Configuring this logic on the HR Profile table satisfies the requirement that profiles be created automatically upon user creation.

HR criteria define conditions on HR profile, case, or related fields; when matched, they drive template selection and routing. In this scenario, the team needs dynamic routing based on employee and case attributes, so HR criteria is the correct component. It evaluates conditions at case creation and applies the associated HR template, which can specify assignment group and other defaults.

HR Criteria can evaluate case attributes such as the topic or selected catalog item and determine the assignment group dynamically. This allows a single HR service to route payroll cases to Payroll and benefits cases to Benefits based on the criteria matched. It satisfies the requirement of conditional routing within one HR service definition.

HR criteria are conditions that determine which HR services are available to a user. By creating criteria that check the employee's legal entity (e.g., using the HR profile or user record), and applying those criteria to the relevant HR services, the administrator can ensure that employees only see services for their entity. This is the standard mechanism for controlling service visibility.

HR Case Management provides the central workspace where an HR administrator views, filters and manages every HR case across the organisation, regardless of assignment group. It satisfies the stem's requirement to see and manage all cases system-wide from one module.

HR Templates predefine the case structure, tasks and fields generated for a given HR request, ensuring consistent handling. It is a valid HR Service Delivery component, sitting alongside HR Services and HR Tasks in the ServiceNow HR application architecture.

Integration Hub provides reusable spokes and actions for outbound REST or SOAP calls to third-party providers. Using it satisfies the background check integration requirement, keeping external calls governed and separate from core case processing logic.

HR Criteria control which users can view a catalog item on the Employee Center by evaluating conditions such as department, location or role. If the criteria exclude the user, the item stays hidden even when the catalog and service are correctly published.

Taxonomy underpins the Employee Center by organising content into a structured hierarchy of topics and categories, which drives the mega-menu navigation and targeted content delivery. This satisfies the architecture's requirement for a governed classification framework, letting employees browse curated knowledge by department, location or service rather than relying on unstructured search.

The HR case table is a fundamental table in HR Service Delivery, storing all HR cases created from the HR catalog or by agents. It holds case details, assignment, state, and related HR profile information. It is the central transactional table for HR service delivery and is used for reporting, routing, and agent workspaces. This makes it part of the standard data model.

A Data Retention Policy defines destruction rules on the HR case table, automatically deleting records once they reach the seven-year threshold. This satisfies the compliance requirement without manual intervention, unlike archiving or scheduled jobs that merely move or flag data.

Task Templates define the standard task structure generated for an HR case, specifying which tasks are created and their sequencing. They satisfy the requirement by providing the reusable blueprint that shapes each case's task hierarchy.

HR Criteria build condition-based filters that evaluate user attributes such as location, employment type or department. HR services and templates consume these criteria to determine applicability, making reusable filtering their primary function rather than case routing or approval.

Employment Start Date is a standard HR Profile field because it records when the employee's tenure with the organisation begins. This satisfies the stem's requirement for standard HR Profile information, as opposed to IT-specific attributes such as device assignments or software licences, which belong to other record types.

Employee Center provides the standard self-service interface where employees raise requests, track cases, and access HR knowledge articles. It satisfies the stem's requirement for a single, unified portal for HR interactions, unlike the backend ServiceNow platform interface or agent-facing workspaces used by HR staff.

HR criteria allow the system to evaluate employee attributes such as country and automatically select the appropriate HR service and assignment group. By matching on the employee's country, the case will be routed to the UK payroll team and use the UK payroll service, meeting the requirement precisely.

The HR Profile record is the central HRSD data model record that stores employee-specific HR information such as hire date, termination date, HR department, and other HR attributes. It is linked to the user record but is separate, so HR data is kept distinct from platform user data. This record is used throughout HRSD for case creation, HR criteria evaluation, and reporting.

HR ACLs are user-defined access control lists that restrict record-level access, so only the assigned HR agent holds write permission on that case. They enforce the assignment constraint directly at the record level, unlike role-based or table-level controls.

Scripts define HR Criteria audiences through the ServiceNow HR Criteria engine, which evaluates server-side JavaScript against user and HR profile attributes. This satisfies the stem's requirement for a supported audience-definition method, unlike static groups or manual lists, because the script returns a true/false condition that dynamically determines membership.

HR Criteria define the audience conditions that determine which employees see a catalog item, satisfying the targeting requirement for HR Catalog Items. Without criteria, the item cannot be scoped to specific employee groups, so it is a mandatory component alongside the catalog item itself.

HR policy articles are stored in kb_knowledge, the base knowledge table, distinguished by knowledge base and category rather than a separate HR-specific table. This satisfies the stem because HR knowledge reuses the standard knowledge architecture.

Job details sit in the HR Profile because it stores employment-specific data such as position, department and employment type. This satisfies the stem by identifying one of the three profile information categories, distinct from personal and work contact details.

Task Templates populate fields on child tasks automatically, satisfying the requirement to standardise data entry across related HR cases. When a parent task spawns child tasks, inherited values flow into mapped fields, eliminating manual re-entry and reducing inconsistency. This mechanism differs from workflow routing or approval logic, which govern task progression rather than field-level data propagation.

HR ACLs apply record-level rules that restrict read access to cases matching the Benefits HR Service, limiting visibility to the HR Benefits group. This satisfies the stem's constraint that only that group can read those sensitive cases.

HR Services define the categories of HR requests, such as payroll or benefits, and carry configuration like templates and criteria. They connect employees to the appropriate case handling and routing. As a standard architectural component, the HR Service is central to how requests are structured and processed, making it a required element in the data model design.

The Assignment Group field determines which department's queue receives the HR case, driving routing and ownership. Populating it satisfies the requirement that cases reach the correct department, since assignment rules and group membership then notify the appropriate agents.

Topic detail refines the topic by defining the specific category an HR service belongs to, and it is a mandatory field on the HR service record. Configuration fails validation unless a topic detail is selected alongside the parent topic.

The HR Service is the record defining the case type, its fields and associated workflows; it drives which routing logic applies when a case is created, anchoring the lifecycle routing process alongside assignment rules and groups.

HR Profile is a primary component of the HR Service Delivery architecture, storing employee data that drives case routing, approvals and service catalogue personalisation. It satisfies the stem's requirement by acting as the foundational record linking HR services to individual employees, enabling scoped access and automated workflows across the HR Service Delivery application.

Mapping cases to services by Category is configured through HR Administration > HR Services, where each service record defines the Category value it responds to. This path satisfies the requirement to route Employee Center cases to the correct HR service automatically.

HR Criteria are condition sets evaluated against the user's profile and HR profile, and they gate catalogue item visibility. This satisfies the stem's requirement by controlling which users see a specific HR catalog item, rather than user criteria or catalogue permissions alone.

The HR profile table stores employee-specific HR data and is the correct place to add custom fields like hire date or compensation grade. It is referenced by HR criteria, so extending it makes those attributes available for routing decisions. Each employee has one HR profile record linked to their user record, making it the central data source for HR attributes.

HR Criteria evaluate user attributes to determine which catalog items a user is eligible to see or request. Applied to HR Catalog items, they define audience eligibility, matching the stem's stated function rather than controlling pricing, fulfilment or approval routing.

ACLs define which users or groups may read, write or delete specific records and fields, so they are the first place to inspect when HR data appears in IT-visible reports. Checking ACLs reveals whether overly permissive read rules on HR tables are exposing records beyond the intended HR audience.

Assignment rules evaluate conditions on the HR case and route it to the appropriate assignment group or agent. They directly determine which group receives the case, satisfying the routing factor requirement alongside topic detail and HR service definition.

Flow Designer builds the approval directly into the HR Service workflow, letting HR admins add approval actions without scripting. This satisfies the stem's efficiency constraint by defining the approval in one place, rather than splitting logic across separate workflow or business rule records.

Performance Analytics collects indicator data over time, giving trend dashboards and breakdowns of HR processes such as case volumes and resolution times. It satisfies the monitoring requirement by providing historical, aggregated insight rather than real-time transaction-level diagnostics.

To link an HR case to multiple employees, a many-to-many relationship is needed because a case can involve multiple employees and an employee can be involved in multiple cases. A custom table that stores case-to-profile associations allows this flexibility and can include additional attributes about the relationship, such as the role of each employee on the case.

Taxonomy governs how Employee Center content is categorised and organised, letting administrators structure topics and subtopics that surface HR information. It is one of the two administration areas, controlling the navigational hierarchy users browse rather than the portal's visual layout or widgets.

Domain separation in the HR Service Delivery data model creates distinct domains for Germany and the United States, and HR agents assigned to a domain can only access records within that domain. This satisfies the requirement to use identical HR services and forms while enforcing country-specific visibility of HR cases and HR profiles. It is the standard architecture for multi-country HRSD implementations.

HR Case ACLs control record-level read, write and create access, so restricting them to the HR Tier 1 group limits visibility to those members only. This satisfies the constraint that sensitive cases be viewable solely by that group.

A Record Producer can be attached to an HR Service so that the producer's catalogue item generates the correct case type with mapped variables. This link satisfies the requirement by connecting the request intake form to the service definition.

The `sn_hr_core_case` table is the base class from which every HR case type inherits, including HR service cases, lifecycle events and employee relations cases. This inheritance hierarchy satisfies the stem's requirement for a single parent entity, since child tables extend it rather than defining separate roots.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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 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.

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.

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 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.

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.

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.