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

Implement shield platform encryption to encrypt files.

Explanation:

This question involves encrypting sensitive file data in Salesforce. Shield Platform Encryption is the native, Salesforce-managed solution that provides encryption at rest for files and attachments without disrupting standard functionality. It is the recommended approach for robust, built-in security.

Correct Option:

A. 🛡️ Implement Shield Platform Encryption to encrypt files. This is the correct answer because Shield Platform Encryption is Salesforce's native solution designed specifically for this purpose. It encrypts files (attachments, Salesforce Files) at rest transparently, maintains field-level security, and complies with stringent regulatory requirements without custom code.

Incorrect Options:

B. 🔐 Use classic encryption to encrypt files. "Classic Encryption" is not a specific Salesforce feature for files. It may refer to older, less secure methods or custom encryption, which is complex to maintain, could break functionality, and may not be compliant, unlike the managed Shield solution.

C. 📦 Implement 3rd-party AppExchange app to encrypt files. While an AppExchange app could work, it is an unnecessary overhead when a native, Salesforce-supported solution (Shield) exists. A third-party app introduces additional licensing costs, maintenance, and potential integration points of failure.

D. 🌐 Store files outside of Salesforce and access them in real time. This violates the core requirement of storing files in Salesforce. It adds significant complexity for integration, security, governance, and auditing, making it an inefficient and insecure workaround.

Reference:
Salesforce Help: Encrypt Files and Attachments with Shield Platform Encryption

Utilize the Authorization Form Consent object to capture the consent.

Explanation:

✅ C. Utilize the Authorization Form Consent object:
This is correct. Salesforce provides a standard, ready-to-use object called AuthorizationFormConsent specifically designed to track customer consents for purposes like marketing. Using this native object ensures best practices and compliance without custom development.

❌ A. Use custom fields...:
This is incorrect. While adding a single checkbox field is simple, it lacks the robustness to properly track consent details like the consent date, expiration, version of the form, or the channel it was collected through.

❌ B. Create a custom object...:
This is incorrect. Although a custom object could be built to replicate the functionality, it is unnecessary. Salesforce already offers a standard object for this exact purpose, which saves development time and aligns with platform best practices.

❌ D. Use AppExchange solution...:
This is incorrect. While AppExchange solutions exist, it is not the first recommendation. Before seeking a third-party paid tool, a data architect should always evaluate if Salesforce's native functionality can meet the requirement, which it can in this case.

Summary:
The requirement is to build a solution for capturing and managing customer marketing consent, which is a common regulatory need (like GDPR). The solution must natively handle consent details like status, date, and channel.

Reference:
Salesforce Help: About the Consent Data Model

validation Rule

Explanation:

✅ A. Validation Rule:
This is the correct solution. A Validation Rule can check the values across both the Phone and Email fields. It can prevent a record from being saved if both fields are empty, perfectly enforcing the "either/or" conditional requirement.

❌ B. Required Fields:
This is incorrect. Marking both fields as "required" would force users to enter data into both fields. This is stricter than the requirement, which only needs one of the two to be populated.

❌ C. Apex Class:
This is incorrect. While an Apex trigger could be written to enforce this, it is overly complex for this simple declarative need. Validation Rules are the standard, easier-to-maintain tool for this type of data quality check.

❌ D. Process Builder:
This is incorrect. Process Builder is an automation tool for triggering actions, not for validating data and preventing a record from being saved. It cannot stop a save operation if the requirement isn't met.

Summary:
The business requires that every customer account registration must include either a phone number or an email address. This is a conditional requirement that depends on the data in two different fields.

Reference:
Salesforce Help: Validation Rules

Use data loader to export the data from source org and then import or Upsert into the target org in sequential order.

Create a external id field for each object in the target org and map source record ID’s to this field.

Replace source record ID’s with new record ID’s from the target org in the import file.

Explanation:

During migration, preserving relationships is key. Since Salesforce record IDs change between orgs, the strategy must rely on external IDs and sequential migration order. The process involves mapping source IDs to external IDs, exporting/importing in correct sequence, and replacing old IDs with the new ones in child records.

Correct Options

A. 🟢 Use Data Loader to export the data from source org and then import or Upsert into the target org in sequential order
Loading in sequence (parents first, then children) ensures references are valid. This prevents orphan records and maintains hierarchy.

B. 🔴 Create an external ID field for each object in the target org and map source record IDs to this field
External IDs act as anchors, letting you map relationships across orgs. They’re especially useful when upserting data during migration.

D. 🟡 Replace source record IDs with new record IDs from the target org in the import file
Because record IDs are org-specific, you must update child references with the corresponding new IDs in the target org after the parent records are inserted.

Incorrect Options

C. 🔵 Redefine the master-detail relationship fields to lookup relationship fields in the target org
This alters the data model unnecessarily. NTO wants to preserve relationships exactly, not weaken them.

E. 🟠 Keep the relationship fields populated with the source record IDs in the import file
Source IDs are meaningless in the target org, so relationships would break. They must be replaced or mapped using external IDs.

Reference:
Salesforce Help – Best Practices for Data Migration