Universal Containers implemented Sales Cloud and requested that sales agents have access to products and prices the company sells, and to be able to create opportunities for its customers.
What should the organization-wide defaults be for pricebook?
Correct Answer:
C
The organization-wide default (OWD) for Pricebook should be set to Use to allow sales agents to view pricebooks and their products, as well as to select a pricebook when creating Opportunities. The Use access enables users to add products from the pricebook to their opportunities while preventing unauthorized changes to the pricebook or its entries. Setting the OWD to Public Read-Only or View could provide unnecessary access or restrict essential functionality, such as associating products with opportunities. (developer.salesforce.com)
Universal Containers (UC) has a custom Apex class that enforces a business process and updates opportunities. UC has noticed that fields with Field-Level Security permission of Read-Only on certain users?? profiles are being updated by this class.
How should the architect fix this problem?
Correct Answer:
C
In Apex, the IsUpdateable() method of the Schema.DescribeFieldResult class checks if the current user has permission to update a specific field. Using this method ensures that the Apex class respects Field-Level Security (FLS) for all profiles, avoiding unauthorized updates.
✑ Option A: Adding the "With Sharing" keyword enforces record-sharing rules but
does not enforce field-level security.
✑ Option B: Placing the code in an inner class with "With Sharing" does not address the field-level security issue.
✑ Option C (Correct): Using IsUpdateable() ensures field permissions are honored programmatically, preventing updates to read-only fields.
References:
✑ Schema.DescribeFieldResult Methods
✑ Enforcing Field-Level Security in Apex
Universal Containers (UC) operates worldwide, with offices in more than 100 regions in 10 different countries, and has established a very complex Role Hierarchy to control data
visibility. In the new fiscal year, UC is planning to reorganize the roles and reassign account owners.
Which feature should an architect recommend to avoid problems with this operation?
Correct Answer:
B
✑ Parallel Sharing Rule Recalculation:
✑ Why Option B is Correct:
✑ Why Others Are Incorrect:
For more details, refer to Salesforce Sharing Recalculation Best Practices: https://help.salesforce.com/
A consulting company uses the Salesforce mobile app for its field consultants and uses Case object to track customer specific consulting done by field consultants. The company also has a large number of customer service representatives who takes calls from customers on company issued desktops and uses case object to track customer issues and grievances. The company would like to capture images of customer site captured by field consultants while they are editing the case record during customer site visit. The Director of IT wants to minimize customization and promote reuseability of code artifacts wherever possible.
What recommendations should an architect give to the company to implement the image capture requirement, while ensuring customer that the service rep can continue to use same lightning pages they were trained to use?
Correct Answer:
A
✑ Mobile-Specific Customization: Salesforce allows overriding standard actions like ??Edit?? with custom Lightning components that are conditionally applied for mobile or desktop experiences.
✑ Why Option A is Correct:
✑ Why Others Are Incorrect:
For detailed implementation guidelines, see Salesforce Lightning Component Customization: https://help.salesforce.com/
A junior account manager owns an account and creates a new opportunity to manage a complex deal. She needs the help of the product specialist and solution engineer. Given the size of this deal, she knows the account is likely to be reassigned to a senior account manager in the near future.
What is the optimal way for the junior account manager to share the opportunity, given the private sharing model?
Correct Answer:
C
The Opportunity Team feature is the most effective way to collaborate on an opportunity in a private sharing model. By adding the product specialist and solution engineer to the Opportunity Team, the junior account manager can share specific permissions for the opportunity without altering ownership. Additionally, Opportunity Team settings remain intact even if the account ownership changes to a senior manager.
✑ Option A: Manual sharing is less flexible and requires re-sharing if the account is reassigned.
✑ Option B: Sharing the account doesn??t ensure access to opportunities since sharing is record-specific in a private model.
✑ Option C (Correct): Opportunity Teams allow role-based collaboration and persistent sharing, ensuring access is unaffected by ownership changes.
References:
✑ Opportunity Team Overview