Sharing-and-Visibility-Designer試験無料問題集「Salesforce Certified Sharing and Visibility Designer 認定」

A. The report owner and users with the "View All Data" permission

B. The report owner

C. The report owner and anybody in the role hierarchy above the report owner

D. The report owner and any users who have been given access to the "My Private Reports" folder

A. Partner super user

B. Delegate external user

C. Partner community admin.

D. Permission set to grant community admin permission

A. Read-only access to parent account for a user with access to a child case

B. Read-only access to parent account for a user, based on a criteria-based sharing rule

C. Access to child opportunities for the owner of the parent account

D. Access to related leads for the owner of the parent campaign

A. Granular Locking

B. Skinny table

C. Deferred Sharing Recalculation

D. Partition data using Divisions

E. Parallel Sharing Rule recalculation

A. Create a new profile without edit access to Category and assign it to the users.

B. Create a new page layout with the Category Field set to read-only for these users.

C. Create a permission set in the Category field to read-only and assign it to the users.

D. Create a custom permission to grant read-only access to Category and assign it to the users.

A. Put the code in an class that uses the With Sharing keyword.

B. Add With Sharing keyword to the class.

C. Use the With SECURYT_ENFORCED keyword in the SOQL statement.

D. Use the IsUpdateable() Apex method to test each field prior to allowing updates.

A. Enable Salesforce Platform Encryption and select the 12 contact fields to be encrypted.

B. Implement a custom Apex trigger to automatically encrypt the PII data using the Apex Crypto Class.

C. Update the field type of each of the 12 fields to "Text (Encrypted)" so that they are encrypted at rest.

D. Use an external, third party encryption service to encrypt PII before it enters Salesforce.

A. Create a batch job that creates sharing rules as needed, based on the cases created.

B. Build a trigger that create manual sharing of cases as needed whenever a new case is created.

C. No changes are needed to the sharing and visibility model to implement this requirement.

D. Create sharing groups that share all cases to all agents under the Dealer manager.

A. Super User does not work in Partner Community

B. Partner User Roles are limited to three levels.

C. The Channel manager Role can not be shared with Partner Community.

D. Partner Community does not support Role Hierarchy.

A. Add a role-based sharing rule so all sales team members have Read/Write access to contacts.

B. Remove sharing rules and replace them with Apex sharing for Unite Air and the other large accounts.

C. Create a permission set for the sales team to grant them Read/Write access to all account fields.

D. Implement an account hierarchy and redistribute the contacts evenly under the child accounts.

A. Review the Account structure to split the United Automotive account into multiple branch accounts.

B. Review the Customer Service Profile to ensure that they have Read/Write access to the appropriate Case and Account Fields.

C. Review all Case Sharing Rules and consolidate where appropriate to reduce the total number of sharing rules.

D. Review all Account sharing rules to ensure that the Customer Service team has Read/Write access to the United Automotive Account.

A. Create an Apex class that implements Filter-Based Opportunity Territory Assignment.

B. Create a process builder process that updates the territory field on the opportunity.

C. Create a criteria-based sharing rule on the opportunity to assign it to a territory

D. The territory with the highest territory type priority is automatically assigned to the opportunity.

A. Review the user provisioning process to not automatically create a user role for any new user.

B. Create an Apex class to replace the User Roles by generic one as soon as they are created.

C. Contact salesforce support and request to increase the number of users' roles allowed.

D. Remove role hierarchy from salesforce org and control the record access using apex managed sharing.

A. Use "With Sharing" keyword to make sure record visibility will always be considered.

B. Use "With Sharing" keyword to enforce field-level security.

C. Use runAs system method to test different users accessing these records.

D. Use "Without Sharing" keyword to make sure record visibility will be considered.