Free Practice Questions for Salesforce Rev-Con-201 Exam

Exact Extracts from Salesforce Billing Implementation Guide:

“Billing Schedule Groups (BSGs) define how and when recurring charges are billed.”

“The Billing Day of Month field on the BSG controls the regular billing date for the customer.”

“Use the Override Next Billing Date field on the BSG to change the billing date for one cycle only without affecting future billing cycles.”

“Inline editing of BSG fields by users with appropriate permissions allows rapid adjustments to billing schedules without amending or recreating assets.”

Step-by-Step Reasoning:

Requirement:

Regular billing date change: from 15th → 20th each month.

One-time exception for April: bill on April 22 only.

Solution:

Edit Billing Schedule Group (BSG):

Set Billing Day of Month = 20 for future cycles.

Set Override Next Billing Date = April 22 for one-time adjustment.

These changes are performed inline without creating a new asset or amendment.

Why A is correct:Meets both permanent and one-time date changes using existing fields in BSG.

Why B and C are incorrect:

B: Unnecessary amendment—no product or contract change required.

C: “Period Boundary Day” is not used for recurring billing adjustments; it affects order period segmentation, not BSG behavior.

References :

Salesforce Billing Implementation Guide — Billing Schedule Groups and Override Billing Dates

Salesforce Subscription Management Implementation Guide — Billing Frequency and Date Adjustments

To automatically generate invoices at a specific time and on a recurring schedule, Salesforce Billing provides the Recurring Invoice Run functionality. This feature allows users to define how often invoice runs should occur (e.g., daily, weekly, monthly) and at what time of day. In this scenario, the correct approach is to schedule a Recurring Invoice Run with a Weekly frequency, specifically set to run every Monday at 6:00 AM.

As described in the Salesforce Billing Implementation Guide, Recurring Invoice Runs allow Billing users to:

Select the frequency (e.g., weekly)

Define the day(s) and time of execution

Automatically generate invoices for completed billing schedules during the configured time window

This method ensures consistency, reduces manual workload, and aligns with operational requirements.

Option A refers to Billing Treatments, which are used to manage how invoices are formatted or communicated, not when they are generated.

Option C, using a custom flow with Invoice Preview, is a non-standard and unnecessarily complex approach for a routine task that is already handled natively by Salesforce Billing.

Exact Extracts from Salesforce Revenue Cloud Documents:

Salesforce Billing Implementation Guide – “Recurring Invoice Runs”:“Use Recurring Invoice Runs to configure automated invoice generation. You can set the recurrence frequency (daily, weekly, etc.), and specify the time of execution to match business needs.”

Billing Operations Guide – “Automation for Scheduled Invoicing”:“Recurring invoice runs simplify billing operations by executing invoice logic for completed billing schedules on a regular cadence.”

Explanation (150–250 words)

A Decision Table in Salesforce CPQ and Revenue Cloud Pricing is used to evaluate business rules and return outputs such as discounts, rates, or pricing logic. When deploying to a sandbox, both the Decision Table definition and any related custom objects that store rule inputs/outputs must first exist in the target environment.

The correct deployment sequence is:

Deploy the custom object and decision table metadata to the staging sandbox (ensuring structural consistency).

Map the decision table into the default pricing recipe, allowing it to integrate with the pricing engine for evaluations.

Refresh or sync Pricing, which updates the pricing engine and ensures all decision table logic and data are active and aligned with the current recipe configuration.

Importing data is optional if the data already exists in the source metadata; however, syncing pricing ensures that the engine recognizes the new logic.

Exact Extract from Salesforce Pricing and Decision Framework Guide:

“After deploying a Decision Table and its supporting custom objects, map it to the pricing recipe and refresh or sync pricing to activate the latest logic within the pricing engine.”

Exact Extracts from Salesforce Subscription Management and Billing Implementation Guides:

“The Cancel button in Managed Assets uses the InitiateCancellation Action API under the hood.”

“Access to this functionality is controlled by the InitiateCancellation permission.”

“Restricting this permission prevents users from triggering the cancellation process, even if the button or flow is visible.”

Step-by-Step Reasoning:

Requirement: Only super users can cancel subscriptions.

Mechanism: The cancel button invokes the InitiateCancellation Action API.

Solution: Remove this API permission for general users.

Why B is Correct:

It directly controls backend access to cancellation logic.

Super users retain permission; others cannot perform cancellations.

Why Others Are Incorrect:

A: Deactivating flows disables global processes — too broad and affects all users.

C: Page layout changes hide the button visually but don’t secure the backend API access.

References :

Salesforce Subscription Management Implementation Guide — Action API Permissions and Managed Assets

Salesforce Billing Implementation Guide — Asset Cancellation and Access Control

Comprehensive and Detailed Explanation From Exact Extract:

The Transaction Line Editor (TLE) supports:

Column filtering and sorting.

Inline editing and recalculation.

Manual save actions.

There is no “drag to sort” capability (A). Changes are not auto-saved (C); users must explicitly save.

Exact Extracts from Salesforce CPQ & Subscription Management Documentation:

“When using Indexed Data for Product Listing and Search, Salesforce Revenue Cloud maintains an index of active products used in Browse Catalog.”

“After creating or modifying products, administrators must run Rebuild Index to include new or updated products in catalog search results.”

“Constraint Models and Ramp Segments are independent configurations and do not control catalog visibility.”

Step-by-Step Reasoning:

Symptom: New product not visible in catalog search despite being active and correctly configured.

Cause: Index not rebuilt — product not yet included in catalog index table.

Solution: Run Rebuild Index from Product Discovery or Catalog Management settings.

Why C is Correct: Required for systems using Indexed Data for catalog browsing.

Why Others Are Incorrect:

A: Constraint Models affect configuration, not catalog visibility.

B: Ramp Segments relate to multi-period pricing, not catalog indexing.

References :

Salesforce CPQ Implementation Guide — Product Discovery and Indexed Data Search

Salesforce Subscription Management Implementation Guide — Catalog Indexing and Product Visibility Maintenance

Explanation (150–250 words)

In Salesforce Revenue Cloud, Product Attributes allow administrators to create dynamic, parameter-driven product definitions—removing the need for separate SKUs for every possible variation. Instead of defining millions of products (e.g., each skill as a unique product), organizations can create a single configurable product with attributes like skill type, level, region, or technology.

Attributes are defined through Product Attribute Sets and linked to one or more products, enabling sales reps to select attribute values during configuration or quoting. This approach drastically reduces catalog complexity, improves quote performance, and provides flexibility for price rules, approvals, and product logic.

By contrast, Product Categories and Product Classifications are for grouping, filtering, or reporting purposes, not for modeling variation.

Exact Extract from Salesforce CPQ Implementation Guide:

“Use Product Attributes to define product variations without creating multiple SKUs. Attributes allow a single product record to represent many configurations.”

Comprehensive and Detailed Explanation From Exact Extract:

In Revenue Cloud / Revenue Lifecycle Management, context mappings control how values (such as attributes or fields) flow between the runtime configuration/quoting experience and underlying Salesforce objects. When defining a mapping, you specify a Mapping Intent, which determines how the data is used and whether it is stored.

The documentation describes the Persistence intent along the lines of:

Persistence

Use this intent when you want the mapped value to be written to and stored on the underlying Salesforce object so it can be used later in downstream processes (such as orders, contracts, billing, or analytics).

This exactly matches the scenario described in the question:

A sales user updates a custom attribute when selecting products for a quote.

The value must be available for downstream processes (for example, contract creation, order generation, billing, or reporting).

Therefore, the value needs to be persisted to an object/field, not just used temporarily in the UI.

Why the other options are incorrect:

Option A – AssociationAssociation intent is used when you want to establish or drive relationships (associations) between records or configurations, not specifically to persist a field value for later downstream processing. It’s more about linking and contextual associations than about durable storage of an attribute value.

Option B – HydrationHydration intent is used when you want to bring values into the runtime configuration or user interface (for example, pre-populating or deriving values), typically for in-session use. These values might not be written back or persisted. Hydration alone does not guarantee that the custom field value will be stored and available for later downstream processes.

Because the requirement explicitly states that the attribute’s value needs to be usable in other downstream processes, the correct Mapping Intent is Persistence (Option C), which aligns with the documented purpose of persisting mapped values to Salesforce objects.

References (Salesforce Revenue Cloud documentation / study materials):

Salesforce Revenue Lifecycle Management / Revenue Cloud: Context Rules, Context Mappings, and Mapping Intents

Salesforce Revenue Lifecycle Management Implementation Guide: Using Mapping Intents – Hydration vs. Persistence vs. Association

Salesforce Help: Attribute and Context Mapping for Quoting and Downstream Processes

Comprehensive and Detailed Explanation From Exact Extract:

The Managed Asset Viewer is a Lightning component that must be added to the Account Lightning page to display and manage assets. In addition, the Asset related list can also be surfaced for basic asset visibility.

Revenue Cloud documentation notes that users may have full object access but still be unable to see assets if:

The Managed Asset Viewer component is not placed on the Account page.

The Asset related list is not included on the layout.

Amend/Renew/Cancel flows (C) drive process but do not control base visibility. Expired assets (B) may still be visible depending on filters; this does not explain “no assets visible” when active ones exist.

Exact Extracts from Salesforce Revenue Cloud Documentation (Pricing Setup and Context Configuration):

“Pricing procedures depend on the active Context Definition configured in Pricing Setup.”

“If the pricing context definition referenced in a pricing procedure does not match the one selected in Pricing Setup, the product discovery flow and pricing engine will fail to initialize.”

“This mismatch can result in catalog browsing errors or configuration failures during quoting.”

Step-by-Step Reasoning:

Issue observed: Product Discovery and configuration errors after new deployments.

Root cause: After deployment, the system’s Pricing Context Definition likely changed or was reset, creating a mismatch between the pricing procedure and the context currently selected in Pricing Setup.

Why C is correct:

The pricing engine reads the active Context Definition from the Pricing Setup page.

If the pricing procedure still points to an old or invalid context definition, pricing and catalog data can fail to load.

Why A & B are incorrect:

The Revenue Settings and Product Discovery Settings contexts control billing or catalog discovery flows, not the pricing engine’s logic context.

References :

Salesforce CPQ Implementation Guide — Pricing Context Definitions and Pricing Setup

Salesforce Subscription Management Implementation Guide — Product Discovery and Pricing Context Integration