What two security settings should be configured to ensure the community is secure and no extra information is available to the authenticated community users?

A customer wants to implement a customer community. Authenticated users will be able to log cases, manage their account and contact information, and apply/view their grant applications.

What two security settings should be configured to ensure the community is secure and no extra information is available to the authenticated community users?
A . Set up Sharing Rules to grant authenticated users access to their Cases. Applications, and Accounts
B . Set Org-Wide Defaults for External Users to Hidden for everything
C . Set up Sharing Sets to grant authenticated users access to their Cases, Applications, and Accounts
D . Set Org-Wide Defaults for External Users to Private for everything

Answer: C,D

Explanation:

Sharing sets are used to give community users access to records associated with them but not owned by them. This setting ensures that authenticated users can view and manage their cases, applications, and account information securely within the community.

Setting the Organization-Wide Defaults (OWD) for external users to private ensures that by default, these users do not have access to any records. Access can then be granted as necessary using sharing rules or sharing sets based on the relationship of the user to the records, thus maintaining strict control over data visibility.