Salesforce Consumer-Goods-Cloud-Accredited-Professional - Consumer Goods Cloud Accredited Professional (AP-204)

In Communications Cloud, modifying an existing commercial service to a higher speed tier (or upgraded variant) is handled through the Change of Plan MACD process. Salesforce defines Change of Plan as the out-of-the-box MACD scenario used when an existing active subscription is upgraded, downgraded, or migrated to a different configuration within the same offer family.

High-speed upgrades typically involve the same commercial product family (e.g., “Internet”) but with modified attributes such as speed tier, bandwidth profile, SLA level, etc. The Change of Plan MACD:

Reuses the existing asset

Captures the new configuration

Decomposes into new or modified technical actions

Avoids unnecessary disconnect/reconnect cycles

Preserves billing continuity

Minimizes order orchestration overhead

Options B (Disconnect & New Order) and C (Modify Order) are not correct: Disconnect/New Order is used only when replacing an entire product with a materially different offering, not speed upgrades. A Modify Order MACD adjusts non-plan attributes—not plan-tier changes. Option D (Apply Promotion) is irrelevant here.

Thus, Change of Plan is the correct MACD for upgrading customers to high-speed offers.

To prevent Einstein from marking the competitor’s product incorrectly as their own product when measuring their share-of-shelf, the field rep should edit product tags. Product tags are labels that identify and count products in an image using Einstein Vision. Einstein Vision is a feature that uses artificial intelligence to detect and count objects in an image. By editing product tags, the field rep can correct any errors or inaccuracies in the object detection process and ensure that their own products and their competitor’s products are tagged correctly. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 24.

Enterprise Sales Management (ESM) for B2B telecom includes Location-Based Feasibility (LBF), which checks whether a product (e.g., fiber, Ethernet access, MPLS, DIA) is technically feasible at a given customer location or site. This is a standard requirement in enterprise fixed-line quoting.

LBF provides:

Real-time or batch feasibility lookup

Integration with GIS, network inventory, or legacy feasibility engines

Support for multi-site enterprise quoting

Feasibility responses (yes/no/conditional)

Auto-blocking non-feasible service requests

Location-Based Serviceability (A) is used in B2C broadband/mass-market sales, not complex enterprise quoting. Product Availability (C) and Eligibility Rules (D) control catalog eligibility, pricing, or contract conditions, not technical feasibility.

Out of Stock, Share of Shelf, and SKU Facings are three KPIs that can be derived using Planogram detection. A Planogram is a visual representation of how products should be arranged on a shelf. Planogram detection is a feature that uses Einstein Vision to compare the actual shelf image with the expected planogram image and calculate metrics such as:

Out of Stock, which measures the percentage of products that are missing from the shelf.

Share of Shelf, which measures the percentage of space occupied by a product or brand on a shelf.

SKU Facings, which measures the number of times a product SKU is visible on a shelf. Verified References: [Salesforce Consumer Goods Cloud Implementation Guide], page 23-24.

This approach allows for an efficient and code-minimal way to check compliance of high-value assets in stores and trigger correction action plans based on Boolean values.

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.