The setup audit trail tracks changes made in your org's setup area for the past 180 days1. You can export the setup audit trail and find the fields in question by filtering by action type, user, or date2.

Leveraging duplicate rules in Salesforce to validate duplicates during the account creation process (option A) is the best option to implement to avoid duplicates, as it allows the sales associates to identify and merge duplicate accounts before they are saved. Developing an Apex class that searches for duplicates and removes them nightly (option B) is not a good option, as it may cause data loss or conflicts, and it does not prevent duplicates from being created in the first place. Implementing an MDM solution to validate the customer information before creating Salesforce (option C) is also not a good option, as it may introduce additional complexity and cost, and it does not address the issue of customers interacting with both the website and the store. Building a custom search functionality that allows sales associates to search for customer in real time upon visiting their retail stores (option D) is also not a good option, as it may not be reliable or user-friendly, and it does not leverage the existing Global Search feature.

To allow only the owner of a contact record to delete that contact, the data architect should create a "before delete" trigger to check if the current user is not the owner. The trigger can use the UserInfo.getUserId() method to get the current user's ID and compare it with the OwnerId field of the contact record. If they are not equal, the trigger can add an error to the record and prevent it from being deleted. The other options are not suitable for meeting the requirements, as they would either restrict the edit access or delete access for all users, regardless of ownership.

The Data Architect should consider the limitations on Org data storage and the Bulk API limitations on picklist fields when denormalizing the data model into a single Transaction object with a Branch Office picklist. The Org data storage limit is the total amount of data that can be stored in a Salesforce Org, and it depends on the edition and license type of the Org 1 . The Bulk API limit on picklist fields is the maximum number of values that can be imported or exported using the Bulk API, and it is 1,000 values per picklist field
2 . These limitations could affect the performance and scalability of the data model, and the Data Architect should plan accordingly.

Changing the master-detail relationship to a lookup relationship is the best solution for allowing the creation of generic discount requests without the custom product object as its master record. A lookup relationship allows you to create child records without requiring a parent record. It also gives you more flexibility in defining the sharing and security settings for each object