A master-detail relationship creates a special parent-child bond where the master object controls certain behaviors of the detail object. A key feature of this relationship is the cascade-delete functionality. When a record of the master object (Supplier) is deleted, all its related detail records (SupplierItemc) are automatically and simultaneously deleted. This behavior directly and precisely meets the stated requirement of the business scenario. The lifecycle of the SupplierItemc records is intrinsically tied to the parent Supplier record.

A. Many-to-many: This is a design pattern, not a single field type. It is implemented using a junction object with two master-detail relationships, but "Master-detail" is the fundamental relationship that provides the required cascade-delete behavior.

B. Indirect lookup: This relationship type is specifically used to link a Salesforce object to an external object using an external ID, which is not the case in this scenario involving two internal Salesforce objects.

C. Hierarchical: This is a special type of lookup relationship that is only available for the User object. It is used to create management chains or other user hierarchies and cannot be used on custom objects like Supplier.

1. Salesforce Help, "Object Relationships Overview": Under the "Master-Detail" section, the documentation states, "The detail and subdetail records inherit security settings and permissions from the master record. Deleting a master record deletes all detail and subdetail records." This directly confirms the cascade-delete behavior.

2. Salesforce Help, "Considerations for Relationships": In the "Master-Detail Relationship Considerations" section, it is noted: "Deleting a master record deletes related detail and subdetail records." This reinforces that the master-detail relationship is the correct choice for this requirement.

3. Salesforce Platform Developer I Certification Guide, "Working with Salesforce Objects": This guide outlines the different relationship types. In the section covering Master-Detail relationships, it emphasizes that the child (detail) object's existence depends on the parent (master), and deleting the parent cascades the deletion to the children. (Note: While this is a certification guide, it reflects the core, officially documented platform behavior).