The Products List API is part of the Product Discovery runtime interface and supports retrieving commercial products according to catalog and category context and specific product identifiers. Therefore,Product2 IDs, Catalog IDs, and Category IDsare valid request criteria for narrowing the products returned to the consuming application.

These parameters align directly with the Product Catalog Management model. Product2 identifies the commercial product itself, Catalog identifies the catalog within which products are published, and Category identifies the navigational/product grouping used in catalog browsing.

Pricebook IDs belong primarily to the pricing domain. Although price books are associated with selling and pricing products, they do not substitute for the product-discovery query parameters described in this API scenario. ProductClassification IDs represent reusable product modeling and attribute structures rather than the primary list-query criteria identified by the question.

The developer can therefore submit a Products List POST request using the supported identifiers and consume the resulting JSON response from the Lightning web component.

Study Guide Reference:Catalog Management — Product Discovery APIs; Products List API; catalogs, categories, and Product2 identifiers.

===============

Adding an attribute to a context definition changes the definition metadata, but Revenue Management services do not consume that revised structure until the context definition isactivated. Activation publishes the current definition so dependent services such as Salesforce Pricing can use its nodes and attributes.

That explains why the newly created custom field is visible in the context-definition configuration but unavailable when the consultant attempts to reference it from the pricing procedure. The definition has not yet been promoted into an active runtime state.

Option A is not the primary missing step identified in this scenario. Tags can be important for locating and semantically identifying contextual attributes, but they do not substitute for activating the modified context definition. Option C is unnecessary. A pricing procedure does not need to be cloned merely because another usable attribute has been added to its associated context.

The correct sequence is to modify the context definition, complete the required mappings,activate the definition, and then configure the pricing procedure to consume the newly available attribute.

Study Guide Reference:Configure, Price, Quote — Context Service and Salesforce Pricing; context definitions; activation and pricing procedure inputs.

===============

Derived Pricing depends on the pricing procedure receiving the correctinput variablesand exposing the resulting value through the appropriateoutput variable. Here, the warranty price must be derived as 10% of the related equipment product ' s list price. If the calculation works for other products but not this warranty, the consultant should inspect the Derived Price element and verify that the required variables are correctly configured.

The pricing procedure needs access to the source equipment price and must write the calculated warranty price into the variable subsequently used by the pricing waterfall. Missing or incorrect variable mappings can cause the element to run without producing the expected result.

Option B changes pricing scope, but the supplied source identifies variable configuration as the defective element in this scenario. Option C is not the relevant Revenue Management configuration pattern; price book entries do not become derived-price sources merely through an Is Derived setting.

Effective troubleshooting requires examining the actual pricing element responsible for the calculation and confirming its inputs and outputs before changing unrelated product metadata.

Study Guide Reference:Configure, Price, Quote — Derived Pricing; pricing procedure elements; input and output variables.

===============

The critical missing skill isSalesforce integration expertise, including REST APIs. The company is implementing omni-channel selling in which Revenue Management transactions originate both from Salesforce sales representatives and from an external third-party website.

The external channel must exchange product, catalog, pricing, quote, order, or other transactional information with Revenue Management. That requires understanding API authentication, request and response structures, integration error handling, transaction limits, data mapping, and the Revenue Management business APIs appropriate for the external commerce scenario.

Option B, Salesforce Flow expertise, remains valuable for internal process automation but does not solve the core external-system integration requirement. Option C may become necessary if specialized user-interface or server-side extensions are required, but the scenario ' s decisive architectural requirement is communication between the third-party website and Salesforce.

Implementation readiness therefore requires staffing according to the architecture rather than only the existing administrators ' skill set.

Study Guide Reference:Implementation Readiness — Implementation Team Skills; REST APIs; external commerce integration; omni-channel Revenue Management architecture.

===============

The Transaction Line Editor is configured as aLightning componenton the transaction record page. To expose an existing supported custom field such as Estimated Delivery Date, the consultant should edit the Quote Lightning Record Page in Lightning App Builder, select the Transaction Line Editor component, and add the field to its configured selected fields.

This approach changes the columns or information presented directly within the Transaction Line Editor without requiring changes to the underlying quote-line page layout or pricing behavior.

Option B is incorrect because Instant Pricing controls when pricing recalculates as users modify transaction data. It does not automatically expose every custom field in the editor. Display configuration and pricing execution are separate concerns. Option C modifies the conventional Quote Line Item page layout, but the Transaction Line Editor has its own component-level field configuration; adding a field to a standard page layout does not automatically make it appear inside the specialized editor.

The key exam distinction is betweenLightning component configurationand traditional page-layout configuration. Transaction Line Editor presentation is customized from the component properties on the Lightning Record Page.

Study Guide Reference:Configure, Price, Quote — Transaction Management; Transaction Line Editor customization; Lightning App Builder.

===============

Dynamic Revenue Orchestrator ' sDecomposition Scopecontrols how many instances of a technical fulfillment product are generated when multiple commercial order lines decompose to the same technical product.

Salesforce documents this exact Shipping Service pattern. When many commercial products all decompose into a common Shipping Service technical product and the business does not want an independent shipping instance for every product, the Shipping Service ' s decomposition scope should beOrder. With Order scope, DRO creates one fulfillment order line item for that technical product per order regardless of how many commercial lines require it.

Bundle scope would create one Shipping Service instance for each bundle in the order. That is useful when each bundle must be fulfilled separately, but it does not meet the stated requirement to consolidate all products in the order into one shipping treatment. Account scope is broader still: it can consolidate across multiple orders from the same customer account, which can unintentionally combine logically separate customer orders.

Thus Order scope provides the correct many-to-one fulfillment granularity:one Shipping Service fulfillment line for the entire order.

Study Guide Reference:Contracts and Orders — Dynamic Revenue Orchestrator; Decomposition Scope; many-to-one decomposition; technical products.

===============

The correct first step is to useSimulateon the pricing procedure. Simulation allows the consultant to evaluate pricing logic in a controlled manner and inspect how individual pricing elements contribute to the final value. This is particularly valuable for complex transactions involving subscription pricing, add-ons, usage tiers, discounts, and contract-driven adjustments.

The consultant should trace the price waterfall from the initial price through applicable adjustments and identify where the calculated amount diverges from expected commercial terms. That provides evidence about whether the problem lies in input context, a decision table, an adjustment, an incorrect procedure step, or another pricing element.

Option A masks the issue by overriding the calculated amount without identifying the defective configuration. Option B is similarly inappropriate; deactivating and reactivating the entire procedure does not diagnose pricing logic and can create operational impact.

A structured troubleshooting approach begins by reproducing and tracing the calculation before modifying configuration. Simulation is therefore the appropriate diagnostic mechanism.

Study Guide Reference:Configure, Price, Quote — Salesforce Pricing; pricing procedures; Simulate; price-waterfall troubleshooting.

===============

The consultant shouldextendthe standard Sales TransactionContext. Extension is designed for exactly this requirement: retain the standard context definition as the inherited foundation while adding organization-specific nodes, attributes, mappings, or other custom components.

The key advantage is upgradeability. Because the customized definition maintains an extension relationship with the standard context rather than becoming an independent copy, upgraded standard components can be incorporated while preserving the customer ' s extension-level customizations.

Cloning, option B, creates an independent context definition. Although a clone provides an immediate copy of standard components, subsequent standard enhancements are not naturally inherited because the clone no longer maintains the same extensibility relationship. Over time, this creates additional maintenance and reconciliation effort.

Option A is also insufficient. Simply upgrading the standard Sales TransactionContext does not provide a controlled location for customer-specific additions and may conflict with the requirement to preserve customizations separately from Salesforce-managed standard content.

This exemplifies an important extensibility principle in Agentforce Revenue Management:extend standard metadata instead of copying or directly modifying it when future Salesforce upgrades must remain consumable.

Study Guide Reference:Agentforce Revenue Management Platform Concepts — Context Service; context definitions; extending standard context definitions; upgrade strategy.

===============

Revenue Management Billing provides native invoice schedulers for automated invoice generation. A Billing Operations user can create an Invoice Scheduler, configure its start date, start time, time zone, activate it, and select a recurrence frequency such as Daily, Weekly, or Monthly.

For the stated requirement, the appropriate configuration is therefore a recurring weekly invoice run scheduled for Monday at 6:00 AM. The scheduler ' s target-date logic determines which Billing Schedules are eligible for that execution, allowing completed schedules from the relevant period to be processed automatically.

A Billing Treatment controls how an order product is billed; it does not function as the enterprise scheduling mechanism for a Monday 6:00 AM invoice batch. Option C unnecessarily introduces custom automation. Salesforce already supplies invoice batch scheduling and specifically recommends using Invoice Schedulers for recurring invoice-generation requirements.

The Billing Operations User permission set is also the documented permission for creating invoice schedulers. Salesforce ' s Billing Trailhead material reinforces that invoice batch runs can be scheduled to automate invoice generation instead of requiring custom flow logic.

Study Guide Reference:Invoice Management — Generate Invoices; automated invoice generation; Invoice Schedulers and recurring invoice batch runs.

===============

A Contract Extraction Template must connect the information that Contracts AI extracts from a source document with the structured Context Service model used to store or process that information. The relevant template details are thereforeAttribute Definition and Context Mapping.

The Attribute Definition specifies what contract information should be extracted—for example, payment terms, renewal language, termination conditions, notice periods, or custom contractual fields. Context Mapping identifies where that extracted attribute fits within the selected context definition so that Contracts AI can transform unstructured PDF content into structured Revenue Management data.

Option A focuses on Record Type and Field Mapping but does not supply the context-level attribute definition required by the extraction architecture. Option B combines Attribute Definition with Field Mapping but omits the Context Mapping needed to associate extracted information with an existing context definition.

This design reflects the broader Agentforce Revenue Management architecture in which Context Service provides a standardized data representation consumed across services. Contracts AI uses the extraction template to bridge unstructured contract documents and that structured contextual model.

Study Guide Reference:Contracts and Orders — Contracts AI; Contract Extraction Templates; Attribute Definitions; Context Mapping.

===============