Rev-Con-201 Salesforce Certified Revenue Management Consultant Exam Topics and Questions
These Salesforce Certified Revenue Management Consultant (Rev-Con-201) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise Rev-Con-201 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Certified Revenue Management Consultant certification exam.
Let's Practice Free Salesforce Rev-Con-201 Questions Aligned with Official Exam Topics
This topic sets the floor for everything else on the exam. Before you can configure a pricing rule or manage an asset lifecycle, you need a working mental model of how the platform holds together: its objects and relationships, its key services, and the access-control layer that governs who can do what. At 18%, this is one of the two heaviest topics, and the questions hit both breadth and depth. β Platform foundations and access control Flows, Lightning page components,...
This topic sets the floor for everything else on the exam. Before you can configure a pricing rule or manage an asset lifecycle, you need a working mental model of how the platform holds together: its objects and relationships, its key services, and the access-control layer that governs who can do what. At 18%, this is one of the two heaviest topics, and the questions hit both breadth and depth.
β Platform foundations and access control
Flows, Lightning page components, permission set licenses, and permission sets form the scaffolding every other feature sits on. The exam tests this layer at a practical level: you need to know which permission set license unlocks which capability, how to assign it correctly, and why a flow built for one context behaves differently in another. Lightning page components matter because context-aware layouts depend on them, and the exam will present scenarios where the wrong component choice produces a broken or incomplete user experience. The gotcha here is conflating permission sets with permission set licenses. They are related but distinct, and the exam exploits that confusion in scenario questions. Know the assignment sequence: license first, then permission set, and understand why reversing that order fails.
β Core services and integration points
Context Service, Omnistudio, and the Business Rules Engine are the three services most candidates underestimate. Context Service is what makes the platform context-aware: it assembles and delivers relevant data to a running process or interface without the developer having to query for it explicitly. Omnistudio provides the declarative tooling (FlexCards, OmniScripts, DataRaptors, Integration Procedures) that surfaces Revenue Management data and logic to users. The Business Rules Engine externalises decision logic so that pricing, eligibility, and validation rules can be changed without touching code. APIs tie these services to external systems, and the exam expects you to know which API pattern fits which integration scenario. Candidates who treat these as background knowledge rather than examinable mechanics tend to lose marks here.
β Objects, relationships, and reporting
The core objects and their relationships are the map you navigate during every scenario question in this topic. You need to know which objects are standard, which are custom to the Revenue Management data model, and how foreign-key relationships constrain what you can query or report on. Context-aware dashboards and KPIs add a reporting dimension: the exam presents a business requirement and expects you to choose the right native Salesforce reporting approach to surface the right metric. Native means no external BI tool. The trap is reaching for a complex Omnistudio solution when a standard report type or a joined report would do the job. Know what each native tool can and cannot do before you decide it is insufficient.
How Agentforce Revenue Management Platform Concepts is tested
At 18%, this topic generates more items than any other except Configure, Price, Quote. Expect scenario-driven questions that present a business or technical requirement and ask you to select the correct configuration approach. The demand is recognition: given a described outcome, which platform feature or combination of features produces it?
The most common trap is answer options that are plausible but wrong at one level of detail. A permission set assigned without the corresponding license will not work. A FlexCard is not interchangeable with an OmniScript. Context Service is not the same as a standard Apex query returning context data. Items reward candidates who know the boundaries between these tools, not just their names.
Reporting questions reward selecting the simplest native tool that meets the stated requirement. Candidates who over-engineer lose marks by choosing a custom Omnistudio component when a standard dashboard suffices. Read the business requirement carefully before committing to a solution tier.
A broad topic like this one is where a full question bank earns its place. Seeing items across all four sub-topic areas lets you spot exactly which layer is tripping you up, whether that is access control, service concepts, or reporting, so you can focus your remaining study time precisely.
The question below targets the kind of platform-concept scenario you will face, where the distinction between two similar-sounding features determines which option holds up.
In Salesforce Revenue Cloud, a consultant is setting up a new user who will primarily be responsible for managing customer assets.
What is a fundamental requirement to ensure this user can effectively view and manage customer assets?
Platform concepts tell you what the system can do. Implementation Readiness is about whether your organisation is actually in a position to do it. At 14%, this topic tests the consulting layer: licences, stakeholder alignment, scope definition, and the discipline of moving a project through build, test, deployment, and adoption without losing control. The questions here are less about technical configuration and more about making the right call when constraints are real. β Licences, toggles, and pre-conditions Before a single...
Platform concepts tell you what the system can do. Implementation Readiness is about whether your organisation is actually in a position to do it. At 14%, this topic tests the consulting layer: licences, stakeholder alignment, scope definition, and the discipline of moving a project through build, test, deployment, and adoption without losing control. The questions here are less about technical configuration and more about making the right call when constraints are real.
β Licences, toggles, and pre-conditions
Before a single object is configured, the environment has to be ready. That means the right licences are provisioned, the required feature toggles are enabled, and the permission sets that depend on those toggles are assigned in the correct order. The exam tests this as a prerequisite-sequencing problem: given a described gap (a feature that will not appear, a user who cannot access a function), identify what is missing and in what order it needs to be resolved. Candidates who memorise feature names without understanding their dependencies will pick options that address the symptom rather than the root cause. Know which toggles gate which features, and know that enabling a toggle in a sandbox does not automatically replicate to production.
β Roles, responsibilities, and project scope
Cross-product implementations involve multiple stakeholders with different accountabilities, and the exam tests whether you can assign those roles correctly. A project plan that misassigns ownership of a workstream is a failure mode the exam surfaces through scenario questions: who approves scope changes, who owns UAT sign-off, who is responsible for data migration decisions. Scope of work questions test your ability to distinguish what belongs inside the Revenue Management implementation from what belongs in an adjacent workstream. Candidates lose marks by either over-scoping (pulling in work that belongs to a different product team) or under-scoping (leaving out deliverables that are clearly part of the Revenue Management engagement). The project plan questions reward realistic sequencing over idealistic parallelism.
β Build, test, deployment, and adoption
The back half of the implementation lifecycle is where many consulting engagements fail, and the exam knows it. Build questions test whether you understand environment strategy: which configuration belongs in a sandbox tier, what gets migrated via change sets or metadata API, and what must be reconfigured manually in production. Test questions focus on who runs which test type and what a failed UAT should trigger. Deployment questions test go-live sequencing and rollback awareness. Adoption questions are the least technical but the most easily underestimated: the exam expects you to know what a post-go-live adoption plan includes and which stakeholder owns it. Items here reward practical, phased thinking over big-bang assumptions.
How Implementation Readiness is tested
At 14%, this topic delivers a meaningful share of the exam, and its items are consistently scenario-based. A typical item describes a project situation (a stakeholder conflict, a missing licence, a failed deployment step) and asks you to identify the best next action or the root cause.
The demand is consultant judgment, not product recall. Items reward candidates who can read a scenario, identify the constraint, and select the response that resolves it without creating a new problem. The trap is choosing the technically correct action that ignores the project context: recommending a full sandbox refresh when the scenario describes a go-live window two days out, for example, is technically defensible but practically wrong.
Stakeholder and scope questions reward precision about who owns what. Vague answers that spread accountability across multiple roles tend to be the distractor, not the strongest option. Read role descriptions in the scenario carefully before committing to an answer.
Working through timed practice questions on this topic is more useful than re-reading a project methodology guide. A question bank lets you check whether your consulting instincts hold up under time pressure, which is exactly the condition the real exam creates.
The question below presents the kind of implementation scenario where project context and licence sequencing both bear on which option is defensible.
What are the steps a user should take to Renew an Asset?
Once the implementation foundation is in place, the product catalog is where revenue logic begins. Catalog Management at 16% covers how products, bundles, and their attributes are structured in the system. The questions split between knowing what the out-of-the-box capability can do and applying that capability to a described business scenario. Candidates who treat this as pure theory without working through scenario applications tend to underperform here. How Catalog Management is tested With two sub-topics, this area tests a tight...
Once the implementation foundation is in place, the product catalog is where revenue logic begins. Catalog Management at 16% covers how products, bundles, and their attributes are structured in the system. The questions split between knowing what the out-of-the-box capability can do and applying that capability to a described business scenario. Candidates who treat this as pure theory without working through scenario applications tend to underperform here.
How Catalog Management is tested
With two sub-topics, this area tests a tight loop: understand the capability, then apply it. Concept questions reward knowing the data model behind the catalog: how products relate to product categories, how attributes attach to product specifications, and how catalog visibility rules control what a user sees in a given context.
Scenario questions present a business requirement (a product that behaves differently depending on the customer segment, a bundle that must enforce a specific component constraint) and ask which out-of-the-box feature satisfies it. The trap is reaching for a custom solution when a native catalog feature would do the job. Items reward candidates who know the boundaries of the standard tooling before they consider customisation.
At 16%, this topic carries enough weight to shift your overall result. Candidates lose marks by confusing catalog structure concepts with pricing concepts: the catalog defines what exists and how it is organised, not what it costs. Keep that boundary clear when reading scenario stems.
Catalog Management scenario questions follow a pattern that becomes readable with repetition. Covering this topic across a full question bank helps you recognise which out-of-the-box feature fits which scenario type, which is exactly what the exam rewards.
The question below tests whether you can match a specific business requirement to the right out-of-the-box Catalog Management feature.
Configure, Price, Quote shares the top weight at 18% and is the most operationally dense topic on the exam. This is where product configuration, pricing logic, and quote generation converge, and where Agentforce capability layers on top of the core CPQ workflow. Candidates who have implementation experience with CPQ tools but not with the Agentforce layer will find the questions push into territory their hands-on work has not covered. β Product configuration and validation The Product Configurator is the tool...
Configure, Price, Quote shares the top weight at 18% and is the most operationally dense topic on the exam. This is where product configuration, pricing logic, and quote generation converge, and where Agentforce capability layers on top of the core CPQ workflow. Candidates who have implementation experience with CPQ tools but not with the Agentforce layer will find the questions push into territory their hands-on work has not covered.
β Product configuration and validation
The Product Configurator is the tool through which components and attributes of a product are assembled and validated. The exam tests this at a scenario level: given a product with specific component rules (required components, excluded combinations, quantity constraints), which configurator settings produce the right outcome? Validation is the part candidates most often get wrong. The exam distinguishes between configuration validation (does this combination of components make a valid product?) and pricing validation (does this configuration meet the criteria for a particular price procedure?). Conflating the two leads to wrong option selections. Know which validation happens in the configurator and which happens downstream in the pricing layer.
β Pricing procedures and customer-specific logic
Pricing procedures are the mechanism by which the system moves from a configured product to a price. They are ordered, conditional, and customer-context-aware. The exam presents customer-specific business cases: a customer with a negotiated discount tier, a scenario where a volume threshold changes the applicable price book, or a case where a promotional adjustment must stack with a standard discount. Items reward knowing the sequence in which pricing procedures execute and the conditions that trigger each step. The trap is assuming that the most specific rule always wins: procedure order matters, and a later procedure can override an earlier one if it is not scoped correctly. Work through how precedence and exclusivity settings interact before exam day.
β Quote generation and Agentforce integration
Generating an accurate quote means the configuration is valid, the pricing procedure has run correctly, and the output document reflects both. The Agentforce dimension adds an AI-assisted layer to this workflow: Agentforce can participate in configuring or refining a quote based on customer context, and the exam tests whether you understand where that capability fits in the quote generation process and what it cannot do on its own. Items in this area reward candidates who understand the handoff points: where human review is still required, where Agentforce output feeds into a downstream step, and where a misconfigured context would produce a quote that looks correct but carries the wrong terms or pricing.
How Configure, Price, Quote is tested
At 18%, CPQ questions are scenario-heavy and often multi-step. A single item might describe a customer requirement, a product configuration constraint, and a pricing condition simultaneously, then ask which configuration approach satisfies all three. Items reward candidates who can hold multiple constraints in view at once rather than optimising for one.
The Agentforce angle is the newest and least practised area for most candidates. Items do not test Agentforce in isolation; they embed it in a CPQ workflow and test whether you understand what it changes about the process and what it leaves unchanged.
Pricing procedure questions are where most marks are dropped. Candidates who know what a pricing procedure is but cannot trace its execution sequence under a specific customer scenario will consistently pick the plausible-but-wrong option. The strongest answers in this area reflect an understanding of procedure order, condition evaluation, and output chaining.
CPQ is the topic where seeing a wide variety of scenario types before the exam pays off most. A full practice test covering this topic exposes you to the range of product configuration and pricing combinations the exam can present, reducing the chance of meeting an unfamiliar scenario structure on the day.
The question below sits at the intersection of pricing procedure logic and customer-specific requirements, the pairing that generates the most difficult CPQ items.
After a quote is accepted, the commercial relationship moves into contracts and orders. At 11%, this topic is narrower than CPQ but still tests scenario-based configuration judgment. Both Salesforce Contracts and Order Management have out-of-the-box capabilities that the exam expects you to match to described business requirements. The questions are less about knowing every field and more about knowing which configuration approach fits which business constraint. How Contracts and Orders is tested Both sub-topics follow the same exam pattern: a...
After a quote is accepted, the commercial relationship moves into contracts and orders. At 11%, this topic is narrower than CPQ but still tests scenario-based configuration judgment. Both Salesforce Contracts and Order Management have out-of-the-box capabilities that the exam expects you to match to described business requirements. The questions are less about knowing every field and more about knowing which configuration approach fits which business constraint.
How Contracts and Orders is tested
Both sub-topics follow the same exam pattern: a scenario describes a business requirement, and you select the configuration approach that satisfies it using standard platform capability. The demand is applied knowledge, not recall of feature names.
For Contracts, the exam tests amendment and renewal scenarios most frequently. Know how contract line items relate to the originating order, how amendments preserve or modify existing terms, and what triggers a renewal workflow. Candidates lose marks by selecting options that would technically work but require custom development when a native configuration path exists.
For Order Management, the exam tests order lifecycle scenarios: splitting, fulfilment routing, and status transitions. Know the conditions under which an order can be modified after activation and what constraints govern that process.
At 11%, this topic will not make or break your result on its own, but clean performance here protects the marks you earn elsewhere. The scenario stems for both sub-topics are usually short and specific, which means there is less room to reason your way to an answer from first principles. Direct knowledge of the configuration options is what items reward.
Because this topic tests specific configuration knowledge rather than broad consulting judgment, checking your weak spots with targeted practice questions is more efficient than re-reading documentation. The free demo of the practice test lets you sample the question style before committing.
The question below presents a contracts or orders scenario where the business requirement points to one specific configuration path over the alternatives.
Contracts and orders mark the point of sale. Asset Management picks up from there, covering what happens to a product after it has been purchased and provisioned. At 16%, this topic carries the same weight as Catalog Management and CPQ, and it follows the same two-part structure: know the capability, then apply it to a scenario. The lifecycle events that drive Asset Management (amendments, suspensions, renewals, terminations) are where most of the exam complexity lives. How Asset Management is tested...
Contracts and orders mark the point of sale. Asset Management picks up from there, covering what happens to a product after it has been purchased and provisioned. At 16%, this topic carries the same weight as Catalog Management and CPQ, and it follows the same two-part structure: know the capability, then apply it to a scenario. The lifecycle events that drive Asset Management (amendments, suspensions, renewals, terminations) are where most of the exam complexity lives.
How Asset Management is tested
Asset Management items follow the same scenario-to-configuration pattern as Catalog Management, but the business context is post-sale rather than pre-sale. A typical item describes a customer who wants to upgrade, downgrade, suspend, or terminate a service mid-term, and asks which Asset Management configuration supports that outcome.
The conceptual layer tests how assets relate to contracts and orders in the data model. Candidates who do not know which object drives an amendment versus a renewal will struggle to select the right configuration path in a scenario question.
The out-of-the-box functionality questions are where precision matters most. The exam distinguishes between what the standard Asset Management tooling handles natively and what requires additional configuration or an adjacent feature. Items reward candidates who know those boundaries. The trap is selecting a technically valid approach that bypasses native Asset Management functionality when the scenario explicitly describes a standard use case. At 16%, consistent performance across both sub-topics is what separates passing scores from borderline ones.
Asset Management covers a range of post-sale lifecycle scenarios, and the variety of ways the exam can present them is wider than most candidates expect. Working through a full set of practice questions across this topic gives you coverage you cannot get from reading the official documentation alone.
The question below describes a post-sale customer scenario and asks you to identify the Asset Management configuration that handles it correctly.
Invoice Management closes the revenue lifecycle by turning fulfilled orders and active assets into billable documents. At 7%, it is the lightest topic on the exam, but the items it generates are specific and unforgiving: there is not much room to reason from general principles when the question is about a billing schedule configuration or an invoice run condition. Candidates who skip this topic because of its weight tend to lose marks they could easily have kept. How Invoice Management...
Invoice Management closes the revenue lifecycle by turning fulfilled orders and active assets into billable documents. At 7%, it is the lightest topic on the exam, but the items it generates are specific and unforgiving: there is not much room to reason from general principles when the question is about a billing schedule configuration or an invoice run condition. Candidates who skip this topic because of its weight tend to lose marks they could easily have kept.
How Invoice Management is tested
The two sub-topics follow the same pattern as Catalog and Asset Management: core concepts first, then scenario application. At 7%, the item count is small, which means each question carries proportionally more weight within the topic than you might expect.
Concept questions test the Invoice Management data model: how invoice lines relate to order products and billing schedules, and what triggers an invoice run. Scenario questions present a billing requirement (a customer billed on a specific cycle, a proration scenario for a mid-term change) and ask which out-of-the-box configuration satisfies it.
The trap in this topic is underpreparation. Candidates who study Invoice Management lightly assume the questions will be straightforward. They are specific. The exam tests billing schedule configuration, invoice run conditions, and the relationship between asset amendments and invoice adjustments at a level of detail that rewards direct familiarity with the feature. Items reward candidates who know how the standard tooling handles edge cases, not just the default billing flow.
With a small item count, every Invoice Management question matters. Checking your readiness on this topic through the practice test before exam day takes less time than you think, and the PDF format lets you review it anywhere without needing to be at a desk.
The question below targets a specific Invoice Management scenario where knowledge of billing configuration details, rather than general intuition, determines which option holds up.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Rev-Con-201 Exam Questions π