Examkin

Question

Difficulty: MediumStandard and Custom Object Management

A Salesforce administrator at a university research library system is configuring a custom object named Manuscript Loan to track archived manuscript borrowing requests associated with the standard Contact object. The administrator needs to evaluate schema management capabilities, relationship requirements, and data governance rules for this setup. Which two statements accurately describe Salesforce standard and custom object capabilities in this scenario? (Select 2)

  1. If a Master-Detail relationship is configured between Contact and Manuscript Loan, deleting a Contact record will automatically delete all related Manuscript Loan records.Answer
  2. Custom objects can be deleted from Object Manager even if they contain data records, as long as all custom field references, Apex code, and workflow dependencies are cleared.Answer
  3. C
    A Roll-Up Summary field can be created on the standard Contact object to count linked Manuscript Loan records when using a standard Lookup relationship.
  4. D
    Restricting visibility of a custom field on the Manuscript Loan Lightning page using Dynamic Forms component rules prevents user access to that field via API integrations.

Answer

Cascading deletion occurs automatically for detail records in a Master-Detail relationship when the master record is deleted, and custom objects containing data can be deleted from Object Manager after clearing component dependencies.
In Salesforce Object Manager schema design, establishing a Master-Detail relationship forces child records to inherit parent lifecycle behavior, meaning deleting the parent Contact automatically deletes related child records. Additionally, administrators can delete custom objects containing records provided component dependencies such as code or custom formula fields are disassociated.

Step-by-Step Solution

1
Analyze relationship lifecycle behavior for standard and custom objects.
Master-Detail relationships enforce cascading deletion of child records upon deletion of the parent record.
Detail records depend entirely on the master record for ownership and access control.
2
Evaluate custom object deletion prerequisites in Object Manager.
Custom objects with existing records can be deleted once hard component dependencies (such as Apex or formula references) are removed.
Salesforce allows schema deletion of custom objects without requiring record purging first, provided non-data metadata dependencies are cleared.
3
Review roll-up summary and UI security limitations against distractors.
Lookup relationships do not support Roll-Up Summary fields without custom code or automation, and Dynamic Forms component visibility does not enforce backend API security.
Roll-Up Summary functionality strictly requires Master-Detail architecture, while Field-Level Security must be managed at the profile/permission set level.

Key Concept

Standard vs Custom Object Lifecycle and Schema Capabilities
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic