The answer is controlled by runtime behavior, not by naming similarity. Salesforce access is layered. Object permissions allow a user to work with a type of record, field-level security controls visibility and editability for individual fields, and a page layout only organizes what the user sees after permission has already been granted. The correct response is therefore D. Set the Organization Wide Default to Private for accounts.
Create criteria-based sharing rules for Each marketing team, and create an Inside Sales Team profile with the
" View All " setting for Accounts.
The scenario is not asking for a feature list. It is asking which configuration produces the requested result with the fewest moving parts. A Salesforce app builder should favor a standard, visible Setup configuration whenever it fully meets the business need. That approach makes the build easier to validate in sandbox and easier to explain during release review.
The other options fall short for clear platform reasons. A (Set the Organization-Wide Default to Public for accounts. Create profiles for each marketing team, and create an Inside Sales Team role that is at the top of the Role Hierarchy.) is not enough: it would require extra assumptions that the scenario does not support. B (Set the Organization Wide Default to Public for accounts. Create criteria-based sharing rules for Each marketing team, and create an Inside Sales Team permission set with the " View All " setting for Accounts.) handles a different concern; Sharing controls record visibility; it does not change field type, page composition, or automation timing. C (Set the Organization-Wide Default to Private for accounts. Create permission sets for each marketing Team, and create an Inside Sales Team profile with the " View All " setting for accounts.) is less defensible because Permission controls are essential for access, but they do not perform calculations or process automation. Before release, test the configuration with the affected profile and realistic records, not only with a system administrator account.
---