Salesforce Certified Industries CPQ Developer Free Sample Questions

The correct sequence involves encapsulating the pricing logic within a Pricing Plan. The Pricing Plan acts as the bridge between the product and the detailed calculation logic. The plan contains steps, one of which will invoke the 'CalculateFiberPrice' Calculation Procedure. This entire plan is then associated with the product via its Price List Entry, ensuring it's triggered during pricing.

Advanced Rules, including compatibility rules, rely on Product Relationship records to understand the connections between products. If the relationship (e.g., 'Requires') is not defined between the '4K Video Add-on' and 'Premium Internet', the rule has no relationship to evaluate.

Entity Filters are used by Advanced Rules to define the set of items to which the rule applies. If the filter's conditions are incorrect, it might not be selecting any line items in the cart, causing the rule to be skipped.

Digital Commerce APIs are specifically architected for high-volume, customer-facing scenarios. They leverage a caching layer (Scale Cache) to provide fast responses for catalog and offer retrieval, making them ideal for guest user and B2C storefronts where performance is critical.

This statement is false. Product Configuration Procedures are powerful and can perform a wide range of actions. By using specific procedure actions (like 'Add/Remove Item' or by manipulating the cart JSON and calling a remote action), a developer can dynamically add or remove optional child products from the bundle based on user input during the guided selling flow.

For the CPQ engine to recognize and process a usage-based price, a Pricing Element must be explicitly defined with a 'Charge Type' of 'Usage'. This Pricing Element must then be associated with the product's price list entry. Furthermore, it needs to be linked to a 'Charge Measurement' record, which defines the unit of measure (e.g., kWh, Gigabytes, Minutes). Without this link, the system doesn't know what unit the usage price applies to.

Context Rules are the standard mechanism for determining eligibility and qualification based on data outside the cart, such as fields on the Account, Contact, or Order objects. By creating a Context Mapping to the Account's loyalty field and using it in a Qualification Rule, the system can efficiently determine if the product should be available.

Industries CPQ heavily relies on a caching layer to improve performance. When new product or pricing metadata is deployed, the cache often holds stale data. Running the 'Clear Managed Platform Cache' or 'Refresh Platform Cache' job from the CMT Administration tab is a mandatory step to force the system to reload the latest configuration, including the new prices.

The Cart-Based APIs use the Field Mapper (%vlocity_namespace%__FieldMap__c) to control which fields are read from and written to SObjects like OrderItem. To include a custom field in the API response, a developer must create a new Field Map record that defines the mapping from the SObject field to the corresponding key in the JSON payload.

Industries CPQ allows price adjustments to be configured directly on child items within a bundle structure. This is the most direct and maintainable way to define pricing that is specific to the context of a bundle. The adjustment will only apply when the 'Live Sports Add-on' is configured as part of the 'Streaming Service' bundle.

During MACD operations, Industries CPQ uses fields on the line item to control behavior. When an asset is brought into the cart for a 'Change' order, the system can be configured to mark it with a Charge Type of 'Existing'. This tells the pricing engine to preserve the original price from the asset instead of recalculating it, unless there is a change that explicitly triggers a reprice.