Salesforce Data-Architect Exam With Confidence Using Practice Dumps

The best data archiving strategies for UC are to use Big objects and Heroku with external objects. Big objects allow storing large amounts of data on the Salesforce platform without affecting performance or storage limits. They also support point-and-click tools, triggers, and Apex code. Heroku is a cloud platform that can host external databases and integrate with Salesforce using external objects. External objects enable on-demand access to external data sources via standard Salesforce APIs and user interfaces. Using bulk API to hard delete cases from Salesforce will free up storage space and improve performance.

The recommended data model for consumer account data to be stored in Salesforce is to use the Account object with Person Accounts and a new B2C page layout. Person Accounts are a special type of accounts that allow you to store information about individual consumers who are not associated with a business account2. Person Accounts have the following advantages3:

They allow you to use the same standard objects and features that you use for business accounts, such as contacts, opportunities, cases, etc.

They enable you to create different page layouts and record types for B2C and B2B customers, which allows you to customize the user interface and business logic for each segment.

They support large data volumes and can scale up to 50 million records or more, which meets the expected growth of consumers over the next five years.

According to Trailhead2, Salesforce Connect is a feature that allows administrators to integrate external data sources with Salesforce without copying or synchronizing the data. Salesforce Connect can use external objects to display the external data in Salesforce as if it were stored in Salesforce objects, enabling seamless user experience and real-time access. Option B is the correct answer because it suggests using Salesforce Connect and an external object to display the order history in Salesforce. Option A is incorrect because using an Apex callout to populate a text area field for displaying the order history can be inefficient and unreliable, as it requires making an HTTP request for each customer record and storing the order history as unstructured text. Option C is incorrect because importing the order history into a custom Salesforce object, update nightly can consume a lot of storage space and cause data latency, as the order history may change more frequently than once a night. Option D is incorrect because embedding the ERP system in an iframe and displaying on a custom tab can degrade the user experience and security, as it requires switching between tabs and authenticating with another system.