CCNA Act ON Data Questions

Activation membership records which unified profiles currently satisfy a segment's criteria and are therefore eligible for activation to a target. It satisfies the stem's requirement by defining the exact profile set exported during activation, distinct from segment membership itself, which only tracks qualification without guaranteeing inclusion in an activation.

Activation can only surface attributes reachable from the segment's root Data Model Object. If the related DMO lacks a valid cardinality relationship mapped back to that root, the join path cannot be resolved, so those attributes are greyed out and unavailable for selection.

Marketing Cloud Engagement is a supported native activation target.

The Business Unit drop-down populates only for Marketing Cloud Engagement users holding administrative rights across that Business Unit, or when the installed package connection is still valid. A missing entry therefore points to insufficient user permissions or an expired package authorisation requiring re-authorisation.

Publishing scales with the number of qualifying profiles, because each activation record must be serialised and delivered. A segment containing millions of members multiplies that work, directly extending batch publishing job duration and degrading overall activation performance.

Recalculating a segment refreshes its membership, and associated activations pick up that updated membership list during their next scheduled run rather than instantly. The activation's own schedule governs when the new segment population is pushed to the downstream target.

Concurrent activation publishes compete for the same API concurrency limits and processing capacity, causing degradation. Staggering publish schedules across separate time windows distributes that load, directly resolving the bottleneck created by multiple large segments activating in the same hour.

Contact Points define which identity fields, such as hashed email addresses or phone numbers, are sent to the advertising platform. The ad network matches those identifiers against its own audience data, so the correct fields must be mapped for activation to reach users.

The Data Action trigger defines when the action fires, such as when a loyalty tier field changes. It links the Data Action Target to the specific data change event and includes the payload mapping. Without a trigger, the Data Action would not execute even if the target is configured.

Data Action Targets subscribe to streaming data events and trigger near real-time, event-driven responses, unlike batch activation targets that run on schedules. This satisfies scenarios needing immediate action on individual streaming events rather than periodic bulk delivery.

An activation needs a segment to define the audience and an activation target to specify the destination platform. Without both configured and active, Data Cloud cannot publish the segment data, so the activation creation fails validation.

The error arises because activation requests exceed the third-party API's permitted call volume. Reducing batch size or spreading scheduled activations lowers the request rate, keeping calls within the target's limits while still completing the activation.

Publishing activations requires the Data Cloud Activation Admin permission set, which grants the create and publish rights on activation targets and data actions. Standard Data Cloud users lack these privileges, so this permission set satisfies the stem's requirement to create and publish activations.

Aligning source data stream refresh, calculated insight recalculation and activation scheduling ensures frequently changing attributes such as current loyalty tier are re-evaluated before each send. Marketing Cloud Engagement personalisation reads attribute values at activation run time, so cadence alignment across all three layers satisfies the stem's requirement for the latest values.

Data Transforms run during ingestion and data modelling, letting you standardise raw phone values into E.164 before they reach the activation. Handling formatting there satisfies the advertising network's E.164 requirement at the source rather than downstream.

Data Actions trigger outbound webhook calls in real time when a qualifying event, such as a high-value purchase, occurs in Data Cloud. This satisfies the scenario's real-time external notification constraint, unlike batch-based activation or segmentation, which cannot push immediate event-driven payloads to an external endpoint.

Activation targets can impose delivery throttling or minimum intervals, and some advertising destinations accept only periodic file drops. Even with an hourly segment and hourly activation schedule, the target's own constraints can cap effective delivery to every six hours. This is the most plausible explanation for the consistent gap between the configured schedule and observed file generation.

Marketing Cloud Engagement requires an installed API integration package to authorise Data 360's connection; the package supplies the Client ID, Client Secret and Authentication URI (tenant-specific subdomain) needed for OAuth 2.0 token exchange, satisfying the authentication prerequisite for the Activation Target.

Cloud storage activations require a primary key to uniquely identify each exported record, and missing or null keys cause records to be dropped or the activation to fail. Verifying the primary key mapping guarantees the stable unique identifier the business requires. This is a core prerequisite for producing a valid, deduplicated file for downstream systems.

Activation membership is recalculated each publish cycle as the underlying segment is re-evaluated, so members flow in and out automatically without manual list maintenance. This satisfies the requirement that membership reflects current segment qualification rather than a frozen snapshot.