Salesforce REV-CON-201 Online Practice Questions and Exam Preparation

Salesforce REV-CON-201 Online Questions & Answers

• Question 1:

  A Cloud Consultant is using Contracts AI to retrieve clauses and contract fields from a PDF. After the initial run, the consultant realizes that a payment method custom field needs to be retrieved that was not initially included.

  What should the consultant do to retrieve this custom field?

  A. Modify the contract extraction template to define the attribute mapping and context mapping for payment method.
  B. Modify the AI prompt template to define the attribute mapping and context mapping for payment method.
  C. Log a support case with Salesforce to enable payment method to be added to the extraction mapping used.
  A. Modify the contract extraction template to define the attribute mapping and context mapping for payment method.

  ---

  Explanation

  In Salesforce Revenue Cloud's Contracts AI functionality, the process of retrieving data such as clauses or contract fields from uploaded documents (e.g., PDFs) relies on Contract Extraction Templates. These templates define which attributes and contextual mappings are used during document extraction. When a new field-such as Payment Method (a custom field)-needs to be retrieved, it must be explicitly added to the extraction template through configuration.

  Exact Extract from Salesforce Revenue Cloud Documentation: "To extract additional custom fields or clauses, users must update the contract extraction template to include attribute and context mappings for each new field. The template defines which contract data points Contracts AI retrieves from the uploaded document."

  - Salesforce Subscription Management Implementation Guide (Contracts AI section) The AI prompt template (Option B) controls the tone and structure of the generated summaries, not data extraction parameters. Logging a support case ( Option C) is unnecessary, as this configuration is fully managed by the consultant or administrator through template updates.

  References:

  Salesforce Subscription Management Implementation Guide - Contracts AI Setup Salesforce Revenue Cloud Implementation Guide - Contract Extraction Templates Salesforce Revenue Cloud Consultant Study Guide

• Question 2:

  A project is moving from the design phase to the build phase.

  What should a Revenue Cloud Consultant do to ensure a successful build cycle?

  A. Set up environments for development, testing, and production, and choose a deployment tool.
  B. Write user stories, have user workshops to confirm requirements, and build test use cases.
  C. Build in the production environment, let users test it live, and provide feedback in real time.
  A. Set up environments for development, testing, and production, and choose a deployment tool.

  ---

  Explanation

  As a Salesforce Revenue Cloud project moves from design into the build phase, it is essential to follow Salesforce's recommended development lifecycle and environment strategy to ensure a smooth, secure, and scalable implementation.

  Per the Salesforce Revenue Cloud Implementation Guide and Project Delivery Framework, the consultant must: Set up multiple environments: such as Developer Sandbox (for configuration and coding), UAT Sandbox (for user testing), and Production (for go-live) Establish a deployment strategy and toolset: using tools like Change Sets, Salesforce CLI, DevOps Center, or third-party CI/CD platforms Maintain proper version control and release planning.

  This approach ensures code quality, traceability, and a safe pathway for validating changes before going live.

  Option B, while valid during design and requirement gathering, should have been completed before build. Option C (building directly in production) violates best practices, increases risk, and lacks rollback and testing controls.

  Exact Extracts from Salesforce Revenue Cloud Documents: Revenue Cloud Delivery Framework - "Environment Strategy":"Create isolated sandboxes for development, QA, and UAT. Always deploy to production through a structured release process." Salesforce Implementation Lifecycle - "Build Phase":"Establish a deployment toolset and environment strategy at the beginning of the build cycle to ensure governance and minimize risk."

  References: Salesforce Revenue Cloud Delivery Framework Salesforce Project Lifecycle Best Practices Salesforce DevOps and Deployment Strategy Documentation

• Question 3:

  An agreement was executed using Revenue Cloud's Contract Lifecycle Management (CLM) functionality, and obligations were created to track compliance for key clauses.

  What is a reason to create the obligations?

  A. Obligations can be assigned Owners and Tasks which helps track contractual commitments.
  B. Obligations can be assigned the Fulfilled status to ensure compliance.
  C. Obligations can be assigned Price Discounts to manage contract pricing agreements.
  A. Obligations can be assigned Owners and Tasks which helps track contractual commitments.

  ---

  Explanation

  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."

  References: Salesforce CLM Implementation Guide Salesforce Revenue Cloud CLM Functional Overview CLM Admin and Template Designer Documentation

• Question 4:

  A Revenue Cloud Consultant is configuring a pricing procedure that depends on multiple context attributes. After updating several attributes in the context definition, the consultant notices inconsistent pricing results.

  What should the consultant do to ensure the pricing procedure uses the latest context values?

  A. Clone the pricing procedure and reassign it to the product.
  B. Activate the updated context definition.
  C. Rebuild the product catalog index.
  B. Activate the updated context definition.

  ---

  Explanation

  In Salesforce Revenue Cloud, context definitions act as the data foundation for pricing procedures by supplying attributes used during pricing evaluation. When modifications are made to a context definition--such as adding or updating attributes--the system does not automatically apply those changes to dependent pricing procedures until the context definition is reactivated.

  Activation ensures that the updated metadata is registered and available for use in pricing logic. Without activation, pricing procedures continue referencing the previous version of the context definition, which leads to inconsistent or outdated pricing results.

  Option A is incorrect because cloning the pricing procedure does not refresh or expose updated context attributes.

  Option C is unrelated, as rebuilding the catalog index affects product search and visibility, not pricing logic.

  References:

  Salesforce Revenue Cloud Pricing Setup Guide ?Context Definition Lifecycle and Activation

• Question 5:

  A solution architect notices that a complex product bundle uses multiple nested Constraint Modeling Language (CML) rules to enforce constraints during product configuration. Users report long load times when adding options to the bundle.

  What should the architect do to improve configuration performance and ensure quotes remain technically and commercially viable?

  A. Refactor and simplify CML constraints to reduce runtime complexity.
  B. Disable constraint rules during configuration and validate selections after deployment.
  C. Replace CML entirely with Apex triggers to enforce constraints at quote submission.
  A. Refactor and simplify CML constraints to reduce runtime complexity.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Revenue Cloud documentation recommends optimizing and simplifying constraint rules when performance issues arise. Key guidance includes: Reducing the number of nested and overlapping CML rules.

  Consolidating rules when possible.

  Avoiding unnecessary complexity that increases runtime evaluation time. Disabling rules (B) breaks guardrails during configuration and goes against best practices; users would be able to configure invalid combinations. Replacing CML with Apex triggers (C) removes real-time configurator guidance and is not recommended; constraints should be enforced in the configurator, not only at submission.

  References:

  Product Configurator and CML Documentation - Performance and Best Practices Revenue Lifecycle Management Implementation Guide - Constraint Rules Optimization

• Question 6:

  A company processes orders.

  When the orders are activated but not submitted, the company wants the assets to be automatically created.

  How should a Revenue Cloud Consultant automatically create assets for all order products?

  A. Use the Assetize Order flow.
  B. Use the Submit Order for Fulfillment flow.
  C. Use the Activate action on the order.
  A. Use the Assetize Order flow.

  ---

  Explanation

  Explanation (150-250 words)

  In Salesforce Revenue Cloud, assetization is the process of converting order products into active Asset records that track entitlements and subscriptions. When a business requires asset creation upon order activation (before submission for fulfillment), the proper approach is to use the Assetize Order flow. The Assetize Order flow automatically generates assets for all qualifying order products as soon as the order reaches the Activated status. It can be configured to run automatically through automation or invoked manually as part of an operational process.

  The Submit Order for Fulfillment flow (option B) triggers fulfillment operations (e.g., provisioning or shipment) and is not intended for early asset creation. The Activate action alone does not create assets unless combined with the Assetize flow.

  Exact Extract from Salesforce Subscription Management Implementation Guide: "Use the Assetize Order flow to automatically create asset records when an order is activated. This process supports early asset creation prior to fulfillment."

  References: Salesforce Subscription Management Implementation Guide - Assetize Order Flow Overview Salesforce Revenue Cloud Data Model - Order to Asset Lifecycle Salesforce CPQ-Billing Integration Guide - Automation for Asset Creation

• Question 7:

  A company selling hardware and software needs to implement a 2-day delay for software provisioning after hardware delivery in its order-to-cash process. While configuring the Dynamic Revenue Orchestrator (DRO) plan, the Fulfillment Designer notices the option for adding this delay is not visible on the provisioning task.

  What should the Revenue Cloud Consultant enable to add this option for the Fulfillment Designer?

  A. Future-Dated Steps in the DRO settings
  B. Modify All Data permission in the Fulfillment Designer's profile
  C. Link Task to Step Source button in the DRO settings
  A. Future-Dated Steps in the DRO settings

  ---

  Explanation

  Exact Extracts from Salesforce Subscription Management and Billing Implementation Guides: "Dynamic Revenue Orchestration (DRO) allows defining future-dated steps to schedule task execution at a specific offset from a preceding step." "Enable 'Future-Dated Steps' in the DRO Settings to allow designers to configure task delays, offsets, or deferred execution logic." "Without this setting enabled, step timing options such as date offsets or delays will not appear in the Fulfillment Designer interface."

  Step-by-Step Reasoning:

  Requirement: Add a 2-day delay between hardware delivery and software provisioning.

  Correct Configuration:

  Enable Future-Dated Steps in DRO settings.

  Once enabled, the "Delay/Offset" options become available for the provisioning task. Why A is Correct:Activates the feature for scheduling tasks with day offsets in orchestration plans.

  Why Others Are Incorrect:

  B: Permissions do not control visibility of DRO feature settings.

  C: "Link Task to Step Source" is unrelated to delay configuration; it associates source objects, not timing.

  References:

  Salesforce Subscription Management Implementation Guide - Dynamic Revenue Orchestration Settings Salesforce Billing Implementation Guide - Fulfillment Task Scheduling and Delays

• Question 8:

  A sales rep amends an existing subscription asset but keeps the quantity unchanged. The rep wants to update pricing based on new price rules.

  Which action should the rep take?

  A. Cancel and recreate the asset.
  B. Reprice the amendment quote.
  C. Change the asset end date and re-add the product.
  B. Reprice the amendment quote.

  ---

  Explanation

  In Revenue Cloud, the amendment process allows changes to existing assets without disrupting service. When the goal is to update pricing only, the correct approach is to create an amendment quote and use the reprice function.

  Repricing applies updated pricing rules while preserving the existing quantity and service continuity. This ensures that the customer's subscription remains active without interruption.

  Option A and C introduce unnecessary lifecycle changes and may cause service gaps or duplication.

  References:

  Revenue Cloud Asset Lifecycle Management ?Amend and Reprice Process

• Question 9:

  A product administrator needs to add a required rule using Constraint Modeling Language (CML) so that whenever a product called Desktop is added to a quote, another standalone product called Monitor will be automatically added.

  What is the correct CML syntax to write this rule?

  A. type Quote { relation desktop: Desktop[0..99]; relation monitor: Monitor[0..99]; constraint(desktop, monitor, "Desktop requires Monitor"); }
  B. type Quote { relation desktop: Desktop[0..99]; relation monitor: Monitor[0..99]; require(desktop [Desktop],monitor[Monitor], "Desktop requires Monitor"); }
  C. type Quote { relation desktop: Desktop; relation monitor: Monitor; require(Desktop[Desktop],Monitor [Monitor], "Desktop requires Monitor"); }
  B. type Quote { relation desktop: Desktop[0..99]; relation monitor: Monitor[0..99]; require(desktop [Desktop],monitor[Monitor], "Desktop requires Monitor"); }

  ---

  Explanation

  Explanation (150-250 words) Constraint Modeling Language (CML) defines logical relationships between quote line items, allowing administrators to automate dependency and compatibility logic in Salesforce CPQ. The keyword require() explicitly establishes a dependency that ensures one product must exist when another is present in a quote.

  The correct syntax must define relationships with multiplicity ranges (e.g., [0..99]) and use the require() function, not constraint(), to specify the rule.

  Option B meets these criteria:

  type Quote {

  relation desktop : Desktop[0..99];

  relation monitor : Monitor[0..99];

  require(desktop[Desktop], monitor[Monitor], "Desktop requires Monitor"); }

  This ensures that when "Desktop" is added, "Monitor" is automatically included. The other options are incorrect because: Option A uses the wrong function (constraint() instead of require()), which defines logical conditions but doesn't enforce automatic inclusion.

  Option C omits multiplicity, which is required for valid relationship definition.

  Exact Extract from Salesforce CPQ Implementation Guide: "The require() statement in CML defines a dependency rule so that when one product is selected, the dependent product is automatically added to the quote."

  References: Salesforce CPQ Implementation Guide - Constraint Rules and CML Syntax Salesforce Revenue Cloud Developer Guide - Defining Product Relationships in CML

• Question 10:

  An order fulfillment orchestrator designer is setting the decomposition scope to Order Line Item at the product record level. The designer created the necessary decomposition rules in a Dynamic Revenue Orchestrator (DRO)-enabled sandbox. To test the changes, an order is created with line items that have the same product for which the decomposition rules exist.

  What will happen when the order is activated?

  A. For every order line item that decomposes, one instance of the fulfillment order line item is created per order item.
  B. For every order line item that decomposes, multiple instances of the fulfillment order line item are created per order item.
  C. For every order line item that decomposes, a single instance of the fulfillment order line item is created combining all order items.
  A. For every order line item that decomposes, one instance of the fulfillment order line item is created per order item.

  ---

  Explanation

  Exact Extracts from Salesforce Subscription Management Implementation Guide (Dynamic Revenue Orchestration):

  "Decomposition scope determines how order data is split into fulfillment records." "When the decomposition scope is set to Order Line Item, the system creates one fulfillment order line item per decomposed order line." "If multiple order lines reference the same product, each is decomposed independently according to its line-level data." "Combining order lines into a single fulfillment record only occurs when decomposition scope is at the Order level."

  Step-by-Step Reasoning:

  Configuration: Decomposition scope = Order Line Item.

  Behavior: Each order line item triggers its own decomposition and fulfillment record.

  Result: One fulfillment line per order line (independent of product similarity). Why A is Correct: Matches the expected behavior of the Order Line Item decomposition scope.

  Why B and C are Incorrect:

  B: Multiple fulfillment records per order item contradicts "one per line" rule.

  C: Combines all items - behavior of "Order" scope, not "Order Line Item."

  References: Salesforce Subscription Management Implementation Guide -

  Dynamic Revenue Orchestration: Decomposition Rules and Scopes Salesforce Billing Implementation Guide - Fulfillment Line Item Creation Logic