The best option to map the data to be used for both segmentation and identity resolution is to create custom fields on the standard Individual DMO. This way, the consultant can leverage the existing fields and functionality of the Individual DMO, such as identity resolution rulesets, calculated insights, and data actions, while adding the additional fields that are specific to the beauty company's data1. Creating a custom DMO from scratch or duplicating the standard Individual DMO would require more effort and maintenance, and might not be compatible with the existing features of Data Cloud. Creating a custom DMO with only the additional fields and mapping it to the standard Individual DMO would create unnecessary complexity and redundancy, and might not allow the use of the custom fields for identity resolution. References:
1: Data Model Objects in Data Cloud

Ensuring High Availability and Fault Tolerance:
High availability refers to systems that are continuously operational and accessible, while fault tolerance is the ability to continue functioning in the event of a failure.
Reference: Salesforce High Availability and Fault Tolerance Whitepaper
Data Distribution Across Multiple Regions and Data Centers:
Salesforce Data Cloud ensures high availability by replicating data across multiple geographic regions and data centers. This distribution mitigates risks associated with localized failures.
If one data center goes down, data and services can continue to be served from another location, ensuring uninterrupted service.
Reference: Salesforce Infrastructure Overview
Benefits of Regional Data Distribution:
Redundancy: Having multiple copies of data across regions provides redundancy, which is critical for disaster recovery.
Load Balancing: Traffic can be distributed across data centers to optimize performance and reduce latency.
Regulatory Compliance: Storing data in different regions helps meet local data residency requirements.
Reference: Salesforce Data Center Locations and Regional Data Hosting
Implementation in Salesforce Data Cloud:
Salesforce utilizes a robust architecture involving data replication and failover mechanisms to maintain data integrity and availability.
This architecture ensures that even in the event of a regional outage, customer data remains secure and accessible.
Reference: Salesforce Trust and Compliance Documentation

Understanding Unified Individual Profile:
The unified individual profile combines data from multiple sources to create a comprehensive view of each customer.
Reference: Salesforce Unified Profile Documentation
Issue with Latest Email Address:
If the latest email address is not being stored, the reconciliation rules, which determine how data from different sources is combined and updated, may be incorrectly configured.
Reference: Salesforce Data Reconciliation Overview
Reconciliation Rules:
These rules define which data source has priority and how conflicts are resolved when combining data.
Ensuring that these rules are correctly configured is essential for maintaining accurate and up-to-date profiles.
Reference: Salesforce Reconciliation Rules Guide
Steps to Troubleshoot:
Navigate to the reconciliation rules settings in Salesforce Data Cloud.
Review the current rules to ensure the correct handling of email addresses.
Verify that the rules prioritize the most recent data and handle duplicates appropriately.
Reference: Salesforce Reconciliation Rules Configuration Documentation

When setting up Data Cloud for a multi-brand organization, if a consultant cannot map an object for one of the brands during data stream setup, they should navigate to the Data Space tab and select the object to include it in the new data space. Here's why:
Understanding the Issue
The consultant is using data spaces to segregate data for different brands.
While mapping a data stream, they notice that an object is unavailable for one of the brands.
This indicates that the object has not been associated with the new data space.
Why Navigate to the Data Space Tab?
Data Spaces and Object Availability :
Objects must be explicitly added to a data space before they can be used in mappings or transformations within that space.
If an object is missing, it means it has not been included in the data space configuration.
Solution Approach :
By navigating to the Data Space tab , the consultant can add the required object to the new data space.
This ensures the object becomes available for mapping and use in the data stream.
Steps to Resolve the Issue
Step 1: Navigate to the Data Space Tab
Go to Data Cloud > Data Spaces and locate the new data space for the brand.
Step 2: Add the Missing Object
Select the data space and click on Edit .
Add the required object (e.g., a Data Model Object or Data Lake Object) to the data space.
Step 3: Save and Verify
Save the changes and return to the data stream setup.
Verify that the object is now available for mapping.
Step 4: Complete the Mapping
Proceed with mapping the object in the data stream.
Why Not Other Options?
A). Create a new data stream and map the second data stream to the data space :Creating a new data stream is unnecessary if the issue is simply object availability in the data space.
B). Copy data from the default data space to a new DMO using the Data Copy feature and link this DMO to the new data space :This is overly complex and not required if the object can simply be added to the data space.
C). Create a batch transform to split data between different data spaces :Batch transforms are used for data processing, not for resolving object availability issues.
Conclusion
The correct solution is to navigate to the Data Space tab and select the object to include it in the new data space . This ensures the object is available for mapping and resolves the issue efficiently.

To create a new data stream from a custom Salesforce CRM object, the consultant needs to confirm that the View All object permission is enabled in the source Salesforce CRM org. This permission allows the user to view all records associated with the object, regardless of sharing settings1. Without this permission, the custom object will not be available in the New Data Stream configuration2. References:
Manage Access with Data Cloud Permission Sets
Object Permissions