Free Salesforce Rev-Con-201 Practice Exam with Questions & Answers | Set: 2

Explanation (150–250 words)

In Salesforce Billing, when an order product is activated, the system automatically creates a Billing Schedule Group (BSG) to manage all associated Billing Schedules (BSs). The BSG acts as the controlling record that connects multiple BSs generated for the same order product—whether from the initial order or from subsequent amendments.

When an amendment increases product quantity, Salesforce Billing does not create a new BSG; instead, it adds new BSs under the existing BSG. This design ensures that all billing activities for that product line—original or amended—are tracked within one consistent group.

Each Billing Schedule (BS) defines when and how much to bill, while the BSG provides a unified structure for reporting, synchronization, and downstream billing actions (e.g., invoicing, revenue recognition).

Thus, the persistence of the same BSG across amendments reflects correct and expected system behavior—ensuring billing continuity, preventing duplicate invoicing, and maintaining a single view of all schedules related to one order product.

Exact Extracts from Salesforce Revenue Cloud (Billing Implementation Guide):

“A Billing Schedule Group (BSG) acts as a container for all Billing Schedules associated with the same order product. When amendments occur, Salesforce Billing generates new Billing Schedules under the existing Billing Schedule Group.”

“Billing Schedules define the timing and amounts to bill, while Billing Schedule Groups maintain continuity across amendments and changes.”

References (document/source names only; no URLs):

Salesforce Billing Implementation Guide — Billing Schedules and Billing Schedule Groups

Salesforce Billing Implementation Guide — Amendments and Schedule Regeneration

Salesforce Revenue Cloud Data Model — Order Product to Billing Schedule Relationships

Exact Extracts from Salesforce CPQ Implementation Guide (Approvals):

“Smart Approvals skips approvals that have already been approved in a prior submission if the same conditions are met.”

“For Smart Approvals to function, the condition on the approval step must differ from the condition on the stage. If both conditions are identical, Smart Approval logic will not trigger.”

“Duplicating conditions between stages and steps prevents Smart Approvals from evaluating state changes properly.”

Step-by-Step Reasoning:

Requirement: Ensure Smart Approvals reuses previous approvals intelligently.

Issue: Smart Approvals is not working because the system doesn’t detect a conditional difference.

Why A is Correct:

Identical stage and step conditions cause the system to skip evaluation, effectively disabling Smart Approvals.

Why Others Are Incorrect:

B: Different conditions are required for Smart Approvals to function correctly (so this is not the issue—it’s the solution).

C: The number of conditions is irrelevant; it’s about condition parity.

References :

Salesforce CPQ Implementation Guide — Smart Approvals Behavior and Conditional Evaluation

Salesforce Revenue Cloud Study Guide — Approval Workflows and Smart Logic

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

“Any modification to a context definition, such as adding new attributes, requires reactivation for the system to register and make the new fields available to dependent pricing procedures.”

“Inactive context definitions or those not reactivated after edits will not expose newly added attributes for mapping or rule use.”

“Only active context definitions can be referenced in a pricing procedure.”

Step-by-Step Reasoning:

Scenario: The consultant added a new attribute but cannot see it in the pricing procedure.

Root Cause: After modifying a context definition, it must be activated again so Revenue Cloud refreshes its metadata.

Why B is Correct:

Activation publishes the updated context definition to be available in pricing procedure editors.

Why Others Are Incorrect:

A: Tags categorize attributes but do not make them appear in pricing procedures.

C: Cloning pricing procedures doesn’t expose missing context attributes; it duplicates the existing configuration.

References :

Salesforce CPQ Implementation Guide — Context Definition Activation and Pricing Procedure Integration

Salesforce Subscription Management Implementation Guide — Pricing Context Configuration Lifecycle

Explanation (150–250 words)

In Salesforce Billing, tax computation can be handled internally using the Salesforce Tax Engine or externally via integration through the Billing TaxEngineAdapter Apex interface.

When a company uses a custom tax application and wants Salesforce Billing to respect its calculated taxes, the correct and scalable approach is to integrate the custom app directly with this interface.

The TaxEngineAdapter allows Salesforce Billing to call an external system during invoice generation to retrieve tax amounts and details, which are then automatically included in the Invoice Line Tax records. This ensures taxes are calculated, stored, and posted correctly for both existing and new products without manual CSV imports.

Exact Extract from Salesforce Billing Implementation Guide:

“Use the TaxEngineAdapter Apex interface to integrate external tax calculation engines with Salesforce Billing. The adapter is invoked automatically during invoice generation to compute and apply taxes.”

Exact Extracts from Salesforce Billing Implementation Guide:

“When generating invoices, Salesforce Billing uses the billing account attached to the order as the billing entity.”

“If a billing account is specified on the order, its details (including Billing Address) take precedence over the order or account-level billing information.”

“If no billing account is provided, the system falls back to the order’s billing fields, and then to the account’s default billing profile.”

Step-by-Step Reasoning:

Hierarchy for billing address resolution:Billing Account (highest) → Order Billing Address → Account Billing Profile (lowest).

In this case:

Billing Account (Chicago) exists and overrides all others.

Why B is Correct:The billing process will use Chicago, because the billing account attached to the order dictates the billing details.

References :

Salesforce Billing Implementation Guide — Billing Account Hierarchy and Invoice Address Resolution

Salesforce Subscription Management Implementation Guide — Order Billing Account Logic

In Revenue Cloud's billing hierarchy, the Order Product level Billing Treatment takes precedence over the Product Level Billing Treatment. According to Revenue Cloud billing documentation, when a Billing Treatment is configured at multiple levels, the system applies a priority hierarchy where the most specific (transactional) level overrides more general levels.

The Billing Treatment field configures whether a charge should be billed in advance (prior to service delivery) or in arrears (after service delivery). When this setting exists at both the Product level and the Order Product level, the Order Product level configuration is the final determining factor. In the given scenario, even though the Product is configured to bill in arrears, the subscription order will actually bill in advance because the Order Product Billing Treatment explicitly specifies advance billing.

This design allows for customer-specific exceptions and flexibility. The Product level provides a default billing behavior, but sales teams and billing administrators can override this default at the Order Product level for specific deals, negotiated terms, or unique customer arrangements. For example, a customer might negotiate different billing terms than the standard product defaults, and those specific terms are captured at the Order Product level during quote-to-order conversion.

Option A is incorrect; Product Level does not override Order Product level. Option C about Legal Entity is unrelated to Billing Treatment resolution hierarchy. The Order Product level is the transaction-specific configuration point where customer-negotiated terms take final effect, making it the highest priority in the billing treatment resolution logic.

In Salesforce Revenue Cloud’s Contract Lifecycle Management (CLM) module, Sections within a document template are the best tool for organizing complex content such as M&A contracts. Sections help break large documents into logical parts, allowing contract designers to:

Insert reusable clauses

Manage conditional logic

Include dynamic tables or fields

Facilitate easier navigation and updates

As per the CLM Template Designer documentation, sections enable content modularity and simplify the process of customizing contracts for each client or scenario, particularly when dealing with large and complex documents.

Option A is too general — “creating a structure” is achieved by using sections.

Option B refers to child templates, which are useful for reusability but are typically added within sections and do not provide layout or navigation benefits on their own.

Exact Extracts from Salesforce Revenue Cloud Documents:

CLM Implementation Guide – “Creating Structured Templates with Sections”:“Use sections in your document templates to organize clauses, fields, and conditional content. Sections are the primary way to structure large and complex documents like M&A contracts.”

Contract Designer Admin Guide – “Best Practices for Document Layout”:“Sections allow you to modularize the content and manage visibility, clause insertion, and layout more effectively.”

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.

The standard way to identify whether an Asset is managed by Salesforce Revenue Cloud's Lifecycle Management engine is by using the HasLifecycleManagement field. This out-of-the-box field is a Boolean value on the Asset object that indicates whether the asset is tied to Revenue Lifecycle-managed records (e.g., originating from CPQ+ or Subscription Management flows).

This field enables reporting, filtering, and business logic to segment Revenue Cloud-managed assets from assets generated through custom or legacy systems like CK’s app. It is the most appropriate solution in this scenario as it requires no customization and is supported natively by Salesforce.

Option B suggests creating a custom field, which is unnecessary since the platform already provides a system field for this purpose.

Option C (Asset Action Source) refers to tracing asset actions to originating events, but it is not suitable for broad classification of asset origin or management type.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide – “Asset Data Model”:“The HasLifecycleManagement field flags whether an asset is lifecycle-managed by Revenue Cloud. This is useful in environments where assets come from multiple systems.”

Revenue Cloud Data Dictionary – “Asset Object”:“Use HasLifecycleManagement to distinguish system-managed assets from externally generated or legacy assets.”

Explanation (150–250 words)

Salesforce Revenue Cloud uses Context Definitions to pass contextual data—such as ContractId, AccountId, and OrderId—across transaction boundaries (e.g., from Order to Asset). To automatically capture and persist the Contract associated with an Asset, administrators should leverage Context Tags and Context Definitions instead of manual automation.

The correct solution is to:

Create a Contract lookup field on the Asset object.

Define a ContractId tag in the Asset context definition and map it to this lookup field.

Update the OrderToAsset Context Definition to map the Order’s ContractId tag to the Asset’s ContractId tag.

This ensures that when an Order creates Assets, the system automatically maps and populates the Contract reference based on context propagation, maintaining data consistency without extra automation.

Exact Extract from Salesforce Subscription Management Implementation Guide:

“Context Definitions allow for the propagation of key identifiers such as ContractId from Orders to downstream entities like Assets, ensuring accurate linkage for lifecycle management.”