Question 6 of 43

The 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 might cause this?

    Correct Answer: C

    The field has been configured for encryption. Encrypted fields cannot be used in criteria-based sharing rules, hence it would not be shown in the list of available fields.

Question 7 of 43

What should a Salesforce architect recommend to make sure that users that gained access to a custom object record through Apex managed sharing do not lose access to it when its owner is changed?

    Correct Answer: B

    To make sure that users who gained access to a custom object record through Apex managed sharing do not lose access to it when its owner is changed, a Salesforce architect should recommend creating a specific Apex Sharing Reason for the custom object. This ensures that the sharing reason is independent of record ownership and therefore remains intact when the owner changes.

Question 8 of 43

The sales managers at Universal Containers (UC) requested their teams to define each user’s role on their accounts in order to provide an easy way to establish accountability and collaboration. Sales managers also requested that sales associated should only get the following permissions:

Read access to the accounts.

Read access to cases related to the accounts.

No access to deals related to the accounts.

The sales associates may be granted access to opportunities when needed.

Assuming the overall sharing model of the organization is private and no sharing rules are configured on the account object. How can an Architect achieve these requirements?

    Correct Answer: B

    Using Account teams, Opportunity teams, and Case teams is the ideal solution. Account teams can define access to accounts, but they won’t cover the specific requirements for opportunities and cases. Opportunity teams allow for dynamic access to opportunities when access is needed, ensuring that sales associates have no default access to deals (opportunities). Case teams ensure that sales associates have read access to cases related to the accounts. This approach provides flexibility and granularity in permission settings for each type of record as required.

Question 9 of 43

Universal Containers (UC) has implemented Customer Community with customer community plus licenses for its distributors. Some distributors requested granting specific community users (agents) to view cases submitted by other agents of the same distributor.

Which feature only supports these requirements?

    Correct Answer: D

    The Partner Super User feature allows specific users to see and manage cases and other records owned by other users within the same company or account. In this scenario, the requirement is for community users (agents) of the same distributor to view cases submitted by other agents, which aligns with the abilities granted through the Partner Super User feature. While the naming might suggest it is only for Partner Community, it actually supports Customer Community Plus licenses as well, making it the appropriate choice.

Question 10 of 43

Universal Containers (UC) uses a custom Lightning component with an Apex class to display shipment information (custom object, private OWD). UC sales managers are complaining about two important points:

Shipment records that belong to their teams can be seen by other users.

Shipment amount should be visible only by managers, but sales reps are able to view it.

Which two features did the development team miss that is causing the problems? (Choose two.)

    Correct Answer: B, D

    The problems stem from incorrect handling of record visibility and field-level security. To address the issue where Shipment records that belong to teams can be seen by other users, the development team should use the 'With Sharing' keyword in Apex classes. This ensures that sharing rules defined in Salesforce are enforced, restricting record visibility based on user permissions. To resolve the issue where Shipment amounts are visible to sales reps instead of being restricted to managers, the 'isAccessible()' method in Apex classes should be used. This method checks if the current user has permission to access the specific fields, ensuring that sensitive information like Shipment amounts is only accessible to authorized users.