A master-detail relationship creates a tight coupling between two objects. Key characteristics include:

1. The master object can be a standard object (like Account) or a custom object.

2. Roll-up summary fields can be created on the master record to aggregate data (e.g., SUM, COUNT) from related detail records. This feature is exclusive to master-detail relationships.

3. The detail record does not have its own owner field; it inherits ownership and sharing settings from its master record. If a user owns the master record, they implicitly have access to the detail records based on their profile permissions.

A. Permissions for the detail record are inherited from the master record; they are not set independently.

E. A custom object can be on the detail side of a maximum of two master-detail relationships, not five.

1. Salesforce Help, "Object Relationships Overview": This document outlines the behaviors of different relationship types. It states, "The owner of the master record also owns the detail and subdetail records," and "The detail and subdetail records inherit the sharing and security settings of the master record." This supports the correctness of D and the incorrectness of A.

2. Salesforce Help, "Roll-Up Summary Field": This page explicitly states, "A roll-up summary field calculates values from related records, such as those in a related list. You can create a roll-up summary field to display a value in a master record based on the values of fields in a detail record." This confirms the validity of option C.

3. Salesforce Help, "Create a Master-Detail Relationship": In the procedural steps for creating the relationship, the documentation confirms that the "Related To" (master) object can be a standard or custom object, supporting option B.

4. Salesforce Developer Documentation, "Relationships Among Objects": This guide specifies the limitations, noting, "Each custom object can have up to two master-detail relationships." This directly refutes option E.