Master-Detail Relationship

Correct Answer: A and C

You can't delete a custom object if it is on the master side of a master-detail relationship.

And if you delete a custom object that is on the detail side of a master-detail relationship, the relationship is converted to a lookup relationship.

Deleting a detail record moves it to the Recycle Bin and leaves the master record intact; deleting a master record also deletes related detail and subdetail records.

Undeleting a detail record restores it, and undeleting a master record also undeletes related detail and subdetail records.

However, if you delete a detail record and later, separately, delete its master record, you cannot undelete the detail record, as it no longer has a master record to relate to.

By default, records can't be reparented in master-detail relationships.

Administrators can, however, allow child records in master-detail relationships on custom objects to be reparented to different parent records by selecting the <samp>Allow reparenting</samp> option in the master-detail relationship definition.

Other options are incorrect because a master object cannot be a standard object and the detail record also inherits the sharing rule from master records, but the child record cannot inherit the sharing settings from the parent.

Reference:

Sure, here is a detailed explanation of the two correct options for this question:

A. Deleting a parent record will delete all child records:

This statement is true in a master-detail relationship. When you establish a master-detail relationship between two objects in Salesforce, you are essentially creating a parent-child relationship between them. The master object is the parent, and the detail object is the child. In this relationship, the child records are dependent on the parent record. So if you delete the parent record, Salesforce will automatically delete all the child records associated with it. This is known as a cascading delete.

B. The master object cannot be a standard object:

This statement is also true in a master-detail relationship. A standard object is one of the pre-built objects that come with Salesforce, such as Accounts, Contacts, Opportunities, and Cases. In Salesforce, you can create custom objects that are specific to your business needs. When you create a master-detail relationship, the master object must be a custom object, and the detail object can be a standard or custom object. This is because standard objects already have their own relationships with other standard objects, so they cannot be used as the master object in a master-detail relationship.

C. By default, the child record cannot be reparented:

This statement is not true in a master-detail relationship. In fact, the child record can be reparented in a master-detail relationship. However, there are some restrictions. For example, if the child record is associated with a specific record type, you cannot reparent it to a record type that is not associated with the same master record. Also, if there are any validation rules on the child object that prevent it from being reparented, you cannot reparent it.

D. The child record inherits the sharing settings from the parent:

This statement is not true in a master-detail relationship. In fact, sharing settings do not apply to master-detail relationships. In a master-detail relationship, the child record inherits the sharing settings of the parent record only if the sharing settings for the parent object are set to "Controlled by Parent". If the sharing settings for the parent object are set to "Private", the child records will also be private, regardless of the sharing settings of the parent record.