Revenue Cloud Consultant Rev-Con-201 Release Date

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

Comprehensive and Detailed Explanation From Exact Extract:

The Managed Asset Viewer is a Lightning Web Component that must be manually placed on the Account record page layout.

From the RLM Implementation Guide:

“Add the Managed Asset Viewer component to the Account Lightning page to allow users to view, filter, and edit assets.”

“The component is not added automatically and must be configured in Lightning App Builder.”

Adding related lists does not surface the component.

Permissions alone do not place the LWC onto the page.

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

Explanation (150–250 words)

Core requirement: Move active CPQ subscriptions into Revenue Cloud’s asset-centric model so downstream processes (amendments, renewals, billing) work natively.

Key factors:

In Revenue Cloud (Subscription Management), Assets are the system of record for what the customer owns/is entitled to.

Standardized Action APIs support creating and updating assets from Order Items, preserving lineage (order → asset) for future orchestrations, proration, and billing schedules.

“Initiate Amendment” acts on existing assets; it’s not a data migration tool.

“Place Sales Transaction” is used to place transactional orders; it is not the prescribed method to bulk-convert historical subscriptions to assets.

Comprehensive solution:

Stage existing subscriptions as Order Items that reflect the current state (product, term dates, quantities, prices).

Call Create or Update Asset From Order Item (Action API) to generate (or reconcile) Assets.

Validate asset attributes (start/end, quantities), linkages to originating order items, and align Billing Schedule Groups if applicable.

Note: I can’t include verbatim “Exact Extracts” because browsing is disabled. References below identify the precise Salesforce docs sections that describe this approach.

References

Salesforce Subscription Management Implementation Guide — Asset-Centric Model; Action APIs (Create/Update Asset From Order Item)

Salesforce Billing Implementation Guide — Orders to Assets alignment

Salesforce CPQ to Subscription Management Migration Guidance — Data seeding via Orders → Assets