Architect Exams Sharing-and-Visibility-Architect Passing Score

 Instituting a business process that calls for the account manager to be added to the account team once the account becomes a customer, and creating a criteria-based sharing rule that shares the account to the account management group when the type is customer are two methods that could be used to enable this sharing requirement, assuming a private sharing model for accounts. These methods would ensure that only accounts with type customer are shared with the account management users, and only when they are involved in the account team. Creating a public list view, where accounts of type customer are included and share the list view with account management public group is not a method to enable sharing, as it only filters the records that are already visible to the users, not grant access to new ones. Creating an account sharing rule that shares all accounts owned by sales to be shared with account management roles and subordinates is not a method to enable this sharing requirement, as it would share all accounts regardless of their type

Using Apex Managed sharing in a case Trigger that shares the record to the user identified in the Legal SME field is the best way to grant a lawyer access to a specific case when their assistance is needed, as it allows the case owner to dynamically share the case with a specific user based on a custom field value1. Creating a Criteria Based Sharing Rule that shares to the Corporate Legal Team Role when the ‘’legal assistance needed? Field is checked will not work, as it will share the case with all users in that role, not just the lawyer in the Legal SME field. Creating a Criteria Based Sharing Rule that shares to the Legal Public Group when the ‘’legal assistance needed?’’ field is checked will not work, as it will share the case with all users in that group, not just the lawyer in the Legal SME field.

Removing the “Opportunity Delete” permission from the sales team’s user profile in the object permissions is the best way to prevent a certain set of users from deleting opportunities, as it controls whether they can delete any opportunity record in Salesforce. Removing the delete button from the opportunity page layout and record type settings is not effective, as it only removes the button from the user interface, not from other access points such as API or reports. Creating a validation rule that checks the user’s profile before allowing the Is Deleted flag to be set to True is not possible, as validation rules cannot reference system fields such as Is Deleted. Overriding the standard button with a Visualforce page that warns them that they do not have permission to delete is not advisable, as it requires custom code and does not prevent deletion from other access points

To give access to a report folder to someone else in the organization, the user needs to have the “Manage Reports in Public Folders” profile permission and the “Manager” report folder permission. The “Viewer” and “Editor” report folder permissions only allow the user to view or edit the reports in the folder, but not to share the folder with others