Public Sector uses business accounts to represent businesses and Person Accounts to represent individual constituents . Salesforce explicitly states that Person Accounts should represent people applying for licenses, permits, programs, benefits, grants, and government services, while business accounts represent organizations or businesses.

Because the agency has explicitly selected a phased implementation—business constituents first and private constituents later—the appropriate implementation is to establish the Business Account and Contact model for the first release and introduce Person Accounts when the individual-constituent phase is implemented.

Salesforce supports enabling Person Accounts in an existing Public Sector organization. However, the decision requires appropriate planning because Salesforce warns that Person Accounts can't be turned off after they're enabled . Administrators should therefore evaluate and test the implications before activation.

Household Accounts aren't the standard constituent model for Public Sector license and permit applications. Person Accounts are specifically integrated with Individual Applications, Cases, public complaints, and Public Sector constituent experiences. Therefore, C and D use the wrong individual data model. Option A unnecessarily implements the second-phase architecture immediately despite the government's explicit phased rollout.

Study Guide Reference: Agentforce Public Sector Implementation Strategies and Best Practices – Public Sector data model; Business Accounts; Contacts; Person Accounts; phased implementation strategy.

================