Clear the role field in the generic user record.

Create a role at top of role hierarchy and assign the role to the generic user.

Explanation:

Assigning a massive volume of records to a single user can cause severe performance degradation in sharing calculation. This is because Salesforce must continuously recalculate the sharing table for that user. The solution involves optimizing the sharing calculation by either removing the user from the role hierarchy (Option A) or placing them at the very top of it (Option C).

Correct Options:

A. 🟩 Clear the role field in the generic user record.: If a user has no role, they are excluded from the role hierarchy. This means no sharing calculations are triggered based on the hierarchy when records are assigned to them. This is a highly effective way to eliminate the performance overhead.

C. 🟩 Create a role at top of role hierarchy and assign the role to the generic user.: Placing the user at the top of the role hierarchy is also effective. A user at the top of the hierarchy inherently has access to all records below them. Therefore, no additional downward sharing calculations are needed when records are assigned to this top-level user.

Incorrect Options:

B. 🟥 Salesforce handles the assignment... no performance impact.: This is factually incorrect. The sharing recalculation for a user receiving a vast number of records is a known performance bottleneck. It is a documented architectural consideration that requires proactive mitigation, as described in the correct answers.

D. 🟥 Create a pool of generic users and distribute the assignment...: While distributing the load seems logical, it creates more problems than it solves. It complicates automation logic, makes reporting more difficult, and does not fully solve the issue as each user in the pool would still incur its own sharing calculation overhead, though smaller.

Reference:
Salesforce Help: Best Practices for Deploying to Large Data Volumes

Send customer record changes from Salesforce to the system of truth in real time.

Explanation:

With Salesforce as the system of record, the goal is to propagate accurate customer data changes to a central "system of truth" in real time. This ensures all downstream systems consuming from this central point have immediate access to the most current and accurate information, maintaining data integrity across the entire enterprise.

Correct Option:

C. ⚡ Send customer record changes from Salesforce to the system of truth in real time. This is correct because it ensures the central system of truth is updated instantaneously as changes occur in the system of record (Salesforce). This provides the single, most accurate version of the data for all other systems to consume, fulfilling the requirement for accuracy "at all times."

Incorrect Options:

A. 🕛 Send customer data nightly to the system of truth in a scheduled batch job. A nightly batch job creates a significant delay (up to 24 hours), meaning all other systems will be working with stale, inaccurate data for most of the day, violating the "accurate at all times" requirement.

B. 🕛 Send customer record changes from Salesforce to each system in a nightly batch job. This is the least efficient option. It creates the same data staleness issue as option A but also adds complexity by creating multiple point-to-point integrations instead of a single, streamlined integration to the central system.

D. 🔄 Have each system pull the record changes from Salesforce using change data capture. While Change Data Capture (CDC) is a real-time mechanism, having each system pull directly from Salesforce creates a complex integration architecture. It bypasses the designated central system of truth, leading to potential inconsistency and making data governance much more difficult.

Reference:
Salesforce Help: Change Data Capture

Implicit sharing will automatically handle with standard functionality.

Explanation:

This question tests knowledge of how Salesforce automatically handles access between parent and child records. If a user has access to a child object, Salesforce may grant automatic access to the parent, depending on the relationship type. In the Opportunity–Account relationship, Salesforce provides implicit sharing, which ensures users can see the Account when they already have access to its related Opportunity.

✅ Correct Option

B. Implicit sharing will automatically handle with standard functionality
Implicit sharing is a built-in Salesforce feature that gives users read-only access to parent records like Accounts when they have access to child records such as Opportunities or Cases. This behavior ensures data visibility and context without needing manual rules or teams. It simplifies administration by avoiding redundant sharing configurations while preserving security.

❌ Incorrect Options

A. Create a criteria-based sharing rule
Criteria-based sharing rules grant access to records that meet specific field conditions, but they don’t establish access between parent and child records. For example, you could share Accounts based on industry or location, but not because a user has access to a related Opportunity. This makes it unsuitable for the requirement.

C. Add appropriate users to the account team
Account teams are designed to provide manual or automated access to Account records by explicitly adding users with specific roles. However, this requires manual maintenance and does not solve the need for automatic inheritance of access from child Opportunities. It adds unnecessary complexity compared to implicit sharing.

D. Create an owner-based sharing rule
Owner-based sharing rules extend access based on record ownership, allowing records owned by certain users to be shared with others. Since the scenario requires access to Accounts based on related Opportunities rather than ownership, this option does not fulfill the requirement and would be misapplied.

Reference:
Salesforce Help: Implicit Sharing

Data duplication

Data accuracy and quality

Data standardization

Explanation:

A Master Data Management (MDM) solution is designed to create a single, authoritative source of truth for an organization's critical data, such as customer information. The primary issues described (data duplicated across systems, not in sync, and customer complaints about repeated emails) are classic symptoms of a lack of MDM.

✅ C. Data duplication:
This is the core problem MDM solves. It identifies and merges duplicate records across various systems (e.g., Service Cloud, Marketing Cloud, Data Warehouse) to create a single, golden record.

✅ D. Data accuracy and quality:
By centralizing and managing customer data in a single system, an MDM tool ensures that information is accurate and consistent across the enterprise. It provides a governed process for updates, preventing conflicting information from being stored in different places.

✅ E. Data standardization:
MDM enforces consistent data formats, values, and rules across all systems. For example, it can standardize address formats or naming conventions, which is critical for clean, usable data. The problem of customers having to call in to update their information in multiple places is a symptom of poor standardization.

❌ A. Data completeness:
While an MDM solution can help with completeness by merging data from various sources, it is not its primary function. Its main purpose is to manage the "master" data, not to ensure every field is filled out, which is typically a data governance and business process issue.

❌ B. Data loss and recovery:
This is incorrect. Data loss and recovery are functions of backup and disaster recovery systems, not MDM. MDM focuses on managing data consistency and quality, not on recovering data from a system failure.

Use SF Connect to virtualize the data in SF and avoid storage limits.

Explanation:

UC needs to provide Sales Cloud users with access to order data from an on-premise database without exceeding Salesforce storage limits. The solution must balance seamless data access with efficient storage management. Virtualizing data using Salesforce Connect is ideal, as it allows real-time access to external data without storing it in Salesforce, addressing both user needs and storage constraints effectively.

Correct Option:

✅ B. Use SF Connect to virtualize the data in SF and avoid storage limits.
Salesforce Connect enables UC to access order data from the on-premise database in real-time via REST API, presenting it as external objects in Sales Cloud. This avoids storing data in Salesforce, bypassing storage limits while providing seamless access for users. It’s scalable, efficient, and leverages native Salesforce functionality for a smooth user experience.

Incorrect Options:

❌ A. Migrate and persist the data in SF to take advantage of native functionality.
Migrating and storing all order data in Salesforce would consume significant storage, potentially exceeding UC’s limits. While it enables native functionality, it’s impractical given UC’s explicit concern about storage constraints, making this approach less suitable for their needs.

❌ C. Develop a bidirectional integration between the on-premise system and Salesforce.
Bidirectional integration involves syncing data between systems, which still requires storing data in Salesforce, risking storage limit issues. It’s more complex and resource-intensive than virtualization, and doesn’t directly address UC’s need to avoid storage consumption while providing data access.

❌ D. Build a UI for the on-premise system and iframe it in Salesforce.
Embedding an external UI via iframe provides access but disrupts the native Salesforce user experience. It may introduce security concerns, performance issues, and lacks integration with Salesforce features like reporting, making it an inefficient solution for UC’s requirements.

Reference:
Salesforce Help: Salesforce Connect
Salesforce Help: External Objects