Salesforce Certified Industries CPQ Developer (Ind-Dev-201) Exam Topics and Questions
These Salesforce Certified Industries CPQ Developer (Ind-Dev-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 Salesforce Certified Industries CPQ Developer (Ind-Dev-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 Industries CPQ Developer certification exam.
Let's Practice Free Salesforce Certified Industries CPQ Developer (Ind-Dev-201) Questions Aligned with Official Exam Topics
Products carry the highest share of the exam, so this is where a weak foundation hurts most. The domain covers the mechanics of how offerings are modelled in Industries CPQ: bundles, hierarchies, and the attributes that make products configurable. Every other topic, from pricing to rules, sits on top of what you set up here, so errors in product configuration ripple outward in ways that are easy to miss until something downstream breaks. β Bundles and the product model Product...
Products carry the highest share of the exam, so this is where a weak foundation hurts most. The domain covers the mechanics of how offerings are modelled in Industries CPQ: bundles, hierarchies, and the attributes that make products configurable. Every other topic, from pricing to rules, sits on top of what you set up here, so errors in product configuration ripple outward in ways that are easy to miss until something downstream breaks.
β Bundles and the product model
Product bundles in Industries CPQ are not simply grouped line items. A bundle defines parent-child relationships between components, and the way you structure those relationships determines what a sales rep can select, swap, or remove at quote time. You need to know which component types are available, how cardinality and optionality are set, and what happens when a child product is itself a bundle. The exam tests whether you can read a business requirement and decide which bundle structure satisfies it, so focus on the decision logic rather than the click path. Misconfiguring the root product or its allowed component types is a common source of runtime errors, and the exam reflects that.
β Object type hierarchies
Object type hierarchies control how the product catalog is organized and how products inherit properties from parent types. Understanding the inheritance chain matters because a setting at a higher level of the hierarchy can override or be overridden by one at a lower level, and the exam will probe exactly those conflict scenarios. Pay attention to which fields and behaviors are inherited versus explicitly set on a child type. Candidates who treat object types as a simple taxonomy without understanding the inheritance implications tend to lose marks on scenario questions where the wrong level of the hierarchy was configured.
β Attributes and configuration implications
Attributes are the mechanism that makes a product configurable: they capture customer-facing choices such as speed, term, or color and feed those choices into pricing and rules. You need to understand attribute types, how they are scoped to a product or a product family, and how attribute values interact with attribute-based pricing later in the quote lifecycle. The implication side of this sub-topic is equally examinable: if you configure an attribute in a particular way, what downstream behavior does that trigger? The exam expects you to trace a configuration decision to its consequence, not just recall that attributes exist.
How Products: is tested
At 20% of the exam, Products generates more items than any other topic. Most of them are scenario-based: you are given a business requirement or a partially built configuration and asked to identify what is missing, what is wrong, or which approach satisfies the requirement. The items rarely test recall of field names in isolation. Instead, they reward the ability to reason about how bundle structure, hierarchy inheritance, and attribute scope interact. Candidates lose marks in two main places. First, they conflate bundle component types and select an option that looks structurally plausible but violates a cardinality or optionality rule. Second, they miss the downstream implication of an attribute configuration, choosing an answer that solves the immediate setup problem without accounting for how that attribute will behave in pricing or rules. Working through a high volume of scenario items before the exam is the most effective way to train that implication-tracing skill.
The ITExamsTopics practice test covers all seven topics, including a substantial bank of Products items. Running through enough of them lets you spot exactly where your bundle and hierarchy reasoning breaks down, which is more efficient than re-reading documentation when exam day is close.
The question below targets one of the core product configuration decisions this topic demands. Work through it before reading on.
In Vlocity CME. if you want to regenerate the JSON attribute fields forall products in your product catalog, what job should you run?
Note: This question displayed answer options in random order when taking this Test.
Promotions and Discounts sit at the lighter end of the exam by weight, but the topic catches candidates who assume it is simply about applying a percentage off. The real exam pressure comes from knowing when a promotion is the right tool versus a discount, and from understanding how formula fields and roll-up summary fields extend both mechanisms. A wrong choice here in a real implementation would cascade into incorrect pricing, and the exam tests exactly that decision-making. β Promotions...
Promotions and Discounts sit at the lighter end of the exam by weight, but the topic catches candidates who assume it is simply about applying a percentage off. The real exam pressure comes from knowing when a promotion is the right tool versus a discount, and from understanding how formula fields and roll-up summary fields extend both mechanisms. A wrong choice here in a real implementation would cascade into incorrect pricing, and the exam tests exactly that decision-making.
β Promotions and discounts: configuration and selection
Promotions in Industries CPQ are time-bound or condition-driven incentives applied at the cart or product level. Discounts are adjustments to unit or total price and can be manual, automated, or tiered. The exam expects you to know how each is configured and, more importantly, when one is preferable to the other. A scenario might describe a marketing campaign that applies only when a customer adds a specific bundle during a date range: knowing whether that is a promotion, a discount, or a combination of both is the testable skill. Candidates who memorize the setup steps without internalizing the selection criteria tend to pick the structurally valid option that does not match the business requirement.
β Formula fields, roll-up summaries, and their limits
Formula fields and roll-up summary fields extend what promotions and discounts can calculate without custom Apex. A formula field on a quote line can derive a conditional discount based on attribute values; a roll-up summary can aggregate child line totals to drive a parent-level promotion threshold. The exam tests capability and use-case fit: you need to know what each field type can and cannot do in the context of CPQ pricing, and where their limits require a different approach. A common trap is selecting a roll-up summary in a scenario where the relationship type does not support it, or using a formula field where a pricing procedure step would be more appropriate.
How Promotions and Discounts: is tested
Items in this topic tend to be shorter scenarios focused on selection decisions: given these business conditions, which mechanism applies? The weight is modest, but the items are not forgiving, because each one usually has two plausible options that differ only in whether you correctly understand the boundary between promotions and discounts, or between formula fields and other pricing tools. Candidates lose marks by over-applying promotions where a simple discount rule would suffice, or by reaching for a formula field in a context where the field type's limitations make it the wrong choice. The testing section also covers the interplay between these mechanisms and the broader pricing model, so treat this topic as connected to Pricing rather than isolated. Items reward precise knowledge of when each tool is appropriate, not general familiarity with the fact that both exist.
Because this topic is narrow, a targeted session with the ITExamsTopics practice test, filtered to Promotions and Discounts items, tells you quickly whether your selection logic is solid or whether you are guessing between promotion and discount scenarios.
The question below presents a scenario that turns on exactly the kind of selection decision this topic tests. Try it before moving on.
A developer has updated the price of a product but still sees the previous price in the Digital Commerce API response.
What job should the developer run to correct this issue?
Pricing is the second-largest topic and the one where configuration complexity compounds fastest. Where Products defines what can be sold, Pricing defines what it costs and how that cost responds to customer choices, volume, and margin targets. Candidates who treated Products as a standalone topic without connecting attribute configuration to attribute-based pricing will feel that gap here. The domain spans multiple pricing mechanisms, each with distinct triggers and precedence rules. β Foundational pricing and attribute-based pricing Building pricing in Industries...
Pricing is the second-largest topic and the one where configuration complexity compounds fastest. Where Products defines what can be sold, Pricing defines what it costs and how that cost responds to customer choices, volume, and margin targets. Candidates who treated Products as a standalone topic without connecting attribute configuration to attribute-based pricing will feel that gap here. The domain spans multiple pricing mechanisms, each with distinct triggers and precedence rules.
β Foundational pricing and attribute-based pricing
Building pricing in Industries CPQ starts with understanding the pricing model: how list prices are established, how price lists apply to products, and how the sequence of pricing steps is executed. Attribute-based pricing extends this by tying price adjustments to the attribute values a customer selects at configure time. The exam tests whether you can trace a price from its list origin through any attribute-driven adjustments to its final value on the quote line. The non-obvious part is precedence: when multiple pricing rules or attribute conditions could apply simultaneously, which one wins? Candidates who cannot answer that question will consistently pick the wrong option in scenario items that describe a multi-attribute product with overlapping price conditions.
β Pricing adjustments and mechanism selection
Adjustments include manual overrides, automated adjustments from rules, tiered pricing, and negotiated pricing. Each has a different trigger and a different position in the pricing sequence. The exam asks you to determine which type of pricing to use given a specific business scenario, which means you need to know not just what each type does but where in the execution order it takes effect. Selecting a manual override in a scenario that requires automated enforcement, or applying a tier where the requirement is actually a fixed negotiated rate, are the kinds of mismatches the items are designed to surface.
β Cost and margin
Cost and margin configuration gives sales teams visibility into profitability at the line and quote level. The exam covers how cost is attached to a product, how margin is derived, and how both are exposed in the quoting interface. This sub-topic is narrower than the others, but it connects to the broader pricing model because cost inputs can influence automated pricing decisions. Know how cost fields flow through to margin calculations and what happens when cost data is absent or overridden. Items here reward understanding the data flow, not just the field labels.
How Pricing: is tested
At 17% of the exam, Pricing generates a significant number of items, most of them scenario-driven. The dominant item type presents a product configuration or a customer scenario and asks which pricing mechanism applies, how a price is calculated, or why a price is not behaving as expected. Items reward knowing the execution sequence: a candidate who understands that attribute-based adjustments are applied at a different stage than manual overrides will eliminate wrong options that are individually plausible but violate the sequence. Candidates lose marks most often on attribute-based pricing, either by misidentifying which attribute condition triggers a given adjustment or by ignoring the precedence rules when conditions overlap. The cost and margin sub-topic tends to produce items that reward tracing a value through the data model rather than recalling a configuration setting. Connecting this topic to both Products and Troubleshooting during your preparation, rather than studying it in isolation, will serve you better than a narrow focus on pricing mechanics alone.
Timed practice under realistic conditions is particularly valuable for Pricing, where scenario items can be long. The ITExamsTopics practice test lets you work through pricing scenarios at exam pace, so you build the habit of reading the execution-sequence clues before choosing.
The question below focuses on a pricing mechanism decision of the kind this topic regularly produces. Work through your reasoning before checking.
Rules govern what can happen during product configuration: they enforce constraints, automate selections, and guide the user through valid combinations. After working through Products and Pricing, you already know the objects rules act on. The pressure in this topic is knowing which rule type fits a given enforcement need and understanding the execution model well enough to predict what a rule will do when it fires, not just that it will fire. β Context rules and advanced rules Context rules...
Rules govern what can happen during product configuration: they enforce constraints, automate selections, and guide the user through valid combinations. After working through Products and Pricing, you already know the objects rules act on. The pressure in this topic is knowing which rule type fits a given enforcement need and understanding the execution model well enough to predict what a rule will do when it fires, not just that it will fire.
β Context rules and advanced rules
Context rules operate on the current state of the configuration: they evaluate conditions based on what is selected and respond by hiding, showing, requiring, or excluding products and attributes. Advanced rules extend that capability with more complex condition logic and can trigger actions that context rules cannot. The exam tests the boundary between them. A scenario will describe a requirement, and you need to decide whether a context rule is sufficient or whether the complexity of the condition or the action demands an advanced rule. Candidates who treat all rules as interchangeable lose marks on these selection questions, because the items are built around scenarios where only one type produces the described behavior.
β Product configuration procedures and rule selection
Product configuration procedures define a sequence of automated steps that execute during configuration, distinct from event-driven rules. They are appropriate when the logic needs to run in a predictable order rather than in response to a user action. The exam expects you to know when a procedure is the right choice over a rule, and to understand how procedures interact with other rule types in the same configuration. The selection question, which type of rule to use and when, runs through all four sub-topics. Frame your preparation around that decision: for any given business requirement, can you identify the rule type, explain why, and predict the outcome? That is what the items are testing.
How Rules: is tested
Rules items at 12% of the exam are almost entirely scenario-based and selection-oriented. You are given a configuration requirement and asked which rule type satisfies it, or you are given a rule configuration and asked what it will do. The items reward understanding the execution model: when does a rule fire, what conditions does it evaluate, and what action does it trigger? Candidates lose marks in two ways. First, they select a rule type that is conceptually related to the requirement but executes at the wrong time or cannot perform the required action. Second, they misread the interaction between a rule and a product configuration procedure, choosing an answer that would work in isolation but conflicts with another element already in place. Context versus advanced rule boundary questions are particularly common, so make sure you can articulate the difference in terms of what each can and cannot do, not just in terms of complexity.
The ITExamsTopics practice test includes Rules items drawn from across all four sub-topics. Reviewing your misses by sub-topic shows whether your gap is in rule-type selection, execution-model understanding, or the procedure versus rule boundary.
The question below presents a configuration requirement and asks you to apply exactly the kind of rule-selection logic this topic demands.
APIs shift the exam into developer territory. Where the previous topics covered declarative configuration, this one tests whether you understand the programmatic interfaces that power cart operations and digital commerce experiences. At 12%, it carries real weight, and it is the topic most likely to separate developers who have worked with the APIs directly from those who have only read about them. The decision logic between API families is the central examinable skill. β Cart-based APIs: selection and usage The...
APIs shift the exam into developer territory. Where the previous topics covered declarative configuration, this one tests whether you understand the programmatic interfaces that power cart operations and digital commerce experiences. At 12%, it carries real weight, and it is the topic most likely to separate developers who have worked with the APIs directly from those who have only read about them. The decision logic between API families is the central examinable skill.
β Cart-based APIs: selection and usage
The cart-based APIs handle the core quoting and ordering operations: adding products, configuring bundles, applying pricing, and submitting a cart. The exam tests both when to use these APIs and how to use them correctly. For the when question, you need to understand the use cases that make cart-based APIs the appropriate choice over digital commerce APIs. For the how question, you need to know the specific methods available, the parameters each method accepts, and how responses are structured. Confusing parameter names or passing values in the wrong structure are the kinds of errors the items are designed to catch, so precision matters more than general familiarity.
β Digital commerce APIs and sales catalogs
Digital commerce APIs support customer-facing or partner-facing storefront experiences where the interaction pattern differs from a rep-assisted cart. The exam tests the same two dimensions as the cart-based APIs: when this family is appropriate, and how its methods, parameters, and responses differ from the cart-based equivalents. Sales catalog configuration sits alongside the API topics because the catalog structure determines what the APIs can surface. You need to understand how a sales catalog is built, how it relates to the product hierarchy, and how that structure affects what an API call returns. Candidates who know the API methods but have not connected them to catalog configuration will miss items that test that relationship.
How APIs: is tested
API items require a different kind of recall than the declarative topics. Items reward knowing specific method names, the parameters those methods require, and the shape of the responses they return. Scenario items present an integration requirement and ask which API family or which specific method applies. The selection question between cart-based and digital commerce APIs is a reliable item type: the items are written so that both families look plausible, and only the use-case context distinguishes them. Candidates lose marks by relying on general knowledge of REST conventions rather than the specific behaviors of these APIs, and by missing the connection between sales catalog configuration and what the API can return. The troubleshooting topic later in the exam also covers API parameters and responses, so any gaps you have here will cost you twice. Treat the method-parameter-response triad as the atomic unit of study for this topic, not the API family as a whole.
Seeing the item style for API questions before exam day matters, because the precision required is different from scenario topics. The ITExamsTopics practice test lets you experience that style on a free demo before committing, so you know what to expect.
The question below targets the API selection decision at the center of this topic. Read the scenario carefully before answering.
Ordering and Quoting covers the end-to-end user and system experience of taking a configured product from cart to order. After the API topic, which focused on the programmatic layer, this topic brings the business and UX context back into focus. The four sub-topics span what the rep sees in the cart, how multi-site deals are structured, the foundational ordering and quoting setup, and the specialized world of asset-based ordering. β Cart experience and multi-site quoting The cart user experience in...
Ordering and Quoting covers the end-to-end user and system experience of taking a configured product from cart to order. After the API topic, which focused on the programmatic layer, this topic brings the business and UX context back into focus. The four sub-topics span what the rep sees in the cart, how multi-site deals are structured, the foundational ordering and quoting setup, and the specialized world of asset-based ordering.
β Cart experience and multi-site quoting
The cart user experience in Industries CPQ is not just a display concern. How the cart is configured affects which products are visible, how bundles are presented, and what actions are available to the rep or customer. The exam tests whether you understand the configuration decisions that drive that experience, not the visual design itself. Multi-site quoting applies when a single quote spans multiple service locations or accounts. You need to know how sites are configured, how product and pricing assignments work across sites, and how a multi-site quote differs structurally from a standard one. Items in this area tend to present a quoting scenario and ask which configuration supports it.
β Basic ordering and quoting configuration and asset-based ordering
Basic ordering and quoting configuration covers the foundational objects and settings that make a quote flow from creation to order submission. The exam expects familiarity with the key configuration steps and the sequence they must follow. Asset-based ordering (ABO) is the more distinctive sub-topic: it applies when a customer already has active assets and wants to change, suspend, or cancel them. ABO introduces its own object model and action types, and the exam tests whether you can identify when ABO applies and what it does differently from a standard new-order flow. Candidates who understand the standard quoting flow but have not studied the ABO lifecycle will miss items that hinge on that distinction.
How Ordering and Quoting: is tested
Items in this topic span both conceptual and applied knowledge. Cart experience questions reward understanding the link between configuration settings and what appears in the UI, without requiring you to recall pixel-level details. Multi-site quoting items tend to be scenario-based, presenting a deal structure and asking which configuration supports it. Basic configuration items reward knowing the sequence and the key objects involved. Asset-based ordering is the area where candidates most often lose marks, because it requires a separate mental model from standard quoting. Items that involve ABO are written to distinguish candidates who know the ABO action types and lifecycle from those who apply standard ordering logic to an ABO scenario. The interplay between this topic and the APIs topic is also examinable: a scenario might describe an ordering requirement and ask whether it calls for an ABO action, an API call, or a configuration change.
Coverage across all sub-topics is the practical value of a full question bank here. The ITExamsTopics practice test ensures you encounter ABO scenarios, multi-site items, and cart configuration questions, not just the foundational ordering content that is easier to find in documentation.
The question below draws on one of the four sub-topics in this area. Identify which concept it is testing before you select your answer.
Troubleshooting shares the top weight with Products at 20%, which tells you this exam is not satisfied with candidates who can configure things correctly in ideal conditions. It tests whether you can diagnose what went wrong when a product, a pricing rule, a promotion, or an API call does not behave as expected. Every topic you have covered so far feeds into this one: a troubleshooting scenario can draw on bundle structure, attribute-based pricing, rule execution order, or API parameter...
Troubleshooting shares the top weight with Products at 20%, which tells you this exam is not satisfied with candidates who can configure things correctly in ideal conditions. It tests whether you can diagnose what went wrong when a product, a pricing rule, a promotion, or an API call does not behave as expected. Every topic you have covered so far feeds into this one: a troubleshooting scenario can draw on bundle structure, attribute-based pricing, rule execution order, or API parameter errors.
How Troubleshooting: is tested
Items here present a symptom: a price that does not match expectations, a rule that does not fire, a promotion that does not apply, an API response that returns unexpected data. Your job is to identify the cause. The items reward the ability to work backward from the observed behavior to the configuration or code decision that produced it. Candidates lose marks by treating troubleshooting as a recall exercise, trying to match the symptom to a memorized list of error types, rather than reasoning through the execution model. API troubleshooting items require the same parameter and response precision as the APIs topic, but applied to a broken scenario rather than a design one. Product and pricing troubleshooting items often hinge on execution order: the symptom is correct in isolation but wrong in context because something earlier in the sequence set a value that a later step did not override as expected. Prepare for this topic by practicing the skill of tracing a value or a behavior through the full configuration chain, not by studying error messages in isolation.
Troubleshooting is the topic where checking a weak area under timed conditions beats re-reading documentation. The ITExamsTopics practice test puts you in the diagnostic seat repeatedly, so the reasoning pattern becomes automatic before exam day.
The question below presents a broken scenario drawn from one of the two troubleshooting domains. Trace the cause before selecting your answer.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full Salesforce Certified Industries CPQ Developer (Ind-Dev-201) Exam Questions π