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

“Transaction Types define how Revenue Cloud interprets pricing, eligibility, and discount logic for a specific transaction (Sales, Amendment, Renewal, Cancellation, etc.).”

“Volume-Based Pricing applies tiered or bulk discounts based on quantities but can be conditioned by Transaction Type.”

“For initial sales, use the Sales Transaction Type. For renewals or amendments, different types apply.”

Step-by-Step Reasoning:

Requirement: Apply bulk discounts only for business-to-business (B2B) sales (initial purchases).

Solution:

Configure Volume-Based Pricing rules.

Condition them on Sales Transaction Type (so they apply only during initial sales).

Why B is Correct:

Sales Transaction Type accurately represents new B2B purchases.

Enables separation of pricing logic by channel or buyer type.

Why Others Are Incorrect:

A: Quote Transaction Type is metadata used in CPQ quoting but not for pricing control logic.

C: Order Transaction Type applies post-sale; discounts must be calculated pre-order in pricing.

References :

Salesforce CPQ Implementation Guide — Volume-Based Pricing and Transaction Type Logic

Salesforce Subscription Management Implementation Guide — Sales and Renewal Transaction Configuration

Salesforce Billing Implementation Guide — Pricing Control via Transaction Type

The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle-managed records (e.g., originating from CPQ+ or Subscription Management flows).

This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK’s app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce.

Option B suggests creating a custom field, which is unnecessary since the platform already provides a system field for this purpose.

Option C (Asset Action Source) refers to tracing asset actions to originating events, but it is not suitable for broad classification of asset origin or management type.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide – “Asset Data Model”:“The HasLifecycleManagement field flags whether an asset is lifecycle-managed by Revenue Cloud. This is useful in environments where assets come from multiple systems.”

Revenue Cloud Data Dictionary – “Asset Object”:“Use HasLifecycleManagement to distinguish system-managed assets from externally generated or legacy assets.”

In Salesforce Revenue Cloud’s Contract Lifecycle Management (CLM) module, Obligations are used to track post-signature responsibilities and ensure compliance with contractual commitments. An obligation represents an actionable item tied to a contract clause, such as delivering a report, making a payment, or completing a follow-up.

One of the primary benefits of creating obligations is the ability to:

Assign Owners (users or roles)

Attach Tasks

Set due dates, statuses, and related metadata

This allows organizations to track performance on obligations over the lifecycle of the agreement and maintain accountability.

Option A is correct, as assigning owners and tasks is core to the obligation management model.

Option B is partially correct but too narrow; the Fulfilled status is only one aspect of the obligation lifecycle.

Option C is incorrect — price discounts are managed through pricing rules, not obligations.

Exact Extracts from Salesforce Revenue Cloud Documents:

CLM Implementation Guide – “Obligation Management”:“Obligations allow contract owners to assign responsibilities to individuals and track their completion using tasks, due dates, and fulfillment status.”

Revenue Cloud CLM Overview – “Post-Signature Lifecycle Features”:“Use obligations to monitor compliance with agreed-upon clauses by assigning tasks to the appropriate business users.”

Exact Extracts from Salesforce CPQ (Advanced Configurator and CML Guide):

“CML allows you to define typed relationships and constraints within bundles or configurable products.”

“The relation syntax defines cardinality using [min..max] where 0..5 means minimum zero and maximum five related components.”

“The require() statement conditionally enforces the inclusion of components based on logical conditions. The syntax require(condition, target{attribute=value}) is used to mandate configuration rules.”

Step-by-Step Reasoning:

Requirement Analysis:

The “House” can have up to five rooms (0..5).

If more than three rooms exist, include MediaRoom with color = “Blue.”

CML Construction:

Define relation rooms : Room[0..5] to allow zero to five rooms.

Apply require() to enforce conditional inclusion based on count logic.

Why B is Correct:It follows correct CML syntax and semantics:

Proper cardinality expression [0..5].

Correct conditional requirement referencing rooms[MediaRoom]{color="Blue"}.

Why Others Are Incorrect:

A: Cardinality [4,5] enforces a minimum of 4 rooms always—violates the “up to five” requirement.

C: Misuses the House reference inside require(), which should target the related entity (rooms).

References :

Salesforce CPQ Advanced Configurator Developer Guide — Constraint Modeling Language (CML) Syntax and Semantics

Salesforce CPQ Implementation Guide — Advanced Product Configuration and Conditional Rules

Explanation (150–250 words)

In Salesforce Revenue Cloud, managing lifecycle assets—including creating Asset Actions, Asset State Periods, and editing lifecycle-related fields—requires the Customer Asset Lifecycle Management permission set or equivalent access.

This permission enables users to:

Generate and update Asset Actions (e.g., Amend, Renew, Cancel).

Create and edit Asset State Periods for lifecycle tracking.

Modify fields on Lifecycle-managed Assets, which are governed by Subscription Management.

Without this permission, users cannot manipulate lifecycle structures that track asset events or transitions. Option B (“Lifecycle-managed asset”) refers to the object model concept, not a permission. Option C lists lifecycle action permissions but lacks the administrative scope to create and edit the underlying asset records and periods.

Exact Extract from Salesforce Subscription Management Implementation Guide:

“Users managing lifecycle assets, asset actions, or state periods must have the Customer Asset Lifecycle Management permission to access, create, or modify lifecycle-related records.”

Comprehensive and Detailed Explanation From Exact Extract:

In Revenue Cloud Product Catalog Management, Browse Catalog product visibility is controlled using Qualification Rules and Product Qualification decision tables. The standard (“out-of-the-box”) decision table and related qualification rule procedures are designed exactly for use cases like:

Hiding or showing products based on contextual criteria such as region, industry, customer segment, etc.

Evaluating product visibility during Product Discovery / Browse Catalog.

The documented approach is to configure ProductQualification and Qualification Rule Procedures so that they reference customer region (for example, via Account or Quote fields) and drive visibility accordingly. This leverages standard Revenue Cloud capabilities instead of creating custom frameworks.

Option A (custom decision table) is possible but not the recommended Revenue Cloud–specific capability when there is already an out-of-the-box decision table built for product qualification.

Option B (separate price books per region) controls pricing, not visibility, and quickly becomes hard to maintain.

Comprehensive and Detailed Explanation From Exact Extract:

Revenue Cloud recommends using Qualification Rules for:

Contextual product visibility in Browse Catalog and Product Discovery.

Evaluating criteria like region, industry, and account attributes using decision tables and qualification procedures.

Multiple price books (A) address pricing, not visibility. Separate catalogs (B) can be used in some cases, but quickly become complex; qualification-based visibility is the scalable, recommended method.

When using the Products List (POST) API in Salesforce Revenue Cloud, developers can query and filter the list of available products using specific supported parameters. According to the Salesforce Product Catalog and Discovery API documentation, the valid and commonly used filters for the Products List API include:

Product2 IDs: to retrieve specific products directly by their ID

Catalog IDs: to filter products based on a specific product catalog

Category IDs: to filter products that belong to a particular category within a catalog

This allows developers to fetch only relevant products for a specific UI component or experience, such as in a Product Discovery component or a custom Lightning Web Component (LWC).

Option B includes Pricebook IDs, which are not supported as filter parameters in the Products List API. Pricebooks are used in pricing context but are not valid query parameters for this API endpoint.

Option C includes ProductClassification IDs, which are not supported directly in the POST filter payload of the Products List API.

Exact Extracts from Salesforce Revenue Cloud Documents:

Product Discovery API Developer Guide – “Products List (POST)”:“Use Catalog IDs, Category IDs, and Product2 IDs as input filters in the POST request to retrieve relevant product records for discovery or display.”

Revenue Cloud API Reference – “Querying Product Records”:“The Products List API supports filtering by catalog, category, and direct product identifiers. Pricebooks are not queryable through this API.”