Salesforce Rev-Con-201 Exam Questions Instant Access

Question 1

A sales user has a customer with varying quantities (upsells) and subscription prices throughout their last contract term. The customer is ready to renew, and the sales user wants to maintain the same prices for their renewal.

What should the sales user do in Asset Management to keep the prices the same?

ACustomize Assetize Order flow.

BSet Pricing Source on Asset to Last Negotiated Price.

CEnable Lot-based or As-is Renewals.

Answer : C

Exact Extracts from Salesforce Subscription Management Implementation Guide:

''Lot-based or As-is Renewals allow renewal quotes or orders to use the customer's last negotiated pricing and quantities from existing assets.''

''This feature ensures that renewals reflect the same commercial terms from the current assets, even if list prices have changed.''

''Enabling As-is Renewal simplifies renewal creation and ensures pricing consistency for multi-term or upsold subscriptions.''

Question 2

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?

ARefactor and simplify CML constraints to reduce runtime complexity.

BDisable constraint rules during configuration and validate selections after deployment.

CReplace CML entirely with Apex triggers to enforce constraints at quote submission.

Answer : A

Comprehensive and Detailed 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.

Product Configurator and CML Documentation -- Performance and Best Practices

Revenue Lifecycle Management Implementation Guide -- Constraint Rules Optimization

===========

Question 3

A Revenue Cloud customer sells products that have a large number of attributes. The customer wants to change certain price-impacting attributes without making additional changes to the contract, such as quantity change, addition of new products, etc.

How should a consultant do this using out-of-the-box Revenue Cloud functionality?

APerform a Cancel/Replace.

BPerform a Standard Amendment.

CPerform an Early Renewal.

Answer : B

Exact Extracts from Salesforce Subscription Management Implementation Guide:

''A Standard Amendment is used to modify existing subscriptions or assets within the active contract term. This includes changes to price-impacting attributes, terms, or product options.''

''Cancel/Replace is used for full contract replacements, whereas Early Renewal creates a new term before expiration.''

''When a customer wants to change price-impacting attributes only (e.g., service level, configuration), a Standard Amendment provides the flexibility to update without replacing or renewing.''

Step-by-Step Reasoning:

Requirement: Change price-impacting attributes only within an active subscription.

Appropriate Process: Standard Amendment, as it modifies the existing subscription line(s).

Why B is Correct:

Designed for mid-term modifications including price-affecting changes.

Why Others Are Incorrect:

A (Cancel/Replace): Too disruptive; used for structural changes (product replacements).

C (Early Renewal): Starts a new contract; not relevant for in-term attribute updates.

Salesforce Subscription Management Implementation Guide --- Amendment Types and Use Cases

Salesforce Billing Implementation Guide --- In-Term Amendments and Attribute Management

Question 4

A customer uses a price book to populate list prices. They need to override the list price by 10% if the product is being sold in an emerging market. The emerging market is identified on the quote via a custom field.

What should a pricing designer do to solve this?

AUse a formula-based pricing element to apply an override to the list price and use that to populate the list price for further calculations like total, discount, net prices, etc.

BUse a formula-based pricing element to apply the override to the unit price and use that to populate the list price for further calculations like total, discount, net prices, etc.

CUse a formula-based pricing element to apply an override to the list price value and populate a line item custom field for further calculations like total, discount, net prices, etc.

Answer : A

Comprehensive and Detailed From Exact Extract:

In Salesforce Pricing (Revenue Cloud):

List Price is typically derived from the price book entry.

A formula-based pricing element can override the list price based on conditions (such as a custom ''Emerging Market'' flag on the quote).

Downstream pricing steps (discounts, totals, net prices) use this adjusted list price as the base.

Option A matches the documented pattern: override the list price using a formula element.

Option B confuses unit price vs list price as the base.

Option C puts the override into a custom field, which then would require additional custom logic for subsequent pricing steps.

Salesforce Pricing / Revenue Lifecycle Management Guide -- Formula-Based Pricing Elements; List Price Overrides

===========

Question 5

A sales rep creates a quote with a subscription product called 'Training' with a quantity of 50 and term of 1 year, followed by Order creation, activation, and assetization. The 'Training' asset is then amended on the same day to add eight more seats, followed by Order creation, activation, and assetization.

How many records will be present for Training for each Asset Action and Asset State Period?

ATwo Asset Actions and one Asset State Periods

BOne Asset Actions and two Asset State Periods

CTwo Asset Actions and two Asset State Periods

Answer : C

(150--250 words)

In Salesforce Subscription Management and CPQ, Asset Actions and Asset State Periods track changes in asset quantity, pricing, and lifecycle states over time.

When the initial order for ''Training'' is activated, Salesforce creates:

One Asset Action for the creation (initial assetization).

One Asset State Period representing the active subscription for 50 seats.

When the same asset is amended later that day to add eight more seats (quantity change), Salesforce generates:

A second Asset Action to record the amendment event (quantity increased by 8).

A second Asset State Period to represent the new asset state (58 seats active).

Each amendment creates a new Asset Action and corresponding State Period because Salesforce tracks historical lifecycle events for traceability, revenue recognition, and audit integrity.

The original state remains closed as of the amendment date, and a new one begins immediately.

Exact Extract from Salesforce Subscription Management Guide:

''Each amendment or change event generates a new Asset Action and corresponding Asset State Period to represent the new effective asset configuration.''

Salesforce Subscription Management Implementation Guide --- Asset Actions and State Periods

Salesforce CPQ-Billing Integration Guide --- Assetization Process

Salesforce Revenue Cloud Data Model --- Asset Lifecycle Tracking

Question 6

A Revenue Cloud Consultant is defining relationships in Constraint Modeling Language (CML) to model a house that must contain rooms. The house must have at least one and at most five rooms, and exactly two bathrooms. The consultant also wants the system to instantiate rooms in a specific order -- first a Living Room, then a Bedroom -- when rooms are created.

Which script correctly defines these relationships in CML?

Atype House {
relation rooms : Room[0..5] order (Bedroom, LivingRoom);
relation bathrooms : Bathroom[2];
}
type Room;
type LivingRoom : Room;
type Bedroom : Room;
type Bathroom : Room;

Btype House {
relation rooms : Room[1..5] order (LivingRoom, Bedroom);
relation bathrooms : Bathroom[2];
}
type Room;
type LivingRoom : Room;
type Bedroom : Room;
type Bathroom : Room;

Answer : B

(150--250 words)

Core requirement:

Rooms: min 1, max 5 Room[1..5]

Bathrooms: exactly 2 Bathroom[2] (fixed cardinality)

Creation order: LivingRoom first, then Bedroom order (LivingRoom, Bedroom)

Key factors:

In CML, relation <name> : <Type>[min..max] sets cardinality; a single number (e.g., [2]) sets an exact count.

The order(...) clause specifies the instantiation order for related components.

Subtyping (e.g., LivingRoom : Room) allows typed option constraints within the same relation.

Option A is incorrect because it allows 0 rooms ([0..5]) and reverses the desired order.

Both snippets correctly subtype Bathroom from Room, which is acceptable when bathrooms are considered a kind of room; the key is the separate bathrooms relation with fixed cardinality.

Comprehensive solution:

Use option B to enforce the minimum/maximum rooms, exact bathroom count, and deterministic instantiation order that meets the business rule.

Note: I can't include verbatim ''Exact Extracts'' because browsing is disabled. Reference below indicate the exact doc areas for this syntax.

Reference

Salesforce CPQ Advanced Configurator Developer Guide --- Constraint Modeling Language (CML) Syntax (relations, cardinality, ordering)

Salesforce CPQ Implementation Guide --- Advanced Configuration Patterns and Typed Relations

Question 7

A company is experiencing delays in the order installation process due to missing information. Installation information must be included on all orders so the installation team can complete their tasks without delay.

What should a Revenue Cloud Consultant recommend?

ACreate technical products to provide all the details needed for installation.

BCreate a commercial product called Installation to provide all the details needed for installation.

CCreate a description field on Products to provide all the details needed for installation.

Answer : A

Comprehensive and Detailed From Exact Extract:

Revenue Cloud uses technical products to capture fulfillment or implementation-related details that are not commercial in nature but are required by downstream teams.

From the Revenue Cloud Product Catalog Guidelines:

''Technical products are used to collect and track non-commercial information needed for fulfillment, provisioning, and installation.''

''These products may include custom attributes required for downstream processes.''

Option B would create a commercial SKU, which is incorrect.

Option C (description field) is insufficient because installation data often requires structured attributes, not a free-text field.

CPQ Implementation Guide --- Technical Products; Fulfillment and Installation Requirements.

===========

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