Salesforce explicitly states that the Person Account model uses the standard Account object to hold the details about a person . In Public Sector, Person Accounts represent individual constituents who apply for licenses, permits, programs, benefits, grants, and government services.
A Person Account combines selected Account and Contact behavior into a single person-oriented record. Salesforce's Public Sector data-model documentation explains that this record can contain personhood information such as birth date and tax identification information and can relate directly to Cases, Individual Applications, and Public Complaints.
Option B is incorrect because Person Accounts combine Account and Contact characteristics, not Opportunity and Contract fields. Option C is incorrect because the Person Account record type is fundamental to the implementation; Salesforce explicitly identifies Person Account as an Account record type.
Option D is particularly important from an implementation-governance perspective. Salesforce warns that after Person Accounts are enabled in an organization, they cannot be disabled . This is why enabling them requires deliberate architectural planning and testing before activation.
For Public Sector, business constituents should normally be represented by Business Accounts, while individual constituents can use Person Accounts. This separation supports Public Sector data relationships while maintaining a consistent CRM data model.
Study Guide Reference: Agentforce Public Sector - Product-Specific Systems Knowledge – Person Accounts; Account data model; constituents; Person Account record type; implementation considerations.
================
