Key stakeholders from both systems should collaborate with the Architect to determine which system is the system of record on a field level is what the Architect should do to achieve this goal of integrating two different systems with customer records into the Salesforce Account object using Master Data Management.
The system of record is the authoritative source of truth for a given entity or field in a given context. Different systems may have different levels of accuracy, completeness, timeliness, or relevance for different fields.
Therefore, it is important to involve key stakeholders from both systems who have knowledge and expertise about their data quality and business needs to decide which system should be the system of record for each field. The Architect should facilitate this collaboration and document the decisions and rationale for each field. The other options are not correct or feasible, as they would either delegate or abdicate the responsibility of determining the system of record, ignore or disregard the input from key stakeholders, or assume or impose a default system of record without considering the data quality and business needs.

According to the exam guide, one of the objectives is to " describe the use cases and considerations for using various tools and techniques for data migration (for example, Data Loader, Bulk API) " 1 . This implies that option B is the correct way to extract large volumes of data from Salesforce. The Bulk API is designed to handle large-scale data operations and avoid timeouts. Option A is not correct because the SOAP API is not optimized for large data sets and may encounter limits. Option C is not correct because GZIP compression does not prevent timeouts, but rather reduces the size of the data transferred. Option D is not correct because Batch Apex is used to process records asynchronously in Salesforce, not to export data to an external system.

IP restrictions can be used to prevent users from accessing Salesforce from outside the company network or VPN. According to this article, sharing settings can be used to control access to customer information based on record ownership. According to this article, custom Apex can be used to support customer requests for removal of their information from Salesforce.

Identifying a location to store archived data and using scheduled batch jobs to migrate and purge the aged data on a nightly basis can be a way to meet the requirements for an archive solution. The article provides a use case of how to use Heroku Connect, Postgres, and Salesforce Connect to archive old data, free up space in the org, and still retain the option to unarchive the data if needed. The article also explains how this solution can improve Salesforce performance and meet data retention policies.

The recommended solution for Universal Containers (UC) to implement its new Internet of Things technology is to create a new Container Reading custom object with a master-detail relationship to Container which is created when a new measure is received for a specific container. Implement an archiving process that runs every hour. This solution would allow UC to store and access current and historical temperature and humidity data for each container on Salesforce, and use reports and dashboards to analyze it. However, since UC expects a large volume of data over time, they should implement an archiving process that moves data off-platform after a certain period of time to avoid hitting the Org data storage limit and maintain optimal performance. The other options are not recommended, as they would either not store the historical data on Salesforce, or create too many custom fields on the Container object that could impact performance and usability.