MCB Data Cloud Certification Practice Exam

Why is the newly created field "Business Priority" not available in the Salesforce data stream?

1. The Salesforce Integration User lacks Read permissions on the field.

2. The Salesforce Data Loader must be used to upload data.

3. Custom fields on the Case object are unsupported.

4. The field will be added after the data stream refreshes in 24 hours.

The correct answer is: The Salesforce Integration User lacks Read permissions on the field.

The correct answer highlights the importance of user permissions within Salesforce, particularly how they affect data visibility in operations like data streams. If the Salesforce Integration User, which is typically used for automated tasks and integrations, lacks Read permissions on the "Business Priority" field, this means that the user is not authorized to access or interact with that field. Consequently, without the necessary permissions, the field would not be recognized or included in the data stream, rendering it unavailable for downstream processes. Understanding Salesforce's permission model is crucial, as it governs what data is accessible and to whom. In scenarios involving integrations or data operations, permission settings must be properly configured to ensure all relevant data fields are included in the necessary workflows or streams. The other options relate to different aspects of Salesforce’s functionality but do not address the root cause of the unavailability of the field in the data stream due to permission settings. For instance, using the Data Loader for uploads is a different process and does not influence stream access. Meanwhile, the statement about custom fields being unsupported is inaccurate, as Salesforce does support custom fields in many contexts. Lastly, the field's availability being contingent on a 24-hour refresh is typically not how Salesforce operates, as fields can be recognized immediately after permissions are correctly