Given a User Request Scenario, Apply the Appropriate Security Controls Based on the Features and Capabilities of the Salesforce Sharing Model (e.g., Organization-Wide Defaults, Roles and the Role Hierarchy, Manual Sharing, Sharing Rules and Public Groups). PLATFORM-ADMINISTRATOR Practice Questions (Page 1)

Questions 1–5

1. 1foundation · easy

   What is manual sharing in Salesforce?

   • AA feature that defines criteria-based rules to share records with users who meet certain conditions.
   • BA feature that allows record owners to grant additional access to specific users or groups on a record-by-record basis.
   • CA feature that automatically shares records with all users in the same role as the owner.
   • DA feature that sets the baseline access level for all records of an object.
   Reveal Solution Discussion Select an answer first
2. 2foundation · easy

   Which of the following can be included in a public group?

   • AOnly individual users.
   • BOnly records and record types.
   • CIndividual users, roles, and other public groups.
   • DOnly roles and profiles.
   Reveal Solution Discussion Select an answer first
4. 3foundation · easy

   Which user is typically allowed to create a manual share on a record?

   • AOnly the system administrator.
   • BThe record owner, or a user with the 'Modify All Data' permission.
   • CAny user in the organization, regardless of record access.
   • DAny user in a role above the record owner.
   Reveal Solution Discussion Select an answer first
5. 4foundation · easy

   What is the primary purpose of organization-wide defaults in Salesforce?

   • ATo grant record access to specific users or groups chosen by the record owner.
   • BTo automatically share records with all users in the same role as the record owner.
   • CTo define criteria-based rules that extend access to records matching certain conditions.
   • DTo set the baseline level of access that every user has to records of an object, before other sharing mechanisms are applied.
   Reveal Solution Discussion Select an answer first
6. 5application · medium

   Nimbus Consulting uses a custom object 'Project__c' with Organization-Wide Defaults set to Private. The company has two sales teams: 'East Sales' and 'West Sales', each represented by a public group. Management wants every member of the East Sales team to see all projects owned by any East Sales member, and likewise for West Sales. No user should see projects owned by the other team. Which configuration meets this requirement?

   • ACreate one sharing rule on Project__c with 'Criteria-based' as the rule type, source = 'All internal users', target = 'East Sales' and 'West Sales' groups, with 'Read Only' access.
   • BChange the Organization-Wide Default for Project__c to Public Read/Write, then create a sharing rule to restrict access for the West Sales group.
   • CCreate two manual shares for each project record, one granting access to the East Sales group and one to the West Sales group, based on the owner's team.
   • DCreate two sharing rules on Project__c, one for each public group, with 'Record owner' as the rule type, the corresponding group as the source, and 'Read/Write' access.
   Reveal Solution Discussion Select an answer first