In Salesforce Industries Enterprise Product Catalog (EPC), hierarchical product modeling with child specifications and cardinalities is natively supported, which makes option E correct. Defining a voice offer with a “phone add-on” child product and a cardinality of up to 700 leverages standard EPC capabilities such as product specifications, child relationships, and cardinality rules.
However, Salesforce guidance for EPC and Industries CPQ warns that very large cardinalities on child products can introduce performance and processing challenges, especially in high-volume telecom scenarios. During MACD (Modify, Add, Change, Disconnect) operations, every instance of the child product (each phone device) has to be evaluated, updated, and sometimes decomposed into order items or service orders. With hundreds of instances, this can lead to processing inefficiencies and long-running transactions, which supports statement A.
Additionally, although the model technically uses out-of-the-box features, extreme volumes (such as hundreds of children per parent) can stress the decomposition engine. Under heavy load or complex rule combinations, decomposition may time out or fail when the maximum number of instances are ordered, making C valid as well.
Option B is incorrect because EPC does support this pattern; flat-only modeling is not a requirement. Option D is incorrect because using OOTB features does not guarantee optimal MACD and decomposition behavior at very high instance volumes.
