Sharing-and-Visibility-Designer Salesforce Certified Sharing and Visibility Designer (SP19)

Loading demo links...

Showing 7–9 of 10 questions

Question 7

After setting up Customer Community and enabling collaboration, the architect realizes that customers are only seeing Chatter posts from other customers in their account.

What should the architect do to allow viewing Chatter posts from all customers?

Select an option, then click Submit answer.

  • Enable Internal Users Visibility.

  • Enable Community User Visibility.

  • Set View all for Chatter posts.

  • Enable Chatter Super User.

Question 8

Universal Containers (UC) provides shipment tracking for its customers on a custom Shipment object. The total number of shipments made yearly by the customers should be available on the Account record to the Marketing team, but the Marketing team should not have access to Shipment records.

What recommendation should an Architect provide to accomplish this?

Select an option, then click Submit answer.

  • Controlled by Parent (Account) on Shipment, trigger, and Master-Detail relationship to Account.

  • Public organization-wide default on Shipment, process builder, and Lookup relationship to Account.

  • Private organization-wide default on Shipment, rollup summary, and Master-Detail relationship to Account.

  • Private organization-wide default on Shipment, trigger, and Lookup relationship to Account.

Question 9

DreamHouse Realty is designing a new community using the Customer Community license type. They have the following requirements:

- They want the users to complete survey questions through the community interface.

- Responses need to be stored in a Custom Object that has a lookup to the account object.

- Any internal user who has access to the account should be able to see all survey responses.- All Customer Community users should be able to see surveys filled in by other users for their company, but not surveys for other companies.

Which security settings should be used to achieve this goal?

Select an option, then click Submit answer.

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

  • Set the Organization-Wide Default security to be Private for both internal and external users and use Sharing Rules to grant the desired access.

  • Set the Organization-Wide Default security to be Public Read/Write for internal users and a Private for external users.

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