Online Access Free Industries-CPQ-Developer Exam Questions

No.# ✅ Correct Answer: A. Set the Applicable Objects to Product2 Object
When you create a new attribute in Salesforce Industries CPQ (formerly Vlocity), you must define where it can be used by setting the "Applicable Objects" field.
If Felix does not set Product2 as an applicable object, the attribute won’t appear when trying to assign it to product object types, which is why it’s missing from the list.

Why the Other Options Are Incorrect:
B. Refresh the CPQPartition platform cache
🔸 This clears and refreshes cached data for CPQ, but does not affect attribute visibility in object type assignment.
C. Run the ProductAttributesBatchProcessor
🔸 This job is used for attribute processing and JSON updates but not needed just to assign an attribute to an object type.
D. Run the EPCProductAttribJSONBatchJob
🔸 Similar to (C), this job processes JSON representations of attributes, useful after assignments are made, not before.

No.# ✅ Correct Answer: A. How long the price of the child product is changed by the promotion
When you assign a Time Plan to a child product within a promotion, the Time Plan defines the duration for which that child product's pricing adjustment or override is valid.
So, for example:
If a promotion includes a discounted setup fee for 3 months only, the Time Plan ensures that the discount only applies during that period.
After the time plan ends, the pricing reverts to the standard pricing.

❌ Why the other options are incorrect:
B. When the entire promotion expires
→ The promotion’s time policy controls when the promotion starts and ends — not the time plan of an individual child product.
C. Which customers are eligible for the child product
→ That’s controlled by context rules, not the time plan.
D. When the time plan begins for the child product
→ The time plan includes both start and duration, but the primary effect is how long the promotional pricing is active — not just the start date.

No.# ✅ Correct Answer: A. Change to Quote, Change to Order and Move
These are valid operations in Salesforce Industries CPQ for managing assets:
Change to Quote – allows editing and repricing before committing to changes.
Change to Order – initiates a change directly to the active service.
Move – used for relocation scenarios (e.g., moving internet service to a new address).

❌ B. Change to Opportunity, Change to Order and Move
Incorrect because: Change to Opportunity is not a standard action available in asset management. Opportunities are typically used earlier in the sales cycle, not for managing existing assets.

❌ C. MACD, ABO and Copy to Order
Incorrect because:
MACD (Move/Add/Change/Delete) and ABO (Asset-Based Ordering) are strategies or frameworks, not user-facing operations.
Copy to Order is not a standard out-of-the-box operation for managing assets in CPQ.

❌ D. Move, Reprice and Check Contract
Incorrect because:
Move is valid.
Reprice is not a named user action; pricing changes are handled during the quote/order process.
Check Contract is not a standard CPQ operation....

No.# The correct answers are:
✅ A. Creating child price lists for different regions
Parent/child price lists are often used to reuse a base (parent) price list while allowing regional variations via child price lists.
This promotes consistency while supporting localization or market-specific pricing.
✅ C. Changing the pricing of child products in bundles
A child price list allows you to override specific product prices, such as pricing for child products in bundles, without duplicating the entire price list.

❌ B. Applying rules to child price lists
Incorrect: Rules like context or advanced rules are not applied to price lists directly. They’re applied to products or pricing behavior, independent of the price list hierarchy.
❌ D. Changing the pricing of the parent product in a bundle
Incorrect: If you're changing the pricing of the parent product, you can do it in the main (parent) price list or a specific entry; a child price list is not required just for the parent product.

No.# The correct answers are:
✅ C. Is Not Assetizable property
This is the official field in Industries CPQ (Vlocity EPC) used to mark a product as not assetizable.
When this flag is set, the product won’t be converted into an asset during order submission.
✅ D. Virtual Item property
When a product is marked as a Virtual Item, it typically means it is used for grouping, logical packaging, or pricing purposes only.
Virtual items are not assetizable by design.

❌ A. Create a context rule to control assetization
Incorrect: Context rules are used to qualify or disqualify products in product lists or promotions, not for controlling assetization directly.
❌ B. Check the Do Not Assetize property in the Cart's line item configuration window
Misleading: There's no standard "Do Not Assetize" flag in the Cart's UI configuration.
If assetization needs to vary per transaction, it must be handled via custom logic or rules outside the standard Cart UI.

No.# ✅ Correct Answers:
A. Reduce call handling time and training → By simplifying the process, agents don’t need deep technical knowledge to sell.
B. Better customer experience → A guided flow is easier and more intuitive for both agents and end-users.
D. Use functions not found with Vlocity Cart → Guided Selling can include branching logic, custom steps, validations, and pre-defined flows.
F. Include instructions for agents → Prompts, tooltips, and help content can be embedded directly in the experience.

❌ Incorrect Options:
C. To replace the regular Vlocity Cart for order capture
→ Guided Selling complements the Cart, but it does not fully replace it. The Cart is still used to finalize and review selections.
E. To train agents in selling processes before they use the regular Vlocity Cart
→ Guided Selling is a live selling tool, not a training system. It's meant for real-time transactions, not just simulations or onboarding.

No.# ✅ Correct Answer:
C. One-time charges are zeroed out on Change orders.
Explanation:
- One-time charges (OTC) that were part of the original purchase are not applied again, since the customer already paid them.
- In the Cart view, the price reflects recurring charges only, making it look different from the original price shown in Service Asset Management (which includes both one-time and recurring charges for reference).

❌ Why the other options are incorrect:
A. The asset was originally priced for a different user
→ Pricing is typically based on context like price list or account, not the individual user.
B. Asset has a status of Disconnect in Change orders
→ That would apply to a Disconnect order, not a Change order.
D. The product’s price has changed
→ Even if the current price has changed, Change orders reflect the asset's current configuration, and pricing changes (like recurring charges) would only apply based on pricing rules or new adjustments — not retroactively.

No.# ✅ Correct Answers:
A. How long is the subscription commitment for the promotion?
B. When does the subscription start and end?
Official documentation: https://trailhead.salesforce.com/content/learn/modules/industries-cpq-promotions/design-a-promotion

No.# ✅ Correct Answers:
A. Pricing Plans
D. Calculation Procedures & Matrices
See following official documentation https://help.salesforce.com/s/articleView?id=ind.comms_attribute_based_pricing_using_pricing_plans.htm&type=5

No.# ✅ A. Existing
When using Asset-Based Ordering (ABO) in Salesforce Industries CPQ, and a customer like Carole White already has an existing product (in this case, the Family Simple Choice Plan) and the agent adds a new product (like Smart Cloud Security) without making changes to the existing asset:
The existing product remains unchanged.
The system flags the line item for that existing product as Existing to indicate it's part of the customer's current assets and not being modified.
Only the new product (Smart Cloud Security) will have a line item action status of Add, while the Family Simple Choice Plan remains marked as Existing.

No.# ✅ Correct Answers:
B. The product's price should change based on the customer type.
D. The product needs to be sold quickly.
E. Special pricing should only be available for a limited time.

❌ Not Ideal Use Cases:
A. The product should have a cancellation penalty: ❌ Penalties are managed through contract terms or order orchestration, not promotions.
C. The product should only be available to B2C customers: ❌ Product visibility or eligibility should be handled via context or advanced rules, not promotions alone.

No.# ✅ Correct Answer: A. Context Rule – Qualification
Check diagram on the following official documentation https://help.salesforce.com/s/articleView?id=ind.comms_qualification_rules_for_products.htm&type=5

No.# ✅ Correct Answer: B. Before the step Initialize Pricing Context
When adding a custom pricing plan step for Attribute-Based Pricing in the Default Pricing Plan, Salesforce documentation specifies that:
“All attribute-based pricing steps must occur before the Initialize Pricing Context step.”
https://help.salesforce.com/s/articleView?id=ind.comms_set_up_a_custom_pricing_step_for_attribute_based_pricing.htm&type=5

No.# ✅ Correct Answers:
✅ A. Check the Virtual Item flag in Vlocity EPC
- A Virtual Item is a product used for logic or grouping (e.g., containers, config-only items) and should not be assetized.
- Setting this flag ensures the product won’t generate an asset post-order.
✅ B. Check the Not Assetizable flag in Vlocity EPC
- This flag explicitly marks the product as not assetizable, regardless of whether it’s virtual or real.
- When this is enabled, the product is excluded from asset creation in fulfillment processes.

❌ Why the Other Options Are Incorrect:
C. Create a context rule to control assetization: ❌ Context rules affect product eligibility or visibility, not assetization behavior.
D. Do Not Assetize flag in Vlocity Cart: ❌ There is no such flag in the cart UI. Assetization is controlled at the product model level (EPC).

No.# ✅ Correct Answer: D. Time policy
A Time Policy defines:
- Start event (e.g., purchase date)
- Duration (e.g., 12 months, 1 year)
- End behavior (e.g., end of commitment, pro-rated periods, etc.)
It is used to determine when charges begin and end for subscriptions and recurring pricing elements.

❌ Why the Other Options Are Incorrect:
A. Pricing element: Defines the amount and type of price (e.g., recurring, one-time), not the duration or timing.
B. Time plan: ❌ Specifies the duration pattern (e.g., monthly, annually) but doesn’t manage start/end logic tied to events.
C. Pricing variable: ❌ Used to feed attribute values into pricing logic, not to manage subscription timing.

No.# ✅ Correct Answers:
✅ A. Products
- You can conditionally include or exclude sections based on whether specific products are present in the cart or quote.
- Useful for tailoring content depending on selected services, bundles, or add-ons.
✅ B. Advanced Entity Filters
- These filters let you define complex conditions (e.g., account type, contract term, region).
- They evaluate objects and fields in the data model and determine if a section should be shown in the final document.

❌ Incorrect Options:
C. Merge Codes: ❌ Used to populate values (like customer name), not for conditional logic.
D. Browser Version: ❌ Irrelevant — document generation is server-side, not dependent on browser.

No.# ✅ Correct Answer: B. Before the step Initialize Pricing Context
According to the Salesforce help article Set Up a Custom Pricing Step for Attribute-Based Pricing (https://help.salesforce.com/s/articleView?id=ind.comms_set_up_a_custom_pricing_step_for_attribute_based_pricing.htm&type=5), when implementing Attribute-Based Pricing (ABP) using a custom pricing plan step, you must:
“Ensure that all attribute-based pricing steps occur before the Initialize Pricing Context step.”

No.# ✅ Correct Answers:
A. Disconnect
B. Existing
In Salesforce Industries (Vlocity) CPQ, when performing a Move order (i.e., transferring services or products from one account to another), the system must reflect the state of those products both on the source account and the target account.
Here’s how the line item actions behave in the cart during a Move order:
✅ A. Disconnect
- This action is shown for line items on the source account that are being removed as part of the move.
- It reflects the need to terminate or disconnect the service from the original account.
✅ B. Existing
- This action is used to reflect items that are being moved and already exist on the new account as a continuation.
- These line items are not being reconfigured or repriced, just transferred.

❌ Why Not the Others?
C. Change: ❌ Not applicable in a move scenario unless a product is being modified — not the primary action in a Move order.
D. Suspend: ❌ Suspension refers to temporarily disabling a service, not transferring it between accounts....

No.# ✅ Correct Answer: C. The product structure of the bundle
In Salesforce Industries CPQ, when you want to charge different prices for the same product depending on the bundle it is part of, the correct place to do that is in the Product Structure of each bundle.

❌ Why the other options are incorrect:
A. You can't change the price of child products within a bundle: ❌ False – you can override prices for child products via Product Structure
B. The price list where the price list entry is located: ❌ This defines base pricing only, not context-specific (bundle-specific) pricing
D. In the One Time or Recurring order line item columns in the cart: ❌ These reflect calculated prices; they are not where pricing is defined or overridden

No.# ✅ Correct Answer: A. Rule Condition
In Salesforce Industries (Vlocity) Context Rules, the Fail Level determines what happens when a rule condition is not met — whether it results in a hard fail (block the action) or a soft fail (allow it but show a message).

❌ Why the other options are incorrect:
B. Context Dimension: Just defines the context variable (like Account Type); does not control rule behavior
C. Context Mapping: Links context dimension to object/field; also doesn't handle rule logic or outcomes
D. Rule Set: Groups rules and defines overall action (Qualify, Disqualify), but not how individual conditions behave