When applying a Delete rule to an Entity, which rule allows cascading delete of related records?

When applying a Delete rule to an Entity, the rule that allows for cascading delete of related records is the Delete rule. This means that when a record in the main entity is deleted, any associated records in related entities will also be automatically deleted. This is particularly useful in maintaining data integrity, as it prevents orphaned records in the database that no longer have a corresponding parent record.

Cascading deletes help manage relationships between entities effectively, ensuring that related data is handled appropriately when the main record is removed. The Delete rule is intentional, enabling developers to specify how relationships should behave when records are deleted, which is essential when dealing with relational databases.

In contrast, the Protect rule prevents deletion of the record if there are related records, effectively safeguarding against unintentional data loss. The Ignore rule means that the delete operation will not affect related records at all, leaving them intact regardless of the deletion of the parent record. The Archive rule, while useful for preserving data, does not facilitate deletion but rather indicates that the record should be marked as archived rather than actually removed from the database.