The requirement points to a specific Salesforce control. Master-detail relationships create ownership, security, and lifecycle dependency between parent and child records. A junction object uses two master-detail relationships to represent a many-to-many model. The correct response is therefore C. Create a master-detail relationship from Testimonial_to Account and a lookup relationship from Testimonial To Contact.
The scenario is not asking for a feature list. It is asking which configuration produces the requested result with the fewest moving parts. A Salesforce app builder should favor a standard, visible Setup configuration whenever it fully meets the business need. That approach makes the build easier to validate in sandbox and easier to explain during release review.
The wrong answers confuse adjacent platform concepts. A (Create a lookup relationship from Testimonial_to Account and a master-detail relationship from Testimonial to Contact.) is only a partial match because A lookup relationship is more loosely coupled and does not provide every master-detail behavior, especially native roll-up behavior. B (Make Testimonial ca junction object between Account and Contact using master- detail relationships.) misses the mark because Master-detail is powerful, but it is wrong when the records need independent ownership or when the child-parent direction is reversed. D (Make both the Contact and Account fields required on the Testimonial object and create lookup relationships from Testimonial_cto Contact and to Account.) handles a different concern; A lookup relationship is more loosely coupled and does not provide every master-detail behavior, especially native roll-up behavior. This keeps the build declarative, traceable in Setup, and easier to support when the org changes later.
---
---