Salesforce AP-204 Practice Exam Questions & Answers

To meet the requirements of offering regional pricing and ensuring customers can see the correct price before adding the product to the cart (i.e., while browsing the catalog), the solution must rely on Context Rules that evaluate the customer's profile (Region) prior to product configuration.

B . Create a Base Price List and Multiple Child Price Lists associated with Context Rules per region:

In Salesforce Industries (Communications Cloud) CPQ, Price Lists are the primary container for prices. You can create specific price lists for each region (e.g., 'New York Price List,' 'Texas Price List') and use Context Rules to automatically assign the correct price list to the user's session based on their Account or Quote details (Region).

Because the Price List is selected before the product is viewed, the catalog automatically displays the price entries from that specific regional list, satisfying the visibility requirement.

D . Create multiple Price List Entries associated with Context Rules per region:

Alternatively, you can use a single global Price List but create multiple Price List Entries (PLEs) for the same 'Business Internet' product (e.g., one entry for $50, another for $60).

You can apply Context Rules directly to these Price List Entries. When the catalog renders, the system evaluates the rules against the customer's context (Region) and filters the entries, showing only the one valid for that region.

This allows for granular control at the product price level without necessarily duplicating entire price lists.

Why A is incorrect: Attribute-based Pricing Matrices are typically used for calculating prices based on product attributes that a user selects during configuration (e.g., Speed, Color). Since the requirement is to see the price before adding to the cart (pre-configuration), and Region is a context of the customer not a feature they configure on the product, Context Rules (B & D) are the correct architectural choice.

When performing a search in an inventory check task, only the products that are associated with the retail store are considered for the search. This is because the inventory check task is designed to verify the availability and quantity of products in a specific store location. Verified Reference: [Salesforce Consumer Goods Cloud Implementation Guide], page 28.

A promotion check is a type of action plan task that allows a field rep to verify if a promotion is running correctly at a retail store. There are three ways of performing a promotion check during an in-store visit:

General Promotion, which checks if any promotion is running at the store, regardless of the product or category involved.

Individual Product, which checks if a specific product is part of a promotion at the store.

Product Category, which checks if a group of products that belong to the same category are part of a promotion at the store. Verified Reference: [Salesforce Consumer Goods Cloud Implementation Guide], page 27-28.

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 requirement is to introduce a limited-time offer that is available on the website (digital channel/DC APIs) and, once claimed, grants a 10% discount for three months.

This is the definition of a Promotion that uses a Time Plan to define the duration of the discount.

Promotion (A):

In Salesforce Industries CPQ, a Promotion is the container entity used to define a marketing offer that modifies the price of a product (in this case, a 10% discount).

The Promotion entity is what is typically exposed to digital channels (like the website via DC APIs) for customers to claim or qualify for. The search results confirm that Promotions are used to 'apply temporary changes to product pricing, bundles, and product structure'.

Time Plan (B):

The Time Plan is a sub-feature of Promotions (or Price Lists) that defines the duration for which the commercial change (the 10% discount) is active.

The requirement states the discount is only for 'three months.' A Time Plan is specifically configured to start the discount upon activation and automatically end it after the defined period (3 months), ensuring the billing system correctly handles the price change back to the original rate.

D (Discount) is a result of the configuration, not the feature itself. The discount value (10%) is defined within the promotion.

C (Offering) is a synonym often used for a product or bundle, but it does not specify the limited-time discount mechanism required.