• Home
• Salesforce Exams
• Certified Industries CPQ Developer

Certified Industries CPQ Developer Salesforce Practice Test Questions and Exam Dumps

Question 1

A developer has changed the price of a product, but the Digital Commerce API response is still showing the old price. What job should the developer execute to fix this inconsistency?

A. Regenerate Cached API Records job
B. Delete Expired API Cache job
C. Migrate Cache Records job
D. Populate API Cache job

Answer: A

Explanation:
When a developer modifies product-related data, such as pricing, the system may not automatically reflect this in the API response due to cached data. The Digital Commerce API often relies on a cache layer to speed up responses. If the cache hasn’t been refreshed after a price change, users may continue to see the outdated values.

In this case, the most effective way to resolve the discrepancy is to run the Regenerate Cached API Records job. This job rebuilds the API cache using the current product data stored in the backend. It ensures that the latest updates—including new pricing—are incorporated into the cache and thus reflected in the API output.

The Delete Expired API Cache job only removes data that has passed its expiration time. If the outdated price is still within its valid cache period, it won't be cleared by this job, so it won’t help in this case.

The Migrate Cache Records job is typically used during system upgrades or structural changes in the caching mechanism, not for syncing updated product data.

The Populate API Cache job is usually used to preload cache entries, often during initial system setups or after mass updates. However, it doesn’t necessarily replace or update existing cache entries unless they are missing, which is not the issue here.

Therefore, running the Regenerate Cached API Records job is the correct approach to ensure that the cache reflects the newly updated price. This action will directly solve the issue of stale data in the API response.

Question 2

How can a user understand changes to pricing applied in the cart?

A. By clicking the Price Details icon on the line item
B. The display text in the Products list in the cart
C. Pricing adjustments do not display in the cart
D. Popup message window after the order is submitted

Correct answer: A

Explanation:
When users interact with a cart in a Salesforce B2B or B2C Commerce environment (such as Salesforce CPQ or an eCommerce platform), understanding how pricing is calculated is critical for transparency and accuracy in the sales process. This includes being able to view discounts, promotions, taxes, and other pricing-related adjustments in real time.

Option A: By clicking the Price Details icon on the line item
This is the correct and most direct answer. In systems like Salesforce CPQ or Commerce Cloud, users can typically view a Price Details or Price Breakdown icon next to each line item in the cart. Clicking this icon reveals detailed information about the pricing of that item, including:

• List price

• Discounts (manual, automatic, promotional)

• Net price

• Tax or shipping costs (if applicable)

This interaction provides users with a clear audit trail of all price-related changes, empowering them to understand and verify the final price of each item.

Option B: The display text in the Products list in the cart
While some pricing details might appear in the cart summary or product list, this view is generally high-level. It usually shows only the final net price or a summary (e.g., "$100 - 10% discount = $90"), but not a detailed breakdown. Therefore, this option doesn’t fully support the requirement to understand the changes to pricing, especially if multiple pricing rules are involved.

Option C: Pricing adjustments do not display in the cart
This is incorrect. Most modern commerce platforms—especially Salesforce-based solutions—are designed to show real-time pricing updates within the cart. Hiding price adjustments would cause confusion, prevent user trust, and lead to higher cart abandonment rates. Transparency is a core part of user experience design.

Option D: Popup message window after the order is submitted
This is not an ideal or accurate solution. Users need to understand the pricing before they complete the order so they can make informed decisions. Displaying pricing changes after submission is both untimely and ineffective in addressing the question.

In conclusion, the most effective way for users to understand pricing changes applied in the cart is by clicking the Price Details icon on the line item, which shows a full breakdown of how the final price was determined. This level of granularity is essential for trust, compliance, and transparency—especially in B2B sales environments where multiple pricing rules and discounts may apply. Therefore, the correct answer is A.

Question 3

When a developer is using the getCartsProducts method, in which three ways can they narrow down or filter the product list?

A. Using a product category
B. Using a value that will be matched exactly to a value in a Product2 field
C. Using a value that is contained within a product attribute
D. Using a context rule that qualifies a set of products
E . Using a value that is contained within a Product2 field

Answer: A, B, E

Explanation:
The getCartsProducts method is part of the Salesforce Industries (formerly Vlocity) Digital Commerce API, and it is used to retrieve a list of products that are relevant to a particular cart or user session. Developers often need to filter the product list returned by this method to show only relevant options to the end user, which can be done through specific query parameters and rules.

Option A, using a product category, is a valid way to filter product results. Product categories are a built-in method of organizing and grouping products. When a category filter is applied, only products associated with that category will be returned by the API. This is particularly useful in user-facing scenarios where products need to be organized by department or type.

Option B refers to using a value that matches exactly to a field on the Product2 object. This method involves specifying a particular value, such as a product code, status, or name, and the API will return only those products where the Product2 field exactly matches that value. This type of filtering is precise and can help target specific products quickly.

Option E is also valid. It refers to partial matches within a Product2 field. For instance, if a developer is searching for products with names containing a certain substring, the API can return all relevant products using "contains" or "like" style queries. This approach gives more flexibility than exact match filtering, allowing for broader searches.

Option C, using values contained within a product attribute, is not a supported filter for getCartsProducts directly. Product attributes are typically used for configuration after a product is selected, not for filtering product lists at the cart level.

Option D, using context rules to qualify products, relates to how products are conditionally displayed or enabled based on user or session context, such as location or eligibility. However, context rules are not direct filters that a developer applies manually in the getCartsProducts method; they are system-enforced logic that applies separately. So while context rules influence what products appear, they are not explicitly passed by the developer as filter parameters.

Hence, the correct filtering methods directly usable by the developer with the getCartsProducts method are category filtering, exact value matching on Product2 fields, and substring searches within Product2 fields.

Question 4

What is a context mapping?

A. The relational path from a root sObject, such as an Order, to related sObjects, such as Account
B. A multi-dimensional array of sObject data
C. A link to data stored in sObjects, calculated using a function, or typed in during design-time
D. A variable that stores rule condition values

Correct answer: C

Explanation:
In Salesforce Industries (formerly Vlocity), context mapping is a critical concept used to define how data is accessed and utilized within the system, particularly in the context of OmniStudio tools like DataRaptor, Integration Procedures, and OmniScripts. It allows designers to bind data from various sources to components, logic, or calculations.

Option A: The relational path from a root sObject, such as an Order, to related sObjects, such as Account
This describes a data relationship or object hierarchy, which is commonly used in Salesforce when querying related records via relationships like Order.Account.Name. However, this is not what is meant by "context mapping" in the Salesforce Industries context. While the mapping might involve such a path, the definition is more specific.

Option B: A multi-dimensional array of sObject data
This describes a data structure, not a context mapping. While Salesforce Industries tools like DataRaptors can work with JSON arrays or multi-level structures, this answer does not define what context mapping is. It is too broad and technically unrelated to the specific concept being tested.

Option C: A link to data stored in sObjects, calculated using a function, or typed in during design-time
This is the correct definition. Context mapping in Salesforce Industries refers to the way data is bound to components or used in expressions. It can be:

• A direct link to an sObject field (e.g., Account.Name)

• A calculated value derived from functions or expressions (e.g., concat(FirstName, ' ', LastName))

• A static value entered during design time (e.g., entering "USA" into a field)

This mapping is what enables dynamic behavior in OmniScripts or reusable components. It ensures that the data rendered or processed is aligned with the correct business context at runtime.

Option D: A variable that stores rule condition values
This refers more to a variable in decision tables or formula logic, not context mapping. While such variables are used in rule evaluation or logic branching, they are distinct from the concept of mapping data sources to components.

In summary, context mapping defines how and where a component or tool accesses its input data—whether it's pulling from a Salesforce record, calculating a value on the fly, or referencing a static entry. This flexibility allows for efficient and scalable configuration of user interfaces and processes in Salesforce Industries. The correct answer is C.

Question 5

A developer observes that the Digital Commerce APIs are returning either incorrect data or no data at all. Which cache should the developer refresh to address this issue?

A. CachedAPIResponse cache
B. CPQPartition cache
C. VlocityAPIResponse cache
D. VlocityMetadata cache

Answer: C

Explanation:
In the Salesforce Industries (formerly Vlocity) Digital Commerce framework, performance and efficiency are heavily supported by a robust caching mechanism. The system caches API responses and metadata to avoid frequent recalculations and database hits. However, if the cache becomes outdated or inconsistent, it can lead to scenarios where the APIs return stale, incorrect, or even empty results.

In this question, the Digital Commerce APIs are either returning incorrect data or none at all. This behavior typically indicates a cache problem, where the cached responses are no longer aligned with the current data in the system.

The VlocityAPIResponse cache is specifically designed to store the results of Digital Commerce API calls. When a developer or the system makes a request, such as for products, promotions, or pricing, the platform first checks this cache. If the cache contains outdated or invalid entries, then the API will respond with incorrect data. Similarly, if a record expected to be returned by the API isn't cached correctly, it might result in an empty response.

Option A, CachedAPIResponse cache, is not a recognized or commonly used term within the Salesforce Industries documentation and might be a distractor in this context.

Option B, CPQPartition cache, deals with partitioning configurations used by the CPQ engine and is not directly tied to the Digital Commerce APIs' output. It may be related to product rules or pricing partitioning but doesn't control the actual API response cache.

Option D, VlocityMetadata cache, pertains to the cached metadata used across the platform for configuration and performance optimization. While it affects the general performance and metadata loading, it is not responsible for the actual output of the API responses.

Therefore, to address problems where the API responses are incorrect or missing, the VlocityAPIResponse cache should be cleared or refreshed. This ensures that the Digital Commerce APIs pull fresh data from the database and rebuild the cached responses correctly. Refreshing this cache resolves data mismatches and guarantees that any backend updates to product, pricing, or availability are reflected in the API outputs as expected.

Question 6

What can a developer use to make sure a subscription ends at the end of the subscription plan?

A. A time plan
B. A time policy
C. An Effective Until date
D. An Effective From date

Correct answer: C

Explanation:
In Salesforce Industries (formerly Vlocity), managing the lifecycle of a subscription or any time-bound service is crucial, especially for products like telecommunications plans, insurance policies, or recurring services. To control the duration of a subscription, developers must define when the subscription starts and ends. This is where the concept of effective dating comes into play.

Option A: A time plan
A time plan is typically used to structure billing and pricing over a given period. It helps define how charges are applied throughout the life of a product or service but does not itself control when the subscription begins or ends. It focuses more on rate changes or pricing intervals rather than the overall duration of the subscription.

Option B: A time policy
Time policies may govern when a plan or service is valid or how time-based behaviors operate, but in Salesforce Industries, this is not the primary method used to define the termination of a subscription. While it might influence behavior, it’s not the key mechanism used to enforce the end of a subscription.

Option C: An Effective Until date
This is the correct answer. The Effective Until date defines the specific end date of a subscription, meaning the product or service will no longer be active beyond this date. It allows developers and administrators to ensure that the subscription is automatically terminated at the correct time without requiring manual intervention.

For instance, if a one-year subscription starts on January 1, 2025, the Effective From date would be 2025-01-01, and the Effective Until date would be 2025-12-31. After this date, the subscription is considered expired and cannot be used for further billing or provisioning.

Using Effective Until also supports automation and consistency across different systems like CPQ, billing, and service provisioning. This becomes especially useful when subscriptions are auto-renewed or require specific renewal workflows.

Option D: An Effective From date
This field defines when the subscription begins. It ensures the service or product is not considered active before a certain date but does not specify when it ends. To manage both the start and end dates of a subscription, developers use Effective From in combination with Effective Until, but only the Effective Until date enforces the subscription's termination.

In conclusion, while multiple fields and tools help manage subscription timing in Salesforce Industries, the field that directly determines the end of the subscription plan is the Effective Until date. The correct answer is C.

Question 7

A company operates with two telesales teams: one handles business in Russian and the other in English. After enabling the multi-language feature in the shared catalog, a developer finds that Russian translations are not appearing in the Cart during testing. 

What three areas should the developer check to resolve this issue?

A. Russian translations for the products exist in the StringTranslation object
B. User's Language is set to Russian
C. The Russian Locale is activated in the Vlocity Locale Code picklist
D. User's Locale is set to Russian
E. Russian translations for the products exist in the Translation Workbench

Answer: A, B, C

Explanation:
Salesforce Industries (formerly Vlocity) supports multi-language experiences through a combination of platform-level translations and custom translation mechanisms, such as using the StringTranslation object for catalog-related text. When multilingual support is enabled in a shared product catalog, the platform uses specific logic to display the correct language content based on user settings and available translations.

The issue described involves Russian translations not appearing in the Cart, which suggests that either the translations are missing or the system is not correctly configured to display them.

Option A is correct because the StringTranslation object is where Vlocity stores product and attribute translations for multilingual catalogs. If translations for product names, descriptions, or attribute values in Russian do not exist in this object, they will not display in Russian—even if other settings are correct.

Option B is valid since the user’s Language setting determines which language is used to display UI elements and translated text. If this setting is not correctly set to Russian, the platform may default to English or another fallback language. This can directly affect what the user sees in the Cart.

Option C is also correct. The Vlocity Locale Code picklist must include and have Russian activated for it to be a recognized and supported language within the product catalog and CPQ runtime. Without enabling this locale, even if translations exist and the user has the correct language settings, the system will not serve the Russian content.

Option D, which refers to the user’s Locale, is often misunderstood. In Salesforce, Locale primarily controls region-specific settings such as date and number formats, not necessarily the language of the UI or product catalog. So while it’s relevant for formatting, it does not impact whether Russian translations are displayed in the cart, making this option incorrect for this context.

Option E involves the Translation Workbench, which is used for Salesforce standard UI labels and custom label translations. However, the Translation Workbench does not affect the translation of product catalog entries, which are managed separately using StringTranslation in Vlocity. Therefore, even if Russian translations exist in the Workbench, it will not influence catalog product translations in the cart.

To summarize, the developer should verify that the Russian translations exist in the correct data store (StringTranslation), that the user’s Language is set to Russian, and that the Russian locale is active in the Vlocity Locale Code configuration. These three checks ensure that the system is properly set up to show Russian content in the Digital Commerce experience.

Question 8

A product manager wants to create a product bundle that can only be ordered between January 5th and January 31st. How should the developer configure the product bundle to meet this requirement?

A. Enable the Active property on January 5 and disable the Active property on January 31
B. Set the Fulfillment Start Date to January 4, Selling Start Date to January 5, and the End of Life Date to February 1
C. Set the Selling Start Date to January 5 and the Selling End Date to January 31
D. Set the Fulfillment Start Date to January 5 and the End of Life Date to January 31

Correct answer: C

Explanation:
In Salesforce Industries (Vlocity), product availability for ordering is controlled using specific date fields that determine when a product can be sold and when it can be fulfilled. To restrict ordering of a product to a specific time window, the relevant fields are Selling Start Date and Selling End Date.

Option A: Enable the Active property on January 5 and disable the Active property on January 31
While enabling or disabling the Active property affects the product’s availability in general, it is a manual process and not precise. This approach requires manual intervention or scheduled automation to enable and disable the product, which is error-prone and inefficient for clearly defined time-based rules. Additionally, it doesn't provide a programmatic or automated enforcement of ordering windows as Selling Start and End Dates do.

Option B: Set the Fulfillment Start Date to January 4, Selling Start Date to January 5, and the End of Life Date to February 1
This configuration could work for controlling both fulfillment and product lifecycle, but it does not restrict ordering strictly between January 5 and January 31. The End of Life Date controls when the product should be considered obsolete but does not directly prevent orders. Furthermore, Fulfillment Start Date deals with when delivery or provisioning can begin, not when orders can be placed.

Option C: Set the Selling Start Date to January 5 and the Selling End Date to January 31
This is the correct choice. These two fields specifically define the window during which a product is available for ordering. With a Selling Start Date of January 5, the product becomes available on that date. With a Selling End Date of January 31, the product is no longer orderable after that date. This is the most direct and system-enforced way to implement the requirement, without manual intervention.

Option D: Set the Fulfillment Start Date to January 5 and the End of Life Date to January 31
This approach focuses on the product’s availability for fulfillment and its retirement from the catalog. It doesn’t control when a product can be sold. For instance, a product might still be orderable even after the End of Life Date if the Selling End Date is not properly set. Therefore, using only Fulfillment and End of Life dates does not meet the need to strictly control the orderability period.

To summarize, to configure a product bundle so that it can only be ordered between January 5 and January 31, the most appropriate and effective method is to use the Selling Start Date and Selling End Date fields. These fields are designed to define the sales window explicitly, and Salesforce CPQ or Industries systems will enforce them automatically. Thus, the correct answer is C.

Question 9

A developer sets up a new installation product that should be offered to customers at no cost. The product uses the Installation object type and has a code of MODEM5G-INST. The developer avoids setting a price to keep things simple and sets the Selling Start Date to one month in the future. During testing, the developer builds a cart, selects the default price list, and searches for the product, but it does not show up. 

What is the likely reason?

A. The product code contains a non-alphanumeric character (-)
B. The developer did not configure a price
C. The Selling Start Date price is in the future
D. The developer did not run Refresh Platform Cache

Answer: C

Explanation:
In Salesforce Industries (Vlocity) Digital Commerce, several factors affect whether a product is available in the product picker or shown in the cart. One of the most critical factors is the Selling Start Date of a product, which defines when a product becomes visible and available for ordering in the system.

In this scenario, the product was created with a Selling Start Date set one month in the future. This date acts as a filter in the catalog and prevents products from showing up in searches or being selectable in the cart before the configured start date. Therefore, regardless of whether a price is configured or not, the product will not appear until the current system date matches or exceeds the start date. This is the most likely cause for why the developer cannot see the product during testing.

Option A, suggesting that the issue is due to the hyphen in the product code (MODEM5G-INST), is not valid. The Salesforce Industries CPQ system supports special characters like hyphens in product codes and SKUs. These characters are commonly used to make product codes more readable and do not prevent visibility in the product catalog or cart.

Option B, which points to the absence of a price configuration, might seem reasonable, but it is not the root cause here. Products without a price can still be displayed in the cart, especially if they are meant to be free (like installation or setup services). It is even common practice to omit price configuration when the item is not intended to be charged.

Option D, referencing a failure to refresh the platform cache, can sometimes affect visibility when recent changes are made to product data. However, in this specific case, even refreshing the cache would not override the system logic that filters out products with a future Selling Start Date. The cache mechanism cannot bypass date-based visibility rules.

To conclude, the core issue lies in the Selling Start Date being set in the future, which instructs the system not to display the product in any customer-facing interface until that date is reached. Setting the start date to today or a past date would resolve the problem and make the product visible in the cart during testing.

Question 10

Which two line item actions will display in the Cart when performing a Move order from one account to another? (Choose two.)

A. Existing
B. Suspend
C. Change
D. Disconnect

Correct answers: A and D

Explanation:
When performing a Move order in Salesforce Industries (formerly Vlocity), the system is handling the transfer of services or products from one customer account to another. This is a specific order type and is distinct from standard orders like New, Change, Disconnect, etc.

In this context, a Move order involves identifying which services are being moved, then handling them in such a way that reflects the movement from the original account to the new one. The actions visible in the Cart during this process are key indicators of what is happening to each item involved in the move.

Option A: Existing
This is one of the key line item actions that appears in a Move order. It indicates that the product or service already exists on the source account and is being transferred as-is to the target account. It's not being modified or changed—it simply continues in its current configuration under a new ownership. This action allows users to recognize that the service will persist in the new account without disruption.

Option B: Suspend
Suspension of services is typically relevant in scenarios such as temporary disconnection or hold, not during a Move order. The Suspend action is not part of the standard behavior of Move orders. Therefore, this is not one of the line item actions shown during a Move order process.

Option C: Change
Change refers to modifications of existing services, such as altering a plan, upgrading features, or switching components. In a Move order, unless the service is being altered during the move (which would be a hybrid move/change order), this action does not typically appear. The purpose of a standard Move order is to transfer services as-is, without change. So "Change" is not one of the typical Move-specific line item actions.

Option D: Disconnect
This is another standard action that appears during a Move order. When a service is being moved from one account to another, it often involves disconnecting the product or service from the original account as part of the transfer process. This ensures proper closure of the original service instance before it is re-established or transferred to the new account. The Disconnect action shows that the original instance of the service is being terminated from the source account.

Therefore, during a Move order, the cart typically shows line item actions that reflect the continuation of services on the new account (Existing) and the removal from the source account (Disconnect). These two actions work together to complete the move without service change, unless other changes are explicitly specified.

The correct answers are A and D