Universal Containers created a public group with certain sales engineers to help on complex deals, as well as a sharing rule to grant access to these opportunities. The Opportunity organization-wide default is Private.
What is the impact of these sharing settings?

1. A. Sales engineers and their managers in the Role Hierarchy will also have access to these records.
2. B. Subordinates of managers who have sales engineers in the public group will also have access to these records.
3. C. Other sales engineers who are in the same Role Hierarchy as the sales engineers of the public group will also have access to these records.

Correct Answer: A
The Public Group and Sharing Rule approach grants access to specified users and, by default, extends access to their managers in the Role Hierarchy. Here??s how the settings interact:
✑ Public Group: The group includes a specific set of sales engineers.
✑ Sharing Rule: It grants access to opportunities for the Public Group. This rule respects the existing Role Hierarchy.
✑ Role Hierarchy: In Salesforce, managers in the hierarchy automatically gain access to records their subordinates can access, ensuring seamless visibility for leadership.
✑ Option A (Correct): Managers of sales engineers in the Role Hierarchy will gain access because sharing rules honor the Role Hierarchy.
✑ Option B: Subordinates of managers will not gain access because sharing rules do not propagate access downward in the hierarchy.
✑ Option C: Other sales engineers outside the specified Public Group will not gain access unless explicitly included in the sharing rule.
References:
✑ Sharing Rules Overview
✑ Role Hierarchy and Sharing

An architect has a requirement to create a criteria-based sharing rule based on the customer Social Security Number. However, when setting up the rule in Contact Sharing, the field is not shown on the list of available fields.
What is causing this issue?

1. A. The field has been configured for encryption.
2. B. The architect's profile docs not have Field Level Security for this field.
3. C. The architect does not have permission to Compliance fields.

Correct Answer: A
✑ Field-Level Encryption and Sharing Rules:
✑ Why Option A is Correct:
✑ Why Others Are Incorrect:
For further reference, see Salesforce Shield Platform Encryption documentation: https://help.salesforce.com/

Dreamforce presenters need to be able to edit their presention details (summary, presenter biographies, etc) on a private custom object in Salesforce (Presentation). All presenters for a presentation are captured on a Presenters junction object between Presenter and User.
How can this be accomplished?

1. A. Give Edit rights to the Presentation record via a Permission set that is given to the Presenters for a record.
2. B. Trigger on Presenter junction object that adds the user to the Sales Team for the Presentation record.
3. C. Trigger on Presenter junction object that uses Apex Managed sharing to add or remove access to the related Presentation record.

Correct Answer: C
To allow presenters to edit details on a private custom object (Presentation) based on their relationship through a junction object, Apex Managed Sharing is the best solution:
✑ Option A: Permission sets provide global permissions, not record-specific access
based on a junction object.
✑ Option B: Adding users to a Sales Team applies to opportunities, not custom objects like Presentation.
✑ Option C (Correct): Apex Managed Sharing allows the creation of precise, record- specific sharing rules that dynamically grant access based on junction object relationships. This approach ensures presenters can edit only their related Presentation records.
References:
✑ Apex Managed Sharing for Custom Sharing Logic

Universal Containers has a Performance Feedback custom object (Private organization- wide default) used by customers to report any issues with delivery drivers. Feedback should not be visible to the driver, but any feedback records should be accessible to people above them in the Role Hierarchy, even when the driver changes managers.
Assuming managers have Read access to the Feedback object, which three steps are necessary to solve these requirements?

1. A. Remove Read permission on the Driver profile, have feedback ownership transferred to the driver when feedback is submitted, and create an ownership-based sharing rule.
2. B. Remove Read permission on the Driver profile, have feedback ownership transferred to the driver'smanager when feedback Is submitted, and use the Role Hierarchy to give access to a driver's manager.
3. C. Remove Read permission on the Driver profile, have feedback ownership transferred to the driver when feedback is submitted, and use the Role Hierarchy to give access to a driver's manager

Correct Answer: B
✑ Step 1: Remove Read permission on the Driver profile for the Feedback object to ensure that drivers cannot see their feedback records. Object-level permissions control whether users can see, edit, or delete records.
✑ Step 2: Automatically transfer ownership of feedback to the driver's manager upon submission. This ensures that managers own the feedback records, providing a natural ownership hierarchy for data visibility.
✑ Step 3: Leverage the Role Hierarchy to grant access to the manager's superiors, ensuring that visibility extends appropriately up the organizational structure.
✑ Why Option B is Correct: It directly aligns with the requirement that managers (not drivers) need access, and feedback visibility should follow the Role Hierarchy even after a driver??s manager changes.
✑ Why Others Are Incorrect:
For detailed references, see Salesforce Role Hierarchies and Ownership documentation: https://help.salesforce.com/

Users at Universal Containers are complaining that a field has disappeared from the Account page after last weekend's deployment. The page layout did not change with this deployment.
How should the admin troubleshoot this issue?

1. A. Run a Who Sees What report, filtering on Account.
2. B. Leg in as 3 user and check several accounts to isolate the problem records.
3. C. View Field Accessibility in the Object Manager.

Correct Answer: C
If a field disappears from the Account page, the likely cause is that its visibility has been restricted through Field-Level Security (FLS) or a related profile/permission set update. Using Field Accessibility in Object Manager allows the admin to review and troubleshoot field permissions across profiles.
✑ Option A: A "Who Sees What" report is used for record visibility, not field visibility.
✑ Option B: Logging in as a user might help confirm the issue but doesn??t provide insights into why the field is missing.
✑ Option C (Correct): Field Accessibility offers a comprehensive view of field-level security for troubleshooting.
References:
✑ Field Accessibility