Free Salesforce Accredited Agentforce Communications Professional Practice Questions

MACD processing depends on both the customer ' s commercial Assets and the technical inventory state used by Industries Order Management during decomposition. For large estates, the migration should be partitioned and staged so that operational continuity is preserved. Migrated Assets must also have corresponding technical inventory available, commonly created by processing NoChange activity or by another controlled inventory-initialization approach before later MACD orders rely on that state. The key is to represent the requirement in the same layer where Salesforce evaluates that business state. Migrating only commercial Assets leaves Order Management unable to recognize technical resources that already exist. A single monolithic migration also increases operational risk and makes error isolation, reconciliation, and cutover management substantially harder. This avoids mixing customer-facing product logic with downstream technical state or using integration code as a substitute for catalog and orchestration design. When the model is aligned correctly, the platform can validate the request, retain the required lifecycle information, and generate the appropriate downstream action without redundant processing. That improves auditability and makes later changes easier because administrators can adjust the relevant metadata rather than reworking multiple custom components.

Study Guide Reference:Asset migration; Technical Inventory; NoChange MACD; phased migration; MACD readiness.

There are two declarative ways to derive the billing representation from speed characteristics. One is to keep a single CFS, map upload/download speeds into it, and use a Calculation Matrix invoked through an Integration Procedure to return the correct billing code. The other is to use conditional/attribute-based decomposition so that speed combinations select the appropriate technical CFS or fulfillment variant that already carries the billing code. The recommended configuration follows the native Communications Cloud responsibility boundary: catalog and CPQ determine the commercial request, while Order Management, OmniStudio, or the relevant platform service performs the downstream processing required by the use case. An unconditional mapping cannot choose among speed-dependent outcomes, and custom Apex is unnecessary when the standard calculation and decomposition mechanisms can express the mapping. Avoiding duplicate logic is important because repeated rules across catalog, integration, and orchestration layers quickly become inconsistent as products evolve. The selected approach keeps the authoritative data in the correct object model, supports later lifecycle operations, and minimizes additional processing or manual intervention. It should be implemented declaratively wherever the platform feature can express the requirement, with customization reserved only for behavior that genuinely falls outside the supported framework.

Study Guide Reference:CFS modeling; attribute-based decomposition; Calculation Matrices; Integration Procedures; billing-code derivation.

A limited-time customer offer is modeled as a Promotion, while the duration of the promotional pricing is controlled with a Time Plan. The promotion packages the commercial incentive that is exposed through the digital channel, and the Time Plan defines the three-month period during which the reduced price remains effective before normal pricing resumes. This approach is preferable because it uses the platform feature designed for the exact lifecycle stage involved, rather than forcing the requirement into a neighboring layer. A standalone discount does not provide the complete promotional lifecycle and duration semantics, and an Offering is the sellable product itself rather than the temporary commercial campaign applied to it. In Communications Cloud, that separation materially affects maintainability, performance, and the accuracy of future MACD or order-processing behavior. The solution should therefore preserve parent-child and inventory dependencies, use standard qualification or orchestration semantics, and ensure that downstream systems receive only the information relevant to their responsibility. The same design also simplifies regression testing because the business rule is expressed in one authoritative place and can be validated independently from unrelated product or integration behavior.

Study Guide Reference:Promotions; Time Plans; promotional pricing; Digital Commerce; limited-time offers.