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

Explanation (150–250 words)

In Salesforce Revenue Cloud, Field & Attribute Mapping is the mechanism used to transfer key data (such as specifications, attribute values, or configuration selections) from commercial products to their corresponding technical product components during fulfillment decomposition.

During decomposition, a commercial bundle is broken down into its technical components to support downstream fulfillment or provisioning systems. Field & Attribute Mapping ensures that configuration data — such as “RAM = 16 GB” or “SSD = 512 GB” — flows correctly from the quote or commercial item to each technical item, maintaining accuracy across the order-to-fulfillment process.

While Decomposition Execution Rules determine when or how decomposition runs, the Field & Attribute Mapping defines what data is transferred. Quote Line Mapping applies earlier, between quoting and ordering stages, not during fulfillment decomposition.

Exact Extract from Salesforce Subscription Management Implementation Guide:

“Use Field and Attribute Mapping to transfer configuration and specification data from commercial products to their corresponding technical product components during decomposition.”

In Salesforce Revenue Cloud, during the amendment process, the Opportunity record is optional and primarily serves for forecasting and reporting. It does not play a direct role in the automation of asset or subscription updates. The automation of amendments is handled by the Quote, Order, and Contract records. The amendment quote captures the requested changes, and once finalized, it creates an order that updates the contract and related assets automatically.

Exact Extract from Salesforce Revenue Cloud Documentation:

“In an automated amendment lifecycle, an Opportunity is optional and primarily used for forecasting or pipeline tracking. The amendment Quote is the driver of subscription changes. Once the Quote is finalized and converted into an Order, the system automatically updates the Contract and Asset records accordingly.”

— Salesforce Subscription Management Implementation Guide

This confirms that the Opportunity is not mandatory in the amendment process and does not directly perform updates. Instead, the Quote-to-Order flow governs asset and subscription modifications. The Opportunity may be linked for visibility but is not a dependency for automation.

Option B is incorrect because asset updates are never triggered directly from an Opportunity stage change. Option C is also incorrect because Opportunity requirements are not determined by pricing scenarios.

Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and Derived Pricing Documentation):

“Derived Pricing allows a product’s price to be calculated based on another product’s price, either within the same quote or across transactions.”

*“The Derived Pricing Scope determines when and how the derived price is evaluated:

Transactional: The derived price is calculated dynamically when both products are in the same quote or order.

Global: The derived price references a price from the catalog or price book, not quote-specific.”*

“If the Derived Pricing Scope is not set to Transactional, product interdependencies within the same quote will not evaluate.”

Step-by-Step Reasoning:

Scenario: Warranty should price dynamically based on another product in the same transaction.

Root Cause: The Derived Pricing Scope on the warranty product is likely not set to Transactional.

Solution: Update the Derived Price record for the warranty product → set Derived Pricing Scope = Transactional.

Why B is Correct: Ensures the price is recalculated dynamically when the related product exists in the same quote/order.

Why A & C are Incorrect:

A: Variables in the pricing procedure define logic but not scope of calculation.

C: “Is Derived” on price book entries flags derivation capability but not the transaction context for dynamic evaluation.

References :

Salesforce CPQ Implementation Guide — Derived Pricing Concepts and Scopes

Salesforce Subscription Management Implementation Guide — Pricing Dependencies and Derived Price Records

In Salesforce Revenue Cloud, the ability to manage product records within the product catalog is governed by specific permission sets and licenses. If a user can view but not edit product records, they likely lack the proper Permission Set License (PSL) required to perform product catalog modifications.

The correct solution is to assign the Product Catalog Management Designer permission set license, which enables users to:

Create and update product records

Manage attributes, configurations, and pricing

Work with product relationships and dependencies

According to the Salesforce CPQ Implementation Guide, this permission set is essential for users responsible for catalog operations.

Option A (Product Management Queue) is unrelated to user permissions.

Option B (Modify All Data) is overly permissive and not best practice for security and data integrity; it grants unrestricted access to all objects, which is not necessary.

Exact Extracts from Salesforce Revenue Cloud Documents:

CPQ Implementation Guide – “User Permissions for Product Management”:“Assign the Product Catalog Management Designer permission set license to users responsible for managing product and pricing records. This license includes edit access for key product catalog components.”

Revenue Cloud Admin Guide – “Setting Up Product Catalog Roles”:“Use the appropriate PSL to ensure least privilege while granting catalog modification capabilities.”