Revenue Cloud Consultant Rev-Con-201 Passing Score

The standardHasLifecycleManagementindicator differentiates lifecycle-managed Revenue Management assets from assets that are maintained outside the Revenue Management lifecycle framework. This distinction is critical in a merged environment where both organizations use the standard Asset object but only one set of assets is governed by Agentforce Revenue Management lifecycle processing.

Lifecycle-managed assets participate in the Asset Action, Asset Action Source, and Asset State Period model that enables structured amendment, renewal, cancellation, and other lifecycle transactions. Assets originating from CK ' s custom process can remain conventional assets until the processes are consolidated or migrated.

Option B could technically categorize records but introduces unnecessary customization because the question explicitly asks for an out-of-the-box mechanism. Option C misunderstands Asset Action Source. Asset Action Source records provide transactional lineage for lifecycle-managed assets; they are not a universal source-system classification field for distinguishing Revenue Management and non-Revenue-Management assets.

Salesforce also emphasizes that migrated assets require the lifecycle supporting records when they are expected to participate in Amend, Renew, and Cancel operations.

Study Guide Reference:Asset Management — Lifecycle-managed assets; HasLifecycleManagement; coexistence and migration of asset models.

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

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.

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

Option A is correct because this persona must support three distinct activities: maintaining catalog records, browsing products, and testing configurable bundles. Salesforce definesProduct Catalog Management Designeras providing read-write access to Product Catalog Management objects and APIs and supporting Product Discovery setup.Product Discovery Usergrants access to the product-browsing experience.Product Configuratorprovides read-write access to Product Configurator objects and APIs, enabling users to configure and test bundles. Option B substitutes Advanced Configurator Designer and therefore lacks the required Product Configurator runtime access. Option C includes Product Configuration Rules Designer, which is intended for creating and managing configuration rules, but omits Product Discovery User. Therefore, only option A provides the complete permission combination required by the described persona. Study Guide Reference:Catalog Management — Product Catalog Management; Product Discovery; Revenue Management permission sets.

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.

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