QuestionQ114

Declarative Sharing

Universal Containers (UC) offers shipment tracking to its customers through a custom Shipment object. The yearly total of shipments made by customers must be available on the Account record to the Marketing team, while the Marketing team must not be able to access Shipment records.

What should an Architect recommend to achieve this?

  • A Controlled by Parent (Account) on Shipment, trigger, and Master-Detail relationship to Account.
  • B Public organization-wide default on Shipment, process builder, and Lookup relationship to Account.
  • C Private organization-wide default on Shipment, rollup summary, and Master-Detail relationship to Account.
  • D Private organization-wide default on Shipment, trigger, and Lookup relationship to Account.
Explanation

A private organization-wide default prevents broad access to Shipment records. With a lookup relationship, Shipment access is independent of Account access, so Marketing users can view the calculated count on Account without being granted Shipment-record access. Because native roll-up summary fields require a master-detail relationship, an Apex trigger is used to maintain the yearly shipment total for the Account. A master-detail relationship would make detail-record access controlled by the parent, which would expose Shipment records to users who can access the Account.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!