Cisco®
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL®
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk®
ServiceNow®
All Vendors
  2. Home
  3. Exams
  4. Salesforce
  5. Rev-Con-201

Rev-Con-201: Salesforce Certified Revenue Cloud Consultant
Free Practice Exam Questions (page: 3)
Updated On: 10-Jan-2026

Page 3 of 22
PDF with 165 Questions

A Revenue Cloud Consultant needs to run a report on the attribute runtime values when an order is activated and asset records are created. On which objects should the consultant base the report?

  1. Asset State Periods and Asset State Period Attributes
  2. Asset State Periods and Order Product Attribute
  3. Asset Action Source and Product Attribute Definition

Answer(s): A

Explanation:

Asset State Periods and Asset State Period Attributes are the correct objects for reporting on attribute runtime values at the time of asset creation. According to the Revenue Cloud Developer Guide, AssetStatePeriodAttribute represents a virtual object that holds key-value pairs of asset attributes in a specified asset state period.

When an order is activated, Revenue Cloud automatically creates assets from the order products. Along with asset creation, the system generates an initial Asset State Period representing the timespan when the asset has specific quantity, amount, and monthly recurring revenue (MRR) values. Critically, all product attributes configured during quoting are stored as Asset State Period Attributes, creating a permanent record of the exact attribute values at the time of asset creation.

Asset State Period Attributes is a child object of Asset State Period and is available in API version 60.0 and later. The AssetStatePeriodAttribute object stores the AttributeName, AttributeValue, and AttributePicklistValueId for each configured attribute. This relationship allows consultants to query attributes at their point of asset creation and track attribute runtime values across the asset's lifecycle. The Asset State Period object itself contains metadata about when the attribute values were active.

Option B conflates different object types; Order Product Attribute stores attributes on orders, not on assets. Option C (Asset Action Source and Product Attribute Definition) provides historical and definition-level information but not the actual runtime attribute values stored when assets are created. Asset State Period Attributes specifically captures the attribute state at asset creation time.


Reference:

Revenue Cloud Developer Guide - AssetStatePeriodAttribute object, Asset State Period object documentation, Attribute Flow in Revenue Cloud



A company's IT team is planning to implement Revenue Cloud. Their team consists of business analysts and administrators. The company plans to solve a complex and major use case of omni- channel selling, allowing its customers to buy directly from its third-party website as well as via its sales reps. The company also plans to hire new staff to support this project.
Which skill set does the IT team need to successfully implement this project?

  1. Expertise in Salesforce Integration, including REST APIs
  2. Expertise in Salesforce flows
  3. Expertise in Apex and Lightning Web Component development

Answer(s): A

Explanation:

For implementing omni-channel selling with Revenue Cloud where customers can purchase directly from a third-party website and through sales reps, expertise in Salesforce Integration with REST APIs is essential. This integration skill enables the company to connect Revenue Cloud with external systems and third-party platforms.

Revenue Cloud is built on an API-first, modern architecture where every pricing, quoting, and revenue process is exposed via APIs. To enable direct purchases from a third-party ecommerce website while simultaneously processing sales rep transactions, the technical team must understand how to integrate external systems with Revenue Cloud through REST APIs. These APIs allow the website to communicate with Revenue Cloud, create quotes, submit orders, and manage the quote- to-cash process programmatically.

The omni-channel requirement specifically demands integration expertise because the company must synchronize data between its website platform and Revenue Cloud. APIs like Place Sales Transaction, Create Order, and Product Discovery APIs provide the technical foundation for this integration. Without strong integration skills including REST API knowledge, the company cannot effectively connect multiple sales channels to Revenue Cloud.

While Option B (Flows) are useful for automation within Salesforce and Option C (Apex/LWC) can enhance functionality, they are not the primary skill needed for external system integration. Flows are low-code/no-code tools suitable for internal process automation, and custom Apex/LWC are typically tertiary requirements. Integration expertise with REST APIs is the foundational skill that directly addresses the omni-channel architecture requirement.


Reference:

Revenue Cloud API-First Architecture documentation, Revenue Cloud Developer Guide - Integration patterns, Place Sales Transaction API documentation, Revenue Cloud Omni-Channel Implementation



A global manufacturing company is implementing Revenue Cloud alongside Sales Cloud and Service Cloud. The company's product catalog spans multiple business units and markets. The catalog must support reusable attributes, configurable product bundles, and governance controls to prevent inconsistent updates. Stakeholders from product, sales, and IT are involved, but responsibilities need to be clearly defined to avoid bottlenecks and maintain catalog scalability.
Which role assignments support long-term product catalog governance?

  1. Product Managers own all catalog activities end-to-end since they manage product decisions.
  2. Catalog Administrator manages classifications and attributes. Product Designer defines product structures and bundles.
  3. Sales Operations manages attributes and classifications. Salesforce Administrator defines product bundles and hierarchy.

Answer(s): B

Explanation:

According to Salesforce Help documentation on "Product Catalog Management Personas for Revenue

Cloud," the correct role segregation for effective governance uses specialized personas with distinct responsibilities. The Catalog Administrator role manages classifications, attributes, and the broader catalog governance structure, while the Product Designer role focuses specifically on defining product structures and bundle configurations.

The Catalog Administrator persona administers Product Catalog Management, integrates Product Catalog Management features with other systems, maintains data integrity, and assigns permission set groups to other admins who handle specific areas of catalog management. This role ensures consistent governance across business units and markets. They control attribute definitions, product classifications, and reusable components that span the organization.

The Product Designer persona works within the governance framework established by the Catalog Administrator, focusing on designing specific product structures, configuring bundled products, and defining component relationships. Product Designers inherit standardized attributes and classifications from the Catalog Administrator and apply them consistently when building product offerings.

Option A (Product Managers owning all activities) creates bottlenecks and violates segregation of duties principles. Option C (Sales Operations managing attributes and Salesforce Admin managing bundles) splits responsibilities in a way that leads to inconsistency. The separation in Option B ensures that governance controls (classifications, attributes, reusability) are managed centrally by the Catalog Administrator while Product Designers execute within those controls, supporting scalability and preventing inconsistent updates across business units.


Reference:

Salesforce Help - Product Catalog Management Personas for Revenue Cloud, Product Catalog Management Editions and Permission Sets documentation



A Revenue Cloud Consultant is helping a customer service operations manager determine which product lines have the most order fallout.
Which steps should the consultant follow to enable the relevant dashboards?

  1. Within Revenue Settings, enable Revenue Management Intelligence and Install the Dynamic Revenue Orchestrator Analytics App.
  2. Within Revenue Management Intelligence Setup, complete Data Cloud Configurations and install the Dynamic Revenue Orchestrator Analytics App.
  3. Within Tableau Unified Analytics, create a recipe based on the FulfillmentFalloutRule object and design a dashboard with product line filter.

Answer(s): B

Explanation:

To enable dashboards that identify product lines with the most order fallout, the consultant must follow the Revenue Management Intelligence setup process documented in Salesforce Help. The correct approach involves accessing Revenue Management Intelligence Setup (not general Revenue Settings), completing necessary Data Cloud Configurations, and installing the Dynamic Revenue Orchestrator Analytics App.

Revenue Management Intelligence provides a comprehensive suite of Tableau Einstein dashboards specifically designed to assess revenue strategies and achieve cost-effective results. The Dynamic Revenue Orchestrator Analytics App includes specialized dashboards for order fulfillment analysis, including order fallout metrics by product line. These dashboards leverage data collected during the order fulfillment orchestration process.

The setup process requires completing Data Cloud Configurations first. Data Cloud serves as the unified data platform that ingests data from Revenue Cloud transactions, order fulfillment activities, and decomposition events. The configuration ensures that fulfillment data, including fallout metrics, flows properly into the analytics layer. Once Data Cloud is configured, installing the Dynamic Revenue Orchestrator Analytics App provisions the pre-built dashboards that analyze fulfillment performance and identify fallout patterns.

Option A references Revenue Settings, which is used for general Revenue Cloud enablement but not specifically for analytics setup. Option C mentions Tableau Unified Analytics and FulfillmentFalloutRule object, but this approach requires custom development and is not the out-of- the-box solution. The documented out-of-the-box approach through Revenue Management Intelligence Setup with Data Cloud Configurations and the Dynamic Revenue Orchestrator Analytics App is the correct path for accessing pre-built fallout analysis dashboards.


Reference:

Salesforce Help - Revenue Management Intelligence for Revenue Cloud, Set Up Revenue Management Intelligence documentation, Dynamic Revenue Orchestrator Analytics



A large enterprise customer, Universal Containers (UC), has negotiated a special, long-term agreement with a software vendor for its enterprise-wide licensing. This agreement includes custom pricing tiers, specific discounts that apply only to UC across various product families, and unique billing frequencies tied to UC's fiscal year. The sales team needs to ensure that all future quotes and orders for UC automatically reflect these pre-negotiated terms. How should the sales team consistently apply these specific pricing and billing conditions for UC?

  1. Use Discount Schedules on relevant products, with a Price Rule that applies these custom schedules only when UC is the designated account.
  2. Establish a dedicated price book for UC that is populated with UC's negotiated prices, and includes all custom rates and specific billing rules for its products.
  3. Create a Contracted Pricing record on the contract associated with the UC Account that details product-specific prices, tiered discounts, and special billing arrangements.

Answer(s): C

Explanation:

Contract Pricing in Revenue Cloud is the correct mechanism for managing long-term, negotiated customer-specific terms like those in UC's enterprise agreement. According to Salesforce Help documentation on "Contract Pricing in Revenue Cloud," Contract Pricing allows sales teams to negotiate and manage custom pricing agreements by creating Contract Item Prices and Price Adjustment Schedules tied to a specific contract.

When UC signs their enterprise agreement, a Contract record is created and associated with the UC Account. The sales team then creates Contracted Pricing records within this contract, detailing all product-specific prices, tiered volume discounts, and special billing arrangements unique to UC. These contract-based pricing terms become "the negotiated contract prices for the customer" that Revenue Cloud applies to future transactions.

When sales reps create future quotes or orders for UC, they can initiate them from the existing active contract using the "Start a New Quote or Order From a Contract" functionality. Revenue Cloud automatically applies the contract's negotiated prices and billing frequencies to all line items. Additionally, when amending or renewing UC's assets, the system maintains these contract-based pricing terms, ensuring consistency across the entire customer lifecycle.

This approach supports UC's unique requirements: custom pricing tiers are defined in tiered volume adjustments on Contract Item Prices; specific discounts are captured in Price Adjustment Schedules; and billing frequencies tied to UC's fiscal year are configured at the contract level. All future transactions for UC automatically inherit these terms.

Option A (Discount Schedules with Price Rules) applies broadly to any account and doesn't support customer-specific governance. Option B (Dedicated Price Book) lacks the flexibility for tiered billing and special terms. Contract Pricing is specifically designed for long-term, negotiated, customer- specific commercial agreements.


Reference:

Salesforce Help - Contract Pricing in Revenue Cloud, Manage Contract Pricing, Apply

Contract Pricing When You Amend or Renew Assets



A furniture company is selling unassembled furniture with user manuals. The company does not want to show user manuals as a quote line when selling to customers, but it needs to make sure user manuals are included when shipping the unassembled furniture.
What is the recommended approach?

  1. Add the user manuals as quote line, but hide them in the Transaction Line Table and proposal document.
  2. Add the user manuals as an attribute with a value of Included or Excluded under the unassembled furniture product record.
  3. Add the user manuals as a technical product and create associated decomposition rule(s).

Answer(s): C

Explanation:

The recommended approach uses technical products with decomposition rules. According to Revenue Cloud fulfillment documentation, technical products are purpose-built for fulfillment and operational processes rather than commercial sale. User manuals in this scenario should be configured as technical products that accompany the commercial unassembled furniture product but are not visible as separate quote lines to customers.

Decomposition rules govern how commercial products (the unassembled furniture) break down into fulfillment components when an order is activated. By creating a technical product called "User Manual Inclusion" and establishing decomposition rules that link it to the furniture product, the system ensures that when an unassembled furniture order is created and activated, the decomposition process automatically includes the user manual technical product in the fulfillment decomposition.

This approach provides several advantages: customers see only the furniture product in their quote

(not the manual as a separate line item), but during order fulfillment, the decomposition rules ensure that user manuals are included in the shipping package. Technical products do not appear in quoting interfaces, so they remain hidden from customer-facing documentation and proposals while still participating in fulfillment operations.

Option A (hiding quote lines) is not recommended because it adds unnecessary complexity to quotes and can cause confusion. Option B (attributes) doesn't support the fulfillment requirement; attributes describe product features, not orchestrate separate fulfillment items. Technical products with decomposition rules is the purpose-built Revenue Cloud mechanism for handling fulfillment- only items that shouldn't appear as commercial line items.


Reference:

Revenue Cloud Fulfillment Documentation - Technical Products and Decomposition Rules, Dynamic Revenue Orchestrator decomposition configuration



A subscription product that starts on July 1 is assigned a Billing Treatment at the Product Level that bills in arrears. However, the Billing Treatment assigned at the Order Product level is configured to bill in advance.
What is the correct statement regarding Billing Treatment?

  1. Billing Treatment resolution always prefers the Product Level over the Order Product level.
  2. Billing Treatment at the Order Product level overrides the Product Level Billing Treatment.
  3. Billing Treatments are only evaluated when no Legal Entity is defined.

Answer(s): B

Explanation:

In Revenue Cloud's billing hierarchy, the Order Product level Billing Treatment takes precedence over the Product Level Billing Treatment. According to Revenue Cloud billing documentation, when a Billing Treatment is configured at multiple levels, the system applies a priority hierarchy where the most specific (transactional) level overrides more general levels.

The Billing Treatment field configures whether a charge should be billed in advance (prior to service delivery) or in arrears (after service delivery).
When this setting exists at both the Product level and the Order Product level, the Order Product level configuration is the final determining factor. In the given scenario, even though the Product is configured to bill in arrears, the subscription order will actually bill in advance because the Order Product Billing Treatment explicitly specifies advance billing.

This design allows for customer-specific exceptions and flexibility. The Product level provides a default billing behavior, but sales teams and billing administrators can override this default at the Order Product level for specific deals, negotiated terms, or unique customer arrangements. For example, a customer might negotiate different billing terms than the standard product defaults, and those specific terms are captured at the Order Product level during quote-to-order conversion.

Option A is incorrect; Product Level does not override Order Product level. Option C about Legal Entity is unrelated to Billing Treatment resolution hierarchy. The Order Product level is the transaction-specific configuration point where customer-negotiated terms take final effect, making it the highest priority in the billing treatment resolution logic.


Reference:

Revenue Cloud Billing Documentation - Billing Treatment configuration, Order Product field hierarchy documentation



A Revenue Cloud Consultant is setting up the amendment process for assets in Revenue Cloud. The goal is to ensure that when a customer wants to change their subscription, the process is streamlined from initiation to the final update of the asset.

In this automated lifecycle, what is true about the Opportunity?

  1. It is an optional record used for forecasting purposes and does not directly participate in the asset update automation.
  2. It directly updates the Asset record as soon as the opportunity stage is changed to Closed Won, bypassing the need for a quote.
  3. It is only required for amendments that involve a price increase; for other amendments, a quote can be created directly from the account.

Answer(s): A

Explanation:

In Salesforce Revenue Cloud, during the amendment process, the Opportunity record is optional and primarily serves for forecasting and reporting. It does not play a direct role in the automation of asset or subscription updates. The automation of amendments is handled by the Quote, Order, and Contract records. The amendment quote captures the requested changes, and once finalized, it creates an order that updates the contract and related assets automatically.

Exact Extract from Salesforce Revenue Cloud Documentation:

"In an automated amendment lifecycle, an Opportunity is optional and primarily used for forecasting or pipeline tracking. The amendment Quote is the driver of subscription changes. Once the Quote is finalized and converted into an Order, the system automatically updates the Contract and Asset records accordingly."

-- Salesforce Subscription Management Implementation Guide

This confirms that the Opportunity is not mandatory in the amendment process and does not directly perform updates. Instead, the Quote-to-Order flow governs asset and subscription modifications. The Opportunity may be linked for visibility but is not a dependency for automation.

Option B is incorrect because asset updates are never triggered directly from an Opportunity stage change. Option C is also incorrect because Opportunity requirements are not determined by pricing scenarios.


Reference:

Salesforce Subscription Management Implementation Guide

Salesforce Billing Implementation Guide ­ Amendment Lifecycle

Salesforce CPQ Implementation Guide ­ Contracts and Amendments

Salesforce Revenue Cloud Consultant Exam Guide



Viewing page 3 of 22
Viewing questions 9 - 12 out of 165 questions



Post your Comments and Discuss Salesforce Rev-Con-201 exam prep with other Community members:

Rev-Con-201 Exam Discussions & Posts