The sales manager at Cloud Kicks wants a way to report on information from a form their clients fill out during the sales cycle. Once a form has been…

This scenario requires modeling a one-to-many relationship and tracking changes. A custom object (C) is the best solution to store multiple form submissions related to a single parent record (e.g., Opportunity). Each time a client fills out the form, a new record is created on this custom object. This is a scalable and reportable data model. To meet the requirement to "see what changed from one submission to the next," Field History Tracking (D) should be enabled on the fields of this new custom object. This creates a related list that logs the date, time, user, and nature of any changes made to tracked fields on each submission record.

A. Add forms as attachments: Attachments are unstructured files (like PDFs or images). You cannot report on the data within them or easily compare field-level changes between versions.
B. Make custom fields: Adding over 30 fields directly to the parent object is not scalable for multiple submissions. It would require creating duplicate sets of fields, making reporting and management difficult.

1. Salesforce Help. (2024). Create a Custom Object. "Custom objects are the heart of any application. Custom objects let you store data that’s unique to your organization." This is used to model relationships like one-to-many.

2. Trailhead by Salesforce. (2024). Data Modeling module, Create Object Relationships unit. Explains how to use custom objects and lookup/master-detail relationships to model business processes where one record can be related to many other records.

3. Salesforce Help. (2024). Track Field History for Standard and Custom Objects. "You can select certain fields to track and display the field history in the History related list of an object... For each field, the history includes the date and time of the change, the user who made it, and the old and new values."