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

In Salesforce Revenue Cloud, when configurable products are ordered (e.g., internet service with upload/download speeds), the configured values are stored at the Order Product Attribute level. These are linked to the corresponding Order Product, which represents the actual product ordered.

To generate a report that includes both:

The ordered item (Order Product)

Its specific configurations (upload/download speeds)

You need to use a custom report type that includes:

Order Products

Order Product Attributes

While Product Attribute Definition (mentioned in Option B and C) defines the possible attributes at the product catalog level, it does not store the selected values made during quoting or ordering. The actual values chosen are stored in the Order Product Attribute object.

This approach ensures that your report includes actual selections made by customers, not just the available options.

Exact Extracts from Salesforce Revenue Cloud Documents:

Subscription Management Implementation Guide – “Order Product Attribute Usage”:“Order Product Attributes store the selected values from the product configuration process and are linked directly to the corresponding Order Product.”

CPQ Data Model Reference – “Attributes and Orders”:“Reporting on configurable products requires joining Order Product with Order Product Attribute to retrieve both the product and its configured values.”

Exact Extracts from Salesforce Revenue Cloud (Pricing Procedure and CPQ Implementation Guides):

“The Simulate feature in the pricing procedure enables administrators to execute and trace the pricing calculation logic to identify where pricing rules, conditions, or adjustments are applied.”

“Using simulation, consultants can visualize the price waterfall and confirm whether attribute-based, tier-based, or contract-based adjustments are contributing to the final price.”

“This is the recommended first diagnostic step when pricing discrepancies are reported.”

Step-by-Step Reasoning:

Issue: Discrepancy between expected and calculated renewal quote prices.

Correct Action: Use Simulate to run the pricing engine in diagnostic mode and examine the price waterfall.

Why C is Correct:

Allows tracing rule application order and effective discounts.

Identifies where unexpected conditions or overrides occurred.

Why Others Are Incorrect:

A: Manual edits mask the issue rather than diagnose it.

B: Deactivating/re-enabling does not reveal rule logic; it risks production disruption.

References :

Salesforce CPQ Implementation Guide — Pricing Procedures and Price Simulation

Salesforce Subscription Management Implementation Guide — Pricing Debugging Tools and Price Waterfall Analysis

Explanation (150–250 words)

The scenario describes two possible discount triggers:

Condition 1: Partner accounts with orders above 100 units → (1 AND 2)

Condition 2: Customers ordering accessories above 100 units → (2 AND 3)

To model this in a decision table, the consultant should choose Condition Type = Custom Logic and define the logical expression as (1 AND 2) OR (2 AND 3). This expression ensures the decision table returns a discount whenever either condition group is met.

Option A incorrectly mixes unrelated logical paths and would not isolate the two valid scenarios. Option C would require all three conditions to be true simultaneously, which contradicts the “or” requirement.

Exact Extract from Salesforce Pricing and Decision Framework Guide:

“When multiple conditional paths can trigger an output, use Custom Logic and define a Boolean expression such as (1 AND 2) OR (2 AND 3). The decision table evaluates true if any path meets the condition.”

The most common reason products do not appear in Browse Catalog is that they lack an active price book entry in the price book associated with the quote. This is a fundamental requirement for product visibility in Revenue Cloud's Product Discovery process.

Product visibility in Browse Catalog depends on multiple configuration factors, but the price book entry is critical. According to Revenue Cloud troubleshooting documentation, products must have an active price book entry within the specific price book selected on the quote or order. Without this price book entry, even if the product exists and is active, it will not appear in the catalog browse experience.

When a quote is created, it is associated with a specific price book. The Product Discovery process filters products based on this price book association, showing only products that have entries in that particular price book. This ensures that sales users only see products they can actually sell at valid prices. Additionally, the price book entry must be active; inactive entries will not make products visible.

While Option B regarding permissions could affect product visibility in some scenarios, it is not the primary reason for products not appearing in Browse Catalog. The "View All" permission relates to record-level access rather than Product Discovery functionality. Option C about component configuration would prevent access to Browse Catalog entirely, not just hide specific products. The absence of a valid, active price book entry in the quote's associated price book is the most direct and common cause of products not appearing during the browse phase.