Question: 1/50
A university wants a single person record that can represent an applicant, a current student, and later an alumnus without creating duplicates. Which design best supports this requirement in Education Cloud?
Use a single Contact record per person and relate lifecycle-specific records (e.g., applications, program enrollments, affiliations) to that Contact
Create separate Contacts for each lifecycle stage and relate them with a custom lookup field
Use Person Accounts so each lifecycle stage has its own Account and Contact pair
Store applicants as Leads, students as Contacts, and alumni as Person Accounts