To provide the sales team with the required functionality, a data architect should use a mashup page that will present the billing system records within Salesforce. A mashup page is a web page that combines data from multiple sources into a single integrated view. A mashup page can be created using Visualforce or Lightning Web Components, and can use Salesforce Connect or custom integrations to access external data from the on-premise web-based billing and invoice system. This will allow the sales team to pull a customer record and view their account status, invoice history, and opportunities without navigating outside of Salesforce. Option A is incorrect because creating a custom object and migrating the last 12 months of invoice data into Salesforce so it can be displayed on the account layout will consume a lot of storage space and may not reflect the latest data from the billing system. Option B is incorrect because writing an Apex callout and populating a related list to display on the account record will require additional development effort and may not be scalable or performant for large volumes of data. Option D is incorrect because creating a visual force tab with the billing system encapsulated within an iframe will not allow the sales team to view the billing system records within the customer record, but rather in a separate tab.

Option B is correct because data model is a key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Data model describes the structure and relationship of data entities within an organization2. Option C is correct because integration specification is another key artifact that an architect should use to document the data architecture for a multi-system, enterprise Salesforce implementation1. Integration specification defines the scope, requirements, design, testing, and deployment of integration solutions between Salesforce and other systems3. Option A is not correct because user stories are not key artifacts for documenting the data architecture, but agile development tools that capture the features and functionalities that users want from a system4. Option D is not correct because non-functional requirements are not key artifacts for documenting the data architecture, but quality attributes that specify how well a system performs its functions.

Evaluating a third-party AppExchange app, such as OwnBackup or Spanning, etc., for backup and archival purposes is the best approach to address the requirement of having a one-day SLA for any data loss. These apps can provide automated backups, granular restores, and compliance features that can help UC recover from any data loss or corruption scenarios.

Using Salesforce Bulk API in parallel mode can reduce the migration time by processing multiple batches of records simultaneously and leveraging the server resources more efficiently. The Bulk API is designed for loading large amounts of data into Salesforce

According to Trailhead2, record types are a feature that allows administrators to create different business processes, page layouts, and picklist values for different types of records within an object. Record types can be used to maintain different dealer types in Salesforce by creating record types for each of the dealer types and assigning them appropriate attributes, processes, and rules. Option A is the correct answer because it suggests using Accounts for dealers, and creating record types for each of the dealer types. Option B is incorrect because creating dealers as Accounts, and building custom views for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option C is incorrect because using Accounts for dealers and custom picklist field for each of the dealer types does not allow CRM users to enter only attributes related to the customer types, nor does it enable different processes and business rules for each of the customer types. Option D is incorrect because creating Custom objects for each dealer types and custom fields for dealer attributes can be unnecessary and complex, as it requires creating multiple objects and relationships instead of using the standard Account object.