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.