Examkin

Question

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

An administrator is designing a custom compliance tracking application. The requirement states that each Audit Finding record must strictly belong to a parent Vendor Audit record. If a Vendor Audit is deleted, all related Audit Findings must be automatically deleted. Additionally, executive managers require a real-time count of high-priority Audit Findings directly on the Vendor Audit record, and administrators must retain the ability to move an Audit Finding to a different Vendor Audit if it was created under the wrong audit.

Which two relationship configurations and behaviors must the administrator implement to meet these requirements? (Choose 2 answers)

  1. Create a Master-Detail relationship on the Audit Finding object pointing to Vendor Audit to enable Roll-Up Summary fields on Vendor Audit.Answer
  2. Enable the 'Allow reparenting' setting on the Master-Detail relationship field definition to permit reassignment of Audit Findings to another Vendor Audit.Answer
  3. C
    Create a Lookup relationship from Audit Finding to Vendor Audit, which supports native Roll-Up Summary fields for counting related child records.
  4. D
    Use a standard Lookup relationship because deleting a parent record in a Lookup relationship automatically cascade-deletes all associated child records by default.

Answer

The administrator must create a Master-Detail relationship on the Audit Finding object referencing Vendor Audit to support Roll-Up Summary fields and cascade deletion, and explicitly enable the 'Allow reparenting' checkbox on the relationship field definition.
A Master-Detail relationship defined on the Audit Finding child object fulfills the automatic deletion requirement when a parent Vendor Audit is deleted, and enables Roll-Up Summary fields on Vendor Audit to calculate finding counts. Enabling the 'Allow reparenting' checkbox on the Master-Detail relationship field grants administrators permission to reassign an Audit Finding record to a different Vendor Audit.

Step-by-Step Solution

1
Analyze relationship requirements for record deletion and rollup capabilities.
Determine that a Master-Detail relationship is required on Audit Finding.
Cascading deletion of child records and standard Roll-Up Summary fields are only available on Master-Detail relationships, not Lookup relationships.
2
Evaluate requirement for reassigning child records to a different parent record.
Enable 'Allow reparenting' on the Master-Detail field setup.
In Master-Detail relationships, child records are locked to their initial parent record by default unless reparenting is explicitly enabled.

Key Concept

Master-Detail Relationship Capabilities and Reparenting Configuration
Estimated Time:2m 0s
Rate this question

Topics

Object Relationships (Lookup, Master-Detail, Many-to-Many)

More questions from this topic