Examkin

Question

Difficulty: Very hardStandard and Custom Object Management

An administrator at a financial services enterprise is configuring a custom data model to manage client investment portfolios using a custom object Portfolio__c and individual assets using a custom object Holding__c. The business requires that the total monetary value of all related Holding__c records automatically aggregates on the parent Portfolio__c record, that deleting a Portfolio__c record automatically removes all associated Holding__c records, and that users can reassign a Holding__c record to a different Portfolio__c if registered incorrectly. Additionally, compliance officers require that sensitive financial compliance fields on Holding__c are restricted from unauthorized data access across all platform interfaces, including reports and APIs. Which architectural configuration correctly meets all requirements while maintaining data security?

  1. Create a Master-Detail relationship on Holding__c pointing to Portfolio__c, select the 'Allow reparenting' checkbox on the relationship field, create a Roll-Up Summary field on Portfolio__c, and enforce field access using Field-Level Security (FLS).Answer
  2. B
    Create a Lookup relationship on Holding__c pointing to Portfolio__c, enable cascading deletion on the lookup definition, create a native Roll-Up Summary field on Portfolio__c, and configure Field-Level Security (FLS) for compliance fields.
  3. C
    Create a Master-Detail relationship on Holding__c pointing to Portfolio__c without enabling reparenting, expecting child records to automatically orphan and persist if the master Portfolio__c record is deleted, while securing fields via Field-Level Security (FLS).
  4. D
    Create a Master-Detail relationship on Holding__c pointing to Portfolio__c, select 'Allow reparenting', build a Roll-Up Summary field on Portfolio__c, and hide sensitive fields from unauthorized users solely using Dynamic Forms component visibility rules.

Answer

The correct architecture requires creating a Master-Detail relationship on Holding__c referencing Portfolio__c with 'Allow reparenting' enabled, adding a Roll-Up Summary field on Portfolio__c to calculate total value, and enforcing access to sensitive compliance fields using Field-Level Security (FLS).
The correct configuration establishes a Master-Detail relationship on Holding__c pointing to Portfolio__c, which natively supports Roll-Up Summary fields on Portfolio__c for calculating total asset values and automatically cascade-deletes child Holding__c records if a Portfolio__c is removed. Enabling 'Allow reparenting' allows administrators and users to reassign holdings to a different portfolio when misallocated. Securing sensitive fields via Field-Level Security (FLS) ensures data access restrictions are applied universally across the UI, reports, and API integrations.

Step-by-Step Solution

1
Analyze relationship type requirements for aggregation and deletion behavior.
Native Roll-Up Summary fields and automatic cascade deletion require a Master-Detail relationship between the parent Portfolio__c (Master) and child Holding__c (Detail).
Lookup relationships do not support native Roll-Up Summary fields.
2
Evaluate record reassignment needs.
The 'Allow reparenting' option must be explicitly selected on the Master-Detail lookup field definition.
By default, child records in a Master-Detail relationship cannot be reparented to another master record unless reparenting is enabled.
3
Evaluate security constraints for compliance fields.
Field-Level Security (FLS) must be configured on Profiles or Permission Sets to restrict access to sensitive fields.
Dynamic Forms component visibility only controls Lightning page rendering, whereas FLS secures fields across UI, API, reports, and list views.

Key Concept

Master-Detail Relationship Capabilities, Reparenting Controls, and Security Boundaries
Estimated Time:2m 0s
Rate this question

Topics

Standard and Custom Object Management

More questions from this topic