HCM Studio
Sign in

Assessment

Self-check: worker, assignment, work relationship

Four questions on assignment-level security, the primary flags that disagree, the projected dates that do nothing, and which assignment a single-assignment report uses.

4 questionsPass mark 70%Back to the lesson

What this checks

  • Explain assignment-level security
  • Explain where the primary flags disagree
  • State what the projected dates do
  • Choose the assignment for single-assignment reporting

Every incorrect option names the misconception it represents. A wrong answer tells you which model of the process you reached for, which is the part that is worth correcting.

1. A line manager opens a worker’s record and sees only one of the two assignments the worker demonstrably holds. The second one reports to a different manager. What is the explanation?

Explain assignment-level security · targets: Concluding the second assignment was deleted or the person record is corrupt, when the unit of visibility is the assignment and the split is correct.

2. A data-quality report flags a pending worker as holding a primary assignment inside a nonprimary work relationship, and calls it a contradiction. Is it?

Explain where the primary flags disagree · targets: Assuming the primary flag must agree across the work relationship and its assignments, and "fixing" data that is correct.

3. Setting the projected assignment end date makes the application end the assignment on that date.

State what the projected dates do · targets: Building an operational expectation on an informational field, then blaming the field for not acting.

4. A government-style report needs exactly one assignment per person. A person holds three across two work relationships. Which assignment does the report use?

Choose the assignment for single-assignment reporting · targets: Choosing the most recent, the highest-paid, or "the primary-looking one" — all of which make the answer vary for the same person.