Question

Difficulty: MediumObject Relationships (Lookup, Master-Detail, Many-to-Many)

An administrator at a financial services firm is configuring a custom data model to manage vendor compliance. Each Security Audit record must be linked to a parent Vendor record. The business requirements specify that deleting a Vendor record must automatically delete all associated Security Audit records. Furthermore, compliance managers must be able to view a real-time aggregate total of completed Security Audits directly on the Vendor record detail page using standard declarative functionality.

Which relationship type should the administrator establish on the Security Audit object to fulfill these requirements?

  1. Create a Master-Detail relationship field on the Security Audit object referencing the Vendor object.Answer
  2. B
    Create a Lookup relationship field on the Security Audit object and add a Roll-Up Summary field on the Vendor object.
  3. C
    Create a Master-Detail relationship field on the Vendor object referencing the Security Audit object.
  4. D
    Create a Many-to-Many relationship using a custom junction object between Vendor and Security Audit.

Answer

Create a Master-Detail relationship field on the Security Audit object referencing the Vendor object.
Establishing a Master-Detail relationship on the Security Audit custom object with Vendor as the master satisfies both key business requirements natively: deleting a Vendor automatically cascades deletion to child Security Audit records, and administrators can immediately build a standard Roll-Up Summary field on Vendor to count related audits.

Step-by-Step Solution

1
Analyze deletion cascade requirement
Master-Detail relationships enforce record deletion cascade, automatically deleting detail records when the master record is deleted.
Lookup relationships retain child records by default when a parent is deleted, failing the business constraint unless custom automation is built.
2
Analyze standard aggregation requirement
Native Roll-Up Summary fields are exclusively supported on the master object in Master-Detail relationships.
Standard declarative Roll-Up Summary fields cannot be created on parent records linked through Lookup relationships.
3
Determine field placement
The relationship custom field must be created on the child object (Security Audit), selecting Vendor as the master object.
In Salesforce data modeling, relationship fields are always defined on the child/detail side of the relationship.

Key Concept

Master-Detail Relationship Capabilities and Roll-Up Summary Field Dependencies
Estimated Time:1m 30s
Rate this question