Rev-Con-201 Exam Dumps : Salesforce Certified Revenue Management Consultant

The pricing procedure and associated predefined decision table are already active. Active pricing metadata is protected from structural changes that could invalidate runtime pricing. Therefore, the relevant components must first bedeactivatedbefore adding the currency dimension required for multi-currency pricing.

After deactivation, the organization can enable multi-currency and introduce Currency into the applicable decision-table/pricing configuration. Once the metadata is valid and synchronized, the decision table and pricing procedure can be reactivated.

Option A creates unnecessary duplicate procedures and decision tables. Cloning can be useful for versioning or major redesign, but it is not required simply to add the missing multi-currency dimension. Option B assumes the Currency field will automatically become usable after a waiting period; that does not address the inability to structurally modify already active decision-table and pricing metadata.

The key configuration principle is thatactive runtime pricing artifacts must be deactivated before making structural changes, then reactivated after the revised configuration has been completed.

Study Guide Reference:Configure, Price, Quote — Multi-Currency Pricing; Decision Tables; pricing procedure activation lifecycle.

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

The supplied source identifiesChicago, the address associated with theBilling Account, as the address used when Billing processes the order.

Revenue Management distinguishes the customer/account participating in the commercial transaction from the account responsible for billing. Where a Billing Account is explicitly associated with the order, billing-related information can be derived from that billing-specific relationship rather than from the general account default or another address carried on the commercial Order.

The San Francisco address belongs to the Account ' s default Billing Profile. That serves as a default when a more transaction-specific billing source does not take precedence. New York is present directly on the order, but the scenario deliberately introduces a Billing Account with its own Chicago billing address. The supplied answer establishes that the Billing Account has precedence in this hierarchy for billing processing.

This type of precedence matters in B2B scenarios where the buyer, service recipient, and payer can be different organizational entities. Revenue Management must therefore resolve the billing address from the correct financial-account context.

Study Guide Reference:Invoice Management — Billing Accounts; Billing Profiles; billing-address derivation and order billing.

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

A Contract Extraction Template must connect the information that Contracts AI extracts from a source document with the structured Context Service model used to store or process that information. The relevant template details are thereforeAttribute Definition and Context Mapping.

The Attribute Definition specifies what contract information should be extracted—for example, payment terms, renewal language, termination conditions, notice periods, or custom contractual fields. Context Mapping identifies where that extracted attribute fits within the selected context definition so that Contracts AI can transform unstructured PDF content into structured Revenue Management data.

Option A focuses on Record Type and Field Mapping but does not supply the context-level attribute definition required by the extraction architecture. Option B combines Attribute Definition with Field Mapping but omits the Context Mapping needed to associate extracted information with an existing context definition.

This design reflects the broader Agentforce Revenue Management architecture in which Context Service provides a standardized data representation consumed across services. Contracts AI uses the extraction template to bridge unstructured contract documents and that structured contextual model.

Study Guide Reference:Contracts and Orders — Contracts AI; Contract Extraction Templates; Attribute Definitions; Context Mapping.

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