Troubleshooting practice questions

The Connected App callback URL and OAuth scopes

Why wrong: Connected Apps are used for Salesforce-to-Salesforce or internal API integrations, not AWS S3 bucket credentials.

The Marketing Cloud Connector user profile settings

Why wrong: Marketing Cloud Connector settings are irrelevant to AWS S3 storage integrations.

The Einstein Trust Layer activation guardrails

Why wrong: Einstein Trust Layer governs generative AI interactions and has no role in S3 export authentication.

The Einstein Studio model training metrics.

Why wrong: Einstein Studio metrics evaluate machine learning model accuracy, not activation job status.

The Salesforce Core Setup Audit Trail.

Why wrong: Salesforce Core Audit Trail tracks CRM setup changes, not Data Cloud activation publish pipelines.

The Marketing Cloud Journey Builder analytics dashboard.

Why wrong: Journey Builder tracks messaging performance, not Data Cloud backend publishing pipelines.

Marketing Cloud Engagement requires Real-Time Data Graph activation for all Calculated Insights.

Why wrong: Real-Time Data Graph is used for streaming unified profiles, not as a strict prerequisite for batch Calculated Insights activation.

Calculated Insights cannot be exported to Marketing Cloud Engagement due to API limits.

Why wrong: Calculated Insights are routinely used for activation in Marketing Cloud Engagement via standard publishing mechanisms.

Activation targets only support streaming data streams, not batch-based Calculated Insights.

Why wrong: Activation targets can consume batch data, provided the Calculated Insight outputs are correctly mapped to activation-enabled DMOs.

Einstein Trust Layer generative AI moderation guardrails.

Why wrong: Einstein Trust Layer governs AI prompts and responses, not cloud file storage exports.

Salesforce Core CRM Profile object sharing rules.

Why wrong: Core CRM sharing rules do not apply to Data Cloud cloud storage exports.

Marketing Cloud Engagement API connection scopes and OAuth credentials.

Why wrong: Marketing Cloud credentials are irrelevant to Cloud File Storage targets.

Recreate the Identity Resolution ruleset to clear transaction locks.

Why wrong: Identity resolution has no impact on webhook endpoint response timeouts.

Increase the Data Cloud activation target chunk size to 1 million records per request.

Why wrong: Increasing payload size will worsen timeout issues by increasing processing time per request.

Switch the activation target type from webhook to cloud storage.

Why wrong: Changing target types changes the architecture entirely rather than troubleshooting the webhook timeout.

Configuring an activation target with an invalid webhook URL.

Why wrong: Activation targets are completely separate from Calculated Insight compilation.

Failing to enable Salesforce Shield Platform Encryption on the user profile.

Why wrong: Shield encryption status does not cause Calculated Insight SQL compilation failures.

Increase the activation target polling frequency.

Why wrong: Activation targets do not affect identity resolution matching output.

Delete all data spaces and reinstall the Data Cloud package.

Why wrong: Reinstalling packages is unnecessary and destructive.

Modify the Apex controller class in Sales Cloud to trigger the API push.

Why wrong: Ingestion API operates independently via REST endpoints and does not require Sales Cloud Apex controllers.

Update the Identity Resolution match rules to resolve duplicate source records.

Why wrong: Identity Resolution occurs downstream after ingestion; failing ingestion prevents records from reaching DLOs in the first place.

Switch all reconciliation rules from Source Sequence to Longest String.

Why wrong: Reconciliation rules govern field survivorship, not profile linking counts.

Delete all data spaces and restart the entire Salesforce CRM instance.

Why wrong: Restarting the CRM instance is destructive and unnecessary.

Reconciliation rules were set to Most Recent instead of Source Sequence.

Why wrong: Reconciliation rules determine survivorship after records are linked, not whether matching occurs.

Data Cloud requires manual SQL triggers to activate e-commerce data streams.

Why wrong: Data streams run automatically upon ingestion configuration.

The Unified Individual DMO is missing an activation target assignment.

Why wrong: Activation targets have no impact on the identity resolution matching engine.

Increase data stream ingestion frequency from hourly to real-time.

Why wrong: Increasing ingestion frequency would increase the workload and worsen timeout issues.

Restart the core Salesforce CRM production server.

Why wrong: Restarting CRM servers has no impact on Data Cloud background execution jobs.

Switch the reconciliation rule to Highest Frequency.

Why wrong: Reconciliation rules execute after matching; they do not resolve matching phase timeout exceptions.

Unix Epoch timestamp integer (e.g., 1698000000)

Why wrong: Unix epoch integers are not standard for Data Cloud timestamp fields without conversion formulas.

RFC 2822 email date format

Why wrong: RFC 2822 is not supported natively.

US Standard format (MM/DD/YYYY HH:MM AM/PM)

Why wrong: US regional formats cause parsing failures.

The segment was published during off-peak hours.

Why wrong: Publish timing has no impact on attribute cardinality or export row duplication.

The Salesforce CRM license count is too low.

Why wrong: License counts do not affect activation record grain or duplication.

The segment type is set to streaming instead of batch.

Why wrong: Streaming vs batch does not inherently cause duplicate export rows due to related attributes.

Check the core CRM Apex code coverage for all triggers in the organization.

Why wrong: Apex code coverage has no impact on Data Cloud CRM data streams.

Verify that all Data Model Objects have been converted to custom Salesforce objects in Object Manager.

Why wrong: Data Model Objects are native to Data Cloud and are not converted to core CRM custom objects.

Standard CRM objects must be manually recreated as custom Data Source Objects before streaming.

Why wrong: Standard bundles automatically generate Data Source Objects and Data Model Objects upon activation.

The connected CRM org's API version is set higher than Data Cloud supports.

Why wrong: Salesforce handles API version compatibility automatically for native CRM connectors.

The Salesforce CRM connector requires manual Apex trigger creation for every object to be streamed.

Why wrong: Salesforce CRM data streams use standard out-of-the-box change data capture and batch sync mechanisms, not manual Apex triggers.

Calculated Insights stripped out historical records older than 90 days.

Why wrong: Calculated Insights do not alter base DMO data retention unless explicitly truncated.

Batch segmentation only processes the first 10 million records by default.

Why wrong: Batch segmentation processes all matching records without an arbitrary 10 million record cap.

Streaming segments overwrite batch segment membership automatically.

Why wrong: Streaming and batch segments are separate entities and do not overwrite each other unexpectedly.

CASE statements are not supported in Data Cloud Calculated Insights; IF-THEN functions must be used instead.

Why wrong: ANSI SQL CASE statements are fully supported in Calculated Insights.

CASE statements can only reference dimensions, never measures.

Why wrong: CASE statements can evaluate both dimensions and measures in ANSI SQL.

CASE statements must be wrapped inside an aggregate function like SUM() or COUNT().

Why wrong: CASE statements can evaluate conditions independently or wrap inside aggregates, but they are not strictly required to be wrapped inside an aggregate depending on the logic.

Rebuild the segment using a Calculated Insight instead of related object filters.

Why wrong: While CIs can help, rebuilding an entire segment architecture without addressing the underlying query complexity or relationship mapping is inefficient.

Convert the segment into a streaming segment to bypass the batch publishing engine.

Why wrong: Converting a complex multi-object segment with historical order data into a streaming segment is usually impossible due to streaming DMO requirements.

Increase the Data Cloud tenant storage limit to allow more memory for processing.

Why wrong: Timeout errors during segment publishing are typically caused by inefficient query execution plans or data volume scale, not tenant storage limits.

Whether the Calculated Insight is scheduled as streaming or batch.

Why wrong: Calculated Insights have their own scheduling and execution engine types, but incorrect values are primarily a logic or data issue.

The activation target format configured for the resulting segment.

Why wrong: Activation targets are downstream and do not affect the internal calculation logic of a Calculated Insight.

Verify that the Activation Target authorization token is active.

Why wrong: Activation targets do not impact Calculated Insight calculation or execution.

Check that the underlying Data Stream ingestion schedule is set to streaming mode.

Why wrong: Calculated Insights do not require source streams to be streaming.

Confirm that the Segment Canvas refresh schedule matches the Calculated Insight run time.

Why wrong: Segments and Calculated Insights operate on their own independent schedules.