Salesforce Platform Developer Practice Exam 2025 – All-in-One Guide to Ace Your Certification!

Creating a junction object for many-to-many relationships is the correct approach for tracking engines and their parts without orphan records. A junction object serves as an intermediary that associates records from two different objects, which in this case would be engines and parts.

By implementing a junction object, you can effectively create a relationship where multiple engines can be associated with multiple parts, and vice versa. This method ensures that each part is tied directly to its respective engine and that the relationship is stable, preventing orphan records, which could occur if parts are not linked to any engines. This setup also allows for ease of queries and maintenance, as you can manage the associations through the junction object.

Using a master-detail relationship for engines and parts would imply a parent-child relationship, which isn't suitable for many-to-many scenarios. Only one part could be linked to one engine in that case, leading to potential loss of information and flexibility. Similarly, creating a lookup relationship for each part to the engine object assumes a one-to-many relationship, which also wouldn’t capture the necessary complexity of multiple engines sharing parts without duplicating records. An alternative option like creating a champion object might not fully resolve the need for an explicit many-to-many relationship.

Overall, a junction object is the most efficient