Act ON Data practice questions

An organization is setting up a streaming activation to Google Cloud Storage. They notice that records are being delayed significantly before appearing in the destination bucket. What is the most likely architectural bottleneck causing this latency?

Trap 1: The Google Cloud Storage bucket has reached its maximum file count…

Object storage services like GCS support massive file counts; directory limits are not the primary cause of Data Cloud export queuing.

Trap 2: The Connected App token has expired, requiring manual…

An expired token would result in complete failure or authentication errors, not a delay in record processing.

Trap 3: The Data Model Object relationships lack primary key definitions,…

Primary key definitions affect identity resolution and querying, not cloud storage export latency.

A
The Google Cloud Storage bucket has reached its maximum file count limit per directory.
Why it fails: Object storage services like GCS support massive file counts; directory limits are not the primary cause of Data Cloud export queuing.
B
The Connected App token has expired, requiring manual re-authentication.
Why it fails: An expired token would result in complete failure or authentication errors, not a delay in record processing.
C
The activation target is configured for batch publishing rather than real-time streaming, or the micro-batch window is queueing records.
Streaming activations publish records continuously, whereas batch publishing buffers them until the micro-batch window closes. If the target is set to batch, records queue until that interval elapses, producing exactly the significant delay described. Switching to real-time streaming removes the queueing window.
D
The Data Model Object relationships lack primary key definitions, causing full table scans.
Why it fails: Primary key definitions affect identity resolution and querying, not cloud storage export latency.

Question 2mediummultiple choice

An enterprise marketing team wants to publish audience segments to Meta Ads via Data Cloud. When setting up the Activation Target for Meta, what specific identifier type must be mapped from the Data Cloud profile space to successfully match and target users on the ad platform?

Trap 1: Device Advertising ID (IDFA or GAID) exclusively

While mobile IDs can be used in some mobile-specific contexts, standard customer list uploads on Meta rely primarily on hashed PII like email and phone.

Trap 2: Data Cloud Unified Individual ID

Unified Individual ID is an internal Data Cloud GUID and is not recognized by external ad networks like Meta.

Trap 3: Salesforce CRM Contact ID

CRM Contact ID is native to Salesforce Core and is not recognized by Meta Ads for direct user matching.

A
Hashed email address or hashed phone number
Meta Ads matches audiences using hashed identifiers rather than raw personal data. Mapping hashed email or hashed phone from the Data Cloud profile space satisfies the activation target's matching requirement, enabling deterministic audience targeting without exposing plaintext PII.
B
Device Advertising ID (IDFA or GAID) exclusively
Why it fails: While mobile IDs can be used in some mobile-specific contexts, standard customer list uploads on Meta rely primarily on hashed PII like email and phone.
C
Data Cloud Unified Individual ID
Why it fails: Unified Individual ID is an internal Data Cloud GUID and is not recognized by external ad networks like Meta.
D
Salesforce CRM Contact ID
Why it fails: CRM Contact ID is native to Salesforce Core and is not recognized by Meta Ads for direct user matching.

Question 3easymultiple choice

What artifact must be associated with an Activation to determine the communication channel (eんに, email address or phone number) used to reach the audience?

Trap 1: Data Stream Ingestion Object

Ingestion objects are raw staging tables used prior to modeling and activation.

Trap 2: Calculated Insight Summary Table

Calculated insights provide aggregated metrics, not communication channel endpoints.

Trap 3: Identity Resolution Rule Set

Rule sets define how profiles merge, not how communication channels are selected for activation.

A
Data Stream Ingestion Object
Why it fails: Ingestion objects are raw staging tables used prior to modeling and activation.
B
Calculated Insight Summary Table
Why it fails: Calculated insights provide aggregated metrics, not communication channel endpoints.
C
Identity Resolution Rule Set
Why it fails: Rule sets define how profiles merge, not how communication channels are selected for activation.
D
Contact Point Object
The Contact Point Object supplies the channel-specific addressing data, such as email address or phone number, that an activation uses to reach each profile. Associating it with the activation determines which communication channel is applied when the audience is sent.

Question 4mediummultiple choice

A consultant is configuring an activation for a Meta Custom Audience. The client wants to ensure compliance with privacy regulations by hashing all email addresses before export. How should the consultant configure this in Data Cloud?

Trap 1: The consultant must write a custom Apex class to hash emails before…

Hashing is a built-in activation setting for Meta Custom Audience, so custom Apex is unnecessary and would not integrate with the activation pipeline. It is tempting because Apex is the correct choice when a transformation is genuinely unsupported by declarative tools and must run inside Salesforce.

Trap 2: Data Cloud does not support hashing; unhashed emails must be sent…

Data Cloud supports SHA-256 hashing of email addresses as part of activation to Meta Custom Audience, so unhashed SFTP transfer is unnecessary and non-compliant. It is tempting because SFTP is the correct transport when a destination accepts only file-based delivery and no native hashing integration exists.

Trap 3: Hashing must be performed on the source system before data…

Data Cloud hashes email addresses during activation to a Meta Custom Audience, so pre-hashing at source would double-hash and break matching. It is tempting because source-side hashing is the correct approach when exporting to destinations that expect pre-hashed identifiers and perform no hashing themselves.

A
Data Cloud automatically handles hashing for supported ad network activation targets like Meta during the export process.
Data Cloud applies SHA-256 hashing automatically when activating to supported ad-network targets such as Meta Custom Audiences, so no manual transformation is needed. This satisfies the stem's privacy-compliance constraint by ensuring email addresses leave the platform already hashed, with identity resolution and consent checks still applied before export.
B
The consultant must write a custom Apex class to hash emails before segment creation.
Why it fails: Hashing is a built-in activation setting for Meta Custom Audience, so custom Apex is unnecessary and would not integrate with the activation pipeline. It is tempting because Apex is the correct choice when a transformation is genuinely unsupported by declarative tools and must run inside Salesforce.
C
Data Cloud does not support hashing; unhashed emails must be sent over secure SFTP.
Why it fails: Data Cloud supports SHA-256 hashing of email addresses as part of activation to Meta Custom Audience, so unhashed SFTP transfer is unnecessary and non-compliant. It is tempting because SFTP is the correct transport when a destination accepts only file-based delivery and no native hashing integration exists.
D
Hashing must be performed on the source system before data ingestion into Data Cloud.
Why it fails: Data Cloud hashes email addresses during activation to a Meta Custom Audience, so pre-hashing at source would double-hash and break matching. It is tempting because source-side hashing is the correct approach when exporting to destinations that expect pre-hashed identifiers and perform no hashing themselves.

Question 5hardmultiple choice

An organization requires that audience segment data exported to a cloud storage activation target be encrypted at rest using a customer-managed encryption key (CMES). How is this requirement satisfied in Data Cloud?

Trap 1: By setting an activation attribute flag for encryption.

Activation attributes carry demographic data, not encryption instructions.

Trap 2: By writing a custom encryption script in a Data Transform before…

Data transforms process data rows, they do not manage enterprise cryptographic key ceremonies.

Trap 3: By enabling HTTPS TLS 1.3 on the activation target connection…

TLS encrypts data in transit, not data at rest in storage targets.

A
By configuring Customer-Managed Encryption Keys (BYOK) using Salesforce Shield and cloud provider key management services.
BYOK integration ensures data exported to storage targets complies with enterprise encryption standards using customer keys.
B
By setting an activation attribute flag for encryption.
Why it fails: Activation attributes carry demographic data, not encryption instructions.
C
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.
D
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.

Question 6hardmultiple choice

An enterprise client requires that customer data activated to an external marketing platform be automatically scrubbed after 30 days of inactivity in the segment. How should this timing dependency be managed?

Trap 1: Write an Apex batch job in Salesforce Core to delete contacts from…

Apex batch jobs do not manage external ad network audience deletions directly.

Trap 2: Configure a Data Action TTL (Time-To-Live) property in the…

Activation targets do not feature a TTL property for automatic record scrubbing.

Trap 3: Manually purge the activation target bucket every 30 days.

Manual purging violates automation best practices.

A
Write an Apex batch job in Salesforce Core to delete contacts from the activation target daily.
Why it fails: Apex batch jobs do not manage external ad network audience deletions directly.
B
Configure a Data Action TTL (Time-To-Live) property in the activation target settings.
Why it fails: Activation targets do not feature a TTL property for automatic record scrubbing.
C
Manually purge the activation target bucket every 30 days.
Why it fails: Manual purging violates automation best practices.
D
Incorporate recency criteria within the Segment definition and rely on Data Cloud's differential activation publishing to remove expired profiles.
Segment logic handles membership rules (including time-bound recency), and activation publishing synchronizes additions and removals.

Question 7hardmulti select

A consultant is troubleshooting an activation that fails to export files to a Cloud File Storage target. Which TWO factors should the consultant investigate regarding storage permissions and configuration? (Choose two.)

Trap 1: Einstein Trust Layer generative AI moderation guardrails.

Einstein Trust Layer moderation guardrails govern generative AI prompt and response handling, not outbound file writes to Cloud File Storage. They are tempting because both sit within the Data 360 platform and both concern data movement, but guardrails would be the correct focus when securing AI model interactions, not storage export permissions.

Trap 2: Salesforce Core CRM Profile object sharing rules.

Profile object sharing rules govern record visibility inside Salesforce Core CRM, not outbound file writes to external Cloud File Storage. The confusion arises because sharing rules are a familiar access-control lever, and they would be relevant when troubleshooting why users cannot see CRM records, not why an activation export fails.

Trap 3: Marketing Cloud Engagement API connection scopes and OAuth…

Marketing Cloud Engagement OAuth scopes and API credentials authenticate that separate platform's own API calls, not Data 360 activation exports to Cloud File Storage. They are tempting because both involve connected-app credentials, but these would be the correct focus when troubleshooting Marketing Cloud Engagement integrations rather than a Data 360 storage target.

A
AWS IAM role trust relationships or bucket write permissions granted to Data Cloud.
Data Cloud assumes a role in the customer's AWS account to write activation files, so the IAM role's trust relationship must permit Data Cloud's principal to assume it, and the bucket policy must grant that role write access. Either misconfiguration blocks file export.
B
Einstein Trust Layer generative AI moderation guardrails.
Why it fails: Einstein Trust Layer moderation guardrails govern generative AI prompt and response handling, not outbound file writes to Cloud File Storage. They are tempting because both sit within the Data 360 platform and both concern data movement, but guardrails would be the correct focus when securing AI model interactions, not storage export permissions.
C
Salesforce Core CRM Profile object sharing rules.
Why it fails: Profile object sharing rules govern record visibility inside Salesforce Core CRM, not outbound file writes to external Cloud File Storage. The confusion arises because sharing rules are a familiar access-control lever, and they would be relevant when troubleshooting why users cannot see CRM records, not why an activation export fails.
D
Marketing Cloud Engagement API connection scopes and OAuth credentials.
Why it fails: Marketing Cloud Engagement OAuth scopes and API credentials authenticate that separate platform's own API calls, not Data 360 activation exports to Cloud File Storage. They are tempting because both involve connected-app credentials, but these would be the correct focus when troubleshooting Marketing Cloud Engagement integrations rather than a Data 360 storage target.
E
Cloud storage bucket path, prefix, and folder naming configuration settings.
Even with correct permissions, the activation fails if the configured bucket path, prefix or folder naming does not match the actual target structure, or if the folder does not exist. Data Cloud writes to the exact configured location, so path errors prevent file delivery.

Question 8easymulti select

Which TWO benefits does a Data Cloud Consultant gain by using Activation Targets? (Choose two.)

Trap 1: Automated generation of Tableau CRM analytics dashboards.

Activation targets push unified segment membership to external destinations; they generate no analytics dashboards. It is tempting because both concern downstream consumption of Data Cloud data, and dashboard generation would be correct when surfacing insights in Tableau CRM, which reads datasets rather than activation targets.

Trap 2: Automatic ingestion of raw CSV files from external SFTP servers.

Activation targets define where already-harmonised segments are published, such as marketing or advertising platforms; they do not ingest files. It is tempting because activation involves external systems, and SFTP ingestion would be correct when bringing raw CSV data into Data Cloud, which uses data streams instead.

Trap 3: Real-time calculation of Identity Resolution match rules.

Activation Targets define where and how activated segments are delivered, such as marketing platforms or data lakes. Identity Resolution match rules are configured within Identity Resolution itself, not through Activation Targets, so no real-time calculation occurs here. Activation Targets would be correct when specifying outbound destinations for segment publishing.

A
Automated generation of Tableau CRM analytics dashboards.
Why it fails: Activation targets push unified segment membership to external destinations; they generate no analytics dashboards. It is tempting because both concern downstream consumption of Data Cloud data, and dashboard generation would be correct when surfacing insights in Tableau CRM, which reads datasets rather than activation targets.
B
Automatic ingestion of raw CSV files from external SFTP servers.
Why it fails: Activation targets define where already-harmonised segments are published, such as marketing or advertising platforms; they do not ingest files. It is tempting because activation involves external systems, and SFTP ingestion would be correct when bringing raw CSV data into Data Cloud, which uses data streams instead.
C
Real-time calculation of Identity Resolution match rules.
Why it fails: Activation Targets define where and how activated segments are delivered, such as marketing platforms or data lakes. Identity Resolution match rules are configured within Identity Resolution itself, not through Activation Targets, so no real-time calculation occurs here. Activation Targets would be correct when specifying outbound destinations for segment publishing.
D
Reusability, allowing multiple distinct segments to activate data to the same destination platform.
An activation target defines the destination and its configuration once, so several distinct segments can publish to that same platform without rebuilding the connection each time. This reusability satisfies the benefit of activating multiple segments through one shared destination definition.
E
Centralized storage of authentication credentials and connection endpoints for external platforms.
Activation targets hold the endpoint and stored authentication credentials for an external platform in one place, so every activation referencing that target reuses them. This centralisation satisfies the benefit of managing connection details and secrets once rather than per segment or activation.

Question 9mediummultiple choice

A Data Cloud Consultant is setting up an activation for Marketing Cloud Engagement. The marketing team requires subscriber status updates to be reflected in real-time during a flash sale. Which feature must the consultant configure to support near-real-time streaming activation?

Trap 1: Set up a Batch Activation that runs every hour via Data Cloud…

Batch activations do not support near-real-time requirements as they operate on scheduled intervals.

Trap 2: Write a custom Apex trigger in Core CRM to pull segments from Data…

Custom Apex triggers are not used for pulling Data Cloud activations directly.

Trap 3: Use Data Actions to directly push raw DMO records without an…

Activations require activation targets and cannot bypass them using standalone data actions for standard segment delivery.

A
Set up a Batch Activation that runs every hour via Data Cloud orchestrations.
Why it fails: Batch activations do not support near-real-time requirements as they operate on scheduled intervals.
B
Write a custom Apex trigger in Core CRM to pull segments from Data Cloud.
Why it fails: Custom Apex triggers are not used for pulling Data Cloud activations directly.
C
Configure a Streaming Activation targeting Marketing Cloud Engagement with a 15-minute refresh frequency.
Streaming activations allow continuous updates to supported activation targets such as Marketing Cloud Engagement.
D
Use Data Actions to directly push raw DMO records without an activation target.
Why it fails: Activations require activation targets and cannot bypass them using standalone data actions for standard segment delivery.

Question 10mediummultiple choice

A consultant needs to deliver segment membership data to an external SFTP server on a daily schedule. Which activation target type should the consultant select?

Trap 1: Marketing Cloud Activation Target

Marketing Cloud targets deliver data directly to Marketing Cloud data extensions, not generic SFTP servers.

Trap 2: Data Action Target

Data Action Targets handle event-driven streaming payloads, not scheduled file exports.

Trap 3: Advertising Activation Target

Advertising targets are specific to paid media platforms like Meta or Google, not generic SFTP.

A
Cloud Storage Activation Target
Cloud storage activation targets allow exporting segment files directly to bucket locations.
B
Marketing Cloud Activation Target
Why it fails: Marketing Cloud targets deliver data directly to Marketing Cloud data extensions, not generic SFTP servers.
C
Data Action Target
Why it fails: Data Action Targets handle event-driven streaming payloads, not scheduled file exports.
D
Advertising Activation Target
Why it fails: Advertising targets are specific to paid media platforms like Meta or Google, not generic SFTP.

Question 11hardmultiple choice

An organization has configured an activation to Marketing Cloud Engagement. Marketing users report that while new profiles are added successfully, profile updates (such as email address changes) are not propagating to the target data extension. What should the consultant investigate?

Trap 1: Ensure that the segment uses an append-only publishing policy.

Append-only policies would prevent updates by design, but standard updates require correct upsert keys.

Trap 2: Increase the batch size of the Data Stream ingestion job.

Data stream batch size does not impact activation export logic.

Trap 3: Check if the Marketing Cloud connector user has View All…

Marketing Cloud data extension updates are managed via API integrations, not CRM object FLS.

A
Ensure that the segment uses an append-only publishing policy.
Why it fails: Append-only policies would prevent updates by design, but standard updates require correct upsert keys.
B
Increase the batch size of the Data Stream ingestion job.
Why it fails: Data stream batch size does not impact activation export logic.
C
Check if the Marketing Cloud connector user has View All permissions on the Contact object.
Why it fails: Marketing Cloud data extension updates are managed via API integrations, not CRM object FLS.
D
Verify that the primary key and upsert behavior on the target Marketing Cloud Data Extension match the activation membership key.
If the primary key or update configuration on the data extension does not support upserts, updates will fail or result in duplicate rows rather than refreshing existing records.

Question 12hardmultiple choice

An enterprise is using Cloud Storage Activation Targets to export daily segments to an AWS S3 bucket. The data engineering team requests that segment files be delivered in Apache Parquet format rather than CSV. How should the consultant configure this?

Trap 1: Configure an AWS Lambda function to intercept and convert CSV files…

While possible, this is an unnecessary workaround since Data Cloud natively supports Parquet export.

Trap 2: Write a Calculated Insight that automatically converts CSV strings…

Calculated insights perform aggregation, not file format conversion.

Trap 3: Modify the Data Stream schema to enforce Parquet ingestion, which…

Ingestion file formats are separate from activation export formats.

A
Configure an AWS Lambda function to intercept and convert CSV files after they arrive in S3.
Why it fails: While possible, this is an unnecessary workaround since Data Cloud natively supports Parquet export.
B
Select Parquet as the file format option when configuring the Cloud Storage Activation Target or activation export settings.
Data Cloud allows selecting the output file format (CSV or Parquet) for cloud storage activation targets.
C
Write a Calculated Insight that automatically converts CSV strings to Parquet binary code.
Why it fails: Calculated insights perform aggregation, not file format conversion.
D
Modify the Data Stream schema to enforce Parquet ingestion, which automatically formats exports.
Why it fails: Ingestion file formats are separate from activation export formats.

Question 13mediummulti select

Which THREE attributes or details are typically required when setting up an Activation for an advertising platform (e.g., Meta Ads or Google Ads)? (Choose three.)

Trap 1: A custom Apex controller class for payload generation

Custom Apex is not used for advertising activations.

Trap 2: A Marketing Cloud Engagement journey canvas ID

Journey IDs are specific to Marketing Cloud journeys, not ad platform activations.

A
A custom Apex controller class for payload generation
Why it fails: Custom Apex is not used for advertising activations.
B
Contact Point identifiers (such as hashed email or phone)
Ad networks require matching identifiers like hashed emails.
C
An active published Segment
An activation cannot be created without an existing segment.
D
An Advertising Activation Target
The target platform connection must be selected.
E
A Marketing Cloud Engagement journey canvas ID
Why it fails: Journey IDs are specific to Marketing Cloud journeys, not ad platform activations.

Question 14hardmulti select

When designing an activation strategy in Data Cloud, which THREE factors should a consultant consider regarding timing dependencies and performance? (Choose three.)

Trap 1: Streaming activations execute instantly without any underlying data…

Streaming activations still depend on upstream data streams, transformations and refresh schedules, so they cannot bypass dependency checks. The option tempts because streaming ingestion delivers events with low latency, which suits near-real-time use cases once those dependencies are satisfied.

Trap 2: Data actions execute synchronously and block CRM transactions until…

Data actions in Data Cloud run asynchronously, so they do not block CRM transactions while executing. The option tempts because synchronous execution is the correct pattern when a flow must return a result before the calling transaction proceeds, such as validation during record save.

A
Batch activation schedules can be configured to run hourly or daily depending on business needs.
Hourly or daily batch schedules directly address the timing-dependency constraint, letting activation align with business cadence rather than streaming latency. Unlike near-real-time streaming, batch intervals are configurable, so consultants can match delivery frequency to downstream tolerance and avoid unnecessary platform load.
B
Downstream systems must allow sufficient time for asynchronous file generation and export completion.
Downstream systems must allow sufficient time for asynchronous file generation and export completion. Activation in Data Cloud is not instantaneous: segments are written to files, then exported, and the receiving system polls or ingests them later. Scheduling must therefore account for this latency, satisfying the stem's timing-dependency constraint.
C
Streaming activations execute instantly without any underlying data dependency checks.
Why it fails: Streaming activations still depend on upstream data streams, transformations and refresh schedules, so they cannot bypass dependency checks. The option tempts because streaming ingestion delivers events with low latency, which suits near-real-time use cases once those dependencies are satisfied.
D
Segment refresh frequency must precede the activation publishing schedule.
Segment refresh frequency must precede the activation publishing schedule, ensuring Data Cloud recalculates membership before each activation runs. Publishing against a stale segment sends outdated audiences to destinations, so the refresh cadence must complete ahead of the scheduled activation to satisfy the timing dependency the stem requires.
E
Data actions execute synchronously and block CRM transactions until complete.
Why it fails: Data actions in Data Cloud run asynchronously, so they do not block CRM transactions while executing. The option tempts because synchronous execution is the correct pattern when a flow must return a result before the calling transaction proceeds, such as validation during record save.

Question 15mediummultiple choice

A Data Cloud Consultant is configuring a Data Cloud Activation to send audience segments to Marketing Cloud Engagement via Contact Builder. The consultant notices that the activation is failing because the Contact Key mapping is missing. What is the required step to resolve this issue in Data Cloud?

Trap 1: Create a Calculated Insight that aggregates the Contact Key before…

Incorrect. Calculated Insights are used for metric calculation, not for mapping platform keys during activation.

Trap 2: Modify the Data Stream ingestion mapping to automatically designate…

Incorrect. Ingestion mappings define data source to DMO alignment, whereas Activation Targets handle platform-specific key mapping.

Trap 3: Rebuild the Segment definition to include the Subscriber Key…

Incorrect. Segments define audience membership, not platform authentication or key mapping rules.

A
Create a Calculated Insight that aggregates the Contact Key before creating the activation segment.
Why it fails: Incorrect. Calculated Insights are used for metric calculation, not for mapping platform keys during activation.
B
Modify the Data Stream ingestion mapping to automatically designate the Subscriber Key as the primary key.
Why it fails: Incorrect. Ingestion mappings define data source to DMO alignment, whereas Activation Targets handle platform-specific key mapping.
C
Map the Data Cloud Primary Key to the Marketing Cloud Contact Key within the Activation Target configuration.
Correct. The Activation Target must explicitly map the primary identifier to the target platform key field.
D
Rebuild the Segment definition to include the Subscriber Key attribute as an inclusion criterion.
Why it fails: Incorrect. Segments define audience membership, not platform authentication or key mapping rules.

Question 16hardmultiple choice

A consultant is building a Data Cloud activation to a Cloud File Storage target that will export segment data to an Amazon S3 bucket. The organization requires that the exported files include only individuals who have not been activated in the past 30 days to avoid over-contacting. The consultant needs to configure the activation to meet this requirement. What should the consultant do?

Trap 1: Create a calculated insight that flags individuals activated in the…

A calculated insight can compute activation history if the data is available, but it requires additional data streams and processing. It is not the native mechanism for controlling activation frequency; Data Cloud provides activation membership and suppression features that directly address this requirement without building custom logic.

Trap 2: Configure the activation's refresh schedule to run every 30 days…

Changing the refresh schedule only affects how often the activation runs; it does not prevent individuals who were activated in the last 30 days from being included again. Incremental refresh controls data updates, not suppression of recently activated individuals. This approach would still export the same individuals if they remain in the segment.

Trap 3: Add a filter to the segment that excludes individuals with a last…

The Unified Individual DMO does not natively contain a last activation date field. Activation history is tracked separately in activation membership data, not on the Unified Individual DMO. Filtering on a nonexistent field would not work, and even if a custom field existed, it would require custom data ingestion and maintenance, which is not the intended approach.

A
Create a calculated insight that flags individuals activated in the last 30 days and use it as a segment filter to exclude them.
Why it fails: A calculated insight can compute activation history if the data is available, but it requires additional data streams and processing. It is not the native mechanism for controlling activation frequency; Data Cloud provides activation membership and suppression features that directly address this requirement without building custom logic.
B
Use the activation's suppression settings to exclude individuals who were activated within the last 30 days.
Data Cloud activations support suppression rules that can exclude records based on activation history. By configuring a suppression that references the activation's own history or a related activation, the consultant can ensure that individuals activated in the past 30 days are not exported again. This directly meets the frequency capping requirement.
C
Configure the activation's refresh schedule to run every 30 days and enable incremental refresh.
Why it fails: Changing the refresh schedule only affects how often the activation runs; it does not prevent individuals who were activated in the last 30 days from being included again. Incremental refresh controls data updates, not suppression of recently activated individuals. This approach would still export the same individuals if they remain in the segment.
D
Add a filter to the segment that excludes individuals with a last activation date within 30 days, using a date field from the Unified Individual DMO.
Why it fails: The Unified Individual DMO does not natively contain a last activation date field. Activation history is tracked separately in activation membership data, not on the Unified Individual DMO. Filtering on a nonexistent field would not work, and even if a custom field existed, it would require custom data ingestion and maintenance, which is not the intended approach.

Question 17mediummultiple choice

A consultant is configuring a Data Cloud activation to a Marketing Cloud Engagement target. The marketing team wants to send a promotional email to all customers who have opted in to email marketing and have a lifetime value greater than $500. The consultant creates a segment with these filters and maps the required attributes. However, the activation is only sending emails to a subset of the segment. Upon investigation, the consultant finds that the 'Email Opt In' field is a related attribute from a separate data stream. What is the most likely cause of the incomplete activation?

Trap 1: The segment is using a filter on a field that is not activated, so…

Segment filters are evaluated during segmentation, not during activation. The activation simply sends the members of the segment to the target. If a field is used in the segment filter but not activated, it does not affect the activation's ability to send to the segment members. The activation would still send to all segment members, provided the contact point is mapped.

Trap 2: The 'Email Opt In' field is not included in the activation's…

The contact point mapping defines the channel address, such as email address, not consent or filtering attributes. While it is necessary to map the email address to the contact point, the 'Email Opt In' field is used for segmentation, not as a contact point. Its absence in the contact point mapping would not cause a partial send; it would likely cause a failure to send to anyone or an error, rather than a subset.

Trap 3: The activation is configured to send only to profiles with a…

There is no requirement for a postal address when activating to an email channel. The activation targets email addresses, and the presence of a postal address is irrelevant unless the channel is direct mail. This would not cause a subset of email-eligible profiles to be excluded, as the scenario does not mention any address-based filtering.

A
The segment is using a filter on a field that is not activated, so the activation cannot evaluate it.
Why it fails: Segment filters are evaluated during segmentation, not during activation. The activation simply sends the members of the segment to the target. If a field is used in the segment filter but not activated, it does not affect the activation's ability to send to the segment members. The activation would still send to all segment members, provided the contact point is mapped.
B
The 'Email Opt In' field is not included in the activation's contact point mapping.
Why it fails: The contact point mapping defines the channel address, such as email address, not consent or filtering attributes. While it is necessary to map the email address to the contact point, the 'Email Opt In' field is used for segmentation, not as a contact point. Its absence in the contact point mapping would not cause a partial send; it would likely cause a failure to send to anyone or an error, rather than a subset.
C
The related attribute 'Email Opt In' has a cardinality that is not one-to-one, causing only one value to be included per profile.
When a related attribute has a cardinality of one-to-many or many-to-many, Data Cloud includes only the most recent or primary value in the profile unification. If the 'Email Opt In' field comes from a related object with multiple records per individual, the activation may only consider one value, potentially excluding profiles where the opt-in status is true in a non-primary record. This leads to a subset of the segment being activated.
D
The activation is configured to send only to profiles with a complete postal address.
Why it fails: There is no requirement for a postal address when activating to an email channel. The activation targets email addresses, and the presence of a postal address is irrelevant unless the channel is direct mail. This would not cause a subset of email-eligible profiles to be excluded, as the scenario does not mention any address-based filtering.

Question 18hardmultiple choice

A consultant is troubleshooting a Data Cloud activation to a custom REST API endpoint. The activation is configured with a Data Action Target and a Data Action trigger. The external system reports that it is receiving duplicate events for the same individual within a short time frame. The consultant confirms that the source data change occurs only once. What is the most likely cause of the duplicates?

Trap 1: The Data Action trigger is set to fire on both insert and update…

If the source data change occurs only once, it would be either an insert or an update, not both. While triggers can be configured to fire on multiple event types, they would not cause duplicates for a single change unless the record is both inserted and updated in quick succession, which is not the case here.

Trap 2: The Data Action trigger is configured to fire on multiple fields,…

If the trigger fires on multiple fields, it would only cause duplicates if each field update is treated as a separate event. However, the scenario states the source data change occurs only once, so this is unlikely. Additionally, triggers can be configured to fire on any change to specified fields, but they typically coalesce updates within a short window.

Trap 3: The activation is scheduled to run every hour, and the segment…

This scenario involves a Data Action, not a scheduled activation. Data Actions are event-driven, not scheduled. The duplicate events are occurring within a short time frame, not hourly, so the activation schedule is irrelevant. Confusing activations with Data Actions is a common mistake.

A
The Data Action trigger is set to fire on both insert and update events for the same record.
Why it fails: If the source data change occurs only once, it would be either an insert or an update, not both. While triggers can be configured to fire on multiple event types, they would not cause duplicates for a single change unless the record is both inserted and updated in quick succession, which is not the case here.
B
The Data Action trigger is configured to fire on multiple fields, and the source system updates each field separately.
Why it fails: If the trigger fires on multiple fields, it would only cause duplicates if each field update is treated as a separate event. However, the scenario states the source data change occurs only once, so this is unlikely. Additionally, triggers can be configured to fire on any change to specified fields, but they typically coalesce updates within a short window.
C
The activation is scheduled to run every hour, and the segment includes the same individuals each time.
Why it fails: This scenario involves a Data Action, not a scheduled activation. Data Actions are event-driven, not scheduled. The duplicate events are occurring within a short time frame, not hourly, so the activation schedule is irrelevant. Confusing activations with Data Actions is a common mistake.
D
The Data Action Target is configured with a retry policy that resends the payload if it does not receive a timely response.
If the external system is slow to acknowledge receipt, the Data Action Target's retry policy may resend the payload, causing duplicates. This is a common cause when the external endpoint does not return a success status quickly enough. Adjusting the retry settings or improving the endpoint's response time can resolve the issue.

Question 19hardmultiple choice

A consultant is troubleshooting an activation to Marketing Cloud Engagement that is not delivering all expected records. The segment contains 10,000 individuals, but only 7,500 are activated. The consultant notices that many individuals have multiple email addresses, and the activation is configured to use the Email attribute from the Contact Point object. What is the most likely cause of the missing records?

Trap 1: The activation is set to use a specific Contact Point type, and…

If the activation is set to use a specific Contact Point type, it would filter individuals based on that type. However, the scenario does not mention a type filter; it mentions multiple email addresses. If a type filter were the cause, the consultant would need to check the activation configuration, but it's not the most likely cause given the multiple email addresses.

Trap 2: The activation is limited by a throttle set in the Marketing Cloud…

While throttling can limit the number of records sent, it is typically configured as a rate limit (e.g., records per hour) rather than a hard cap per activation. A throttle would not permanently exclude 2,500 records; they would be sent in subsequent batches. The scenario does not mention throttling, and the missing records are likely due to data issues, not a throttle.

Trap 3: The activation is deduplicating records based on the Individual ID,…

Deduplication based on Individual ID would result in one activation per individual, not a reduction from 10,000 to 7,500 unless some individuals are missing altogether. The segment contains 10,000 individuals, so deduplication would still activate 10,000 individuals, just with one Contact Point each. This does not explain the missing 2,500 individuals.

A
The activation is set to use a specific Contact Point type, and only individuals with that type are included.
Why it fails: If the activation is set to use a specific Contact Point type, it would filter individuals based on that type. However, the scenario does not mention a type filter; it mentions multiple email addresses. If a type filter were the cause, the consultant would need to check the activation configuration, but it's not the most likely cause given the multiple email addresses.
B
The activation is limited by a throttle set in the Marketing Cloud Engagement target, which only allows 7,500 records per activation.
Why it fails: While throttling can limit the number of records sent, it is typically configured as a rate limit (e.g., records per hour) rather than a hard cap per activation. A throttle would not permanently exclude 2,500 records; they would be sent in subsequent batches. The scenario does not mention throttling, and the missing records are likely due to data issues, not a throttle.
C
The activation is deduplicating records based on the Individual ID, and some individuals have multiple Contact Point records.
Why it fails: Deduplication based on Individual ID would result in one activation per individual, not a reduction from 10,000 to 7,500 unless some individuals are missing altogether. The segment contains 10,000 individuals, so deduplication would still activate 10,000 individuals, just with one Contact Point each. This does not explain the missing 2,500 individuals.
D
The activation is using the Email attribute from the Contact Point object, and individuals with multiple email addresses are being deduplicated to a single email, but some individuals lack a valid email.
When an activation uses a Contact Point attribute like Email, Data Cloud selects one email per individual based on the Contact Point configuration. If some individuals have no valid email address or if the email is marked as invalid, they may be excluded. The reduction from 10,000 to 7,500 suggests that 2,500 individuals either have no email or their email is not activated due to Contact Point rules, which is the most likely cause.

Question 20hardmulti select

A consultant is setting up a real-time activation to a custom endpoint using a Data Action. The Data Action is configured to trigger when a specific event occurs in Data Cloud. The consultant needs to ensure that the payload sent to the endpoint includes both profile attributes and event attributes. Which two configurations are required to achieve this? (Choose two.)

Trap 1: Create a calculated insight that joins profile and event data, and…

Calculated insights are batch or streaming aggregations, not real-time joins. They are not suitable for per-event payloads because they process data over time windows. Using a calculated insight would not provide the immediate, event-specific attributes needed for a real-time Data Action. The payload should directly reference the event and profile attributes without an intermediate insight.

Trap 2: Configure the Data Action to use a streaming insight that combines…

Streaming insights are used to calculate metrics in real time, but they are not directly used as the payload for a Data Action. While insights can be included as attributes, the Data Action itself must be configured with the desired payload. A streaming insight alone does not automatically combine profile and event data into the payload; the payload must be explicitly defined.

Trap 3: Map the profile attributes to the event schema in Data Cloud.

Profile attributes are not mapped to the event schema. The event schema defines the structure of the event data, while profile attributes come from the unified profile. In a Data Action, you can reference both, but they are separate. Mapping profile attributes to the event schema would be incorrect and could cause data model conflicts. The correct approach is to select both in the Data Action payload.

A
Define the Data Action with a payload that includes both profile and event attributes.
The Data Action payload configuration determines the data sent to the endpoint. To include both profile and event attributes, the payload must explicitly reference them. This is done by selecting the appropriate attributes from the Data Cloud data model when defining the Data Action. Without this, only the default or selected attributes will be sent, potentially missing critical information for the real-time use case.
B
Create a calculated insight that joins profile and event data, and use it in the Data Action.
Why it fails: Calculated insights are batch or streaming aggregations, not real-time joins. They are not suitable for per-event payloads because they process data over time windows. Using a calculated insight would not provide the immediate, event-specific attributes needed for a real-time Data Action. The payload should directly reference the event and profile attributes without an intermediate insight.
C
Configure the Data Action to use a streaming insight that combines profile and event data.
Why it fails: Streaming insights are used to calculate metrics in real time, but they are not directly used as the payload for a Data Action. While insights can be included as attributes, the Data Action itself must be configured with the desired payload. A streaming insight alone does not automatically combine profile and event data into the payload; the payload must be explicitly defined.
D
Map the profile attributes to the event schema in Data Cloud.
Why it fails: Profile attributes are not mapped to the event schema. The event schema defines the structure of the event data, while profile attributes come from the unified profile. In a Data Action, you can reference both, but they are separate. Mapping profile attributes to the event schema would be incorrect and could cause data model conflicts. The correct approach is to select both in the Data Action payload.
E
Ensure the Data Action is triggered by a Data Cloud event that includes the necessary event attributes.
The trigger event determines when the Data Action fires and what event attributes are available. To include event attributes in the payload, the triggering event must contain those attributes. For example, if the event is a 'Cart Abandonment' event, the event attributes like cart value and items must be part of the event schema. Without them, the payload cannot include them.