Sharing-and-Visibility-Designer 無料問題集「Salesforce Certified Sharing and Visibility Designer」

（A）The Sharing button always appears.

（B）The Sharing model is either Private or Public Read only.

（C）The Sharing model is Public Read/Write.

（D）The Sharing model is Public Read/Write/Transfer.

（A）Create a public list view, where accounts of type customer are included and share the list view with account management public group

（B）Create an account sharing rule that shares all accounts owned by sales to be shared with account management roles and subordinates

（C）Institute a business process that calls for the account manager to be added to the account team once the account becomes a customer

（D）Create a criteria-based sharing rule that shares the account to the account management group when the type is customer

（A）Create a scheduled job to automatically run the sharing recalculations on a nightly basis.

（B）Create public groups for each team, and share the jobs with the groups instead of users.

（C）Create a custom Visualforce page to edit the jobs and specify Without Sharing on the controller.

（D）Change the sharing model on the Job object to Public Read/Write.

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

（B）Create a new profile without edit access to Category and assign it to the users.

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

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

（A）Create a public group and assign the Auditors to the group.

（B）Create a criteria-based sharing rule to give access to the public group for high-value Opportunities.

（C）Add the auditors to the default Opportunity Team.

（D）Put the auditors as the highest level of the role hierarchy.

（A）Submit to force security scanner

（B）Manually check for cross site

（C）Manually check for sql injection

（D）Use debug to check hijacked requests

（E）Use web application tool for security

（A）Creation of a Role

（B）Deletion of a Role

（C）Creation of a Territory

（D）Deletion of a Territory

（A）runAs() does not enforce user permissions or field-level permissions in test classes

（B）runAs () counts towards total DML statements issued within transaction

（C）runAs() can be used inside of test classes to validate record-level security

（D）runAs() can be used inside of test classes to validate field-level permissions

（E）runAs() can be used outside of test classes to bypass record-level security

（A）Granular Locking

（B）Parallel Sharing Rule Recalculation

（C）Partitioning by Divisions

（D）Skinny Table Indexing

（E）Deferred Sharing Calculation

（A）Change the record type/page layout assignment for Work Order to be Read Only.

（B）Implement a sharing rule that changes access for all Work Order to Read.

（C）Remove the Work Order Edit permission from the sales representative Profile.

（D）Remove the edit button from the work order page layout.

（A）Implement a Public Read Only/Transfer OWD on Lead

（B）Implement a Public Read Only OWD on Lead.

（C）Implement a Public Read/Write OWD on Lead.

（D）Implement a private OWD on Lead.

（A）Create new user records for the pilot user that they will use for the pilot.

（B）Create a permission set to grant access to the new functionality and hide the old functionality.

（C）Revoke access to legacy function in the Sales Rep profile and create a permission set for the ..

（D）Clone the Sales Rep profile, adjust settings, and assign the pilot users the new profile.

（A）Role hierarchy Implicit sharing was Incorrectly disabled by the Salesforce adman.

（B）Sales managers have only the Read permission on the 5hipment object and should not be able to edit their team records.

（C）Ownership-based sharing rule for Shipment was Incorrectly disabled by the Salesforce admin.

（D）The Grant Access Using hierarchies option on Shipment Sharing Settings was incorrectly disabled by the Salesforce admin.

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

（B）Access to child opportunities for the owner of the parent account

（C）Access to related leads for the owner of the parent campaign

（D）Read-only access to parent account for a user, based on a criteria-based sharing rule

（A）Give View All access for Accounts to the Retail Sales profile.

（B）Create a criteria-based sharing rule giving Retail Sales role access to Accounts of type PersonAccount.

（C）Create an owner-based sharing rule on AccountContactRelation to grant access to at account contact roles records owned by sales reps.

（D）Update Retail Sales profile to grant access to Person Account record type.

（A）Set all Organization-Wide Default security to be "Private" for both internal and external users and use Sharing Rules to grant the desired access

（B）Set all Organization-Wide Default security to be "Public Read/Write" for internal users and "Private" for external users.

（C）Set the custom object to be master-detail to the Account and leave the Organization-Wide Default settings as their default values.

（D）Set all Organization-Wide Default settings to be "Public Read/Write" for both internal and external users.