CCNA Act On Data Questions

Activations in Data Cloud can be scheduled to run at regular intervals. By setting a daily schedule, the activation will automatically refresh and send updated audience data to Google Ads without manual intervention. This is the standard way to automate recurring activations to advertising platforms.

Every Data Action requires a destination, so the target's endpoint URL and its authentication parameters must be supplied for Data 360 to POST the payload securely. Without these, the action cannot leave the platform, satisfying the mandatory target configuration.

An Activation Target can only be selected once a published Segment exists, because activation requires a defined audience to send. Creating and publishing the Segment first satisfies that prerequisite, making its members available for the activation to target.

Connection timeout errors directly evidence a failure to establish the network path to the external endpoint, satisfying the connectivity-failure symptom the stem asks for. Unlike authentication rejections, timeouts occur before any credential exchange, isolating the activation target's reachability as the fault.

Salesforce Event Monitoring captures user-initiated actions such as activation publishing, recording who performed the action and when. Data Cloud audit event logs supplement this with platform-level records, giving the administrator the per-user, timestamped audit trail the scenario demands.

Data Actions evaluate streaming engagement events against defined criteria, and Data Action Targets deliver the resulting payload to an external endpoint via webhook in real time. This satisfies the threshold-triggered, real-time notification requirement without batch latency.

Activation execution history and failure logs expose rejected records, consent blocks and target errors, letting the consultant detect and remediate delivery problems promptly rather than discovering silent data governance breaches after campaigns have already run.

Additional Attributes extend the activation payload beyond the core identifier, letting Loyalty Tier and Lifetime Value travel with each record to the S3 bucket. Configuring them at the activation step satisfies the requirement to enrich the outbound file without altering the underlying data model.

Configuring the file naming convention, prefix and folder path within the Cloud File Storage Activation Target directly controls the output structure written to the bucket, satisfying the downstream pipeline's parsing requirement. These settings govern how each activation file is named and placed, so the warehouse ingestion can reliably interpret partitions without post-processing.

Cloud File Storage activation targets support scheduled exports to SFTP endpoints, satisfying the nightly delivery requirement to an external server. Unlike streaming or API-based targets, this target type writes segment data as files on a recurring schedule, which matches the batch cadence and external hosting constraint specified in the scenario.

Compressing the output reduces the data volume transferred, and partitioning by a key attribute splits the data into multiple files that can be written in parallel. This improves performance and reduces the likelihood of timeouts. For large segments, this is a best practice because it allows the target system to ingest data more efficiently and avoids single large file bottlenecks.

Null handling follows the activation target's schema: Data Cloud either exports null attributes as empty strings or omits them entirely, depending on how that target expects fields. Records lacking optional attribute values therefore do not break the payload structure.

Marketing Cloud Engagement is the activation platform natively supported by Data Cloud for outbound push notifications, email and SMS. It consumes Data Cloud segments and journeys directly, so personalised messages reach customers without custom middleware, matching the stem's native-support constraint.

Correct client credentials still fail if the Connected App's OAuth scopes are insufficient, or the token grant has expired or been revoked. Verifying the associated Connected App scope and token grant status isolates the authentication failure beyond the credentials themselves.

The Data Action Target handles the delivery mechanism, and incorrect target mapping or authorization will cause failures.

The Data Action Target defines the destination webhook endpoint, its URL and payload mapping, giving the action somewhere to send the event. Without this target definition, no outbound call can be made when the customer data event fires.

Activation publishes are batched, so Data Cloud transmits removal or suppression payloads to the external ad platform during the next scheduled refresh. The churned customer's record is therefore deleted from the active audience list at that refresh, not instantly.

A prolonged 'Publishing' status indicates the activation job is stalled within the processing pipeline. The Activation History and Monitor tab exposes per-run job progress, stage timings and error logs, letting the consultant pinpoint which pipeline stage is bottlenecking the run.

The Marketing Cloud Engagement tenant must be connected and provisioned in Data Cloud Setup first, because the activation target references that provisioned connection. Without an established, authenticated tenant link, Data Cloud cannot route activation data to Marketing Cloud Engagement, so this prerequisite must precede target creation.

Streaming Data Transforms process the high-volume event stream in flight, while Data Actions invoke an external system through a webhook Data Action Target, delivering the real-time personalisation the scenario demands. Ingestion alone cannot trigger external action.

Activation succeeds at the transport level, but journey entry requires the Data Cloud identifier mapped as contact key to equal the Subscriber Key or Contact Key in Marketing Cloud Engagement. Mismatched values leave contacts unmatched, so journeys never trigger.

Consent is enforced at activation time by filtering within the segment definition or via consent-based attributes, so opted-out records are excluded before reaching the advertising platform. This satisfies the requirement to suppress only opted-out individuals while retaining all other eligible records.

Data Actions invoke Salesforce Core APIs, so each qualifying event starts a Flow transaction. A high-volume event stream fires many concurrent Flow interviews, breaching Salesforce's simultaneous transaction limits and returning concurrency errors. Throttling or batching the Data Action reduces that contention.

A Data Action Target streams platform events to an external endpoint. Configuring it for Amazon EventBridge or a webhook pushes the fraud flag event out in near-real time, satisfying the immediate-trigger requirement rather than batch processing.

Publishing means the activation has been triggered and is actively transmitting records to the configured target. This distinguishes it from Draft, Active or Failed states, confirming the job is mid-flight rather than merely configured or completed.

Publishing segment activations requires the Data Cloud Marketing Manager or Data Cloud Admin permission set, since these grant the create-and-publish rights on activation objects. Without one of these, a user can build segments but cannot push them to downstream targets, so this satisfies the stem's publishing requirement.

REST Webhook is a Data Action Target type, enabling Data Cloud to send profile-triggered payloads to an external HTTPS endpoint. It differs from other target types, such as Marketing Cloud or CRM targets, by using generic REST invocation rather than a native connector.

Staggering publishing windows spreads outbound API calls across time, keeping each destination below its throttling threshold and preventing concurrent jobs from competing for shared compute. This directly satisfies the stem's performance constraint, since simultaneous multi-channel activation would otherwise trigger rate limits and resource contention.

Cloud storage activation targets allow you to specify a file naming pattern, which can include dynamic elements like date and time. This setting controls the naming convention of the exported files, directly satisfying the requirement for a specific naming convention. It is configured at the target level and applies to all files generated by that activation.

Activation Targets support cloud storage destinations, letting consultants configure Amazon S3 buckets for file-based exports of segment data. This satisfies the stem by naming a supported target type that can be established during Activation Target configuration.

Meta and similar ad platforms match audiences using hashed contact points such as email. Data Cloud therefore enforces those identifier mappings so the exported audience can be securely matched and resolved on the ad platform's side.

Data Cloud writes activation files into the customer's cloud storage using an assumed IAM role, so the role's trust policy and the bucket's write permissions must both allow that access. Missing or incorrect permissions cause the publish to fail before any file lands.

Meta Ads is a native activation platform within Data Cloud, allowing audiences to be pushed directly to Meta advertising destinations without external middleware. This satisfies the stem's requirement for a natively supported activation target rather than a custom or third-party integration.

Additional Attributes let an activation carry fields from a related Related Data Object, such as Total Lifetime Spend from Orders, alongside the primary profile attributes. Configuring them within the Activation supplies the ad network with the enriched values it needs.

Activation History in Data Cloud Setup records each run's status, error messages and record-level failures, exposing why some records were rejected during the S3 export. This directly satisfies the need to diagnose the partial-success root cause.

Activation Mappings translate Data Cloud profile and attribute fields into the schema each activation target expects, satisfying the requirement to deliver segments in a format the destination accepts. Without this field-level correspondence, activations would fail or send mismatched data, so the mapping is what makes outbound delivery to external platforms possible.

Data Spaces partition a single Data Cloud instance so segments, activation targets, and data remain scoped to each business unit, while targeted permission sets restrict who can view or edit them. This satisfies the isolation requirement between Marketing Team A and Team B.

Google Ads is one of the two ad platforms Data Cloud activates to natively, alongside Meta Ads. It satisfies the stem's requirement for native support, meaning segments export directly without custom middleware or third-party connectors.

The Attributes selection step of the activation creation wizard is where additional attributes are chosen alongside the subscriber key before the activation is saved. This step maps those attributes into the outbound payload sent to Marketing Cloud Engagement.

Running the activation daily, immediately after the segment refresh, guarantees the Google Ads audience file reflects the newest segment membership within the required 24-hour window. Sequencing activation after refresh prevents exporting stale data, satisfying the daily delivery constraint the ad platform demands.

Activation exports publish data in multiple chunks, so the job is not atomic. A downstream consumer reading immediately after segment publication can pick up a partially written file set, producing missing or incomplete records until all chunks finish.

Activation requires the attribute's DMO to relate to the Unified Individual DMO, because the segment resolves to unified profiles. Without that relationship, Data Cloud cannot join the attribute values to the correct individual during activation.

Match rates are calculated by the destination platform after upload, not by Data Cloud. Google Ads matches uploaded identifiers against its own user base, so the consultant reviews the resulting match rate within Google Ads' audience manager interface rather than any Data Cloud activation view.

Data Cloud activations support a one-time schedule where you specify a future date and time. This executes the activation exactly once, which aligns with the product launch requirement. It prevents repeated sends and ensures the email is delivered only on the intended date, satisfying the marketing team's need for a single, timed communication.

Streaming Data Actions evaluate events continuously and invoke a webhook immediately, enabling sub-second activation rather than batch segmentation. This satisfies the stem's two-hour abandoned-cart constraint, which requires near-real-time triggering that scheduled batch activations cannot deliver.

Data Action Targets are designed to push individual profile events to external systems in near real time, and they can be triggered by platform events or Data Cloud triggers. Configuring a trigger on the loyalty tier change and mapping the customer identifier and new tier value to the target payload meets the requirement exactly. This is the intended mechanism for event-driven, record-level outbound messaging from Data Cloud.

Rotating the connected app's client secret invalidates the credentials stored in the activation target, so Data Cloud can no longer authenticate to Marketing Cloud Engagement and updates halt. Re-entering the new client secret in the Activation Target setup restores authentication and resumes data extension updates.

Derived attributes and transformed DMO fields apply masking upstream in the data model, so obscured values are already present before activation exports to the ad network. This satisfies the stem's requirement for a final attribute masking rule governing sensitive demographics at export time, rather than relying on downstream controls.

A Cloud File Storage Activation Target delivers segment membership files to cloud object stores such as Google Cloud Storage. It satisfies the nightly push requirement by writing scheduled batch files rather than streaming individual profiles.

External REST endpoints typically enforce their own authentication, so the Data Action Target must supply the required custom headers or API keys. Without these credentials the outbound webhook call is rejected, satisfying the external endpoint's authorisation requirement.

A Data Action pairs a Data Source or Event, which supplies the triggering payload, with a Data Action Target, which defines where that payload is delivered. Both must be linked, since the source alone cannot route data and the target alone has nothing to send.

Data Actions fire only on incoming streaming events matching filter criteria. If no events arrive or filters mismatch payload values, nothing triggers. Verifying the streaming source is actively receiving events and that filter criteria align with payload values isolates the fault.

A published segment supplies the audience criteria that the activation must evaluate. Without it, Data Cloud has no defined population to send, so the batch activation cannot be configured or published, satisfying the stem's requirement for a necessary component.

Publishing to Google Ads or Meta Ads requires an active Activation Target holding valid ad network authentication credentials, plus a published Segment mapped to the identifiers that network expects. Without both, Data Cloud cannot authenticate or transmit the audience.

GZIP compression is selected directly in the file format settings of the Cloud File Storage Activation Target, which governs how Data 360 writes outbound files. This satisfies the stem's constraint that the S3 target requires compressed GZIP delivery, applying compression at write time without external post-processing.

Inspecting the IAM role trust policy and bucket permissions addresses the authentication failure directly: the trust policy must allow the Data 360 service principal to assume the role, and the attached policy must grant s3:PutObject on the target bucket. Membership count is irrelevant, confirming credentials rather than data volume cause the export error.

Activation targets expose batch size and chunking controls that split outbound records into smaller API requests. Reducing records per request keeps each payload beneath the CRM's maximum request limit, resolving the failure while preserving complete data delivery.

Correct. A Data Action Target specifies the destination system (Salesforce CRM) where the event will be sent.

Data Actions evaluate incoming data changes against defined conditions and trigger real-time actions or events in external or internal systems, such as sending notifications or invoking APIs. This event-driven capability distinguishes them from batch segmentation or reporting features.

Marketing Cloud Engagement uses a subscriber key to uniquely identify contacts. When activating from Data Cloud, the consultant must explicitly map the Data Cloud field that holds the subscriber key value to the Marketing Cloud Engagement subscriber key in the activation target configuration. This ensures each activated record is associated with the correct subscriber.

A Data Action Target specifies where real-time Data Actions are sent, such as an external webhook or Salesforce Core feature. This satisfies the stem's requirement by defining the destination endpoint rather than the trigger or payload logic.

Activation targets enforce consent and subscription checks at send time, so profiles in the segment without valid opt-in for the configured channel are suppressed. This precisely explains why the segment count is large but the delivered audience is smaller. Verifying the consent model and communication subscription configuration on the activation target is the correct first step to reconcile the two numbers.

Data Cloud's Consent Management allows you to define consent models and purposes, and activations can be configured to respect these consents. By selecting the correct consent model and purpose, the activation will automatically exclude individuals who do not have an active opt-in at the time of activation. This ensures compliance dynamically, even if consent status changes after segment creation.

Meta Ads requires hashed email or phone as a mandatory identity attribute for audience matching. If the segment lacks these identifiers, Data Cloud cannot map it to Meta's schema, so the segment is greyed out during activation target selection.

Data Action Target setup includes a custom headers and authentication section where arbitrary HTTP headers such as X-API-Key are defined and sent with each webhook call. Configuring it there satisfies the external endpoint's authorisation requirement at the target level.

An installed package using OAuth 2.0 client credentials with API integrations enabled satisfies the requirement to authenticate Data Cloud's connection to Marketing Cloud Engagement. Unlike user-based flows, this server-to-server mechanism needs no interactive login, letting Data Cloud activate audiences directly into Marketing Cloud Engagement.

An Activation Target holds the connection credentials and destination settings that Data Cloud uses to send segment data to an external platform. It satisfies the stem's requirement by defining where and how activations are delivered, separating destination configuration from the activation itself so multiple activations can reuse one target.

Append-only activation only inserts or updates records in the Marketing Cloud data extension; it never deletes. Contacts who no longer meet the segment criteria therefore persist, matching the reported symptom. A full refresh or differential update supporting removals would delete them.

Scheduling decouples segment evaluation from publication: Data Cloud recalculates membership on the defined cadence, then pushes the refreshed audience to the activation target. This automates both the evaluation frequency and the outbound publish, satisfying the requirement to keep the target current without manual intervention.

Timeout errors on a custom REST webhook indicate the external endpoint is too slow to acknowledge payloads within the gateway's limit. Verifying endpoint performance and response latency directly addresses that constraint, unlike retrying or altering the Data Action Target schema.

Activation Targets under Setup > Data Cloud holds the connectors for advertising platforms, including Meta Ads. Navigating there lets the consultant create and authenticate the Meta Ads activation target, satisfying the requirement to establish the connection within Data Cloud setup.

Contact Point Email and Contact Point Phone supply the verified address or number that a digital marketing channel requires for delivery, satisfying the stem's demand for mappable delivery attributes. During activation configuration, Data 360 maps these contact point objects to the channel's recipient field, enabling the platform to dispatch the segment to the destination.

Activation History retains row-level diagnostics for each publish run, exposing the exact failure codes and rejected records behind the 'Completed with Errors' status. Unlike aggregate job metrics, it pinpoints individual records that failed to export, directly satisfying the consultant's need to identify which specific records were affected.

Matching the activation frequency to the segment refresh schedule ensures the activation triggers only after Identity Resolution completes and membership updates, satisfying the stem's sequencing constraint. This avoids activating stale membership or running before the refreshed segment is available.

Segment membership only updates when the segment refresh job runs, and activation publishing then follows its own batch schedule. The ad network therefore reflects CRM changes only after both intervals elapse, which explains the multi-hour latency without implying a fault.