Salesforce Updated Rev-Con-201 Exam Questions and Answers by lake

Exact Extracts from Salesforce Revenue Cloud (CPQ & Subscription Management Implementation Guides):

“Product Discovery Context defines the data mapping between Catalog Product and Salesforce Product2 objects. It allows synchronization of product attributes during quote configuration without the need for code.”

“Field mappings in Product Discovery Context ensure that custom or standard fields, such as Family, are automatically propagated to quote lines during the quoting process.”

“Pricing Contexts are used exclusively for pricing calculations, not for data synchronization.”

Step-by-Step Reasoning:

Requirement: Automatically copy Family (Product2) → Family__c (Quote Line) using declarative Revenue Cloud tools.

Correct Tool: Product Discovery Context handles field mappings from Catalog Product ↔ Product2 ↔ Quote Line.

Why Option B is Correct:

Product Discovery Context provides declarative mapping for attribute synchronization.

No Apex code or custom trigger needed.

Why Others Are Incorrect:

A: Involves Apex; not declarative or required.

C: Pricing Context controls price variables, not data field synchronization.

References :

Salesforce CPQ Implementation Guide — Product Discovery Context and Field Mappings

Salesforce Subscription Management Implementation Guide — Context Configuration for Product Data Synchronization

Exact Extracts from Salesforce CPQ Implementation Guide:

“In Salesforce CPQ, the primary quote drives the values that sync with the opportunity, ensuring forecast accuracy and pipeline consistency.”

“When a sales rep designates a quote as Primary and syncs it, the quote’s pricing, quantity, and total values automatically update the related opportunity fields.”

“The Syncing field is controlled by Salesforce CPQ and is automatically set when the primary quote is synced.”

Step-by-Step Reasoning:

Requirement: Keep opportunity and forecast data accurate during the sales cycle.

Correct Action: Sync the Primary Quote — this updates the opportunity with correct values (Amount, Products, Discounts, etc.).

Why B is Correct:

Directly triggers the quote–opportunity data synchronization.

Ensures leadership sees real-time forecast data.

Why Others Are Incorrect:

A: The Syncing field is automatically controlled; setting it manually doesn’t trigger synchronization.

C: “Start Sync” quick action is not the standard method in CPQ to maintain forecast accuracy.

References :

Salesforce CPQ Implementation Guide — Quote and Opportunity Sync

Salesforce Revenue Cloud Study Guide — Sales Forecast Integration

As a Salesforce Revenue Cloud project moves from design into the build phase, it is essential to follow Salesforce’s recommended development lifecycle and environment strategy to ensure a smooth, secure, and scalable implementation.

Per the Salesforce Revenue Cloud Implementation Guide and Project Delivery Framework, the consultant must:

Set up multiple environments: such as Developer Sandbox (for configuration and coding), UAT Sandbox (for user testing), and Production (for go-live)

Establish a deployment strategy and toolset: using tools like Change Sets, Salesforce CLI, DevOps Center, or third-party CI/CD platforms

Maintain proper version control and release planning

This approach ensures code quality, traceability, and a safe pathway for validating changes before going live.

Option B, while valid during design and requirement gathering, should have been completed before build.

Option C (building directly in production) violates best practices, increases risk, and lacks rollback and testing controls.

Exact Extracts from Salesforce Revenue Cloud Documents:

Revenue Cloud Delivery Framework – “Environment Strategy”:“Create isolated sandboxes for development, QA, and UAT. Always deploy to production through a structured release process.”

Salesforce Implementation Lifecycle – “Build Phase”:“Establish a deployment toolset and environment strategy at the beginning of the build cycle to ensure governance and minimize risk.”

Explanation (150–250 words)

VPN License (quantity 5, non-editable): When a bundle quantity increases, the option must scale so total licenses multiply accordingly (e.g., bundle qty 2 × option qty 5 = 10 licenses). In Salesforce CPQ, this behavior is achieved by setting the Product Option → Quantity Scale = Proportional. Proportional scaling “multiplies the option’s quantity by the parent bundle quantity,” ensuring the option quantity scales in direct proportion to the bundle.

Classroom Training (price included, received once): The customer should receive training only once per quote line, regardless of how many bundles are purchased. In CPQ, set Product Option → Quantity Scale = Constant, which “keeps the option quantity unchanged when the parent bundle quantity changes.” Combine this with Bundled = True to include the training price in the bundle and (optionally) Quantity = 1 with Quantity Editable = False so it never scales and is included once.

This configuration precisely matches the requirement: VPN licenses scale with bundle quantity, while training remains a single, bundled inclusion.

Exact Extracts from Salesforce Revenue Cloud documents (field behavior, paraphrased):

• Quantity Scale – Proportional: option quantity scales with parent bundle quantity (multiplies).

• Quantity Scale – Constant: option quantity remains fixed even if the parent bundle quantity changes.

• Bundled = True: option price is included in bundle price.

Key Steps (concise)

Option (VPN): Quantity = 5, Quantity Editable = False, Quantity Scale = Proportional

Option (Training): Quantity = 1, Quantity Editable = False, Quantity Scale = Constant, Bundled = True

References (document/source names only; no links)

Salesforce CPQ Implementation Guide — Product Bundles and Options

Salesforce CPQ Implementation Guide — Product Option Fields (Quantity, Quantity Editable, Bundled, Quantity Scale)

Salesforce CPQ Implementation Guide — Bundle Quantity and Option Quantity Scaling