1Z0-1046-20 · Question #113
Which three options are true about the Global Person model? (Choose three.)
The correct answer is A. Person records are global, independent of legal employers, and created only once for any person. B. Person records continue to exist even when the person has no current work relationships in the D. Person records hold information that is personal, such as name, date of birth, and disability. Explanation/Reference:
Question
Which three options are true about the Global Person model? (Choose three.)
Options
- APerson records are global, independent of legal employers, and created only once for any person.
- BPerson records continue to exist even when the person has no current work relationships in the
- CPerson records cease to exist when a person is terminated from an organization.
- DPerson records hold information that is personal, such as name, date of birth, and disability
- EPerson records are auto-archived two years after a person is terminated from an organization.
How the community answered
(24 responses)- A79% (19)
- C8% (2)
- E13% (3)
Explanation
Explanation/Reference:
Topics
Community Discussion
6A, B, and D are your three. The Global Person model exists precisely so that a person's core record, name, date of birth, national identifiers, disability information, that kind of biographical data, lives independently of any employment relationship or legal employer. You create the person once and every work relationship just hangs off that single record, which is why A and D are both correct. B follows directly from that architecture, because terminating someone ends the work relationship, not the person record itself, so the record sticks around and stays queryable. C is flat wrong and just describes the opposite of how the model works, and E is made up entirely, there is no two-year auto-archive behavior in the person model. If you see answer choices that introduce specific time windows for system behavior you have never configured, treat them as traps because Oracle does not auto-purge person records on a timer out of the box.
The only thing worth adding is that the "stays queryable after termination" behavior Aleksei describes in B is exactly why you can rehire someone without recreating their record, which is the practical payoff of that design that shows up on the exam as its own question type.
Tripped on C, person records outlive termination entirely, right?
A, B, D is exactly right, and here is the way I think about it. Imagine the county clerk's office keeps one file folder per resident, no matter how many jobs that person holds around town. That folder does not get shredded when someone quits a job, and it sure does not disappear just because they are between employers right now. That is the whole point of the Global Person model in Oracle HCM, one person record that lives independently of any work relationship and stores the stuff that belongs to the human being, not the job, things like name, date of birth, and disability information (option D). Option C trips people up every year because it sounds logical, but termination ends the work relationship, not the person record, which is why rehires work so cleanly in this system. Option E is a total invention, there is no two-year auto-archive timer anywhere in the standard product.
I am locked in on C because it just makes logical sense to me that once Oracle HCM terminates a person record, the system cleans house and removes it to keep the data lean. The whole point of termination is closure, and I cannot see Oracle leaving ghost records floating around in a global model that is supposed to stay clean and organized.
Marisol, Oracle HCM never deletes the person record on termination, it just end-dates the work relationship, which is exactly why A, B, and D are correct, because the person record stays intact for audit history and potential rehire, and the system keeps data lean through end-dating, not deletion.