Last Attempt Rev-Con-201 Questions

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 user already has the required permissions and licenses, and the scenario explicitly confirms that active assets exist. Therefore, the remaining issue is theAccount page configuration.

The Managed Asset Viewer must be placed on the relevant Lightning record page to give users the specialized lifecycle-management interface used to review and initiate asset transactions. The Asset-related presentation must also be available as required by the configured page experience. If these components are absent, valid asset data can exist in Salesforce while remaining unavailable from the Account page where the user expects to manage it.

Option A concerns the lifecycle flow executed after a user initiates Amend, Renew, or Cancel. It does not explain why the existing assets themselves are not visible. Option B directly conflicts with the scenario because the assets are stated to be active.

This illustrates the separation betweensecurity, underlying lifecycle data, and Lightning user-interface configuration. All three must be properly configured for users to manage assets successfully.

Study Guide Reference:Asset Management — Managed Asset Viewer; Account Lightning Record Page configuration; asset visibility and management.

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

This requirement has bothindividual component limitsand acombined group limit, which is why option B is correct. Local cardinality controls the valid quantity range for each product relationship. Setting T-shirts to 1–3 and caps to 1–3 prevents either component from exceeding three units.

However, local limits alone would still permit three T-shirts plus three caps, producing six items. The designer therefore also needs a Product Group containing both components with a maximum group cardinality of five. That second constraint limits the aggregate number selected across the group.

Option A incorrectly forces exactly three units of each component and simultaneously permits six at group level, directly violating the requirement. Option C controls only T-shirts and does nothing to constrain caps or the combined bundle quantity.

This illustrates the distinction betweenlocal cardinalityandgroup cardinalityin product modeling. Local cardinality constrains an individual component relationship, while group cardinality constrains selection or quantity across a set of grouped products.

Study Guide Reference:Catalog Management — Product Bundles; Product Groups; local and group cardinality.

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

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.

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