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

Activating a customized Browse Catalog flow does not automatically make Product Discovery use it. The consultant must configure the newFlow Name in Product Discovery Setupso that the runtime browsing experience invokes the customized active flow.

Product Discovery owns the catalog-browsing experience used during product selection. Consequently, its setup area contains configuration directly related to how catalog browsing operates, including the flow used to drive the experience.

Option A is incorrect because Pricing Settings governs price calculation configuration rather than which flow renders Product Discovery. Option C is too broad: Revenue Settings includes general Revenue Management behaviors, but the question concerns a feature-specific Product Discovery flow and the supplied source places that reference in Product Discovery Setup.

This follows the same general pattern seen with other customizable Salesforce-provided flows: creating or activating a clone is only part of the process. The feature must also be explicitly pointed to the replacement flow.

Study Guide Reference:Catalog Management — Product Discovery Setup; Browse Catalog flow; runtime product-browsing customization.

===============

ACredit Memorepresents a reduction in the amount that a customer owes. Negative amendments, cancellations, returns, overcharges, or other downward billing adjustments can therefore produce credit amounts that must be retained and subsequently applied against outstanding invoice balances.

Salesforce explicitly defines a credit memo as a seller-issued document acknowledging a reduction in the customer ' s amount owed. Revenue Management supports standalone credit memos, credit memos against invoice lines, automated application of available credits to invoices, and automatic conversion of negative invoice lines into credit memo lines.

This directly matches the scenario: the system must preserve a customer credit and later use that available balance to settle invoices before collecting additional payment.

A Debit Memo has the opposite financial effect: it increases the amount owed. “Cash Memo” is not the applicable Revenue Management billing instrument for this use case.

Using Credit Memos also preserves accounting traceability because the credit remains separately identifiable and its applied and unapplied amounts can be monitored as it is allocated against customer invoices.

Study Guide Reference:Invoice Management — Credit Memos; negative invoice lines; credit application and invoice settlement.

===============

The required permission isPlace Change Order. In-flight order changes address situations where an activated order has entered the order lifecycle but requires modification before fulfillment is complete. Quantity increases, decreases, and similar supported modifications are processed as change-order activity rather than by directly editing the committed original order.

Assigning the appropriate Place Change Order permission enables designated Order Managers to initiate the supported Revenue Management process for these post-activation adjustments.

Option B, Place Supplemental Order, represents a different order concept and is not the permission identified by the supplied source for changing existing in-flight order quantities. Option C likewise does not correspond to the standard permission required for this use case.

The business principle is important: after an order reaches a committed lifecycle state, changes should remaintransactionally traceable. A change order preserves the relationship between the original order and the subsequent adjustment rather than silently overwriting the original commercial commitment.

Study Guide Reference:Contracts and Orders — In-Flight Order Management; Change Orders; Place Change Order permission.

===============

Lot-based or As-is Renewalsare designed for assets whose commercial history contains different quantities and prices acquired through multiple transactions. Rather than flattening those historical lots into a single price, this renewal behavior preserves the relevant pricing structure from the existing asset state when the subscription is renewed.

That matches the scenario because the customer experienced several upsells and different negotiated subscription prices during the previous term. The sales user wants those existing prices carried forward rather than repricing the full quantity uniformly.

Option A is unrelated. Assetize Order controls creation of lifecycle-managed asset records from order products; modifying it is not the mechanism for determining renewal pricing. Option B simplifies the requirement into a single Last Negotiated Price. Where multiple acquisition lots exist, one latest price may not accurately represent the differentiated historical pricing that must be preserved.

Lot-based/As-is renewal behavior retains the granular commercial lineage required to renew quantities according to their existing price basis.

Study Guide Reference:Asset Management — Renewal Pricing; Lot-Based Renewals; As-Is Renewals; Asset Action Source pricing lineage.

===============

Product qualification duringBrowse Catalogrequires the Product Discovery process to have the customer data that qualification rules evaluate. A Product Discovery context definition can model this information through nodes and attribute mappings—for example, Account Tier, customer location, and other relevant customer or transaction attributes.

Context Service hydrates those values into the runtime context. Qualification procedures and decision logic can then evaluate them and determine which products should be displayed or excluded in real time.

Option B incorrectly frames product visibility as user-profile record security. The requirement concernscustomer-specific commercial eligibility, not Salesforce record-level access for the logged-in user. Sales Transaction context can be important elsewhere in Revenue Management, but the source specifically identifies Product Discovery context for Browse Catalog qualification.

Option C relies on Product2 custom fields, page layouts, and validation rules. Page layouts cannot dynamically implement catalog qualification based on customer context, and validation after product selection would occur too late.

The correct architectural pattern is therefore:hydrate customer context → evaluate qualification logic → return the eligible catalog products during Product Discovery.

Study Guide Reference:Catalog Management — Product Discovery; Context Service; qualification rules; context-driven product eligibility.

The GSI is creating separate SKUs for values that are better modeled ascharacteristics of a reusable commercial offering. Product Attributes allow those variations—such as technology skill, seniority, certification, region, specialization, or competency—to be represented as configurable values rather than separate Product2 records.

For example, instead of creating distinct products for “Senior Salesforce Architect,” “Senior AWS Architect,” and “Senior Azure Architect,” the organization can model a reusable consulting-role product and expose technology or skill as attributes. This sharply reduces Product2 proliferation while maintaining configurability during quoting.

Product Categories, option A, organize products for browsing and discovery but do not eliminate the need for separate SKUs if each skill continues to be modeled as a different product. Product Classification, option C, provides a reusable structural definition for products and their associated attributes. It is valuable in the overall model, but the mechanism directly eliminating the million-SKU pattern described here is the use ofProduct Attributes to represent variation.

The architectural objective is to distinguish a true commercial product from configurable characteristics of that product.

Study Guide Reference:Catalog Management — Product Attributes; Product Classification; SKU rationalization and reusable product modeling.

===============

TheOrder Product-level Billing Treatment takes precedenceover the Billing Treatment inherited from the Product. Product-level configuration establishes reusable default billing behavior, while transaction-level configuration provides a more specific value for the individual commercial order product.

In this scenario, the Product default says to bill in arrears, but the Order Product explicitly specifies advance billing. Revenue Management therefore uses the more specific Order Product treatment, resulting in advance rather than arrears billing.

Option A reverses this precedence and would prevent transaction-specific billing requirements from overriding defaults. Option C incorrectly links Billing Treatment evaluation to whether a Legal Entity exists. Legal Entity determines important financial, tax, and accounting context, but it does not eliminate the normal Billing Treatment resolution described here.

This illustrates the common configuration principle ofdefault versus transactional override: product configuration supplies standard behavior, while Order Product values can refine that behavior for a specific transaction.

Study Guide Reference:Invoice Management — Billing Treatments; Order Product billing configuration; Product-level defaults and override precedence.

===============

Adding an attribute to a context definition changes the definition metadata, but Revenue Management services do not consume that revised structure until the context definition isactivated. Activation publishes the current definition so dependent services such as Salesforce Pricing can use its nodes and attributes.

That explains why the newly created custom field is visible in the context-definition configuration but unavailable when the consultant attempts to reference it from the pricing procedure. The definition has not yet been promoted into an active runtime state.

Option A is not the primary missing step identified in this scenario. Tags can be important for locating and semantically identifying contextual attributes, but they do not substitute for activating the modified context definition. Option C is unnecessary. A pricing procedure does not need to be cloned merely because another usable attribute has been added to its associated context.

The correct sequence is to modify the context definition, complete the required mappings,activate the definition, and then configure the pricing procedure to consume the newly available attribute.

Study Guide Reference:Configure, Price, Quote — Context Service and Salesforce Pricing; context definitions; activation and pricing procedure inputs.

===============