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

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 Revenue Cloud (CPQ & Billing Implementation Guides):

“During quote-to-contract conversion, the selection options presented in the discount popup are derived from the Contract Item Price object’s Discount Type picklist field.”

“Administrators can remove or rename values from the Discount Type picklist to customize which discount options appear to users during the conversion process.”

“The screen flow and LWC components rely on metadata values; modifying these underlying picklist entries changes the available options in the UI.”

Step-by-Step Reasoning:

Requirement: Remove “None” option from the discount-selection popup.

Configuration Location: The options come from Contract Item Price → Discount Type picklist.

Solution: Remove the “None” picklist value in object metadata setup.

Why B is Correct:Declaratively removes the undesired value from the popup.

Why Others Are Incorrect:

A: The “Create Contract From Quote” flow references existing metadata and does not define picklist values.

C: LWC modification is not required for removing a metadata-driven value.

References :

Salesforce Billing Implementation Guide — Quote-to-Contract Conversion and Discount Mapping

Salesforce CPQ Implementation Guide — Contract Item Price Configuration

Comprehensive and Detailed Explanation From Exact Extract:

Revenue Cloud Product Discovery provides a Default Catalog option in Product Discovery Settings so that:

If there is only one primary catalog, it can be preselected automatically.

Users are not prompted to choose a catalog each time.

Customizing flows (A) is unnecessary. Skipping catalogs (C) would bypass key Product Catalog Management features and is not aligned with the recommended architecture.

Exact Extracts from Salesforce CPQ & Subscription Management Implementation Guides:

“Product Discovery Context Definitions provide the framework for dynamic filtering and qualification rules during catalog browsing and product configuration.”

“Context definitions can include nodes that map Account, Contact, and related attributes (such as customer tier, geography, or historical data) for rule evaluation.”

“This enables dynamic, real-time product visibility and eligibility control during Browse Catalog.”

Step-by-Step Reasoning:

Requirement:

Dynamic catalog filtering during quoting based on Account Tier, Location, and Purchase History.

Correct Mechanism:

Product Discovery Context Definition — defines what contextual data (Account, Tier, Location, etc.) is available for evaluation in qualification rules.

Why A is Correct:

It uses declarative context definition mapping (no code) to feed rule logic during catalog browsing.

Why B and C are Incorrect:

B: Sales Transaction Context applies to pricing and calculation logic, not catalog discovery visibility.

C: Product2 custom fields and layouts don’t control dynamic filtering or interact with context definitions; they’re static metadata.

References :

Salesforce CPQ Implementation Guide — Product Discovery Context Definitions and Qualification Rules

Salesforce Subscription Management Implementation Guide — Dynamic Product Eligibility using Context Definitions