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

Salesforce best practice for Order Management is:

▶ Use a single Orchestration Plan Definition when the overall fulfillment flow is the same,

but

▶ Use conditional Orchestration Items to handle differences (e.g., activation vs. deactivation).

In this case, the provisioning system needs different payloads for activation and deactivation, but the product is the same. Designing two separate orchestration plan definitions creates duplication, maintenance overhead, and inconsistent lifecycle behavior.

Instead:

Use one Orchestration Plan Definition.

Include two Orchestration Item Definitions, one for Activation and one for Deactivation.

Apply mutually exclusive conditions using Product Action = Add (activation) or Disconnect (deactivation).

Map both actions in one Scenario.

This achieves minimal configuration and full flexibility.

In Salesforce Communications Cloud, when multiple commercial offers decompose into the same technical product, the system performs attribute mapping during decomposition using the configured Commercial-to-Technical Product relationships. Public Industries documentation explains that when two or more commercial products share an attribute with the same target technical product attribute, the system does not throw an error automatically. Instead, Communications Cloud uses a “last write wins” behavior during value assignment.

In this scenario, both the Internet and TV commercial offers have the same attribute “Installation Type”, and both map to the same attribute on the shared technical product (access line). When a customer orders Internet + TV together, the decomposition engine executes sequentially. The attribute mapping is processed for the Internet offer first (or whichever is configured first in the order). Next, the TV offer decomposes and updates the same attribute on the same technical product instance.

Because no conflict-handling mechanism is defined out of the box, and no mutual-exclusivity rules are enforced by default, the value from the last processed offer simply overwrites the earlier one. This is expected behavior in native EPC + OM decomposition when two attributes of identical name and mapping collide.

Therefore:

No design-time error occurs → eliminating option B.

No runtime decomposition error occurs → eliminating option D.

The attribute is not set to null → eliminating option C.

The system instead sets the technical product’s Installation Type to whichever product’s value was processed most recently.