Explanation:

Criteria-based sharing rules precisely meet these requirements. The first rule grants access to Person Accounts (retail customers), while the second explicitly excludes Business Accounts (commercial customers). Option B (AccountContactRelation) doesn't properly address the record type distinction. Option C (profile settings) alone cannot restrict access to only Person Accounts. The solution: 1) Maintains private OWD for security 2) Automatically shares all retail accounts 3) Explicitly blocks commercial account access 4) Requires no manual maintenance. Criteria rules evaluate record attributes (like type or record type) to determine sharing, making them ideal for this segmentation. As new retail accounts are created, they automatically become visible to the sales team without administrator intervention. The solution properly implements the principle of least privilege while meeting all business requirements. It's also scalable as the organization grows, maintaining proper data segregation between retail and commercial operations. This approach demonstrates effective use of Salesforce's sharing capabilities to enforce complex business rules while minimizing administrative overhead.

Explanation:

Public Groups are the mechanism in Salesforce designed to bundle unrelated users—across roles, profiles, or territories—into a single sharing unit. Once defined, you can reference the group in sharing rules, manual shares, or Apex managed sharing to grant record access.

→ Role Hierarchy is strictly vertical; you can’t use it to group peers or cross-functional teams who don’t report to each other.
→ Sharing Sets are only for high-volume community licenses and grant access based on profiles and record owner, not arbitrary clusters of users.

Thus, when you need to share records with a specific team or committee that doesn’t map to the org’s structural hierarchy, you create a Public Group containing exactly those users. A sharing rule can then grant read or read/write access to that group.

Explanation:

The Partner Community license (now called Partner Relationship Management) is designed for B2B relationships and supports access to objects like Opportunities, Accounts, and custom objects. It allows for complex sharing models and supports up to millions of users. Customer Community Plus and Customer Community licenses do not provide access to Opportunities, which are required here. Hence, only Partner Community meets the requirements for high-scale, Opportunity visibility in a community.

Explanation:

Account Teams provide:
Read access to accounts.
Read access to related cases (via Account Team sharing settings).
No access to opportunities unless explicitly added.

Scalability:

Teams are dynamic—no need for sharing rules.

Explanation:

Sharing Sets dynamically grant access to unrelated users (e.g., community users) based on criteria like record ownership or attributes.

Use Case:

Ideal for ad-hoc groups needing access to specific records (e.g., projects, cases).

Alternatives Rejected:

Role Hierarchy (A): Requires parent-child relationships.

Public Groups (C): Static; impractical for dynamic record sets.