Act ON Data practice questions

It schedules the batch frequency of data stream refreshes from source systems.

Why wrong: Data stream refresh schedules govern ingestion timing, not activation memberships.

It defines the structural schema of the Data Model Object used for ingestion.

Why wrong: Ingestion schema mapping defines DMO structures, not activation memberships.

It acts as the encryption key for secure cloud storage activation targets.

Why wrong: Encryption keys are managed via Salesforce Shield or BYOK services, not activation memberships.

The Google Cloud Storage bucket has reached its maximum file count limit per directory.

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

The Connected App token has expired, requiring manual re-authentication.

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

The Data Model Object relationships lack primary key definitions, causing full table scans.

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

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.

Create a new Segment for every possible spending bracket.

Why wrong: Creating separate segments for every bracket is inefficient when activation attributes can dynamically export those values.

Export the raw data via Data Share and write a custom script on the ad network side.

Why wrong: Data Cloud supports native attribute inclusion within activations without requiring custom data share scripts.

Write a custom Apex trigger on the Unified Individual object to push attributes to the ad network API.

Why wrong: Apex triggers do not run on Data Cloud Unified Individual objects for external ad network distribution.

Enable Einstein Studio model scoring

Why wrong: Einstein Studio models are unrelated to standard segment activations.

Establish a Direct Data Share with Snowflake

Why wrong: Data Shares are used for data sharing with external warehouses, not as a prerequisite for activations.

Configure a Calculated Insight with at least three metrics

Why wrong: Calculated insights are optional and not required to create an activation.

Calculated Insights batch job with an automated email alert

Why wrong: Calculated Insights run on batch schedules and do not natively trigger real-time webhooks upon threshold breach.

Segment Activation to Marketing Cloud Engagement

Why wrong: Segment activation is batch-oriented and publishes audiences, whereas a real-time threshold check requires a data action.

Salesforce Flow triggered by a scheduled report export

Why wrong: Salesforce Flow cannot directly listen to Data Cloud streaming events without a Data Action bridge.

Device Advertising ID (IDFA or GAID) exclusively

Why wrong: 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.

Data Cloud Unified Individual ID

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

Salesforce CRM Contact ID

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

A Connected App with a JSON Web Token (JWT) Bearer Flow configured in Salesforce Setup.

Why wrong: JWT Bearer flow is typically used for cross-cloud Core CRM or external API integrations, not Marketing Cloud Engagement activation targets.

A Data Share certificate and private key uploaded via the Security Certificates menu in Data Cloud.

Why wrong: Data Shares are used for Snowflake or Databricks integrations, not Marketing Cloud Engagement activation targets.

A username, security token, and managed package license assigned to a dedicated integration user.

Why wrong: Username and security token are used for SOAP/REST API integrations to Core CRM, not Marketing Cloud Engagement activation.

Removals are only supported for real-time streaming data actions, not batch activations.

Why wrong: Batch activations fully support differential updates and suppression handling upon each run.

Data Cloud automatically deletes the contact record from the external ad platform entirely.

Why wrong: Data Cloud removes the user from the specific segment/audience list, but does not delete the master contact record from the ad platform.

Segment removals require a manual CSV export and upload by an administrator.

Why wrong: Activations automate this process without requiring manual CSV uploads.

Salesforce CPQ

Why wrong: CPQ is used for quote and pricing generation, not marketing activations.

Salesforce Core Case Management

Why wrong: Case Management is an internal CRM service feature, not an activation platform for multi-channel marketing campaigns.

Tableau CRM Analytics

Why wrong: Tableau CRM is a reporting and analytics platform, not an activation target for audience delivery.

Disable Identity Resolution to reduce the number of linked profile attributes.

Why wrong: Disabling Identity Resolution degrades data quality and is not a valid solution for API payload limits.

Increase the Data Cloud heap size limit in the org-wide governor settings.

Why wrong: Heap size limits are Apex governor limits in Core CRM and cannot be adjusted for Data Cloud activations.

Convert the activation into a streaming Data Action target.

Why wrong: Streaming data actions are designed for single-event triggers, not bulk audience segment exports.

Inside the activation membership criteria builder.

Why wrong: Activation memberships manage segment criteria, not HTTP transport headers.

In the Named Credentials setup within Salesforce Core CRM.

Why wrong: Data Cloud Data Action Targets manage their own endpoints and authentication settings independently of Core CRM Named Credentials.

Via a custom Ingestion API payload transformation script.

Why wrong: Ingestion API handles incoming data ingestion, not outgoing Data Action webhook headers.

Rely on the ad network to automatically parse and format messy phone numbers.

Why wrong: Ad networks typically reject records that do not match their strict formatting criteria (like E.164).

Write an activation-level formula field using unsupported custom SQL.

Why wrong: Activations do not support custom SQL formula fields at the output stage.

Configure a formatting mask in the Activation Target properties menu.

Why wrong: Activation targets receive data as-is from the segment; they do not perform complex regex formatting or data cleansing.

Data Stream Ingestion Object

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

Calculated Insight Summary Table

Why wrong: Calculated insights provide aggregated metrics, not communication channel endpoints.

Identity Resolution Rule Set

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

The Connected App has exceeded its daily API call allocation.

Why wrong: API call limits result in total blocking rather than intermittent concurrency locks.

Data Cloud batch jobs are conflicting with real-time segment activation schedules.

Why wrong: Batch jobs and real-time streams run in separate execution pipelines and do not cause Core Flow concurrency locks.

The Identity Resolution ruleset is re-matching profiles while the flow runs.

Why wrong: Identity resolution runs asynchronously and does not lock Core CRM transaction threads.

System Administrator in Core CRM without permission set assignment

Why wrong: Data Cloud requires explicit permission set assignments even for Core System Administrators.

Salesforce CPQ Advanced Approver profile

Why wrong: CPQ profiles govern quote generation and pricing approvals, not Data Cloud features.

Marketing Cloud Administrator without Data Cloud permissions

Why wrong: Marketing Cloud permissions alone do not grant access to configure activation targets inside Data Cloud setup.

Increase the Data Cloud DMO storage capacity limit.

Why wrong: Rate limits are imposed by external target APIs, not Data Cloud data storage capacity.

Switch the activation target from batch to real-time streaming.

Why wrong: Streaming increases request frequency, which would exacerbate rate limit violations.

Delete and recreate the Identity Resolution ruleset.

Why wrong: Identity resolution has no impact on external API rate limits during activation exports.

Rely on manual activation republishing triggered by an administrator every morning.

Why wrong: Manual refreshes are inefficient and prone to human error; scheduling automates this process.

Set the Activation to stream in real-time to Google Ads using webhooks.

Why wrong: Google Ads custom audience uploads operate on batch file/API transfers rather than real-time webhooks.

Configure the Data Stream refresh rate to 24 hours.

Why wrong: Data stream refresh governs ingestion from sources, not the activation export schedule to ad networks.

To define the demographic criteria used to build audience segments.

Why wrong: Demographic criteria are defined in the Segment canvas, not the activation target.

To ingest raw data files from an external cloud storage bucket.

Why wrong: Ingestion is handled by Data Streams and Ingestion APIs, not activation targets.

To merge duplicate customer profiles into a single unified record.

Why wrong: Profile merging is handled by Identity Resolution rulesets, not activation targets.

The Identity Resolution match rules summary report.

Why wrong: Match rules summary tracks profile merging statistics, not user activation audits.

The Data Stream refresh history dashboard.

Why wrong: Data Stream history only tracks data ingestion jobs, not activation publishing actions.

The Connected App access token expiration log.

Why wrong: Token expiration logs track OAuth handshakes, not user publishing history.