Hard Difficulty Questions

The connected user was not assigned the Data Cloud Admin permission set in Salesforce CRM.

Why it fails: Data Cloud Admin is a Salesforce CRM permission set governing Data Cloud features, not Marketing Cloud API scopes; the connected Marketing Cloud user needs Marketing Cloud permissions such as the Data Cloud integration user role. It tempts because permission-set misassignment commonly causes connector failures, but the wrong platform's permission set is being checked.

The Marketing Cloud tenant URL was entered using HTTP instead of HTTPS.

Why it fails: An HTTP versus HTTPS tenant URL affects transport security and connector reachability, not the connected user's authorisation to read Marketing Cloud objects, so streams would fail on authentication or permission errors rather than initialisation. It tempts because URL scheme errors do break connectors, but the stem specifies a permissions failure.

The Marketing Cloud Business Unit was not mapped to a Data Space.

Why it fails: Business Unit to Data Space mapping controls which data lands where after ingestion, not whether the connector authenticates; unmapped spaces cause ingestion or routing errors, not initialisation failures. It tempts because Data Space configuration is a required connector step, but the stem's symptom is the connected user lacking permissions.

Reject orders not denominated in USD during the S3 batch file upload.

Why it fails: Rejecting non-USD orders discards valid EUR and GBP transactions, so totals omit two-thirds of revenue. Currency harmonisation requires converting each order to a common currency using exchange rates during transformation. Rejection suits filtering out malformed or test records, not normalising multi-currency financial data.

Store all monetary amounts as text strings and let SQL queries perform manual string stripping.

Why it fails: Text storage prevents numeric aggregation, and string stripping cannot apply currency-specific rates. Monetary fields must be stored as numeric values with currency codes, then converted during harmonisation so Calculated Insights can sum a single normalised currency accurately.

Hardcode an exchange rate multiplier in an Apex trigger during ingestion.

Why it fails: Hardcoding a single multiplier in Apex cannot convert three currencies correctly and bypasses Data 360's harmonisation tooling. Currency conversion belongs in the transformation and modelling layer, where per-record rates are applied before Calculated Insights aggregate the normalised values.

By setting an activation attribute flag for encryption.

Why it fails: Activation attributes carry demographic data, not encryption instructions.

By writing a custom encryption script in a Data Transform before export.

Why it fails: Data transforms process data rows, they do not manage enterprise cryptographic key ceremonies.

By enabling HTTPS TLS 1.3 on the activation target connection string.

Why it fails: TLS encrypts data in transit, not data at rest in storage targets.

Export the data to Tableau, merge the profiles, and re-import via API.

Why it fails: Identity resolution runs inside Data 360 using match and reconciliation rules; exporting to Tableau and re-importing via API bypasses that engine entirely. Tableau is a visualisation tool, appropriate for reporting on unified profiles, not for performing the merge itself.

Modify the Data Model Object primary key to be a composite name key.

Why it fails: Identity resolution matches on configured match rules, not on Data Model Object primary keys; altering the key does not add fuzzy name comparison. Composite keys suit uniqueness constraints, whereas normalised name match rules handle spelling variations.

Write an Apex trigger to normalize names prior to data stream ingestion.

Why it fails: Apex triggers cannot run before data stream ingestion, so names stay unnormalised when match rules execute. Normalisation belongs in the ingestion transform or a calculated field. Apex is for record-level automation after data lands, which is why it tempts here.

Create manual database constraints in the underlying Data Lake Object storage.

Why it fails: Identity Resolution matches and reconciles source profiles through match rules and reconciliation rules configured in Data Cloud; it does not create database constraints in the Data Lake Object storage layer. Manual constraints are tempting because Data Cloud stores data in Data Lake Objects, but those govern storage structure, not profile unification logic.

Execute a batch SOQL query via Data Loader to export merged profiles.

Why it fails: Identity Resolution runs as a batch process within Data Cloud, producing unified profiles in the Unified Profile object; exporting merged profiles via Data Loader is an output activity, not a configuration step. Data Loader is tempting for bulk data movement, but it neither defines match rules nor reconciles records.

Write a custom Apex trigger to merge duplicate contact records in Sales Cloud.

Why it fails: Identity Resolution runs inside Data Cloud using match and reconciliation rulesets; Apex triggers operate on Sales Cloud records and cannot unify Data Cloud profiles. It is tempting because deduplication sounds similar, and would be correct for merging duplicate CRM records within Sales Cloud itself.

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

Why it fails: Reconciliation rules only decide which source value survives once records already match; they never determine whether a match occurs. Source Sequence versus Most Recent affects field survivorship, so this cannot explain records with identical emails failing to merge.

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

Why it fails: Data Cloud ingests and harmonises streams through configured connectors and data streams; no manual SQL triggers exist for activation. This is tempting because stream activation sounds relevant, but identity resolution merges records via match rules, not SQL execution.

The Unified Individual DMO is missing an activation target assignment.

Why it fails: Activation target assignment governs where a Unified Individual is published, such as to a data space or activation platform. It has no bearing on match processing; failed merges despite matching emails point to match rule or reconciliation configuration instead.

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

Why it fails: Real-time ingestion increases processing volume and load, worsening the memory and timeout exception. It is tempting because real-time streams suit low-latency use cases, and would be correct when the business requires immediate data availability rather than batch processing.

Restart the core Salesforce CRM production server.

Why it fails: Restarting the CRM server does not address the Identity Resolution batch job's memory or timeout limits, which run on Data 360 infrastructure. It is tempting because restarting clears transient faults, and would be correct if the CRM application itself were unresponsive.

Switch the reconciliation rule to Highest Frequency.

Why it fails: Highest Frequency changes which value survives reconciliation, not the match rule's memory footprint, so the timeout persists. It is tempting because reconciliation settings affect job behaviour, and would be correct when resolving conflicting field values between matched profiles.

The Individual DMO is locked and does not accept outgoing foreign key relationships.

Why it fails: Standard DMOs accept incoming relationships from custom or other standard DMOs.

Custom DMOs cannot have relationships with standard DMOs under any circumstances.

Why it fails: Custom DMOs can be related to standard DMOs.

Standard DMO relationships can only be established using SQL queries in Calculated Insights.

Why it fails: Relationships are defined in the Data Model UI canvas.

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

Why it fails: 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 it fails: Data Model Objects are native to Data Cloud and are not converted to core CRM custom objects.

Configure Activation Targets to automatically shift timestamps by the recipient's UTC offset.

Why it fails: Activation targets transmit payloads as configured; they do not perform dynamic time zone conversions.

Modify the Data Lake Object primary key data type from Timestamp to Text.

Why it fails: Changing primary keys to text breaks temporal comparison functions entirely.

Change the Data Cloud instance timezone setting in Setup.

Why it fails: Data Cloud stores all temporal data in UTC; instance-level display settings do not alter backend segment date evaluations.

Calculated Insights only support Standard SQL and do not permit aggregate functions like AVG().

Why it fails: Calculated Insights fully support aggregate functions like AVG, SUM, and COUNT.

The AOV result is stored as a text field instead of a numerical measure.

Why it fails: Measures in Calculated Insights must be numeric, but the error relates to dimension mapping.

The query references a streaming data model object directly without a time window.

Why it fails: Streaming DMOs can be used in Calculated Insights with proper aggregation.

Custom API calls

Why it fails: Custom API calls require bespoke development and authentication handling, and they do not render Data Cloud calculated insights natively on a Lightning record page. They are tempting because APIs do expose Data Cloud data programmatically, which suits external systems or middleware integrations rather than embedded record-page display.

Visualforce Page

Why it fails: Visualforce renders custom pages using Apex controllers, so displaying Data Cloud insights demands bespoke controller code and offers no standard Data Cloud record-page component. It is tempting because Visualforce can embed on record pages, but it is legacy UI technology rather than the supported integration for calculated insights.

Salesforce Flow

Why it fails: Salesforce Flow automates records and business processes but has no native component that surfaces Data Cloud calculated insights on a Lightning record page. It is tempting because Flow can call external services, yet that requires custom Apex or HTTP callouts rather than the purpose-built Data Cloud record-page component.

The data space must be deleted and re-provisioned for rule changes to take effect.

Why it fails: Data spaces isolate data and metadata but deleting one destroys all contained data; rule changes never require re-provisioning. Re-provisioning is relevant when setting up a new data space or correcting provisioning faults, not when applying updated match rules.

Match rule changes only apply to newly ingested data and cannot re-evaluate historical profiles.

Why it fails: Match rules do re-evaluate historical profiles during the next identity resolution run; they are not limited to newly ingested data. Restricting rules to new data would be relevant only if the ruleset were configured to run in a limited scope, which is not the default behaviour.

Unified profiles are cached for exactly 30 days and cannot be cleared manually.

Why it fails: Unified profiles are not cached for 30 days; identity resolution recalculates on a scheduled batch cycle, so counts and links lag until the next run completes. Caching is not the mechanism — the reconciliation job is. A 30-day cache would be relevant to long-lived session tokens, not profile unification.

Calculated Insights stripped out historical records older than 90 days.

Why it fails: Calculated Insights compute derived metrics; they do not delete source records or sever foreign keys to Unified Individual. It is tempting because retention windows exist elsewhere in Data 360, but the missing keys stem from identity resolution failing to match profiles, not from insight retention.

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

Why it fails: Batch segmentation has no fixed 10-million-record cap; it processes the full segment population. It is tempting because large volumes do affect processing time, but the missing foreign keys indicate identity resolution did not link those Engagement DMO records to a Unified Individual, not a row limit.

Streaming segments overwrite batch segment membership automatically.

Why it fails: Streaming and batch segments maintain separate membership; streaming does not overwrite batch results. It is tempting because both segment types can target the same population, but the absent foreign keys point to identity resolution failing to unify those profiles, not segment-type interference.

Write an Apex transformation class to replace pipes with commas.

Why it fails: Apex transformations run after ingestion, so pipes would already have been parsed as a single column before replacement, corrupting the schema. Apex suits complex row-level business logic, not delimiter handling. The delimiter belongs in the data stream's file format settings, applied at read time.

Rename the file extension from `.csv` to `.pipe` so Data Cloud auto-detects it.

Why it fails: Data Cloud detects delimiters from file content during schema parsing, not from the file extension, so renaming to .pipe changes nothing and may break ingestion. Extension-based detection is irrelevant here; the correct approach sets the delimiter explicitly in the data stream's file format configuration.

Convert all files to JSON because CSV does not support custom delimiters.

Why it fails: CSV parsing in Data Cloud accepts a configurable delimiter, so pipes can be declared directly in the source format settings; converting to JSON is unnecessary. JSON suits semi-structured, nested payloads, and would be the right choice only when the source emits hierarchical objects rather than flat delimited rows.

Data Cloud configuration is fully preserved and requires no manual intervention after a sandbox refresh.

Why it fails: Data Cloud connections and data streams are not fully preserved through a sandbox refresh; the connection breaks and streams fail until reconfigured. It is tempting because most Salesforce metadata is copied, so administrators expect Data Cloud configuration to survive intact without intervention.

Data Cloud data streams automatically switch to mock test data after a sandbox refresh.

Why it fails: Data Cloud does not substitute mock test data after refresh; streams simply fail because the connection to the underlying storage is broken. It is tempting because sandboxes are used for testing, suggesting synthetic data might be generated automatically, but no such mechanism exists.

Sandbox refreshes automatically clone all data lakes and S3 buckets linked to Data Cloud.

Why it fails: Sandbox refreshes do not replicate Data Cloud data lakes or their underlying S3 storage; those connections break and must be reconfigured. It is tempting because Salesforce metadata is copied on refresh, leading admins to assume associated external storage is cloned alongside it.

Recreate the Identity Resolution ruleset to clear transaction locks.

Why it fails: Identity Resolution rulesets govern profile consolidation, not outbound HTTP connectivity, so recreating them cannot fix a webhook timeout. It is tempting because ruleset rebuilds clear stuck transactions, and would be correct where activation failures stem from unresolved identity conflicts rather than network reachability.

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

Why it fails: Raising chunk size to a million records enlarges each payload, worsening the timeout by increasing request duration and memory pressure. Large chunks suit high-throughput batch targets, and would be correct where the endpoint tolerates long requests and the bottleneck is per-request overhead, not latency.

Switch the activation target type from webhook to cloud storage.

Why it fails: Switching to cloud storage abandons the REST webhook entirely, so the timeout against the custom endpoint is never diagnosed or resolved. Cloud storage targets suit bulk file delivery, and would be correct if the requirement were batch export rather than real-time webhook delivery.

Streaming segments are restricted to a maximum refresh frequency of once every 24 hours.

Why it fails: Streaming segments refresh near-continuously as new data arrives, not once every 24 hours; that cadence describes batch segments. The 24-hour figure is tempting because it reflects a real batch refresh limit, but applying it to streaming inverts the actual behaviour and fails the scenario.

Streaming segments can only be published to Marketing Cloud Engagement and no other targets.

Why it fails: Streaming segments can activate to multiple targets, including Data Cloud and other connected platforms, not Marketing Cloud Engagement alone. Restricting to one destination is tempting because Marketing Cloud Engagement is a common activation target, but it is not an actual limitation of streaming segments.

Standard Data Stream bundle with scheduled syncs

Why it fails: Standard data streams replicate data into Data Cloud, creating duplicate storage and ingestion overhead.

Ingestion API push streaming

Why it fails: Ingestion API pushes data into Data Cloud storage, which introduces storage duplication.

Amazon S3 Cloud File Storage batch connector

Why it fails: S3 connector copies and stages data into Data Cloud storage, failing the requirement to avoid storage duplication.

The Calculated Insight must be exported to Amazon S3 before it can be used in segments.

Why it fails: Calculated Insights become segment-eligible only once their Data Space is activated for segmentation; exporting to Amazon S3 addresses external data sharing, not segment availability. The S3 export path is genuinely used when feeding insights into external analytics or downstream platforms, which is why it looks relevant here.

The user lacks the 'View Setup and Configuration' permission in core CRM.

Why it fails: Segment availability of a Calculated Insight depends on Data Space configuration and the user's Data 360 segment permissions, not core CRM object permissions. 'View Setup and Configuration' governs access to CRM setup menus, so it would matter for administering CRM metadata, not for consuming Data 360 insights.

Calculated insights cannot be used in segments; only Data Model Objects can be used.

Why it fails: Calculated Insights are usable in segments when their dimensions and measures are properly configured, so this blanket prohibition is false. The likely oversight is that the insight lacks a segment-compatible dimension or is not activated for segmentation. This option would be correct only if the platform genuinely restricted segments to Data Model Objects.