Consumer-Goods-Cloud-Accredited-Professional Exam Dumps - Consumer Goods Cloud Accredited Professional (AP-204)

Salesforce Communications Cloud supports product dependencies through Relies-On Relationships. These relationships enforce commercial dependencies (e.g., Roaming requires Voice Service) and guide technical decomposition so that dependent products are fulfilled together.

To satisfy the requirement that the provisioning system receive a single activation request for both Voice Service and Roaming, the dependency must be modeled using:

✔ Relies-On Relationship

This ensures the commercial cart enforces prerequisite activation rules—Roaming cannot be purchased or activated without Voice Service.

✔ Decomposition Scope = Order Item

When decomposition scope is set to Order-Item for the technical product relationship, both commercial products decompose into a single technical activation request for fulfillment. This is the exact Salesforce-recommended pattern when dependent commercial products must trigger one consolidated orchestration/activation flow.

Why other options are incorrect:

A (Scope = Account): would merge across the whole account, not just the order.

C (Scope = Relies-On): no such decomposition scope exists; invalid choice.

D (Bundle Product + Multilevel Decomposition): bundling is not required, and it changes the commercial product structure unnecessarily.

In Salesforce Communications Cloud Order Management, orchestration steps execute through Apex-based orchestration jobs. When order volume rises sharply—as happens when additional sellers or regional teams begin submitting orders—the system may hit Salesforce’s platform limit for queued Apex jobs (50 × number of licensed Salesforce users). Once this limit is reached, orchestration fails.

Salesforce’s official scalability recommendation is to enable Platform Events for Orchestration. This switches Order Management from synchronous Apex-queue processing to asynchronous, event-driven orchestration, which drastically reduces reliance on Apex jobs. Platform Events allow OM to process far more concurrent orchestration steps without hitting queue limits and provide better throughput and resilience for enterprise-scale flows.

Options A and B are incorrect because Salesforce does not increase Apex job limits, and splitting orders is not a best-practice. Option D reduces automation and violates OM design principles.

In Salesforce Communications Cloud, the B2C customer model follows a structured, layered hierarchy designed to support ordering, billing, service management, and asset lifecycle handling. When migrating existing B2C customers into Communications Cloud, Salesforce’s public architecture guidance specifies a top-down data dependency sequence to ensure that parent records exist before child records referencing them are inserted.

The migration sequence begins with Users, since many operational objects (orders, cases, ownership, provisioning workflows) require an active user as the record owner or last modified by. Next, Contacts are required for each B2C customer because Communications Cloud uses Contacts associated with a Consumer Account to represent the individual subscriber. Although Person Accounts are supported in some Salesforce products, Communications Cloud standard data model for B2C uses Consumer Accounts + Contacts, which aligns with option A—not C.

Once contacts are created, Consumer Accounts must be migrated so that customer identity, householding, service relationships, and billing mappings can be referenced. With accounts in place, Billing Accounts are imported next to link financial agreements, billing preferences, and invoicing relationships.

Service Accounts follow, serving as the service location or logical container for active telecom services. Only after these parent entities are established can Subscriptions be migrated, as they represent the commercial products the customer is consuming. Finally, Assets are migrated, representing the technical products or devices (routers, SIMs, set-top boxes) associated with active subscriptions and services.

Options B, C, and D omit Subscriptions, which are essential for B2C migration into Communications Cloud. Option C incorrectly uses Person Accounts, which does not match the Communications Cloud standard B2C data model.

These steps enable the setup of survey assessment tasks in Consumer Goods Cloud, ensuring the surveys are well-defined and integrated with retail store activities.

Salesforce EPC provides Object Types to group products that share common attributes. For mobile devices that all share color, storage, screen size, the correct modeling approach is:

✔ Create a Mobile Offer Spec Type

Add all common attributes (color, storage, screen size).

Set parent = Base Offer Spec Type (standard hierarchy).

Associate mobile device products with this Object Type.

This ensures:

Attribute reuse

Cleaner catalog modeling

Easier maintenance

Declared inheritance from Base Offer Spec Type → Mobile Offer Spec Type → Device Offer

Why others are incorrect:

A: Associates devices with Base Type instead of Mobile-specific type.

B: Suggests reversing hierarchy (incorrect structure).

D: Putting all attributes on Base Offer Spec Type violates specialization and bloats the base type.

KPI Type is a required field for setting up Retail Store KPIs. Retail Store KPIs are key performance indicators that measure how well a retail store is performing against a specific goal or target. The KPI Type defines the type of metric that is being measured, such as share of shelf, out of stock, or promotion compliance. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 30.