An administrator needs to create a one-to-many relationship between two objects with limited access to child records. What type of field should the administrator use?

Question

Options

• ARoll-up summary
• BMaster-detail field
• CCross Object formula
• DLookup field

• A
  17% (3)
• B
  72% (13)
• C
  6% (1)
• D
  6% (1)

Explanation

Master-detail is correct because it creates a tightly coupled one-to-many relationship where child (detail) records inherit their security and sharing settings from the parent (master) - meaning access to child records is automatically restricted based on the parent's permissions, not set independently.

Why the others are wrong:

• A. Roll-up summary - This is a field placed on the master object to aggregate child data (SUM, COUNT, etc.); it's a product of a master-detail relationship, not the relationship type itself.
• C. Cross-object formula - This lets a formula field reference a field on a related object, but it neither creates a relationship nor controls record access.
• D. Lookup field - Also creates a one-to-many relationship, but it's loosely coupled: child records can exist without a parent, and they do not inherit the parent's sharing settings, so access is not restricted.

Memory tip: Think "Master = Boss." The master record controls everything about the detail - its existence, its sharing, its access. If the boss (master) is deleted, the employees (detail records) go too. When a question mentions limited or restricted access tied to the parent, that's your signal it's a master-detail.

No community discussion yet for this question.