Examkin

Question

Difficulty: Very hardStandard and Custom Object Management

An administrator at a global logistics organization is configuring a custom data model for tracking machinery assets and maintenance logs. The business requires that deleting an asset record automatically deletes all associated maintenance logs, that security access and record ownership of maintenance logs are derived strictly from the parent asset record, and that users can reassign a maintenance log record to a different asset record if it was originally linked incorrectly. Which two configuration steps must the administrator take to fulfill these business requirements? (Select 2)

  1. Create a Master-Detail relationship field on the child Maintenance Log object referencing the Asset object.Answer
  2. Check the 'Allow reparenting' option on the Master-Detail relationship field definition.Answer
  3. C
    Create a Lookup relationship field on the Maintenance Log object and enable the 'Cascade Delete' setting in the relationship options.
  4. D
    Set the Organization-Wide Default (OWD) sharing setting for the Maintenance Log object to Controlled by Parent.

Answer

The administrator must create a Master-Detail relationship field on the Maintenance Log object pointing to the Asset object and check the 'Allow reparenting' checkbox on the field configuration.
Creating a Master-Detail relationship on the child object enforces automatic deletion of child logs when the parent asset is deleted and dictates that access to child logs is governed by access to the parent asset. Enabling the 'Allow reparenting' option on the field definition overrides the default restriction that prevents detail records from being reassigned to a different master record.

Step-by-Step Solution

1
Evaluate object relationship requirements for cascading deletion and access inheritance.
Determined that a Master-Detail relationship is required because Lookup relationships do not natively cascade deletes or control security/ownership on custom objects.
Master-Detail relationships automatically delete child records upon master deletion and inherit record access and ownership from the master object.
2
Evaluate record reassignment (reparenting) requirements.
Determined that 'Allow reparenting' must be explicitly enabled on the Master-Detail relationship field.
Child records in a Master-Detail relationship are locked to their initial master record by default unless reparenting is enabled.

Key Concept

Master-Detail Relationship Behaviors and Reparenting Configuration
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic