Universal Containers sells customizable laptops. A fulfillment designer needs to ensure that selected specifications (for example, RAM, SSD) from the commercial laptop product are correctly transferred to its technical product components during decomposition for accurate fulfillment.Which mechanism should the fulfillment designer use to transfer the technical product components?
Answer(s): B
(150250 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."
Salesforce Subscription Management Implementation Guide -- Decomposition Framework and Data MappingSalesforce Revenue Cloud Fulfillment Integration Guide -- Commercial-to-Technical Product MappingSalesforce Solution Architect Handbook -- Fulfillment Design Patterns and Mapping Logic
An IT service provider purchased Revenue Cloud. Currently, the provider needs to mark its Super Duper Product as an automatically renewable product with no manual interaction from users.How should a Revenue Cloud Consultant handle this requirement?
Answer(s): C
(150250 words)In Salesforce CPQ and Subscription Management, automatic renewal behavior is driven at the product level via the Auto Renew field on the Product2 record. When this checkbox is selected, any subscription created for that product automatically inherits the renewal behavior -- meaning that the system will create renewal opportunities, quotes, or contracts automatically without user intervention.The Auto Renew setting on Product2 defines renewal eligibility for all subscriptions derived from that product, ensuring consistent automation across all customers and contracts.The Asset object does not directly control renewal logic; instead, it reflects renewal status after processing. The Product Selling Model defines how products are sold (one-time, recurring, usage- based), but renewal logic is still determined by the Product2-level Auto Renew setting.Exact Extract from Salesforce Subscription Management Guide:"To enable automatic subscription renewal without user action, select the Auto Renew checkbox on the Product2 record. Subscriptions created from this product will automatically renew upon term completion."
Salesforce Subscription Management Implementation Guide -- Auto-Renewal ConfigurationSalesforce CPQ Implementation Guide -- Subscription Product and Renewal BehaviorSalesforce Revenue Cloud Data Model -- Product2 and Subscription Relationship
A consultant is tasked to create an advanced decision table that will provide a discount % as output based on the following scenario.The discount is eligible for Partner accounts where they have products ordered in quantities greater than 100, or if customers order an accessory in quantities greater than 100.Conditions:Account Source = PartnerOrdered Quantity > 100Product Category = AccessoryWhile defining the conditions during the creation of a decision table, how should the consultant configure the table to satisfy the conditions above?
(150250 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."
Salesforce Revenue Cloud Pricing Implementation Guide -- Decision Table Conditions and Custom LogicSalesforce CPQ Advanced Rules Framework -- Custom Logic SyntaxSalesforce Pricing Engine Developer Guide -- Conditional Evaluation Behavior
After activating an order for a usage-based analytics subscription, a billing specialist wants to confirm that the system has generated the necessary components to support usage tracking, entitlement enforcement, and billing readiness.Which set of records is created automatically as part of the usage management process?
(150250 words)When a usage-based subscription is activated in Salesforce Billing or Subscription Management, the system automatically generates a hierarchy of records that support usage tracking, entitlement enforcement, and billing readiness.These include:Usage Entitlement Account (UEA): Identifies the customer's entitlement context for usage collection.Usage Entitlement Bucket (UEB): Stores individual usage events or quantities accumulated for a given period and product.Wallet: Tracks prepaid balances or usage credits and integrates with rating and billing to manage consumption and renewals.This structure ensures all usage data is captured, rated, and invoiced accurately according to entitlements.Option A represents general asset and entitlement records but not specific usage entities. Option B lists derived financial records, not the foundational usage structures.Exact Extract from Salesforce Billing Implementation Guide:"Upon activation of a usage-based order product, Salesforce Billing creates a Usage Entitlement Account, Usage Entitlement Bucket, and Wallet to support usage capture, entitlement enforcement, and billing integration."
Salesforce Billing Implementation Guide -- Usage Management OverviewSalesforce Revenue Cloud Data Model -- Usage Entitlement EntitiesSalesforce Subscription Management Implementation Guide -- Wallet and Usage Tracking
A product bundle has defined a constraint model that is currently in use and has been actively sold for the last few months. A new product will be launched next month and will be sold as part of the same bundle. The product designer updated the bundle structure under Product Catalog Management to add the new product.What must the product designer do to ensure that the child product is added to the constraint model within the product bundle?
(150250 words)In Salesforce Revenue Cloud, Constraint Models define configuration logic through Constraint Modeling Language (CML). When a new child product is added to an existing bundle, the system does not automatically include it in the associated constraint model. To bring the new product into scope, the designer must:Create a new type in the CML Editor that corresponds to the newly added product.Import the product associations from Product Catalog Management to ensure the constraint model references the correct product hierarchy and rules.This approach integrates the new component into the model while retaining existing logic and rule structure. Option A incorrectly assumes the Visual Builder can auto-import relationships for new products, and option B would create a new constraint model rather than updating the existing one.Exact Extract from Salesforce CPQ Implementation Guide:"When new products are added to an existing bundle, define a new type for the product in the Constraint Model and import the associations from Product Catalog Management to ensure inclusion in configuration rules."
Salesforce CPQ Implementation Guide -- Constraint Model Maintenance and CML Editor UsageSalesforce Revenue Cloud Catalog Management Guide -- Updating Bundles with New ComponentsSalesforce Solution Architect Handbook -- Constraint Model Versioning and Governance
Post your Comments and Discuss Salesforce Rev-Con-201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the Rev-Con-201 content, but please register or login to continue.