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

Salesforce REV-CON-201 Online Questions & Answers

• Question 151:

  A customer is migrating asset data into Revenue Cloud and needs to generate Asset Actions, Asset State Periods, and edit Lifecycle Asset fields.

  Which permission does the customer need to achieve this?

  A. Customer Asset Lifecycle Management
  B. Lifecycle-managed asset
  C. InitiateAmend, InitiateCancellation, InitiateRenewal
  A. Customer Asset Lifecycle Management

  ---

  Explanation

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

  References: Salesforce Subscription Management Implementation Guide - Lifecycle Asset Management Permissions Salesforce Revenue Cloud Setup Guide - Permission Sets for Asset and State Management Salesforce Solution Architect Handbook - Data Migration and Asset Lifecycle Enablement

• Question 152:

  A company has a policy requiring all new business quotes to be automatically associated with an Opportunity to ensure accurate forecasting.

  How should a consultant enforce this policy so that users are unable to create a quote without an Opportunity?

  A. Create a validation rule on the Quote object to ensure OpportunityId is not null.
  B. Update Opportunity Settings and enable "Require Quotes on Opportunities."
  C. Update Quote Settings and set "Create Quotes Without a Related Opportunity" to False.
  C. Update Quote Settings and set "Create Quotes Without a Related Opportunity" to False.

  ---

  Explanation

  Exact Extracts from Salesforce CPQ and Revenue Cloud Implementation Guides: "The Quote Settings page includes the setting 'Create Quotes Without a Related Opportunity.' When set to False, users must associate a quote with an Opportunity before saving." "This enforces alignment between quotes and opportunities for accurate forecasting and pipeline reporting."

  Step-by-Step Reasoning:

  Requirement: Prevent quote creation unless it's tied to an opportunity.

  Declarative Solution:

  Navigate to Quote Settings # Disable Create Quotes Without a Related Opportunity.

  This enforces association at save time system-wide.

  Why C is Correct: It's the standard, supported configuration in CPQ for Opportunity-Quote relationship enforcement.

  Why Others Are Incorrect:

  A: A validation rule would work but is redundant and not best practice when a native setting exists.

  B: Opportunity Settings do not provide this control; Quote Settings do.

  References:

  Salesforce CPQ Implementation Guide - Quote Settings and Opportunity Association Salesforce Revenue Cloud Admin Guide - Forecasting Alignment and Quote Creation Controls

• Question 153:

  A sales rep needs to renew multiple assets. Some assets can be renewed at the same prices and do not require negotiation, so the rep can directly create a renewal order. Other assets need higher prices and require a quote for negotiation.

  When the sales rep starts the renewal process, they cannot choose whether to create a quote or an order.

  How should a Revenue Cloud Consultant address this issue?

  A. Change the Revenue Cloud settings to allow renewal quote and order creation.
  B. Override the standard Salesforce flow to allow renewal quote and order creation.
  C. Customize the Manage Asset component to allow renewal quote and order creation.
  A. Change the Revenue Cloud settings to allow renewal quote and order creation.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: Revenue Cloud Renewal Management includes settings that control whether renewals create: A renewal quote, A renewal order, Or allow the user to choose between the two.

  The recommended approach is to configure Revenue Cloud / Renewal Settings appropriately so users can pick the desired path during renewal. Overriding flows (B) or customizing managed components (C) is not the recommended or supported first step.

  References:

  Revenue Lifecycle Management Implementation Guide - Renewal Configuration and Settings Asset-Based Renewals Documentation - Controlling Quote vs Order Creation

• Question 154:

  A billing administrator wants invoices to be generated automatically every Friday at 8:00 PM.

  Which feature should be used?

  A. Billing Treatment
  B. Recurring Invoice Run
  C. Invoice Preview Flow
  B. Recurring Invoice Run

  ---

  Explanation

  Recurring Invoice Runs in Salesforce Billing enable automated invoice generation based on defined schedules. Administrators can configure frequency (daily, weekly, monthly) and execution time.

  In this scenario, setting a weekly recurring invoice run for Friday at 8:00 PM ensures consistent and automated invoice processing.

  Billing Treatments control invoice formatting and behavior, not scheduling. Invoice Preview is used for manual or testing purposes.

  References:

  Salesforce Billing Implementation Guide ?Recurring Invoice Runs

• Question 155:

  After a quote is created from amending a bundle asset, a user unselects a bundle component inside the configurator and saves and exits to the Transaction Line Editor.

  How will the user identify the unselected bundle component?

  A. No line items will be displayed for the unselected component.
  B. It will show a red cancel tag next to the product that was unselected, and the quantity will be -1.
  C. The line item status field will show "Canceled", and quantity will be 1.
  B. It will show a red cancel tag next to the product that was unselected, and the quantity will be -1.

  ---

  Explanation

  Comprehensive and Detailed Explanation From Exact Extract: When a user removes (unselects) a bundle component during an amendment, Salesforce displays the removed item in the quote as a cancellation action.

  From the RLM / CPQ Configurator documentation: "When a component is removed during an amendment, the TLE displays a red cancellation indicator." "The system shows the cancellation as a negative quantity (-1 or reduction of original quantity)."

  Option A is incorrect because removed items must appear in the amendment quote.

  Option C uses Status = Canceled but does not reflect the required cancellation tag or quantity behavior.

  References:

  Revenue Lifecycle Management Implementation Guide - Amendments Bundle Component Removal Behavior

  Cancellation Line Indicators.

• Question 156:

  A company is offering a subscription service with a standard monthly price of US$200. The proration settings are as follows: Proration Period: Monthly Period Boundary: Align to Calendar Partial Periods Allowed: Yes A customer begins their subscription on March 20, 2021, and ends it on December 31, 2021.

  For the initial partial period (March 20-31), which formula should the consultant use to calculate the proration multiplier?

  A. Proration Multiplier = Number of remaining days in March / Total number of days in March
  B. Proration Multiplier = Number of days used in March / Total number of days in March
  C. Proration Multiplier = Number of days used in a year / Total number of days in a year
  A. Proration Multiplier = Number of remaining days in March / Total number of days in March

  ---

  Explanation

  In Salesforce Billing and Subscription Management, proration is applied when a customer begins or ends service mid-period. With Monthly Proration and Calendar-Aligned Boundaries, the system determines the correct prorated charge by calculating the proportion of the month the service is active. For a start date of March 20, the service is active from March 20 to March 31. The correct proration multiplier formula is: Number of remaining days in March / Total number of days in March.

  This calculates the billable fraction of the month and applies it to the monthly price. In March, there are 31 days, so the proration multiplier is:

  (31 - 20 + 1) / 31 = 12 / 31 # 0.3871

  This aligns with Salesforce's proration logic when "Partial Periods Allowed = Yes" and "Align to Calendar" is selected.

  Option B incorrectly calculates used days, not remaining days.

  Option C applies to Annual Proration, not monthly, and is not relevant here.

  Exact Extracts from Salesforce Revenue Cloud Documents: Subscription Management Implementation Guide - "Proration Settings":"For calendar-aligned billing periods, the proration multiplier is calculated as (remaining days in period / total days in period)." Billing Implementation Guide - "Partial Period Calculation Examples":"When partial periods are enabled, proration applies from service start to end of period based on remaining days."

  References: Salesforce Subscription Management Implementation Guide Salesforce Billing Implementation Guide Proration and Billing Period Calculations Guide

• Question 157:

  A Revenue Cloud Consultant needs to display a list of products to be shown in the browse phase of a guided selling journey.

  Which Product Catalog Management business API should the consultant use to retrieve a list of products that belong to a specific catalog?

  A. Products List (GET)
  B. Product Related Records List (POST)
  C. Products List (POST)
  C. Products List (POST)

  ---

  Explanation

  The Products List (POST) API is the correct choice for retrieving a list of products belonging to a specific catalog during the browse phase of guided selling in Revenue Cloud. This API endpoint is specifically designed as a composite API for Product Discovery and provides comprehensive filtering capabilities. According to the Revenue Cloud Developer Guide, the Products List (POST) resource is located at /connect /cpq/products and accepts POST requests with a JSON body.

  This API allows consultants to specify multiple parameters including catalogId, categoryId, priceBookId, productClassificationId, and various filtering criteria. The POST method is preferred over GET because it can handle complex request bodies with multiple filter criteria, user context information, and qualification/pricing procedures. The API supports essential Product Discovery features such as enableQualification and enablePricing flags, which are critical during the browse phase. It can also include contextDefinition and contextMapping parameters to ensure proper data flow during guided selling. The Products List (POST) returns a paginated list of products with complete details including pricing information, qualification status, and catalog associations.

  Option A (Products List GET) does not exist as a standard Product Catalog Management business API.

  Option B (Product Related Records List POST) is used for retrieving related records like ProductRampSegment or ProductUsageGrant, not for product lists. The Products List (POST) API is explicitly documented in the Product Discovery Business APIs section of the Revenue Cloud Developer Guide for browsing and discovering products during the sales transaction process.

  References:

  Revenue Cloud Developer Guide - Product Discovery Business APIs, Product Catalog Management Business APIs section

• Question 158:

  A company wants to ensure Salesforce acts as the system of record for product and pricing data.

  What is the recommended approach?

  A. Use ERP as the primary source
  B. Centralize product data in Salesforce Product Catalog
  C. Sync data nightly from external systems
  B. Centralize product data in Salesforce Product Catalog

  ---

  Explanation

  Salesforce Revenue Cloud recommends using the Product Catalog as the single source of truth for commercial data. This ensures consistency in quoting, pricing, and order management.

  External systems should integrate with Salesforce rather than overwrite it.

  References:

  Revenue Cloud Architecture Best Practices

• Question 159:

  A pricing administrator aims to configure pricing for a smartphone so that the monthly installment price varies based on the selected memory options (128 GB, 256 GB, 512 GB) and contract term options (12 months, 24 months). The price should be equally divided for each month, considering the combinations of memory and contract term as price impacting attributes, with no interest charges applied.

  How many records need to be present in the Attribute-Based Adjustments pricing schedule to satisfy this scenario?

  A. 6
  B. 3
  C. 5
  A. 6

  ---

  Explanation

  Exact Extracts from Salesforce CPQ Implementation Guide: "Attribute-Based Pricing allows administrators to define price adjustments based on one or more attribute combinations."

  "Each unique combination of attributes (e.g., Memory Size x Contract Term) represents one record in the adjustment schedule."

  "If there are three memory options and two contract term options, there are six total combinations that require six entries in the Attribute-Based Adjustment matrix." Step-by-Step Reasoning: Attributes: Memory Options: 128 GB, 256 GB, 512 GB # 3 values

  Contract Term Options: 12 months, 24 months # 2 values

  Combinations: 3 x 2 = 6 unique attribute pairs. Each combination requires one adjustment record. Why A is Correct: Six pricing adjustment records ensure accurate monthly installment calculation for each combination.

  Why Others Are Incorrect:

  B: Only accounts for one attribute (memory).

  C: Arbitrary number; doesn't represent all possible pairs.

  References:

  Salesforce CPQ Implementation Guide - Attribute-Based Pricing and Adjustment Matrices Salesforce Revenue Cloud Pricing Configuration Guide - Combining Attribute-Driven Pricing Dimensions

• Question 160:

  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?

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

  ---

  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.

  References:

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