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

A. Account records can be accessed due to implicit sharing from Opportunity.

B. Account records can be access due to role hierarchy.

C. Contact records can be accessed due to implicit sharing from Account.

D. Contact records can be accessed due to implicit sharing from Opportunity.

A. Private

B. Read Only and Read/Write

C. Read Only

D. Private and Read Only

A. A sharing rule is missing to share Invoices to the AR team.

B. The AR team profile needs to be assigned an Invoice Page layout.

C. A sharing rule is missing to share Accounts to the AR team.

D. The Accounts receivable profile does not have read Permission to the Invoice Object.

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. Public tad Only

B. Private

C. Public Read Write

D. Public Read/Transfer

A. There are no other options besides using field level security.

B. Create a new custom object controlled by parent and a Master-Detail relationship to Employee to store new restricted information.

C. Create a new custom object with private OWD and Lookup relationship to Employee to store new restricted information.

D. Change OWD of Employee custom object to private and a Lookup self-relationship to store only new restricted information.

A. Clone the Sales Rep profile, adjust settings, and assign the pilot users the new profile.

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

C. Create a permission set to grant access to the new functionality and hide the old functionality.

D. Create new user records for the pilot user that they will use for the pilot.

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

B. Give View All access for Accounts to the Retail Sales profile.

C. Update Retail Sales profile to grant access to Person Account record type.

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

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. Store the value in a text field on a protected custom setting in the package.

B. Store the value in a static variable in a class included in the managed package.

C. Store the value in an encrypted field on a custom object in the package.

D. Store the value in the text field on a list custom setting in the managed package.

A. Tab Settings

B. Page Layout Assignments

C. Record Types

D. Login Hours

A. Sales reps on the same will have Read access to the Accounts for Opportunities owned by their.

B. Sales Reps on the same team will have Edit access to the Accounts for Opportunity owned by their.

C. All sales reps will have Read access to all Accounts.

D. All sales reps will have Read access to Accounts for all Opportunities.

A. Leverage default Account team.

B. Create a permission set with "view all data" and assign to supporting users.

C. Create a public group and replace the account ownership with it.

D. Create a criteria-based sharing rule to grant access to other users.

A. The user and users with View All Data permission.

B. Only the user.

C. The user and users above him/her in the Role Hierarchy.

A. Susan and users with a shared chatter post link to the file.

B. Susan and users with the View All Data permission.

C. Susan only.

D. Susan and users with access to the record.

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.