Salesforce AP-204 Exam Questions

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 Industries (formerly Vlocity) environments---especially relevant for Telecom, Media, and Energy---scenarios involving runtime price changes, agent-driven adjustments, and approval workflows are handled through Discounts, not Promotions or Context Rules. Discounts are specifically designed to allow flexible, rule-driven, and approval-controlled adjustments across the catalog, making them ideal when a company wants to equip call-center or retention agents with the ability to negotiate offers with outgoing customers.

Salesforce's public guidance explains that Discounts support both manual and automated application methods. Administrators can enable runtime/manual discounts, specify discount types (percentage or fixed amount), and attach approval rules via the Industries Pricing Compliance framework. These can be targeted across the entire product catalog, specific product hierarchies, or only selected offers. This aligns perfectly with ABC Telecom's requirement to apply pricing adjustments across the catalog and allow agents to make on-the-spot price changes.

While Promotions are useful for predefined marketing offers, they do not support agent-driven runtime flexibility. Context Rules automate pricing logic but do not provide agent-level manual control. CPQ Hooks require custom development and are not intended for business-driven discounting workflows.

Therefore, Discounts are the recommended and Salesforce-aligned feature for agent-controlled runtime adjustments, catalog-wide applicability, and approval process integration, exactly matching the needs of a telecom retention team.

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.

The object where a Consumer Goods Cloud Admin needs to establish the expected value for the planogram metrics is Assessment Indicator Definition. A planogram is a visual representation of how products should be arranged on a shelf. A planogram metric is a measure of how well the actual shelf image matches the expected planogram image. An Assessment Indicator Definition is an object that defines an indicator or metric that can be used to assess the performance or compliance of a retail store or an action plan task. By creating an Assessment Indicator Definition for the planogram metric, such as out of stock, share of shelf, or SKU facings, an admin can establish the expected value for that metric and use it to calculate the actual value based on the shelf image. Verified Reference: [Salesforce Consumer Goods Cloud Implementation Guide], page 23-24.

When assets are migrated into Communications Cloud, Salesforce best practices require performing a ''No-Change MACD Order'' after data loading. This process creates a technical MACD order that does not modify any service, but instead tests whether the MACD orchestration, decomposition, and asset-based ordering logic work correctly with the migrated asset records.

Salesforce documentation explains that migrated assets must be fully compatible with:

Order decomposition mappings

Technical product relationships

Association to Service Accounts, Billing Accounts, Premises

Child/parent asset hierarchies

Fulfillment Request Line generation

Change order processing (A B transitions)

A no-change MACD validates that the migrated assets are structurally correct and ''MACD-ready.'' If this test fails, the migration did not properly map assets to the Communications Cloud asset data model.

Options A and C overlap with validation but do not address MACD execution. Option B (Inventory Items) is not created through MACD and is unrelated.