Rev-Con-201 Exam Dumps - Salesforce Certified Revenue Management Consultant

The pricing procedure and associated predefined decision table are already active. Active pricing metadata is protected from structural changes that could invalidate runtime pricing. Therefore, the relevant components must first bedeactivatedbefore adding the currency dimension required for multi-currency pricing.

After deactivation, the organization can enable multi-currency and introduce Currency into the applicable decision-table/pricing configuration. Once the metadata is valid and synchronized, the decision table and pricing procedure can be reactivated.

Option A creates unnecessary duplicate procedures and decision tables. Cloning can be useful for versioning or major redesign, but it is not required simply to add the missing multi-currency dimension. Option B assumes the Currency field will automatically become usable after a waiting period; that does not address the inability to structurally modify already active decision-table and pricing metadata.

The key configuration principle is thatactive runtime pricing artifacts must be deactivated before making structural changes, then reactivated after the revised configuration has been completed.

Study Guide Reference:Configure, Price, Quote — Multi-Currency Pricing; Decision Tables; pricing procedure activation lifecycle.

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

The supplied source identifies anorder-line-based migrationusing the Create or Update Asset From Order Item Action API. The goal is not simply to copy CPQ Subscription records into Asset records; Revenue Management needs properly structured lifecycle-managed assets that can subsequently support amendments, renewals, and cancellations.

Converting the existing subscriptions into order-line representations provides the commercial transaction inputs from which Revenue Management can generate or update asset data consistently. The asset-creation action can then establish the lifecycle-managed representation required by the target platform.

Option B uses Place Sales Transaction for a different transaction-processing purpose and is not the migration mechanism identified for converting the installed subscription base. Option C misuses Initiate Amendment. Amendment assumes an existing lifecycle-managed asset that is being changed; it is not the foundational migration operation for importing CPQ subscriptions.

Migration architecture is important because downstream lifecycle processes depend on more than Product2 and Asset records. Asset Actions, State Periods, and transaction lineage must remain logically coherent.

Study Guide Reference:Asset Management — Salesforce CPQ migration; asset migration from order items; lifecycle-managed assets.

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

There are two independent price-impacting attributes:MemoryandContract Term. Memory has three possible values—128 GB, 256 GB, and 512 GB—while Contract Term has two possible values—12 months and 24 months.

The number of unique pricing combinations is therefore:

3 memory values × 2 contract-term values = 6 combinations.

Each combination can require its own Attribute-Based Adjustment entry because the administrator wants pricing to vary based on the specific pair of selected attribute values. Examples include 128 GB/12 months, 128 GB/24 months, 256 GB/12 months, and so forth until all six combinations are represented.

Option B accounts only for the three memory choices and ignores the term dimension. Option C does not correspond to the Cartesian product of the two attribute value sets.

After the applicable price is identified from the adjustment schedule, the total can be divided across the selected number of months. Because there is no interest, no financing-rate calculation is required.

Study Guide Reference:Configure, Price, Quote — Attribute-Based Pricing; price-impacting attributes; Attribute-Based Adjustments.

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

The sales rep requiresProduct Discovery Useraccess to use the product-browsing experience during quote and order creation. Salesforce explicitly defines Product Discovery User as the permission set that gives users access to the product browsing experience. It is normally included as part of the Sales Operations or Revenue Management sales-user access model.

Product Discovery controls the runtime experience in which a sales rep selects a catalog, searches or filters eligible products, and adds those products to a sales transaction. Without the required Product Discovery access, the sales rep cannot properly invoke that browsing functionality.

Option A addresses a different stage. Product Configurator provides access to configure products and bundles after a configurable product has been selected. It does not grant the basic product-discovery capability. Option B is a design-time permission set used by administrators or product designers to create Product Configuration Rules; it should not be assigned merely so a sales rep can browse products.

Consequently, missing Product Discovery User permission is the configuration issue most directly associated with the absent Browse Products/Browse Catalogs functionality.

Study Guide Reference:Catalog Management — Product Discovery; Revenue Management permission sets; Product Discovery User.

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

Adisqualification ruleis the most efficient design because the product is available almost everywhere and prohibited in only two exceptional countries. Salesforce Product Catalog Management treats products as generally qualified and allows qualification/disqualification logic to determine customer eligibility and availability during Product Discovery.

Salesforce specifically illustrates this design pattern: when a newly launched product is available everywhere except a small number of locations, it is simpler to create disqualification criteria for the exceptions rather than qualification records for every permitted location.

A qualification-rule design would require representing the much larger allowed set—in this scenario, 36 countries. A disqualification design requires only the two prohibited-country conditions, minimizing maintenance, data volume, and administrative complexity. Recommendation rules do not enforce eligibility; they help suggest appropriate products rather than preventing prohibited ones from being sold.

During Product Discovery, disqualified products can be excluded from Browse Catalogs so sales reps cannot add them to quotes or orders for restricted customers.

Study Guide Reference:Catalog Management — Product Qualification and Disqualification; Product Discovery; geographic eligibility rules.

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

AStandard Amendmentis the appropriate lifecycle transaction when an active customer ' s existing product configuration must change during the current term. Changing a price-impacting product attribute is a modification to the existing asset state and therefore fits the amendment lifecycle.

The amendment can bring the lifecycle-managed asset into a quote or order, allow the relevant configurable attributes to be changed, recalculate pricing where necessary, and then process the resulting order so that the asset ' s lifecycle state is updated.

Option A, Cancel/Replace, is unnecessarily disruptive because the customer is not replacing the entire subscription or product arrangement. The requirement specifically states that only selected attributes need to change. Option C, Early Renewal, starts a new renewal period earlier than normal and is appropriate where the commercial intention is to renegotiate or replace the term, not merely update attributes during the existing term.

Using Standard Amendment preserves the existing contract and transaction lineage while applying only the required configuration changes.

Study Guide Reference:Asset Management — Amendments; configurable asset attributes; price-impacting attribute changes.

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

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.

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

The requirement is to delay execution of a fulfillment step until a future point relative to another fulfillment milestone. Therefore, the relevant Dynamic Revenue Orchestrator capability isFuture-Dated Steps.

Once enabled, a fulfillment plan can represent temporal dependencies such as provisioning software two days after hardware delivery rather than executing immediately when the predecessor completes. This supports business processes involving activation windows, scheduled installations, cooling-off periods, delayed provisioning, or other time-dependent fulfillment behavior.

Option B grants broad Salesforce administrative access but does not expose a functional DRO scheduling capability. Modify All Data is also inappropriate from a least-privilege perspective and would not solve a missing feature-setting issue. Option C concerns linking tasks or orchestration metadata rather than enabling future-dated execution.

The scenario provides a strong diagnostic clue: the Fulfillment Designer cannotsee the optionrequired to configure a delay. This indicates that the organizational DRO feature setting has not been enabled rather than the plan logic being incorrect.

Study Guide Reference:Contracts and Orders — Dynamic Revenue Orchestrator; fulfillment plans; Future-Dated Steps and fulfillment dependencies.

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