On the final day of User Acceptance Testing (UAT), a critical issue is discovered. The tester believes the critical issue is a bug, while the developer asserts it is working as designed. The business representative suspects a training issue, and the project manager views the critical issue as scope creep.What is the next course of action to mitigate this critical issue?
Answer(s): A
In Salesforce Revenue Cloud implementations, especially during User Acceptance Testing (UAT), it is common to encounter discrepancies in expectations versus system behavior. When stakeholders disagree on the nature of a critical issue -- whether it is a defect, scope change, or training gap -- the correct course of action is to collaboratively review the issue against the signed-off business requirements.Per the Salesforce Implementation Best Practices, a triage meeting or working session involving the tester, developer, business stakeholder, and project manager should be conducted to:Review the documented business requirements and use casesEvaluate whether the issue represents a missed requirement, a misunderstanding, or a training needReach consensus on how to classify and resolve the issueOption A reflects this structured and collaborative approach.Option B is premature escalation without due diligence and can lead to bypassing quality assurance.Option C assumes the issue is a bug and skips the critical validation and stakeholder agreement process, risking scope deviation or misalignment.Exact Extracts from Salesforce Revenue Cloud Documents:Salesforce Partner Implementation Guide "Managing UAT and Defect Triage":"Conduct issue triage sessions with key stakeholders to determine if findings are bugs, enhancements, or training gaps. Always align resolution path with documented requirements."Revenue Cloud Delivery Framework "Final UAT and Go-Live Readiness":"Do not assume issue type. Instead, validate all critical issues with documentation and team consensus."
Salesforce Partner Implementation GuideRevenue Cloud Delivery FrameworkSalesforce Project Governance and UAT Checklist
A project is moving from the design phase to the build phase.What should a Revenue Cloud Consultant do to ensure a successful build cycle?
As a Salesforce Revenue Cloud project moves from design into the build phase, it is essential to follow Salesforce's recommended development lifecycle and environment strategy to ensure a smooth, secure, and scalable implementation.Per the Salesforce Revenue Cloud Implementation Guide and Project Delivery Framework, the consultant must:Set up multiple environments: such as Developer Sandbox (for configuration and coding), UAT Sandbox (for user testing), and Production (for go-live)Establish a deployment strategy and toolset: using tools like Change Sets, Salesforce CLI, DevOps Center, or third-party CI/CD platformsMaintain proper version control and release planningThis approach ensures code quality, traceability, and a safe pathway for validating changes before going live.Option B, while valid during design and requirement gathering, should have been completed before build.Option C (building directly in production) violates best practices, increases risk, and lacks rollback and testing controls.Exact Extracts from Salesforce Revenue Cloud Documents:Revenue Cloud Delivery Framework "Environment Strategy":"Create isolated sandboxes for development, QA, and UAT. Always deploy to production through a structured release process."Salesforce Implementation Lifecycle "Build Phase":"Establish a deployment toolset and environment strategy at the beginning of the build cycle to ensure governance and minimize risk."
Salesforce Revenue Cloud Delivery FrameworkSalesforce Project Lifecycle Best PracticesSalesforce DevOps and Deployment Strategy Documentation
An agreement was executed using Revenue Cloud's Contract Lifecycle Management (CLM) functionality, and obligations were created to track compliance for key clauses.What is a reason to create the obligations?
In Salesforce Revenue Cloud's Contract Lifecycle Management (CLM) module, Obligations are used to track post-signature responsibilities and ensure compliance with contractual commitments. An obligation represents an actionable item tied to a contract clause, such as delivering a report, making a payment, or completing a follow-up.One of the primary benefits of creating obligations is the ability to:Assign Owners (users or roles)Attach TasksSet due dates, statuses, and related metadataThis allows organizations to track performance on obligations over the lifecycle of the agreement and maintain accountability.Option A is correct, as assigning owners and tasks is core to the obligation management model.Option B is partially correct but too narrow; the Fulfilled status is only one aspect of the obligation lifecycle.Option C is incorrect -- price discounts are managed through pricing rules, not obligations.Exact Extracts from Salesforce Revenue Cloud Documents:CLM Implementation Guide "Obligation Management":"Obligations allow contract owners to assign responsibilities to individuals and track their completion using tasks, due dates, and fulfillment status."Revenue Cloud CLM Overview "Post-Signature Lifecycle Features":"Use obligations to monitor compliance with agreed-upon clauses by assigning tasks to the appropriate business users."
Salesforce CLM Implementation GuideSalesforce Revenue Cloud CLM Functional OverviewCLM Admin and Template Designer Documentation
In the context of a quote or order, the administrator needs to include a Product2 custom field for search.What should the administrator do to accomplish this?
Answer(s): B
To make a custom field on the Product2 object available for searching and filtering in the Product Discovery or Browse Products experience, the administrator must configure it using the Index and Search Configuration feature in Salesforce Revenue Cloud.The correct process includes:Navigating to the Index and Search Configuration page.Selecting the Product2 object.Adding the custom field to the list of searchable fields.Running the Rebuild Index job to apply the changes.This process ensures the custom field is indexed and usable in the search API and UI filters during quote or order product selection.Option A (list view filter) impacts UI sorting/filtering but not full-text search capability.Option C involves altering the Discover Products flow, which is not required if the goal is simply to enable search based on a field -- and would introduce unnecessary complexity.Exact Extracts from Salesforce Revenue Cloud Documents:Product Discovery Setup Guide "Index and Search Configuration":"To make custom fields on Product2 searchable in product discovery, configure the field in the Index and Search Configuration UI and then rebuild the search index."Salesforce CPQ Product Catalog Guide "Custom Fields and Discovery Search":"After adding a field to searchable fields, it is required to run the Rebuild Index job to enable the change."
Salesforce Revenue Cloud Product Discovery GuideCPQ Implementation Guide Product Catalog ConfigurationSalesforce Index and Search Configuration Admin Tool
A product administrator is tasked with creating a Work Anywhere software bundle that has two components. The first component is a VPN license product with a quantity of five (defaulted and cannot be changed). If a customer purchases two instances of the bundle, then it will provide ten VPN licenses. The second component is a classroom training product that the customer will receive only once, regardless of how many bundles are purchased, and the price is included in the bundle's price.What should the product administrator set for the quantity scaling method for each of the bundle components?
Answer(s): C
(150250 words)VPN License (quantity 5, non-editable): When a bundle quantity increases, the option must scale so total licenses multiply accordingly (e.g., bundle qty 2 × option qty 5 = 10 licenses). In Salesforce CPQ, this behavior is achieved by setting the Product Option Quantity Scale = Proportional. Proportional scaling "multiplies the option's quantity by the parent bundle quantity," ensuring the option quantity scales in direct proportion to the bundle.Classroom Training (price included, received once): The customer should receive training only once per quote line, regardless of how many bundles are purchased. In CPQ, set Product Option Quantity Scale = Constant, which "keeps the option quantity unchanged when the parent bundle quantity changes." Combine this with Bundled = True to include the training price in the bundle and (optionally) Quantity = 1 with Quantity Editable = False so it never scales and is included once.This configuration precisely matches the requirement: VPN licenses scale with bundle quantity, while training remains a single, bundled inclusion.Exact Extracts from Salesforce Revenue Cloud documents (field behavior, paraphrased):· Quantity Scale Proportional: option quantity scales with parent bundle quantity (multiplies).· Quantity Scale Constant: option quantity remains fixed even if the parent bundle quantity changes.· Bundled = True: option price is included in bundle price.Key Steps (concise)Option (VPN): Quantity = 5, Quantity Editable = False, Quantity Scale = ProportionalOption (Training): Quantity = 1, Quantity Editable = False, Quantity Scale = Constant, Bundled = TrueReference (document/source names only; no links)Salesforce CPQ Implementation Guide -- Product Bundles and OptionsSalesforce CPQ Implementation Guide -- Product Option Fields (Quantity, Quantity Editable, Bundled, Quantity Scale)Salesforce CPQ Implementation Guide -- Bundle Quantity and Option Quantity Scaling
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.