Universal Containers has a legacy client server app that has a relational database that needs to be migrated to Salesforce.
What are the three key actions that should be done when data modeling in Salesforce? (Choose three.)

Universal Containers (UC) loads bulk leads and campaigns from third-party lead aggregators on a weekly and monthly basis. The expected lead record volume is 500K records per week, and the expected campaign records volume is 10K campaigns per week.
After the upload, Lead records are shared with various sales agents via sharing rules and added as Campaign members via Apex triggers on Lead creation. UC agents work on leads for 6 months, but want to keep the records in the system for at least 1 year for reference. Compliance requires them to be stored for a minimum of 3 years. After that, data can be deleted. What statement is true with respect to a data archiving strategy for UC?

Universal Containers wishes to maintain Lead data from Leads even after they are deleted and cleared from the Recycle Bin. What approach should be implemented to achieve this solution?

Northern Trail Outfitters has these simple requirements for a data export process:
1. File format should be in CSV.
2. Process should be scheduled and run once per week.
3. The export should be configurable through the Salesforce UI.
Which tool should a data architect leverage to accomplish these requirements?

Universal Containers (UC) wants to store product data in Salesforce, but the standard Product object does not support the more complex hierarchical structure which is currently being used in the product master system.
How can UC modify the standard Product object model to support a hierarchical data structure in order to synchronize product data from the source system to Salesforce?